diff --git a/src/validations/constraints/fedramp-external-constraints.xml b/src/validations/constraints/fedramp-external-constraints.xml index a565fcd05..2417d4537 100644 --- a/src/validations/constraints/fedramp-external-constraints.xml +++ b/src/validations/constraints/fedramp-external-constraints.xml @@ -3,22 +3,8 @@ - - - - - - - Duplicate response point at '{ path(.) }'. - - -

This appears in FedRAMP profiles and resolved profile catalogs.

-

For control statements, it signals to the CSP which statements require a response in the SSP.

-

For control objectives, it signals to the assessor which control objectives must appear in the assessment results, which aligns with the FedRAMP test case workbook.

-
-
-
- + + @@ -31,43 +17,49 @@ - - - - - Each data center address must contain a country code. - - - Each data center must have an address that is within the United States. - - - + - - + - A FedRAMP document MUST define a user with a type. + A FedRAMP document MUST define a user with at least one authorized privilege by a privilege identifier. A FedRAMP document MUST define a user with a privilege for their use of the system. + + + A FedRAMP document MUST define a user with at least one role by a role identifier. + A FedRAMP document MUST define a user with a sensitivity level of their use of the system. - + - A FedRAMP document MUST define a user with at least one role by a role identifier. + A FedRAMP document MUST define a user with a type. - - - A FedRAMP document MUST define a user with at least one authorized privilege by a privilege identifier. + + + + + + + + + + Duplicate response point at '{ path(.) }'. + +

This appears in FedRAMP profiles and resolved profile catalogs.

+

For control statements, it signals to the CSP which statements require a response in the SSP.

+

For control objectives, it signals to the assessor which control objectives must appear in the assessment results, which aligns with the FedRAMP test case workbook.

