Removed 3 constraints that are handled by the schema, and cleaned up …

…targets

features/fedramp_extensions.feature

@@ -59,12 +59,6 @@ Examples:
   | has-rules-of-behavior-PASS.yaml |
   | has-security-impact-level-FAIL.yaml |
   | has-security-impact-level-PASS.yaml |
-  | has-security-objective-availability-FAIL.yaml |
-  | has-security-objective-availability-PASS.yaml |
-  | has-security-objective-confidentiality-FAIL.yaml |
-  | has-security-objective-confidentiality-PASS.yaml |
-  | has-security-objective-integrity-FAIL.yaml |
-  | has-security-objective-integrity-PASS.yaml |
   | has-security-sensitivity-level-FAIL.yaml |
   | has-security-sensitivity-level-PASS.yaml |
   | has-separation-of-duties-matrix-FAIL.yaml |
@@ -134,9 +128,6 @@ Examples:
   | has-information-system-contingency-plan |
   | has-rules-of-behavior |
   | has-security-impact-level |
-  | has-security-objective-availability |
-  | has-security-objective-confidentiality |
-  | has-security-objective-integrity |
   | has-security-sensitivity-level |
   | has-separation-of-duties-matrix |
   | has-user-guide |

src/validations/constraints/content/ssp-all-INVALID.xml

@@ -86,9 +86,6 @@
       </information-type>
     </system-information>
     <!-- security-impact-level was removed to ensure that test fails correctly. -->
-    <!-- security-objective-confidentiality was removed to ensure that test fails correctly. -->
-    <!-- security-objective-integrity was removed to ensure that test fails correctly. -->
-    <!-- security-objective-availability was removed to ensure that test fails correctly. -->
     <status state="operational"/>
 
     <authorization-boundary>

src/validations/constraints/fedramp-external-constraints.xml

@@ -71,21 +71,12 @@
             <expect id="has-federation-assurance-level" target="./system-characteristics" test="prop[@name eq 'federation-assurance-level']" level="INFORMATIONAL">
             <message>This FedRAMP SSP does define its NIST SP 800-63 federation assurance level (IAL).</message>
             </expect>
-            <expect id="has-security-sensitivity-level" target="./system-characteristics" test="security-sensitivity-level" level="ERROR">
+            <expect id="has-security-sensitivity-level" target="system-characteristics" test="security-sensitivity-level" level="ERROR">
                 <message>An OSCAL SSP document must specify a FIPS 199 categorization.</message>
             </expect>
-            <expect id="has-security-impact-level" target="./system-characteristics" test="security-impact-level" level="ERROR">
+            <expect id="has-security-impact-level" target="system-characteristics" test="security-impact-level" level="ERROR">
                 <message>An OSCAL SSP document must specify a security impact level.</message>
             </expect>
-            <expect id="has-security-objective-confidentiality" target="./system-characteristics"  test="security-impact-level/security-objective-confidentiality" level="ERROR">
-                <message>An OSCAL SSP must specify a confidentiality security objective.</message>
-            </expect>
-            <expect id="has-security-objective-integrity" target="./system-characteristics"  test="security-impact-level/security-objective-integrity" level="ERROR">
-                <message>An OSCAL SSP must specify an integrity security objective.</message>
-            </expect>
-            <expect id="has-security-objective-availability" target="./system-characteristics"  test="security-impact-level/security-objective-availability" level="ERROR">
-                <message>An OSCAL SSP must specify an availability security objective.</message>
-            </expect>
         </constraints>
     </context>
     <context>