From a7f902230255fd5e57ac35fa00cc8147d5461b6a Mon Sep 17 00:00:00 2001 From: Gabeblis Date: Thu, 5 Dec 2024 13:23:21 -0500 Subject: [PATCH] Add exists() to tests and remove duplicate constraint and fix system-implementation context (#966) Remove duplicate constraint and fix system-implementation context --- .../fedramp-external-constraints.xml | 133 ++++++++---------- .../unique-inventory-item-asset-id-FAIL.yaml | 2 +- 2 files changed, 61 insertions(+), 74 deletions(-) diff --git a/src/validations/constraints/fedramp-external-constraints.xml b/src/validations/constraints/fedramp-external-constraints.xml index 3dfd51728..b5a552a93 100644 --- a/src/validations/constraints/fedramp-external-constraints.xml +++ b/src/validations/constraints/fedramp-external-constraints.xml @@ -119,33 +119,33 @@ - + Has Configuration Management Plan A FedRAMP SSP MUST have a Configuration Management Plan attached. - + Has Incident Response Plan A FedRAMP SSP MUST have an Incident Response Plan attached. - + Has Information System Contingency Plan A FedRAMP SSP MUST have a Contingency Plan attached. - + Has Rules Of Behavior A FedRAMP SSP MUST have Rules of Behavior. - + Has Separation Of Duties Matrix A FedRAMP SSP MUST have a Separation of Duties Matrix attached. - + Has User Guide A FedRAMP SSP MUST have a User Guide attached. @@ -155,7 +155,7 @@ Every supporting artifact found in a citation MUST have at least one base64 or rlink element. - + Resource Has Title Every supporting artifact found in a citation SHOULD have a title. @@ -241,13 +241,13 @@ A FedRAMP SSP MUST define the address of the responsible party for whom the document was prepared. - + Role Defined Authorizing Official POC A FedRAMP SSP MUST define a role for the point of contact for an authorizing official. - + Role Defined Information System Security Officer A FedRAMP SSP MUST define a role for the point of contact for an information system security officer. @@ -262,7 +262,7 @@ A FedRAMP SSP MUST define a role for which the document was prepared. - + Role Defined System Owner A FedRAMP SSP MUST define the system owner role. @@ -285,7 +285,7 @@ A FedRAMP SSP information-type categorization MUST have a correct system attribute. FedRAMP only supports the system value 'https://doi.org/10.6028/NIST.SP.800-60v2r1'. - + Categorization Has Information Type ID A FedRAMP SSP information type categorization MUST have at least one information type identifier. @@ -315,27 +315,27 @@ A FedRAMP SSP MUST define its NIST SP 800-63 authenticator assurance level (AAL). - + Has Authorization Boundary Diagram A FedRAMP SSP MUST have at least one authorization boundary diagram. - + Has Authorization Boundary Diagram Caption Each FedRAMP SSP authorization boundary diagram MUST have a caption. - + Has Authorization Boundary Diagram Description A FedRAMP SSP document authorization boundary diagram MUST have a description. - + Has Authorization Boundary Diagram Link Each FedRAMP SSP authorization boundary diagram MUST have a link. - + Has Authorization Boundary Diagram Link Rel Each FedRAMP SSP authorization boundary diagram MUST have a link rel attribute. @@ -345,7 +345,7 @@ Each FedRAMP SSP authorization boundary diagram MUST have a link rel attribute with the value "diagram". - + Has Cloud Deployment Model A FedRAMP SSP MUST define a cloud deployment model. @@ -358,7 +358,7 @@

A FedRAMP SSP MUST use precise classifications for cloud deployment models. It MUST NOT use generic classifications like "hybrid-cloud".

- + Has Cloud Service Model A FedRAMP SSP MUST define a cloud service model. @@ -368,37 +368,37 @@ A FedRAMP SSP with a cloud service model of "other" MUST supply remarks to explain this choice. - + Has Data Flow A FedRAMP SSP MUST include a data flow section. - + Has Data Flow Description An OSCAL SSP document with a data flow MUST have a description. - + Has Data Flow Diagram A FedRAMP SSP MUST have at least one data flow diagram. - + Has Data Flow Diagram Caption Each FedRAMP SSP data flow diagram MUST have a caption. - + Has Data Flow Diagram Description Each FedRAMP SSP data flow diagram MUST have a description. - + Has Data Flow Diagram Link Each FedRAMP SSP data flow diagram MUST have a link. - + Has Data Flow Diagram Link Rel Each FedRAMP SSP data flow diagram MUST have a link rel attribute. @@ -408,7 +408,7 @@ Each FedRAMP SSP data flow diagram MUST have a link rel attribute with the value "diagram". - + Has Data Flow Diagram Uuid An OSCAL SSP document with a data flow diagram MUST have a unique identifier. @@ -428,32 +428,32 @@ A FedRAMP SSP MUST define its NIST SP 800-63 identity assurance level (IAL). - + Has Network Architecture A FedRAMP SSP MUST include a network architecture. - + Has Network Architecture Diagram A FedRAMP SSP MUST have at least one network architecture diagram. - + Has Network Architecture Diagram Caption Each FedRAMP SSP network architecture diagram MUST have a caption. - + Has Network Architecture Diagram Description Each FedRAMP SSP network architecture diagram MUST have a description. - + Has Network Architecture Diagram Link Each FedRAMP SSP network architecture diagram MUST have a link. - + Has Network Architecture Diagram Link Rel Each FedRAMP SSP network architecture diagram MUST have a link rel attribute. @@ -463,37 +463,37 @@ Each FedRAMP SSP network architecture diagram MUST have a link rel attribute with the value "diagram". - + Has Security Impact Level A FedRAMP SSP document MUST specify a security impact level. - + Has Security Sensitivity Level A FedRAMP SSP document MUST specify a FIPS 199 categorization. - + Has System Id A FedRAMP SSP MUST have a FedRAMP system identifier. - + Has System Name Short A FedRAMP SSP MUST have a short system name. - + Information Type Has Availability Impact A FedRAMP SSP information type MUST have an availability impact. - + Information Type Has Confidentiality Impact A FedRAMP SSP information type MUST have a confidentiality impact. - + Information Type Has Integrity Impact A FedRAMP SSP information type MUST have an integrity impact. @@ -512,18 +512,18 @@
- - + + Authentication Method Has Remarks Each authentication method in a FedRAMP SSP MUST have a remarks field. - - System Implementation Has Inventory Items - - A FedRAMP SSP system implementation section MUST have at least two inventory items. - + + System Implementation Has Inventory Items + + A FedRAMP SSP system implementation section MUST have at least two inventory items. + Leveraged Authorization Has Authorization Type @@ -538,11 +538,16 @@ Leveraged Authorization Has System Identifier A FedRAMP SSP MUST define exactly one system identifier for each leveraged authorization entry. - + - Network Component Has Connection Security Property - - All network components in a FedRAMP SSP system implementation MUST define at least one interconnection security property. + Network Component Has Connection Security Property + + All network components in a FedRAMP SSP system implementation MUST define at least one interconnection security property. + + + Component Has Implementation Point + + A FedRAMP SSP with service components and CLI software components performing cross-boundary network communication MUST indicate exactly one time if the point of implementation is internal or external to the system. Unique Asset Identifier @@ -553,13 +558,13 @@

A FedRAMP SSP's inventory item MUST have an Asset ID that is unique across all inventory items in the system and its components.

-
-
+ + - + Fedramp Version A FedRAMP document's metadata MUST define a valid FedRAMP version. @@ -573,7 +578,7 @@ All documents submitted to FedRAMP MUST define a valid publication date. - + FedRAMP data sensitivity classification identifier. A FedRAMP document MUST have a marking that defines its data classification. @@ -591,23 +596,5 @@ - - - - - Unique Asset Identifier - Ensure each inventory item has a unique asset-id property. - - - -

A FedRAMP SSP's inventory item MUST have an Asset ID that is unique across all inventory items in the system and its components.

-
-
- - Component Has Implementation Point - - A FedRAMP SSP with service components and CLI software components performing cross-boundary network communication MUST indicate exactly one time if the point of implementation is internal or external to the system. - -
-
+ diff --git a/src/validations/constraints/unit-tests/unique-inventory-item-asset-id-FAIL.yaml b/src/validations/constraints/unit-tests/unique-inventory-item-asset-id-FAIL.yaml index 327c9789a..806d1ad70 100644 --- a/src/validations/constraints/unit-tests/unique-inventory-item-asset-id-FAIL.yaml +++ b/src/validations/constraints/unit-tests/unique-inventory-item-asset-id-FAIL.yaml @@ -8,4 +8,4 @@ test-case: - constraint-id: unique-inventory-item-asset-id fail_count: type: "exact" - value: 2 \ No newline at end of file + value: 1 \ No newline at end of file