+
+ @@ -79,126 +71,160 @@ else if (//security-impact-level//* = 'fips-199-moderate') then ('fips-199-moderate') else ('fips-199-low')"/> - - Every supporting artifact found in a citation should have a title. - - - Every supporting artifact found in a citation must have at least one base64 or rlink element. - - - A FedRAMP SSP must have a User Guide attached. - - - A FedRAMP SSP must have Rules of Behavior. - - - A FedRAMP SSP must have a Contingency Plan attached. - - - A FedRAMP SSP must have a Configuration Management Plan attached. - - - A FedRAMP SSP must have an Incident Response Plan attached. - - - A FedRAMP SSP must have a Separation of Duties Matrix attached. - + A FedRAMP SSP information-type categorization requires a correct system attribute. FedRAMP only supports the system value 'https://doi.org/10.6028/NIST.SP.800-60v2r1'. - A FedRAMP SSP information type categorization must have at least one information type identifier. + + A FedRAMP SSP information type categorization MUST have at least one information type identifier. - - A FedRAMP SSP must define its NIST SP 800-63 identity assurance level (IAL). + + + When SP 800-60 base and selected impacts levels differ for a given information type, the SSP MUST include a justification for the difference. - - A FedRAMP SSP must define its NIST SP 800-63 authenticator assurance level (AAL). + + + A FedRAMP SSP information type confidentiality, integrity, or availability impact MUST specify the selected impact. - - A FedRAMP SSP must define its NIST SP 800-63 federation assurance level (FAL). + + + A FedRAMP SSP MUST define its NIST SP 800-63 authenticator assurance level (AAL). - A FedRAMP SSP must have at least one authorization boundary diagram. + + A FedRAMP SSP MUST have at least one authorization boundary diagram. + + + + Each FedRAMP SSP authorization boundary diagram MUST have a caption. - A FedRAMP SSP document authorization boundary diagram must have a description. + + A FedRAMP SSP document authorization boundary diagram MUST have a description. - Each FedRAMP SSP authorization boundary diagram must have a link. + + Each FedRAMP SSP authorization boundary diagram MUST have a link. - Each FedRAMP SSP authorization boundary diagram must have a link rel attribute. + + Each FedRAMP SSP authorization boundary diagram MUST have a link rel attribute. - Each FedRAMP SSP authorization boundary diagram must have a link rel attribute with the value "diagram". + + Each FedRAMP SSP authorization boundary diagram MUST have a link rel attribute with the value "diagram". - - Each FedRAMP SSP authorization boundary diagram must have a caption. + + + A FedRAMP SSP MUST have a Configuration Management Plan attached. - - A FedRAMP SSP must include a network architecture. + + + A FedRAMP SSP MUST include a data flow section. - - A FedRAMP SSP must have at least one network architecture diagram. + + + An OSCAL SSP document with a data flow MUST have a description. - - Each FedRAMP SSP network architecture diagram must have a description. + + + A FedRAMP SSP MUST have at least one data flow diagram. - - Each FedRAMP SSP network architecture diagram must have a link. + + + Each FedRAMP SSP data flow diagram MUST have a caption. - - Each FedRAMP SSP network architecture diagram must have a caption. + + + Each FedRAMP SSP data flow diagram MUST have a description. - - Each FedRAMP SSP network architecture diagram must have a link rel attribute. + + + Each FedRAMP SSP data flow diagram MUST have a link. - - Each FedRAMP SSP network architecture diagram must have a link rel attribute with the value "diagram". + + + Each FedRAMP SSP data flow diagram MUST have a link rel attribute. - - A FedRAMP SSP must include a data flow section. + + + Each FedRAMP SSP data flow diagram MUST have a link rel attribute with the value "diagram". - - A FedRAMP SSP must have at least one data flow diagram. + + + An OSCAL SSP document with a data flow diagram MUST have a unique identifier. - - An OSCAL SSP document with a data flow must have a description. + + + A FedRAMP SSP MUST define its NIST SP 800-63 federation assurance level (FAL). - - An OSCAL SSP document with a data flow diagram must have a unique identifier. + + + A FedRAMP SSP MUST define its NIST SP 800-63 identity assurance level (IAL). - - Each FedRAMP SSP data flow diagram must have a description. + + + A FedRAMP SSP MUST have an Incident Response Plan attached. - - Each FedRAMP SSP data flow diagram must have a link. + + + A FedRAMP SSP MUST have a Contingency Plan attached. - - Each FedRAMP SSP data flow diagram must have a caption. + + + A FedRAMP SSP MUST include a network architecture. - - Each FedRAMP SSP data flow diagram must have a link rel attribute. + + + A FedRAMP SSP MUST have at least one network architecture diagram. - - Each FedRAMP SSP data flow diagram must have a link rel attribute with the value "diagram". + + + Each FedRAMP SSP network architecture diagram MUST have a caption. - - - A FedRAMP SSP document MUST specify a FIPS 199 categorization. + + + Each FedRAMP SSP network architecture diagram MUST have a description. + + + + Each FedRAMP SSP network architecture diagram MUST have a link. + + + + Each FedRAMP SSP network architecture diagram MUST have a link rel attribute. + + + + Each FedRAMP SSP network architecture diagram MUST have a link rel attribute with the value "diagram". + + + + A FedRAMP SSP MUST have Rules of Behavior. - A FedRAMP SSP document MUST specify a security impact level. + + + + A FedRAMP SSP document MUST specify a FIPS 199 categorization. + + + + A FedRAMP SSP MUST have a Separation of Duties Matrix attached. - A FedRAMP SSP must have a FedRAMP system identifier. + A FedRAMP SSP MUST have a FedRAMP system identifier. - - - A FedRAMP SSP SHOULD define its FIPS-199 security sensitivity level to match the highest security impact level for the system's confidentiality, integrity, and availability objectives. + + + A FedRAMP SSP MUST have a short system name. + + + + A FedRAMP SSP MUST have a User Guide attached. @@ -211,6 +237,10 @@

A FedRAMP SSP MUST use a valid FedRAMP catalog to reference security controls. It MUST NOT reference controls from a non-FedRAMP catalog.

+ + + A FedRAMP SSP information type MUST have an availability impact. + A FedRAMP SSP information type MUST have a confidentiality impact. @@ -219,38 +249,45 @@ A FedRAMP SSP information type MUST have an integrity impact. - - - A FedRAMP SSP information type MUST have an availability impact. + + + Every supporting artifact found in a citation MUST have at least one base64 or rlink element. - - - A FedRAMP SSP information type confidentiality, integrity, or availability impact MUST specify the selected impact. + + + Every supporting artifact found in a citation SHOULD have a title. - - - When SP 800-60 base and selected impacts levels differ for a given information type, the SSP MUST include a justification for the difference. + + + A FedRAMP SSP SHOULD define its FIPS-199 security sensitivity level to match the highest security impact level for the system's confidentiality, integrity, and availability objectives. - - - A FedRAMP SSP MUST have a short system name. +
+
+ + + + + + + Each implemented requirement MUST have at least one by-component reference to the source component implementing it. + + + + There MUST be one or more alternate data center(s). + - - There must be at least two (2) data centers listed. + + There MUST be at least two (2) data centers listed. - - There must be a single primary data center. - - - - There must be one or more alternate data center(s). + + There MUST be a single primary data center. Index of parties of type "person". @@ -260,25 +297,34 @@ - For roles 'system-owner' and 'information-system-security-officer', the responsible-role party must be a party of type 'person'. + For roles 'system-owner' and 'information-system-security-officer', the responsible-role party MUST be a party of type 'person'. - - A FedRAMP SSP must define the system owner role. - - A FedRAMP SSP must define a role for the point of contact for an authorizing official. + A FedRAMP SSP MUST define a role for the point of contact for an authorizing official. - A FedRAMP SSP must define a role for the point of contact for an information system security officer. + + A FedRAMP SSP MUST define a role for the point of contact for an information system security officer. + + + + A FedRAMP SSP MUST define the system owner role. + - + - - Each implemented requirement must have at least one by-component reference to the source component implementing it. + + + Each data center address MUST contain a country code. + + + + Each data center MUST have an address that is within the United States. + \ No newline at end of file