From ea95ffa7fd90f706c6f73a78d08bff1006e08b68 Mon Sep 17 00:00:00 2001
From: "~ . ~" <paul.n.wand@gsa.gov>
Date: Wed, 4 Dec 2024 12:49:03 -0500
Subject: [PATCH] deprecate ssp-all-valid

---
 features/fedramp_extensions.feature           |   3 -
 src/validations/constraints/CONTRIBUTING.md   |   4 +-
 ...p-control-implementation-status-VALID.xml} |   0
 ...ndary-diagram-link-href-target-VALID-1.xml |   2 +-
 ...-flow-diagram-link-href-target-VALID-1.xml |   2 +-
 ...cture-diagram-link-href-target-VALID-1.xml |   7 +-
 .../ssp-interconnection-direction-VALID.xml   | 625 ++++++++++++++++++
 .../ssp-interconnection-security-VALID.xml    | 625 ++++++++++++++++++
 .../unit-tests/address-type-PASS.yaml         |   2 +-
 .../unit-tests/attachment-type-PASS.yaml      |   2 +-
 ...uthentication-method-has-remarks-PASS.yaml |   2 +-
 .../unit-tests/authorization-type-PASS.yaml   |   2 +-
 ...ion-has-correct-system-attribute-PASS.yaml |   2 +-
 ...rization-has-information-type-id-PASS.yaml |   2 +-
 ...act-has-adjustment-justification-PASS.yaml |   2 +-
 .../cia-impact-has-selected-PASS.yaml         |   2 +-
 .../unit-tests/cloud-service-model-PASS.yaml  |   2 +-
 ...ponent-has-authentication-method-PASS.yaml |   2 +-
 ...as-non-provider-responsible-role-PASS.yaml |   2 +-
 ...esponsible-role-references-party-PASS.yaml |   2 +-
 .../unit-tests/component-type-PASS.yaml       |   2 +-
 .../control-implementation-status-PASS.yaml   |   2 +-
 .../data-center-alternate-PASS.yaml           |   2 +-
 .../unit-tests/data-center-count-PASS.yaml    |   2 +-
 .../data-center-country-code-PASS.yaml        |   2 +-
 .../unit-tests/data-center-primary-PASS.yaml  |   2 +-
 .../unit-tests/data-center-us-PASS.yaml       |   2 +-
 .../unit-tests/deployment-model-PASS.yaml     |   2 +-
 ...ernal-system-nature-of-agreement-PASS.yaml |   2 +-
 .../unit-tests/fedramp-version-PASS.yaml      |   2 +-
 .../fully-operational-date-is-valid-PASS.yaml |   2 +-
 .../fully-operational-date-type-PASS.yaml     |   2 +-
 ...as-authenticator-assurance-level-PASS.yaml |   2 +-
 ...s-authorization-boundary-diagram-PASS.yaml |   2 +-
 ...ization-boundary-diagram-caption-PASS.yaml |   2 +-
 ...ion-boundary-diagram-description-PASS.yaml |   2 +-
 ...horization-boundary-diagram-link-PASS.yaml |   2 +-
 ...oundary-diagram-link-href-target-PASS.yaml |   2 +-
 ...zation-boundary-diagram-link-rel-PASS.yaml |   2 +-
 ...y-diagram-link-rel-allowed-value-PASS.yaml |   2 +-
 .../has-cloud-deployment-model-PASS.yaml      |   2 +-
 ...s-cloud-deployment-model-remarks-PASS.yaml |   2 +-
 .../has-cloud-service-model-PASS.yaml         |   2 +-
 .../has-cloud-service-model-remarks-PASS.yaml |   2 +-
 ...as-configuration-management-plan-PASS.yaml |   2 +-
 .../unit-tests/has-data-flow-PASS.yaml        |   2 +-
 .../has-data-flow-description-PASS.yaml       |   2 +-
 .../has-data-flow-diagram-PASS.yaml           |   2 +-
 .../has-data-flow-diagram-caption-PASS.yaml   |   2 +-
 ...as-data-flow-diagram-description-PASS.yaml |   2 +-
 .../has-data-flow-diagram-link-PASS.yaml      |   2 +-
 ...ta-flow-diagram-link-href-target-PASS.yaml |   1 -
 .../has-data-flow-diagram-link-rel-PASS.yaml  |   2 +-
 ...w-diagram-link-rel-allowed-value-PASS.yaml |   2 +-
 .../has-data-flow-diagram-uuid-PASS.yaml      |   2 +-
 .../has-federation-assurance-level-PASS.yaml  |   2 +-
 .../has-fully-operational-date-PASS.yaml      |   2 +-
 .../has-identity-assurance-level-PASS.yaml    |   2 +-
 .../has-incident-response-plan-PASS.yaml      |   2 +-
 ...ormation-system-contingency-plan-PASS.yaml |   2 +-
 .../unit-tests/has-inventory-items-PASS.yaml  |   2 +-
 .../has-network-architecture-PASS.yaml        |   2 +-
 ...has-network-architecture-diagram-PASS.yaml |   2 +-
 ...ork-architecture-diagram-caption-PASS.yaml |   2 +-
 ...architecture-diagram-description-PASS.yaml |   2 +-
 ...etwork-architecture-diagram-link-PASS.yaml |   2 +-
 ...tecture-diagram-link-href-target-PASS.yaml |   2 +-
 ...rk-architecture-diagram-link-rel-PASS.yaml |   2 +-
 ...e-diagram-link-rel-allowed-value-PASS.yaml |   2 +-
 .../unit-tests/has-published-date-PASS.yaml   |   2 +-
 .../has-rules-of-behavior-PASS.yaml           |   2 +-
 .../has-security-impact-level-PASS.yaml       |   2 +-
 .../has-security-sensitivity-level-PASS.yaml  |   2 +-
 .../has-separation-of-duties-matrix-PASS.yaml |   2 +-
 .../unit-tests/has-system-id-PASS.yaml        |   2 +-
 .../has-system-name-short-PASS.yaml           |   2 +-
 .../unit-tests/has-user-guide-PASS.yaml       |   2 +-
 ...t-profile-has-available-document-PASS.yaml |   2 +-
 ...file-resolves-to-fedramp-content-PASS.yaml |   2 +-
 ...ion-type-has-availability-impact-PASS.yaml |   2 +-
 ...-type-has-confidentiality-impact-PASS.yaml |   2 +-
 ...mation-type-has-integrity-impact-PASS.yaml |   2 +-
 .../unit-tests/information-type-id-PASS.yaml  |   2 +-
 .../information-type-system-PASS.yaml         |   2 +-
 .../interconnection-direction-PASS.yaml       |   2 +-
 .../interconnection-security-PASS.yaml        |   2 +-
 ...y-item-allows-authenticated-scan-PASS.yaml |   2 +-
 .../inventory-item-public-PASS.yaml           |   2 +-
 .../inventory-item-virtual-PASS.yaml          |   2 +-
 ...orization-has-authorization-type-PASS.yaml |   2 +-
 ...d-authorization-has-impact-level-PASS.yaml |   2 +-
 ...horization-has-system-identifier-PASS.yaml |   2 +-
 ...orization-has-valid-impact-level-PASS.yaml |   2 +-
 ...uthorization-nature-of-agreement-PASS.yaml |   2 +-
 .../constraints/unit-tests/marking-PASS.yaml  |   2 +-
 ...ent-has-connection-security-prop-PASS.yaml |   2 +-
 ...mponent-has-implementation-point-PASS.yaml |   2 +-
 ...responsible-role-references-user-PASS.yaml |   2 +-
 .../unit-tests/party-has-name-PASS.yaml       |   2 +-
 .../unit-tests/privilege-level-PASS.yaml      |   2 +-
 .../resource-has-base64-or-rlink-PASS.yaml    |   2 +-
 .../unit-tests/resource-has-title-PASS.yaml   |   2 +-
 .../responsible-party-is-person-PASS.yaml     |   2 +-
 .../responsible-party-prepared-by-PASS.yaml   |   2 +-
 ...party-prepared-by-location-valid-PASS.yaml |   2 +-
 .../responsible-party-prepared-for-PASS.yaml  |   2 +-
 ...arty-prepared-for-location-valid-PASS.yaml |   2 +-
 ...defined-authorizing-official-poc-PASS.yaml |   2 +-
 ...ormation-system-security-officer-PASS.yaml |   2 +-
 .../role-defined-prepared-by-PASS.yaml        |   2 +-
 .../role-defined-prepared-for-PASS.yaml       |   2 +-
 .../role-defined-system-owner-PASS.yaml       |   2 +-
 ...saas-has-leveraged-authorization-PASS.yaml |   2 +-
 .../unit-tests/scan-type-PASS.yaml            |   2 +-
 .../unit-tests/security-level-PASS.yaml       |   2 +-
 ...el-matches-security-impact-level-PASS.yaml |   2 +-
 .../unique-inventory-item-asset-id-PASS.yaml  |   2 +-
 .../unit-tests/user-authentication-PASS.yaml  |   2 +-
 .../user-has-authorized-privilege-PASS.yaml   |   2 +-
 .../unit-tests/user-has-role-id-PASS.yaml     |   2 +-
 .../unit-tests/user-has-user-type-PASS.yaml   |   2 +-
 .../unit-tests/user-privilege-level-PASS.yaml |   2 +-
 .../user-sensitivity-level-PASS.yaml          |   2 +-
 .../unit-tests/user-type-PASS.yaml            |   2 +-
 124 files changed, 1371 insertions(+), 128 deletions(-)
 rename src/validations/constraints/content/{ssp-all-VALID.xml => ssp-control-implementation-status-VALID.xml} (100%)
 create mode 100644 src/validations/constraints/content/ssp-interconnection-direction-VALID.xml
 create mode 100644 src/validations/constraints/content/ssp-interconnection-security-VALID.xml

diff --git a/features/fedramp_extensions.feature b/features/fedramp_extensions.feature
index 42b267a3d0..e9c9696bcf 100644
--- a/features/fedramp_extensions.feature
+++ b/features/fedramp_extensions.feature
@@ -11,9 +11,6 @@ Scenario Outline: Documents that should be valid are pass
 Examples:
 | valid_file     |
 | ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml |
-# | ssp-all-VALID.xml |
-# | ../../../content/awesome-cloud/xml/AwesomeCloudSSP1.xml |
-# | ../../../content/awesome-cloud/xml/AwesomeCloudSSP2.xml |
 
 @full-coverage
 Scenario: Preparing constraint coverage analysis
diff --git a/src/validations/constraints/CONTRIBUTING.md b/src/validations/constraints/CONTRIBUTING.md
index 2edc2a4fcf..47d9934d80 100644
--- a/src/validations/constraints/CONTRIBUTING.md
+++ b/src/validations/constraints/CONTRIBUTING.md
@@ -107,7 +107,7 @@ npm run constraint
 You can add a constraint and test to this repository by following these high-level steps.
 
 1. Create a new constraint in [the appropriate constraints file](#which-constraint-file-do-i-edit). Note the `id`, you will use it later.
-2. Add the necessary, correct data to [`./content/ssp-all-VALID.xml`](./content/ssp-all-VALID.xml) for a positive test of the constraint.
+2. Add the necessary, correct data to [`../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml`](../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml) for a positive test of the constraint.
 3. Add the YAML metadata for the positive test in [`./unit-tests`](./unit-tests/). The name of the file should start with the name of the assembly, field, or flag, and end with `-PASS.yaml`. For example, a new constraint and test for a [`//metadata/party/prop`](https://pages.nist.gov/OSCAL-Reference/models/v1.1.2/system-security-plan/json-reference/#/system-security-plan/metadata/parties) assembly should be `party-PASS.yaml`. The content should be like the example below.
 
 ```yaml
@@ -115,7 +115,7 @@ You can add a constraint and test to this repository by following these high-lev
 test-case:
   name: Positive Test for party
   description: This test case validates the behavior of constraint party
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: party
       result: pass
diff --git a/src/validations/constraints/content/ssp-all-VALID.xml b/src/validations/constraints/content/ssp-control-implementation-status-VALID.xml
similarity index 100%
rename from src/validations/constraints/content/ssp-all-VALID.xml
rename to src/validations/constraints/content/ssp-control-implementation-status-VALID.xml
diff --git a/src/validations/constraints/content/ssp-has-authorization-boundary-diagram-link-href-target-VALID-1.xml b/src/validations/constraints/content/ssp-has-authorization-boundary-diagram-link-href-target-VALID-1.xml
index ebeecfc3e3..13ce45a02d 100644
--- a/src/validations/constraints/content/ssp-has-authorization-boundary-diagram-link-href-target-VALID-1.xml
+++ b/src/validations/constraints/content/ssp-has-authorization-boundary-diagram-link-href-target-VALID-1.xml
@@ -169,7 +169,7 @@
             <description>
                <p>A diagram-specific explanation.</p>
             </description>
-            <link href="./ssp-all-VALID.xml" rel="diagram"/>
+            <link href="https://www.fedramp.gov/assets/resources/documents/Agency-Authorization-Auth-Boundary-Diagram-Job-Aid.pdf" rel="diagram"/>
             <caption>Authorization Boundary Diagram</caption>
          </diagram>
     </authorization-boundary>
diff --git a/src/validations/constraints/content/ssp-has-data-flow-diagram-link-href-target-VALID-1.xml b/src/validations/constraints/content/ssp-has-data-flow-diagram-link-href-target-VALID-1.xml
index fc8e9a1177..bd5564b7c6 100644
--- a/src/validations/constraints/content/ssp-has-data-flow-diagram-link-href-target-VALID-1.xml
+++ b/src/validations/constraints/content/ssp-has-data-flow-diagram-link-href-target-VALID-1.xml
@@ -193,7 +193,7 @@
         <description>
           <p>A diagram-specific explanation.</p>
         </description>
-        <link href="./ssp-all-VALID.xml" rel="diagram"/>
+        <link href="https://www.fedramp.gov/assets/resources/documents/Agency-Authorization-Auth-Boundary-Diagram-Job-Aid.pdf" rel="diagram" />
         <caption>Data Flow Diagram</caption>
       </diagram>
     </data-flow>
diff --git a/src/validations/constraints/content/ssp-has-network-architecture-diagram-link-href-target-VALID-1.xml b/src/validations/constraints/content/ssp-has-network-architecture-diagram-link-href-target-VALID-1.xml
index a7d82a3c9a..28a50101a3 100644
--- a/src/validations/constraints/content/ssp-has-network-architecture-diagram-link-href-target-VALID-1.xml
+++ b/src/validations/constraints/content/ssp-has-network-architecture-diagram-link-href-target-VALID-1.xml
@@ -85,9 +85,6 @@
     <responsible-party role-id="system-owner">
       <party-uuid>22222222-0000-4000-9000-000000000002</party-uuid>
     </responsible-party>
-    <responsible-party role-id="authorizing-official">
-      <party-uuid>22222222-0000-4000-9000-000000000002</party-uuid>
-    </responsible-party>
     <responsible-party role-id="authorizing-official-poc">
       <party-uuid>22222222-0000-4000-9000-000000000002</party-uuid>
     </responsible-party>
@@ -181,7 +178,7 @@
         <description>
           <p>A diagram-specific explanation.</p>
         </description>
-        <link href="./ssp-all-VALID.xml" rel="diagram"/>
+        <link href="https://www.fedramp.gov/assets/resources/documents/Agency-Authorization-Auth-Boundary-Diagram-Job-Aid.pdf" rel="diagram"/>
         <caption>Network Diagram</caption>
       </diagram>
     </network-architecture>
@@ -234,7 +231,7 @@
       <description>
         <p>Secure connection to an external API for data enrichment.</p>
       </description>
-      <prop name="interconnection-security" value="vpn" ns="https://fedramp.gov/ns/oscal"/>
+      <prop name="connection-security" value="vpn" ns="https://fedramp.gov/ns/oscal"/>
       <prop name="interconnection-direction" value="in/out" ns="https://fedramp.gov/ns/oscal"/>
       <status state="operational"/>
       <responsible-role role-id="system-admin">
diff --git a/src/validations/constraints/content/ssp-interconnection-direction-VALID.xml b/src/validations/constraints/content/ssp-interconnection-direction-VALID.xml
new file mode 100644
index 0000000000..715a29c660
--- /dev/null
+++ b/src/validations/constraints/content/ssp-interconnection-direction-VALID.xml
@@ -0,0 +1,625 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<system-security-plan xmlns="http://csrc.nist.gov/ns/oscal/1.0"
+                      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+                      xsi:schemaLocation="http://csrc.nist.gov/ns/oscal/1.0 https://github.com/usnistgov/OSCAL/releases/download/v1.1.2/oscal_ssp_schema.xsd"
+                      uuid="12345678-1234-4321-8765-123456789012">
+  <metadata>
+    <title>Enhanced Example System Security Plan</title>
+    <published>2024-08-01T14:30:00Z</published>
+    <last-modified>2024-08-01T14:30:00Z</last-modified>
+    <version>1.1</version>
+    <oscal-version>1.1.2</oscal-version>
+    <document-id scheme="https://example.com/identifiers">SSP-2024-002</document-id>
+    <prop name="fedramp-version" ns="https://fedramp.gov/ns/oscal" value="fedramp-3.0.0rc1-oscal-1.1.2"/>
+    <prop name="marking" value="cui"/>
+    <role id="authorizing-official">
+      <title>Authorizing Official</title>
+      <description>
+        <p>Senior official with authority to formally assume responsibility for operating a system at an acceptable level of risk.</p>
+      </description>
+    </role>
+    <role id="prepared-by">
+      <title>Prepared By</title>
+      <description>
+        <p>This party prepared the SSP.</p>
+      </description>
+    </role>
+    <role id="prepared-for">
+      <title>Prepared For</title>
+      <description>
+        <p>The organization for which this SSP was prepared. Typically the CSP.</p>
+      </description>
+    </role>
+    <role id="creator">
+      <title>Document Creator</title>
+    </role>
+    <role id="content-approver">
+      <title>Content Approver</title>
+    </role>
+    <role id="system-admin">
+      <title>System Administrator</title>
+    </role>
+    <role id="asset-owner">
+      <title>Asset Owner</title>
+    </role>
+    <role id="system-owner">
+      <title>System Owner</title>
+    </role>
+     <role id="authorizing-official-poc">
+       <title>Authorizing Official Point of Contact</title>
+     </role>
+     <role id="information-system-security-officer">
+       <title>Information System Security Officer (or Equivalent)</title>
+     </role>
+     <role id="system-poc-management">
+      <title>Information System Management Point of Contact (POC)</title>
+      <description>
+         <p>The highest level manager who is responsible for system operation on behalf of the System Owner.</p>
+      </description>
+      </role>
+      <role id="system-poc-technical">
+          <title>Information System Technical Point of Contact</title>
+          <description>
+            <p>The individual or individuals leading the technical operation of the system.</p>
+          </description>
+      </role>
+      <role id="system-poc-other">
+          <title>General Point of Contact (POC)</title>
+          <description>
+            <p>A general point of contact for the system, designated by the system owner.</p>
+          </description>
+      </role>
+
+    <location uuid="27b78960-59ef-4619-82b0-ae20b9c709ac">
+      <title>CSP HQ</title>
+      <address type="work">
+        <addr-line>Suite 0000</addr-line>
+        <addr-line>1234 Some Street</addr-line>
+        <city>Haven</city>
+        <state>ME</state>
+        <postal-code>00000</postal-code>
+        <country>US</country>
+      </address>
+    </location>
+    <location uuid="11111112-0000-4000-9001-000000000009">
+      <address >
+        <country>US</country>
+      </address>
+      <prop name="type" value="data-center" class="primary"/>
+    </location>
+    <location uuid="11111112-0000-4000-9000-000000000003">
+      <address >
+        <country>US</country>
+      </address>
+      <prop name="type" value="data-center" class="alternate"/>
+    </location>
+    <party uuid="3360e343-9860-4bda-9dfc-ff427c3dfab6" type="person">
+      <name>Person Name 1</name>
+      <prop name="job-title" value="Individual's Title"/>
+      <prop name="mail-stop" value="Mailstop A-1"/>
+      <email-address>name@example.com</email-address>
+      <telephone-number>2020000001</telephone-number>
+      <location-uuid>27b78960-59ef-4619-82b0-ae20b9c709ac</location-uuid>
+      <member-of-organization>6b286b5d-8f07-4fa7-8847-1dd0d88f73fb</member-of-organization>
+    </party>
+    <party uuid="6b286b5d-8f07-4fa7-8847-1dd0d88f73fb" type="organization">
+      <name>Cloud Service Provider (CSP) Name</name>
+      <short-name>CSP Acronym/Short Name</short-name>
+      <link href="#31a46c4f-2959-4287-bc1c-67297d7da60b" rel="logo"/>
+      <location-uuid>27b78960-59ef-4619-82b0-ae20b9c709ac</location-uuid>
+    </party>
+    <party uuid="11111111-0000-4000-9000-000000000001" type="organization">
+      <name>Example Organization</name>
+      <short-name>ExOrg</short-name>
+      <link rel="website" href="https://example.com"/>
+    </party>
+    <party uuid="22222222-0000-4000-9000-000000000002" type="person">
+      <name>Jane Doe</name>
+      <email-address>jane.doe@example.com</email-address>
+    <address type="work"  />
+    </party>
+
+    <responsible-party role-id="prepared-by">
+      <party-uuid>3360e343-9860-4bda-9dfc-ff427c3dfab6</party-uuid>
+    </responsible-party>
+    <responsible-party role-id="prepared-for">
+      <party-uuid>6b286b5d-8f07-4fa7-8847-1dd0d88f73fb</party-uuid>
+    </responsible-party>
+    <responsible-party role-id="creator">
+      <party-uuid>11111111-0000-4000-9000-000000000001</party-uuid>
+    </responsible-party>
+    <responsible-party role-id="content-approver">
+      <party-uuid>22222222-0000-4000-9000-000000000002</party-uuid>
+    </responsible-party>
+
+    <responsible-party role-id="system-owner">
+      <party-uuid>22222222-0000-4000-9000-000000000002</party-uuid>
+    </responsible-party>
+    <responsible-party role-id="authorizing-official">
+      <party-uuid>22222222-0000-4000-9000-000000000002</party-uuid>
+    </responsible-party>
+    <responsible-party role-id="authorizing-official-poc">
+      <party-uuid>22222222-0000-4000-9000-000000000002</party-uuid>
+    </responsible-party>
+    <responsible-party role-id="system-poc-management">
+      <party-uuid>22222222-0000-4000-9000-000000000002</party-uuid>
+    </responsible-party>
+    <responsible-party role-id="system-poc-technical">
+      <party-uuid>22222222-0000-4000-9000-000000000002</party-uuid>
+    </responsible-party>
+    <responsible-party role-id="system-poc-other">
+      <party-uuid>22222222-0000-4000-9000-000000000002</party-uuid>
+    </responsible-party>
+    <responsible-party role-id="information-system-security-officer">
+      <party-uuid>22222222-0000-4000-9000-000000000002</party-uuid>
+    </responsible-party>
+
+    <remarks>
+      <p>This SSP is an example for demonstration purposes.</p>
+    </remarks>
+  </metadata>
+  
+  <import-profile href="../../../../dist/content/rev5/baselines/xml/FedRAMP_rev5_HIGH-baseline-resolved-profile_catalog.xml"/>
+  
+  <system-characteristics>
+    <system-id identifier-type="https://fedramp.gov">F00000001</system-id>
+    <system-name>Enhanced Example System</system-name>
+    <system-name-short>System's Short Name or Acronym</system-name-short>
+    <description>
+      <p>This is an enhanced example system for demonstration purposes, incorporating more FedRAMP-specific elements.</p>
+    </description>
+    <prop name="cloud-deployment-model" value="public-cloud">
+      <remarks>
+        <p>Remarks are required if deployment model is "hybrid-cloud" or "other". Optional otherwise.</p>
+      </remarks>
+    </prop>
+    <prop name="cloud-service-model" value="other">
+      <remarks>
+        <p>Remarks are required if service model is "other". Optional otherwise.</p>
+      </remarks>
+    </prop>
+    <prop name='authorization-type' value='fedramp-agency' ns="https://fedramp.gov/ns/oscal"/>
+    <prop name="identity-assurance-level" value="2"/>
+    <prop name="authenticator-assurance-level" value="2"/>
+    <prop name="federation-assurance-level" value="2"/>
+    <prop ns="https://fedramp.gov/ns/oscal" name="fully-operational-date" value="2023-01-01+00:00"/>
+    <security-sensitivity-level>fips-199-moderate</security-sensitivity-level>
+    <system-information>
+      <information-type  uuid="33333333-0000-4000-9000-000000000003">
+        <title>Financial Information</title>
+        <description>
+          <p>Contains sensitive financial data related to organizational operations.</p>
+        </description>
+        <categorization system="https://doi.org/10.6028/NIST.SP.800-60v2r1">
+          <information-type-id>C.2.8.12</information-type-id>
+        </categorization>
+        <confidentiality-impact>
+          <base>fips-199-high</base>
+          <selected>fips-199-high</selected>
+          <!-- adjustment-justification removed to ensure cia-impact-has-adjustment-justification passes when base and selected have the same impact level -->
+        </confidentiality-impact>
+        <integrity-impact>
+          <base>fips-199-moderate</base>
+          <selected>fips-199-low</selected>
+          <adjustment-justification>
+            <p>Required if the base and selected values do not match.</p>
+          </adjustment-justification>
+        </integrity-impact>
+        <availability-impact>
+          <base>fips-199-high</base>
+          <selected>fips-199-low</selected>
+          <adjustment-justification>
+            <p>Required if the base and selected values do not match.</p>
+          </adjustment-justification>
+        </availability-impact>
+      </information-type>
+    </system-information>
+    <security-impact-level>
+      <security-objective-confidentiality>fips-199-moderate</security-objective-confidentiality>
+      <security-objective-integrity>fips-199-moderate</security-objective-integrity>
+      <security-objective-availability>fips-199-moderate</security-objective-availability>
+    </security-impact-level>
+    <status state="operational"/>
+    <authorization-boundary>
+      <description>
+        <p>The authorization boundary includes all components within the main data center and the disaster recovery site.</p>
+      </description>
+      <diagram uuid="dbf46c27-52a9-49c4-beb6-b6399cd75497">
+            <description>
+               <p>A diagram-specific explanation.</p>
+            </description>
+            <link href="#d2eb3c18-6754-4e3a-a933-03d289e3fad5" rel="diagram"/>
+            <caption>Authorization Boundary Diagram</caption>
+         </diagram>
+    </authorization-boundary>
+    <network-architecture>
+      <description>
+        <p>A holistic, top-level explanation of the network architecture.</p>
+      </description>
+      <diagram uuid="e97c3395-433a-48c1-8cc7-dd1e1555941c">
+        <description>
+          <p>A diagram-specific explanation.</p>
+        </description>
+        <link href="#61081e81-850b-43c1-bf43-1ecbddcb9e7f" rel="diagram"/>
+        <caption>Network Diagram</caption>
+      </diagram>
+    </network-architecture>
+    <data-flow>
+      <description>
+        <p>A holistic, top-level explanation of the system's data flows.</p>
+      </description>
+      <diagram uuid="e3b98448-4219-46a5-b229-412423c566f3">
+        <description>
+          <p>A diagram-specific explanation.</p>
+        </description>
+        <link href="#ac5d7535-f3b8-45d3-bf3b-735c82c64547" rel="diagram"/>
+        <caption>Data Flow Diagram</caption>
+      </diagram>
+    </data-flow>
+  </system-characteristics>
+  
+  <system-implementation>
+
+    <leveraged-authorization uuid="233e0f09-fe5e-47e2-bca3-5f32df75e57a">
+      <title>GovCloud</title>
+      <prop ns="https://fedramp.gov/ns/oscal" name="leveraged-system-identifier" value="F1603047866"/>
+      <prop ns="https://fedramp.gov/ns/oscal" name="authorization-type" value="fedramp-agency"/>
+      <prop ns="https://fedramp.gov/ns/oscal" name="impact-level" value="fips-199-moderate"/>
+      <link href="//path/to/leveraged_system_ssp.xml"/>
+      <party-uuid>f0bc13a4-3303-47dd-80d3-380e159c8362</party-uuid>
+      <date-authorized>2015-01-01</date-authorized>
+      <remarks>
+        <p>Use one leveraged-authorization assembly for each underlying system. In the legacy world, these may be general support systems.</p>
+        <p>The link fields are optional, but preferred when known. Often, a leveraging system's SSP author will not have access to the leveraged system's SSP, but should have access to the leveraged system's CRM.</p>
+      </remarks>
+    </leveraged-authorization>
+
+    <user uuid="44444444-0000-4000-9000-000000000004">
+      <title>System Administrator</title>
+      <prop name="type" value="internal"/>
+      <prop ns="https://fedramp.gov/ns/oscal" name="privilege-level" value="read-write"/>
+      <prop ns="https://fedramp.gov/ns/oscal" name="sensitivity" value="high-risk"/>
+      <role-id>system-admin</role-id>
+      <authorized-privilege>
+        <title>Admin</title>
+        <description><p>admin user</p></description>
+        <function-performed>administration</function-performed>
+      </authorized-privilege>
+    </user>
+    
+    <component uuid="55555555-0000-4000-9000-000000000005" type="this-system">
+      <title>Primary Application Server</title>
+      <description>
+        <p>Main application server hosting the core system functionality.</p>
+      </description>
+      <purpose>main line</purpose>
+      <status state="operational"/>
+      <responsible-role role-id="system-admin">
+        <party-uuid>11111111-0000-4000-9000-000000000001</party-uuid>
+      </responsible-role>
+      <remarks>
+        <p>This is the primary application server for the system.</p>
+      </remarks>
+    </component>
+    <component uuid="66666666-0000-4000-9000-000000000007" type="service">
+      <title>Firebase CLI Connection</title>
+      <description>
+        <p>CLI for updating firebase Secure connection to an external API for data enrichment.</p>
+      </description>
+      <prop ns="https://fedramp.gov/ns/oscal" name="authentication-method" value="yes">
+        <remarks>
+          <p>Some description of the authentication method.</p>
+        </remarks>
+      </prop>
+      <prop name="interconnection-security" value="vpn" ns="https://fedramp.gov/ns/oscal"/>
+      <prop name="interconnection-direction" value="in/out" ns="https://fedramp.gov/ns/oscal"/>
+      <prop name="leveraged-authorization-uuid" value="233e0f09-fe5e-47e2-bca3-5f32df75e57a"/>
+      <prop name="asset-type" value="cli"/>
+      <prop name="implementation-point" value="external"/>
+      <status state="operational"/>
+      <responsible-role role-id="system-admin">
+        <party-uuid>11111111-0000-4000-9000-000000000001</party-uuid>
+      </responsible-role>
+      <remarks>
+        <p>This connection is used for secure data exchange with external systems.</p>
+      </remarks>
+    </component>
+    <component uuid="6ac88fd2-7c7b-4357-af2e-f22ccd3ead26" type="system">
+      <title>An External Leveraged System</title>
+      <description>
+        <p>An external leveraged system.</p>
+      </description>
+      <prop name="leveraged-authorization-uuid" value="233e0f09-fe5e-47e2-bca3-5f32df75e57a"/>
+      <prop name="implementation-point" value="external"/>
+      <prop name="nature-of-agreement" ns="https://fedramp.gov/ns/oscal" value="sla"/>
+      <prop ns="https://fedramp.gov/ns/oscal" name="authentication-method" value="yes">
+        <remarks>
+          <p>Some description of the external authentication method.</p>
+        </remarks>
+      </prop>
+      <status state="operational"/>
+      <responsible-role role-id="provider">
+        <party-uuid>11111111-0000-4000-9000-000000000001</party-uuid>
+      </responsible-role>
+      <responsible-role role-id="system-admin">
+        <party-uuid>11111111-0000-4000-9000-000000000001</party-uuid>
+      </responsible-role>
+      <responsible-role role-id="administrator">
+        <prop name="privilege-uuid" value="44444444-0000-4000-9000-000000000004" ns="https://fedramp.gov/ns/oscal" />
+      </responsible-role>
+    </component>
+
+    <component uuid="66666666-0000-4000-9000-000000000006" type="interconnection">
+      <title>External API Connection</title>
+      <description>
+        <p>Secure connection to an external API for data enrichment.</p>
+      </description>
+      <prop name="leveraged-authorization-uuid" value="233e0f09-fe5e-47e2-bca3-5f32df75e57a"/>
+      <prop name="connection-security" value="vpn" ns="https://fedramp.gov/ns/oscal"/>
+      <prop name="interconnection-security" value="vpn" ns="https://fedramp.gov/ns/oscal"/>
+      <prop name="interconnection-direction" value="in/out" ns="https://fedramp.gov/ns/oscal"/>
+      <prop ns="https://fedramp.gov/ns/oscal" name="authentication-method" value="yes">
+        <remarks>
+          <p>Some description of the authentication method.</p>
+        </remarks>
+      </prop>
+      <status state="operational"/>
+      <responsible-role role-id="provider">
+        <party-uuid>11111111-0000-4000-9000-000000000001</party-uuid>
+      </responsible-role>
+      <responsible-role role-id="system-admin">
+        <party-uuid>11111111-0000-4000-9000-000000000001</party-uuid>
+      </responsible-role>
+      <remarks>
+        <p>This connection is used for secure data exchange with external systems.</p>
+      </remarks>
+    </component>
+
+    <component uuid="77777777-0000-4000-9000-000000000007" type="software">
+      <title>Name of External System</title>
+      <description>
+          <p>Briefly describe the external system.</p>
+      </description>
+      <prop name="connection-security" value="vpn" ns="https://fedramp.gov/ns/oscal"/>
+      <prop name="direction" value="in/out" ns="https://fedramp.gov/ns/oscal"/>      
+      <prop name="asset-type" value="cli"/>
+      <prop name="implementation-point" value="external"/>
+      <prop name="nature-of-agreement" ns="https://fedramp.gov/ns/oscal" value="isa"/>
+      <prop ns="https://fedramp.gov/ns/oscal" name="authentication-method" value="yes">
+        <remarks>
+          <p>Some description of the authentication method.</p>
+        </remarks>
+      </prop>
+      <status state="operational"/>
+      <responsible-role role-id="provider">
+        <party-uuid>11111111-0000-4000-9000-000000000001</party-uuid>
+      </responsible-role>
+      <responsible-role role-id="system-admin">
+        <party-uuid>11111111-0000-4000-9000-000000000001</party-uuid>
+      </responsible-role>
+    </component>
+    
+    <inventory-item uuid="77777777-0000-4000-9000-000000000007">
+      <description>
+        <p>Primary database server</p>
+      </description>
+      <prop name="asset-id" value="DB-001" ns="http://csrc.nist.gov/ns/oscal"/>
+      <prop name="asset-type" value="database"/>
+      <prop name="allows-authenticated-scan" value="yes"/>
+      <prop name="public" value="no"/>
+      <prop name="virtual" value="yes"/>
+      <prop name="scan-type" value="database" ns="https://fedramp.gov/ns/oscal"/>
+      <responsible-party role-id="asset-owner">
+        <party-uuid>11111111-0000-4000-9000-000000000001</party-uuid>
+      </responsible-party>
+      <implemented-component component-uuid="55555555-0000-4000-9000-000000000005">
+        <prop name="asset-id" value="DB-001" ns="http://csrc.nist.gov/ns/oscal"/>
+      </implemented-component>
+    </inventory-item>
+
+    <inventory-item uuid="77777777-0000-4000-9001-000000000007">
+      <description>
+        <p>Secondary database server</p>
+      </description>
+      <prop name="asset-id" value="DB-002" ns="http://csrc.nist.gov/ns/oscal"/>
+      <prop name="asset-type" value="database"/>
+      <prop name="allows-authenticated-scan" value="yes"/>
+      <prop name="public" value="no"/>
+      <prop name="virtual" value="yes"/>
+      <prop name="scan-type" value="database" ns="https://fedramp.gov/ns/oscal"/>
+      <responsible-party role-id="asset-owner">
+        <party-uuid>11111111-0000-4000-9000-000000000001</party-uuid>
+      </responsible-party>
+      <implemented-component component-uuid="55555555-0000-4000-9001-000000000005">
+        <prop name="asset-id" value="DB-002" ns="http://csrc.nist.gov/ns/oscal"/>
+      </implemented-component>
+    </inventory-item>
+
+  </system-implementation>
+  
+  <control-implementation>
+    <description>
+      <p>Implementation of controls for the Enhanced Example System</p>
+    </description>
+    <implemented-requirement uuid="88888888-0000-4000-9000-000000000008" control-id="ac-1">
+      <prop name="control-origination" value="sp-system" ns="https://fedramp.gov/ns/oscal"/>
+      <prop name="implementation-status" value="partial" ns="https://fedramp.gov/ns/oscal"/>
+      <statement statement-id="ac-1_stmt.a" uuid="99999999-0000-4000-9000-000000000009">
+      </statement>
+      <by-component component-uuid="55555555-0000-4000-9000-000000000005" uuid="aaaaaaaa-0000-4000-9000-00000000000a">
+        <description>
+          <p>Access Control Policy and Procedures (AC-1) is fully implemented in our system.</p>
+        </description>
+        <prop ns="https://fedramp.gov/ns/oscal" name="implementation-status" value="implemented"/>
+        <responsible-role role-id="system-admin">
+          <party-uuid>11111111-0000-4000-9000-000000000001</party-uuid>
+        </responsible-role>
+      </by-component>
+    </implemented-requirement>
+    
+    <implemented-requirement uuid="bbbbbbbb-0000-4000-9000-00000000000b" control-id="cm-8">
+      <prop name="control-origination" value="sp-system" ns="https://fedramp.gov/ns/oscal"/>
+      <statement statement-id="cm-8_stmt.a" uuid="cccccccc-0000-4000-9000-00000000000c">
+      </statement>
+      <by-component component-uuid="55555555-0000-4000-9000-000000000005" uuid="dddddddd-0000-4000-9000-00000000000d">
+        <description>
+          <p>Information System Component Inventory (CM-8) is partially implemented.</p>
+        </description>
+        <prop ns="https://fedramp.gov/ns/oscal" name="implementation-status" value="partial"/>
+        <responsible-role role-id="system-admin">
+          <party-uuid>11111111-0000-4000-9000-000000000001</party-uuid>
+        </responsible-role>
+      </by-component>
+    </implemented-requirement>
+  </control-implementation>
+  
+  <back-matter>
+    <resource uuid="eeeeeeee-0000-4000-9000-00000000000e">
+      <title>Access Control Policy</title>
+      <description>
+        <p>Detailed access control policy document</p>
+      </description>
+      <prop name="type" value="policy" ns="https://fedramp.gov/ns/oscal"/>
+      <rlink href="https://example.com/policies/access-control.pdf"/>
+    </resource>
+    <resource uuid="90a128ac-c850-48f6-8fff-a55692f80b41">
+      <title>User's Guide</title>
+      <description>
+         <p>User's Guide</p>
+      </description>
+      <prop name="type" value="users-guide"/>
+      <prop name="published" value="2023-01-01T00:00:00Z"/>
+      <rlink href="./documents/guides/sample_guide.pdf"/>
+      <remarks>
+         <p>Table 12-1 Attachments: User's Guide Attachment</p>
+         <p>May use <code>rlink</code> with a relative path, or embedded as <code>base64</code>.</p>
+      </remarks>
+   </resource>
+   <resource uuid="489112e1-57f2-4c29-8dd0-95b1442fbf3b">
+    <title>Document Title</title>
+    <description>
+       <p>Rules of Behavior</p>
+    </description>
+    <prop name="type" value="rules-of-behavior"/>
+    <prop name="published" value="2023-01-01T00:00:00Z"/>
+    <prop name="version" value="Document Version"/>
+    <rlink href="./documents/rob.docx" media-type="application/msword"/>
+    <base64 filename="rob.docx" media-type="application/msword">00000000</base64>
+    <remarks>
+       <p>Table 12-1 Attachments: Rules of Behavior (ROB)</p>
+       <p>May use <code>rlink</code> with a relative path, or embedded as <code>base64</code>.</p>
+    </remarks>
+ </resource>
+ <resource uuid="c7860916-f2f4-43aa-b578-d48cf8e6d381">
+  <title>Document Title</title>
+  <description>
+     <p>Contingency Plan (CP)</p>
+  </description>
+  <prop name="type" value="plan" class="information-system-contingency-plan"/>
+  <prop name="published" value="2023-01-01T00:00:00Z"/>
+  <prop name="version" value="Document Version"/>
+  <rlink href="./documents/cp.docx" media-type="application/msword"/>
+  <base64 filename="cp.docx" media-type="application/msword">00000000</base64>
+  <remarks>
+     <p>Table 12-1 Attachments: Contingency Plan (CP) Attachment</p>
+     <p>May use <code>rlink</code> with a relative path, or embedded as <code>base64</code>.</p>
+  </remarks>
+</resource>
+<resource uuid="ab56cf27-0dae-40d6-89b7-d750137309af">
+  <title>Document Title</title>
+  <description>
+     <p>Configuration Management (CM) Plan</p>
+  </description>
+  <prop name="type" value="plan" class="configuration-management-plan"/>
+  <prop name="published" value="2023-01-01T00:00:00Z"/>
+  <prop name="version" value="Document Version"/>
+  <rlink href="./documents/CM_Plan.docx" media-type="application/msword"/>
+  <base64 filename="CM_Plan.docx" media-type="application/msword">00000000</base64>
+  <remarks>
+     <p>Table 12-1 Attachments: Configuration Management (CM) Plan Attachment</p>
+     <p>May use <code>rlink</code> with a relative path, or embedded as <code>base64</code>.</p>
+  </remarks>
+</resource>
+<resource uuid="3f771ab5-8016-4571-98d1-f0fb962e15e2">
+  <title>Document Title</title>
+  <description>
+     <p>Incident Response (IR) Plan</p>
+  </description>
+  <prop name="type" value="plan" class="incident-response-plan"/>
+  <prop name="published" value="2023-01-01T00:00:00Z"/>
+  <prop name="version" value="Document Version"/>
+  <rlink href="./documents/IR_Plan.docx" media-type="application/msword"/>
+  <base64 filename="IR_Plan.docx" media-type="application/msword">00000000</base64>
+  <remarks>
+     <p>Table 12-1 Attachments: Incident Response (IR) Plan Attachment</p>
+     <p>May use <code>rlink</code> with a relative path, or embedded as <code>base64</code>.</p>
+  </remarks>
+</resource>
+<resource uuid="49fb4631-1da2-41ca-b0b3-e1b1006d4025">
+  <title>Separation of Duties Matrix</title>
+  <description>
+     <p>Separation of Duties Matrix</p>
+  </description>
+  <prop ns="https://fedramp.gov/ns/oscal" name="type" value="separation-of-duties-matrix"/>
+  <prop name="published" value="2023-01-01T00:00:00Z"/>
+  <prop name="version" value="Document Version"/>
+  <rlink href="./documents/Sep_Matrix.docx" media-type="application/msword"/>
+  <base64 filename="Sep_Matrix.docx" media-type="application/msword">00000000</base64>
+  <remarks>
+     <p>May use <code>rlink</code> with a relative path, or embedded as <code>base64</code>.</p>
+  </remarks>
+</resource>
+
+    <resource uuid="d2eb3c18-6754-4e3a-a933-03d289e3fad5">
+      <title>Boundary Diagram</title>
+      <description>
+        <p>The primary authorization boundary diagram.</p>
+      </description>
+      <prop name="type" value="image" class="authorization-boundary" />
+      <rlink href="./attachments/diagrams/boundary.png"/>
+      <base64 filename="logo.png" media-type="image/png">00000000</base64>
+      <remarks>
+        <p>Section 8.1, Figure 8-1 Authorization Boundary Diagram (graphic)</p>
+        <p>This should be referenced in the system-characteristics/authorization-boundary/diagram/link/@href flag using a value of "#11111111-2222-4000-8000-001000000054"</p>
+        <p>May use <code>rlink</code> with a relative path, or embedded as <code>base64</code>.</p>
+        <p>FedRAMP prefers <code>base64</code> for images and diagrams.</p>
+        <p>Images must be in sufficient resolution to read all detail when rendered in a browser via HTML5.</p>
+      </remarks>
+    </resource>
+
+    <resource uuid="61081e81-850b-43c1-bf43-1ecbddcb9e7f">
+      <title>Network Diagram</title>
+      <description>
+        <p>The primary network diagram.</p>
+      </description>
+      <prop name="type" value="image" class="network-architecture" />
+      <!-- Use rlink and/or base64 -->
+      <rlink href="./attachments/diagrams/network.png"/>
+      <base64 filename="network.png" media-type="image/png">00000000</base64>
+      <remarks>
+        <p>Section 8.1, Figure 8-2 Network Diagram (graphic)</p>
+        <p>This should be referenced in the system-characteristics/network-architecture/diagram/link/@href flag using a value of "#11111111-2222-4000-8000-001000000055"</p>
+        <p>May use <code>rlink</code> with a relative path, or embedded as <code>base64</code>.</p>
+        <p>FedRAMP prefers <code>base64</code> for images and diagrams.</p>
+        <p>Images must be in sufficient resolution to read all detail when rendered in a browser via HTML5.</p>
+      </remarks>
+    </resource>
+
+    <resource uuid="ac5d7535-f3b8-45d3-bf3b-735c82c64547">
+      <title>Data Flow Diagram</title>
+      <description>
+        <p>The primary data flow diagram.</p>
+      </description>
+      <prop name="type" value="image" class="data-flow" />
+      <rlink href="./attachments/diagrams/dataflow.png"/>
+      <base64 filename="dataflow.png" media-type="image/png">00000000</base64>
+      <remarks>
+        <p>Section 8.1, Figure 8-3 Data Flow Diagram (graphic)</p>
+        <p>This should be referenced in the system-characteristics/data-flow/diagram/link/@href flag using a value of "#11111111-2222-4000-8000-001000000056"</p>
+        <p>May use <code>rlink</code> with a relative path, or embedded as <code>base64</code>.</p>
+        <p>FedRAMP prefers <code>base64</code> for images and diagrams.</p>
+        <p>Images must be in sufficient resolution to read all detail when rendered in a browser via HTML5.</p>
+      </remarks>
+    </resource>
+  </back-matter>
+</system-security-plan>
\ No newline at end of file
diff --git a/src/validations/constraints/content/ssp-interconnection-security-VALID.xml b/src/validations/constraints/content/ssp-interconnection-security-VALID.xml
new file mode 100644
index 0000000000..715a29c660
--- /dev/null
+++ b/src/validations/constraints/content/ssp-interconnection-security-VALID.xml
@@ -0,0 +1,625 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<system-security-plan xmlns="http://csrc.nist.gov/ns/oscal/1.0"
+                      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+                      xsi:schemaLocation="http://csrc.nist.gov/ns/oscal/1.0 https://github.com/usnistgov/OSCAL/releases/download/v1.1.2/oscal_ssp_schema.xsd"
+                      uuid="12345678-1234-4321-8765-123456789012">
+  <metadata>
+    <title>Enhanced Example System Security Plan</title>
+    <published>2024-08-01T14:30:00Z</published>
+    <last-modified>2024-08-01T14:30:00Z</last-modified>
+    <version>1.1</version>
+    <oscal-version>1.1.2</oscal-version>
+    <document-id scheme="https://example.com/identifiers">SSP-2024-002</document-id>
+    <prop name="fedramp-version" ns="https://fedramp.gov/ns/oscal" value="fedramp-3.0.0rc1-oscal-1.1.2"/>
+    <prop name="marking" value="cui"/>
+    <role id="authorizing-official">
+      <title>Authorizing Official</title>
+      <description>
+        <p>Senior official with authority to formally assume responsibility for operating a system at an acceptable level of risk.</p>
+      </description>
+    </role>
+    <role id="prepared-by">
+      <title>Prepared By</title>
+      <description>
+        <p>This party prepared the SSP.</p>
+      </description>
+    </role>
+    <role id="prepared-for">
+      <title>Prepared For</title>
+      <description>
+        <p>The organization for which this SSP was prepared. Typically the CSP.</p>
+      </description>
+    </role>
+    <role id="creator">
+      <title>Document Creator</title>
+    </role>
+    <role id="content-approver">
+      <title>Content Approver</title>
+    </role>
+    <role id="system-admin">
+      <title>System Administrator</title>
+    </role>
+    <role id="asset-owner">
+      <title>Asset Owner</title>
+    </role>
+    <role id="system-owner">
+      <title>System Owner</title>
+    </role>
+     <role id="authorizing-official-poc">
+       <title>Authorizing Official Point of Contact</title>
+     </role>
+     <role id="information-system-security-officer">
+       <title>Information System Security Officer (or Equivalent)</title>
+     </role>
+     <role id="system-poc-management">
+      <title>Information System Management Point of Contact (POC)</title>
+      <description>
+         <p>The highest level manager who is responsible for system operation on behalf of the System Owner.</p>
+      </description>
+      </role>
+      <role id="system-poc-technical">
+          <title>Information System Technical Point of Contact</title>
+          <description>
+            <p>The individual or individuals leading the technical operation of the system.</p>
+          </description>
+      </role>
+      <role id="system-poc-other">
+          <title>General Point of Contact (POC)</title>
+          <description>
+            <p>A general point of contact for the system, designated by the system owner.</p>
+          </description>
+      </role>
+
+    <location uuid="27b78960-59ef-4619-82b0-ae20b9c709ac">
+      <title>CSP HQ</title>
+      <address type="work">
+        <addr-line>Suite 0000</addr-line>
+        <addr-line>1234 Some Street</addr-line>
+        <city>Haven</city>
+        <state>ME</state>
+        <postal-code>00000</postal-code>
+        <country>US</country>
+      </address>
+    </location>
+    <location uuid="11111112-0000-4000-9001-000000000009">
+      <address >
+        <country>US</country>
+      </address>
+      <prop name="type" value="data-center" class="primary"/>
+    </location>
+    <location uuid="11111112-0000-4000-9000-000000000003">
+      <address >
+        <country>US</country>
+      </address>
+      <prop name="type" value="data-center" class="alternate"/>
+    </location>
+    <party uuid="3360e343-9860-4bda-9dfc-ff427c3dfab6" type="person">
+      <name>Person Name 1</name>
+      <prop name="job-title" value="Individual's Title"/>
+      <prop name="mail-stop" value="Mailstop A-1"/>
+      <email-address>name@example.com</email-address>
+      <telephone-number>2020000001</telephone-number>
+      <location-uuid>27b78960-59ef-4619-82b0-ae20b9c709ac</location-uuid>
+      <member-of-organization>6b286b5d-8f07-4fa7-8847-1dd0d88f73fb</member-of-organization>
+    </party>
+    <party uuid="6b286b5d-8f07-4fa7-8847-1dd0d88f73fb" type="organization">
+      <name>Cloud Service Provider (CSP) Name</name>
+      <short-name>CSP Acronym/Short Name</short-name>
+      <link href="#31a46c4f-2959-4287-bc1c-67297d7da60b" rel="logo"/>
+      <location-uuid>27b78960-59ef-4619-82b0-ae20b9c709ac</location-uuid>
+    </party>
+    <party uuid="11111111-0000-4000-9000-000000000001" type="organization">
+      <name>Example Organization</name>
+      <short-name>ExOrg</short-name>
+      <link rel="website" href="https://example.com"/>
+    </party>
+    <party uuid="22222222-0000-4000-9000-000000000002" type="person">
+      <name>Jane Doe</name>
+      <email-address>jane.doe@example.com</email-address>
+    <address type="work"  />
+    </party>
+
+    <responsible-party role-id="prepared-by">
+      <party-uuid>3360e343-9860-4bda-9dfc-ff427c3dfab6</party-uuid>
+    </responsible-party>
+    <responsible-party role-id="prepared-for">
+      <party-uuid>6b286b5d-8f07-4fa7-8847-1dd0d88f73fb</party-uuid>
+    </responsible-party>
+    <responsible-party role-id="creator">
+      <party-uuid>11111111-0000-4000-9000-000000000001</party-uuid>
+    </responsible-party>
+    <responsible-party role-id="content-approver">
+      <party-uuid>22222222-0000-4000-9000-000000000002</party-uuid>
+    </responsible-party>
+
+    <responsible-party role-id="system-owner">
+      <party-uuid>22222222-0000-4000-9000-000000000002</party-uuid>
+    </responsible-party>
+    <responsible-party role-id="authorizing-official">
+      <party-uuid>22222222-0000-4000-9000-000000000002</party-uuid>
+    </responsible-party>
+    <responsible-party role-id="authorizing-official-poc">
+      <party-uuid>22222222-0000-4000-9000-000000000002</party-uuid>
+    </responsible-party>
+    <responsible-party role-id="system-poc-management">
+      <party-uuid>22222222-0000-4000-9000-000000000002</party-uuid>
+    </responsible-party>
+    <responsible-party role-id="system-poc-technical">
+      <party-uuid>22222222-0000-4000-9000-000000000002</party-uuid>
+    </responsible-party>
+    <responsible-party role-id="system-poc-other">
+      <party-uuid>22222222-0000-4000-9000-000000000002</party-uuid>
+    </responsible-party>
+    <responsible-party role-id="information-system-security-officer">
+      <party-uuid>22222222-0000-4000-9000-000000000002</party-uuid>
+    </responsible-party>
+
+    <remarks>
+      <p>This SSP is an example for demonstration purposes.</p>
+    </remarks>
+  </metadata>
+  
+  <import-profile href="../../../../dist/content/rev5/baselines/xml/FedRAMP_rev5_HIGH-baseline-resolved-profile_catalog.xml"/>
+  
+  <system-characteristics>
+    <system-id identifier-type="https://fedramp.gov">F00000001</system-id>
+    <system-name>Enhanced Example System</system-name>
+    <system-name-short>System's Short Name or Acronym</system-name-short>
+    <description>
+      <p>This is an enhanced example system for demonstration purposes, incorporating more FedRAMP-specific elements.</p>
+    </description>
+    <prop name="cloud-deployment-model" value="public-cloud">
+      <remarks>
+        <p>Remarks are required if deployment model is "hybrid-cloud" or "other". Optional otherwise.</p>
+      </remarks>
+    </prop>
+    <prop name="cloud-service-model" value="other">
+      <remarks>
+        <p>Remarks are required if service model is "other". Optional otherwise.</p>
+      </remarks>
+    </prop>
+    <prop name='authorization-type' value='fedramp-agency' ns="https://fedramp.gov/ns/oscal"/>
+    <prop name="identity-assurance-level" value="2"/>
+    <prop name="authenticator-assurance-level" value="2"/>
+    <prop name="federation-assurance-level" value="2"/>
+    <prop ns="https://fedramp.gov/ns/oscal" name="fully-operational-date" value="2023-01-01+00:00"/>
+    <security-sensitivity-level>fips-199-moderate</security-sensitivity-level>
+    <system-information>
+      <information-type  uuid="33333333-0000-4000-9000-000000000003">
+        <title>Financial Information</title>
+        <description>
+          <p>Contains sensitive financial data related to organizational operations.</p>
+        </description>
+        <categorization system="https://doi.org/10.6028/NIST.SP.800-60v2r1">
+          <information-type-id>C.2.8.12</information-type-id>
+        </categorization>
+        <confidentiality-impact>
+          <base>fips-199-high</base>
+          <selected>fips-199-high</selected>
+          <!-- adjustment-justification removed to ensure cia-impact-has-adjustment-justification passes when base and selected have the same impact level -->
+        </confidentiality-impact>
+        <integrity-impact>
+          <base>fips-199-moderate</base>
+          <selected>fips-199-low</selected>
+          <adjustment-justification>
+            <p>Required if the base and selected values do not match.</p>
+          </adjustment-justification>
+        </integrity-impact>
+        <availability-impact>
+          <base>fips-199-high</base>
+          <selected>fips-199-low</selected>
+          <adjustment-justification>
+            <p>Required if the base and selected values do not match.</p>
+          </adjustment-justification>
+        </availability-impact>
+      </information-type>
+    </system-information>
+    <security-impact-level>
+      <security-objective-confidentiality>fips-199-moderate</security-objective-confidentiality>
+      <security-objective-integrity>fips-199-moderate</security-objective-integrity>
+      <security-objective-availability>fips-199-moderate</security-objective-availability>
+    </security-impact-level>
+    <status state="operational"/>
+    <authorization-boundary>
+      <description>
+        <p>The authorization boundary includes all components within the main data center and the disaster recovery site.</p>
+      </description>
+      <diagram uuid="dbf46c27-52a9-49c4-beb6-b6399cd75497">
+            <description>
+               <p>A diagram-specific explanation.</p>
+            </description>
+            <link href="#d2eb3c18-6754-4e3a-a933-03d289e3fad5" rel="diagram"/>
+            <caption>Authorization Boundary Diagram</caption>
+         </diagram>
+    </authorization-boundary>
+    <network-architecture>
+      <description>
+        <p>A holistic, top-level explanation of the network architecture.</p>
+      </description>
+      <diagram uuid="e97c3395-433a-48c1-8cc7-dd1e1555941c">
+        <description>
+          <p>A diagram-specific explanation.</p>
+        </description>
+        <link href="#61081e81-850b-43c1-bf43-1ecbddcb9e7f" rel="diagram"/>
+        <caption>Network Diagram</caption>
+      </diagram>
+    </network-architecture>
+    <data-flow>
+      <description>
+        <p>A holistic, top-level explanation of the system's data flows.</p>
+      </description>
+      <diagram uuid="e3b98448-4219-46a5-b229-412423c566f3">
+        <description>
+          <p>A diagram-specific explanation.</p>
+        </description>
+        <link href="#ac5d7535-f3b8-45d3-bf3b-735c82c64547" rel="diagram"/>
+        <caption>Data Flow Diagram</caption>
+      </diagram>
+    </data-flow>
+  </system-characteristics>
+  
+  <system-implementation>
+
+    <leveraged-authorization uuid="233e0f09-fe5e-47e2-bca3-5f32df75e57a">
+      <title>GovCloud</title>
+      <prop ns="https://fedramp.gov/ns/oscal" name="leveraged-system-identifier" value="F1603047866"/>
+      <prop ns="https://fedramp.gov/ns/oscal" name="authorization-type" value="fedramp-agency"/>
+      <prop ns="https://fedramp.gov/ns/oscal" name="impact-level" value="fips-199-moderate"/>
+      <link href="//path/to/leveraged_system_ssp.xml"/>
+      <party-uuid>f0bc13a4-3303-47dd-80d3-380e159c8362</party-uuid>
+      <date-authorized>2015-01-01</date-authorized>
+      <remarks>
+        <p>Use one leveraged-authorization assembly for each underlying system. In the legacy world, these may be general support systems.</p>
+        <p>The link fields are optional, but preferred when known. Often, a leveraging system's SSP author will not have access to the leveraged system's SSP, but should have access to the leveraged system's CRM.</p>
+      </remarks>
+    </leveraged-authorization>
+
+    <user uuid="44444444-0000-4000-9000-000000000004">
+      <title>System Administrator</title>
+      <prop name="type" value="internal"/>
+      <prop ns="https://fedramp.gov/ns/oscal" name="privilege-level" value="read-write"/>
+      <prop ns="https://fedramp.gov/ns/oscal" name="sensitivity" value="high-risk"/>
+      <role-id>system-admin</role-id>
+      <authorized-privilege>
+        <title>Admin</title>
+        <description><p>admin user</p></description>
+        <function-performed>administration</function-performed>
+      </authorized-privilege>
+    </user>
+    
+    <component uuid="55555555-0000-4000-9000-000000000005" type="this-system">
+      <title>Primary Application Server</title>
+      <description>
+        <p>Main application server hosting the core system functionality.</p>
+      </description>
+      <purpose>main line</purpose>
+      <status state="operational"/>
+      <responsible-role role-id="system-admin">
+        <party-uuid>11111111-0000-4000-9000-000000000001</party-uuid>
+      </responsible-role>
+      <remarks>
+        <p>This is the primary application server for the system.</p>
+      </remarks>
+    </component>
+    <component uuid="66666666-0000-4000-9000-000000000007" type="service">
+      <title>Firebase CLI Connection</title>
+      <description>
+        <p>CLI for updating firebase Secure connection to an external API for data enrichment.</p>
+      </description>
+      <prop ns="https://fedramp.gov/ns/oscal" name="authentication-method" value="yes">
+        <remarks>
+          <p>Some description of the authentication method.</p>
+        </remarks>
+      </prop>
+      <prop name="interconnection-security" value="vpn" ns="https://fedramp.gov/ns/oscal"/>
+      <prop name="interconnection-direction" value="in/out" ns="https://fedramp.gov/ns/oscal"/>
+      <prop name="leveraged-authorization-uuid" value="233e0f09-fe5e-47e2-bca3-5f32df75e57a"/>
+      <prop name="asset-type" value="cli"/>
+      <prop name="implementation-point" value="external"/>
+      <status state="operational"/>
+      <responsible-role role-id="system-admin">
+        <party-uuid>11111111-0000-4000-9000-000000000001</party-uuid>
+      </responsible-role>
+      <remarks>
+        <p>This connection is used for secure data exchange with external systems.</p>
+      </remarks>
+    </component>
+    <component uuid="6ac88fd2-7c7b-4357-af2e-f22ccd3ead26" type="system">
+      <title>An External Leveraged System</title>
+      <description>
+        <p>An external leveraged system.</p>
+      </description>
+      <prop name="leveraged-authorization-uuid" value="233e0f09-fe5e-47e2-bca3-5f32df75e57a"/>
+      <prop name="implementation-point" value="external"/>
+      <prop name="nature-of-agreement" ns="https://fedramp.gov/ns/oscal" value="sla"/>
+      <prop ns="https://fedramp.gov/ns/oscal" name="authentication-method" value="yes">
+        <remarks>
+          <p>Some description of the external authentication method.</p>
+        </remarks>
+      </prop>
+      <status state="operational"/>
+      <responsible-role role-id="provider">
+        <party-uuid>11111111-0000-4000-9000-000000000001</party-uuid>
+      </responsible-role>
+      <responsible-role role-id="system-admin">
+        <party-uuid>11111111-0000-4000-9000-000000000001</party-uuid>
+      </responsible-role>
+      <responsible-role role-id="administrator">
+        <prop name="privilege-uuid" value="44444444-0000-4000-9000-000000000004" ns="https://fedramp.gov/ns/oscal" />
+      </responsible-role>
+    </component>
+
+    <component uuid="66666666-0000-4000-9000-000000000006" type="interconnection">
+      <title>External API Connection</title>
+      <description>
+        <p>Secure connection to an external API for data enrichment.</p>
+      </description>
+      <prop name="leveraged-authorization-uuid" value="233e0f09-fe5e-47e2-bca3-5f32df75e57a"/>
+      <prop name="connection-security" value="vpn" ns="https://fedramp.gov/ns/oscal"/>
+      <prop name="interconnection-security" value="vpn" ns="https://fedramp.gov/ns/oscal"/>
+      <prop name="interconnection-direction" value="in/out" ns="https://fedramp.gov/ns/oscal"/>
+      <prop ns="https://fedramp.gov/ns/oscal" name="authentication-method" value="yes">
+        <remarks>
+          <p>Some description of the authentication method.</p>
+        </remarks>
+      </prop>
+      <status state="operational"/>
+      <responsible-role role-id="provider">
+        <party-uuid>11111111-0000-4000-9000-000000000001</party-uuid>
+      </responsible-role>
+      <responsible-role role-id="system-admin">
+        <party-uuid>11111111-0000-4000-9000-000000000001</party-uuid>
+      </responsible-role>
+      <remarks>
+        <p>This connection is used for secure data exchange with external systems.</p>
+      </remarks>
+    </component>
+
+    <component uuid="77777777-0000-4000-9000-000000000007" type="software">
+      <title>Name of External System</title>
+      <description>
+          <p>Briefly describe the external system.</p>
+      </description>
+      <prop name="connection-security" value="vpn" ns="https://fedramp.gov/ns/oscal"/>
+      <prop name="direction" value="in/out" ns="https://fedramp.gov/ns/oscal"/>      
+      <prop name="asset-type" value="cli"/>
+      <prop name="implementation-point" value="external"/>
+      <prop name="nature-of-agreement" ns="https://fedramp.gov/ns/oscal" value="isa"/>
+      <prop ns="https://fedramp.gov/ns/oscal" name="authentication-method" value="yes">
+        <remarks>
+          <p>Some description of the authentication method.</p>
+        </remarks>
+      </prop>
+      <status state="operational"/>
+      <responsible-role role-id="provider">
+        <party-uuid>11111111-0000-4000-9000-000000000001</party-uuid>
+      </responsible-role>
+      <responsible-role role-id="system-admin">
+        <party-uuid>11111111-0000-4000-9000-000000000001</party-uuid>
+      </responsible-role>
+    </component>
+    
+    <inventory-item uuid="77777777-0000-4000-9000-000000000007">
+      <description>
+        <p>Primary database server</p>
+      </description>
+      <prop name="asset-id" value="DB-001" ns="http://csrc.nist.gov/ns/oscal"/>
+      <prop name="asset-type" value="database"/>
+      <prop name="allows-authenticated-scan" value="yes"/>
+      <prop name="public" value="no"/>
+      <prop name="virtual" value="yes"/>
+      <prop name="scan-type" value="database" ns="https://fedramp.gov/ns/oscal"/>
+      <responsible-party role-id="asset-owner">
+        <party-uuid>11111111-0000-4000-9000-000000000001</party-uuid>
+      </responsible-party>
+      <implemented-component component-uuid="55555555-0000-4000-9000-000000000005">
+        <prop name="asset-id" value="DB-001" ns="http://csrc.nist.gov/ns/oscal"/>
+      </implemented-component>
+    </inventory-item>
+
+    <inventory-item uuid="77777777-0000-4000-9001-000000000007">
+      <description>
+        <p>Secondary database server</p>
+      </description>
+      <prop name="asset-id" value="DB-002" ns="http://csrc.nist.gov/ns/oscal"/>
+      <prop name="asset-type" value="database"/>
+      <prop name="allows-authenticated-scan" value="yes"/>
+      <prop name="public" value="no"/>
+      <prop name="virtual" value="yes"/>
+      <prop name="scan-type" value="database" ns="https://fedramp.gov/ns/oscal"/>
+      <responsible-party role-id="asset-owner">
+        <party-uuid>11111111-0000-4000-9000-000000000001</party-uuid>
+      </responsible-party>
+      <implemented-component component-uuid="55555555-0000-4000-9001-000000000005">
+        <prop name="asset-id" value="DB-002" ns="http://csrc.nist.gov/ns/oscal"/>
+      </implemented-component>
+    </inventory-item>
+
+  </system-implementation>
+  
+  <control-implementation>
+    <description>
+      <p>Implementation of controls for the Enhanced Example System</p>
+    </description>
+    <implemented-requirement uuid="88888888-0000-4000-9000-000000000008" control-id="ac-1">
+      <prop name="control-origination" value="sp-system" ns="https://fedramp.gov/ns/oscal"/>
+      <prop name="implementation-status" value="partial" ns="https://fedramp.gov/ns/oscal"/>
+      <statement statement-id="ac-1_stmt.a" uuid="99999999-0000-4000-9000-000000000009">
+      </statement>
+      <by-component component-uuid="55555555-0000-4000-9000-000000000005" uuid="aaaaaaaa-0000-4000-9000-00000000000a">
+        <description>
+          <p>Access Control Policy and Procedures (AC-1) is fully implemented in our system.</p>
+        </description>
+        <prop ns="https://fedramp.gov/ns/oscal" name="implementation-status" value="implemented"/>
+        <responsible-role role-id="system-admin">
+          <party-uuid>11111111-0000-4000-9000-000000000001</party-uuid>
+        </responsible-role>
+      </by-component>
+    </implemented-requirement>
+    
+    <implemented-requirement uuid="bbbbbbbb-0000-4000-9000-00000000000b" control-id="cm-8">
+      <prop name="control-origination" value="sp-system" ns="https://fedramp.gov/ns/oscal"/>
+      <statement statement-id="cm-8_stmt.a" uuid="cccccccc-0000-4000-9000-00000000000c">
+      </statement>
+      <by-component component-uuid="55555555-0000-4000-9000-000000000005" uuid="dddddddd-0000-4000-9000-00000000000d">
+        <description>
+          <p>Information System Component Inventory (CM-8) is partially implemented.</p>
+        </description>
+        <prop ns="https://fedramp.gov/ns/oscal" name="implementation-status" value="partial"/>
+        <responsible-role role-id="system-admin">
+          <party-uuid>11111111-0000-4000-9000-000000000001</party-uuid>
+        </responsible-role>
+      </by-component>
+    </implemented-requirement>
+  </control-implementation>
+  
+  <back-matter>
+    <resource uuid="eeeeeeee-0000-4000-9000-00000000000e">
+      <title>Access Control Policy</title>
+      <description>
+        <p>Detailed access control policy document</p>
+      </description>
+      <prop name="type" value="policy" ns="https://fedramp.gov/ns/oscal"/>
+      <rlink href="https://example.com/policies/access-control.pdf"/>
+    </resource>
+    <resource uuid="90a128ac-c850-48f6-8fff-a55692f80b41">
+      <title>User's Guide</title>
+      <description>
+         <p>User's Guide</p>
+      </description>
+      <prop name="type" value="users-guide"/>
+      <prop name="published" value="2023-01-01T00:00:00Z"/>
+      <rlink href="./documents/guides/sample_guide.pdf"/>
+      <remarks>
+         <p>Table 12-1 Attachments: User's Guide Attachment</p>
+         <p>May use <code>rlink</code> with a relative path, or embedded as <code>base64</code>.</p>
+      </remarks>
+   </resource>
+   <resource uuid="489112e1-57f2-4c29-8dd0-95b1442fbf3b">
+    <title>Document Title</title>
+    <description>
+       <p>Rules of Behavior</p>
+    </description>
+    <prop name="type" value="rules-of-behavior"/>
+    <prop name="published" value="2023-01-01T00:00:00Z"/>
+    <prop name="version" value="Document Version"/>
+    <rlink href="./documents/rob.docx" media-type="application/msword"/>
+    <base64 filename="rob.docx" media-type="application/msword">00000000</base64>
+    <remarks>
+       <p>Table 12-1 Attachments: Rules of Behavior (ROB)</p>
+       <p>May use <code>rlink</code> with a relative path, or embedded as <code>base64</code>.</p>
+    </remarks>
+ </resource>
+ <resource uuid="c7860916-f2f4-43aa-b578-d48cf8e6d381">
+  <title>Document Title</title>
+  <description>
+     <p>Contingency Plan (CP)</p>
+  </description>
+  <prop name="type" value="plan" class="information-system-contingency-plan"/>
+  <prop name="published" value="2023-01-01T00:00:00Z"/>
+  <prop name="version" value="Document Version"/>
+  <rlink href="./documents/cp.docx" media-type="application/msword"/>
+  <base64 filename="cp.docx" media-type="application/msword">00000000</base64>
+  <remarks>
+     <p>Table 12-1 Attachments: Contingency Plan (CP) Attachment</p>
+     <p>May use <code>rlink</code> with a relative path, or embedded as <code>base64</code>.</p>
+  </remarks>
+</resource>
+<resource uuid="ab56cf27-0dae-40d6-89b7-d750137309af">
+  <title>Document Title</title>
+  <description>
+     <p>Configuration Management (CM) Plan</p>
+  </description>
+  <prop name="type" value="plan" class="configuration-management-plan"/>
+  <prop name="published" value="2023-01-01T00:00:00Z"/>
+  <prop name="version" value="Document Version"/>
+  <rlink href="./documents/CM_Plan.docx" media-type="application/msword"/>
+  <base64 filename="CM_Plan.docx" media-type="application/msword">00000000</base64>
+  <remarks>
+     <p>Table 12-1 Attachments: Configuration Management (CM) Plan Attachment</p>
+     <p>May use <code>rlink</code> with a relative path, or embedded as <code>base64</code>.</p>
+  </remarks>
+</resource>
+<resource uuid="3f771ab5-8016-4571-98d1-f0fb962e15e2">
+  <title>Document Title</title>
+  <description>
+     <p>Incident Response (IR) Plan</p>
+  </description>
+  <prop name="type" value="plan" class="incident-response-plan"/>
+  <prop name="published" value="2023-01-01T00:00:00Z"/>
+  <prop name="version" value="Document Version"/>
+  <rlink href="./documents/IR_Plan.docx" media-type="application/msword"/>
+  <base64 filename="IR_Plan.docx" media-type="application/msword">00000000</base64>
+  <remarks>
+     <p>Table 12-1 Attachments: Incident Response (IR) Plan Attachment</p>
+     <p>May use <code>rlink</code> with a relative path, or embedded as <code>base64</code>.</p>
+  </remarks>
+</resource>
+<resource uuid="49fb4631-1da2-41ca-b0b3-e1b1006d4025">
+  <title>Separation of Duties Matrix</title>
+  <description>
+     <p>Separation of Duties Matrix</p>
+  </description>
+  <prop ns="https://fedramp.gov/ns/oscal" name="type" value="separation-of-duties-matrix"/>
+  <prop name="published" value="2023-01-01T00:00:00Z"/>
+  <prop name="version" value="Document Version"/>
+  <rlink href="./documents/Sep_Matrix.docx" media-type="application/msword"/>
+  <base64 filename="Sep_Matrix.docx" media-type="application/msword">00000000</base64>
+  <remarks>
+     <p>May use <code>rlink</code> with a relative path, or embedded as <code>base64</code>.</p>
+  </remarks>
+</resource>
+
+    <resource uuid="d2eb3c18-6754-4e3a-a933-03d289e3fad5">
+      <title>Boundary Diagram</title>
+      <description>
+        <p>The primary authorization boundary diagram.</p>
+      </description>
+      <prop name="type" value="image" class="authorization-boundary" />
+      <rlink href="./attachments/diagrams/boundary.png"/>
+      <base64 filename="logo.png" media-type="image/png">00000000</base64>
+      <remarks>
+        <p>Section 8.1, Figure 8-1 Authorization Boundary Diagram (graphic)</p>
+        <p>This should be referenced in the system-characteristics/authorization-boundary/diagram/link/@href flag using a value of "#11111111-2222-4000-8000-001000000054"</p>
+        <p>May use <code>rlink</code> with a relative path, or embedded as <code>base64</code>.</p>
+        <p>FedRAMP prefers <code>base64</code> for images and diagrams.</p>
+        <p>Images must be in sufficient resolution to read all detail when rendered in a browser via HTML5.</p>
+      </remarks>
+    </resource>
+
+    <resource uuid="61081e81-850b-43c1-bf43-1ecbddcb9e7f">
+      <title>Network Diagram</title>
+      <description>
+        <p>The primary network diagram.</p>
+      </description>
+      <prop name="type" value="image" class="network-architecture" />
+      <!-- Use rlink and/or base64 -->
+      <rlink href="./attachments/diagrams/network.png"/>
+      <base64 filename="network.png" media-type="image/png">00000000</base64>
+      <remarks>
+        <p>Section 8.1, Figure 8-2 Network Diagram (graphic)</p>
+        <p>This should be referenced in the system-characteristics/network-architecture/diagram/link/@href flag using a value of "#11111111-2222-4000-8000-001000000055"</p>
+        <p>May use <code>rlink</code> with a relative path, or embedded as <code>base64</code>.</p>
+        <p>FedRAMP prefers <code>base64</code> for images and diagrams.</p>
+        <p>Images must be in sufficient resolution to read all detail when rendered in a browser via HTML5.</p>
+      </remarks>
+    </resource>
+
+    <resource uuid="ac5d7535-f3b8-45d3-bf3b-735c82c64547">
+      <title>Data Flow Diagram</title>
+      <description>
+        <p>The primary data flow diagram.</p>
+      </description>
+      <prop name="type" value="image" class="data-flow" />
+      <rlink href="./attachments/diagrams/dataflow.png"/>
+      <base64 filename="dataflow.png" media-type="image/png">00000000</base64>
+      <remarks>
+        <p>Section 8.1, Figure 8-3 Data Flow Diagram (graphic)</p>
+        <p>This should be referenced in the system-characteristics/data-flow/diagram/link/@href flag using a value of "#11111111-2222-4000-8000-001000000056"</p>
+        <p>May use <code>rlink</code> with a relative path, or embedded as <code>base64</code>.</p>
+        <p>FedRAMP prefers <code>base64</code> for images and diagrams.</p>
+        <p>Images must be in sufficient resolution to read all detail when rendered in a browser via HTML5.</p>
+      </remarks>
+    </resource>
+  </back-matter>
+</system-security-plan>
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/address-type-PASS.yaml b/src/validations/constraints/unit-tests/address-type-PASS.yaml
index 65ca540903..6dbb63acdb 100644
--- a/src/validations/constraints/unit-tests/address-type-PASS.yaml
+++ b/src/validations/constraints/unit-tests/address-type-PASS.yaml
@@ -2,7 +2,7 @@
 test-case:
   name: Test Valid Address Type Use
   description: Test that the specified address type is valid.
-  content: ../content/ssp-all-VALID.xml # the content to run
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml # the content to run
   expectations: # check the constraint result
   - constraint-id: address-type
     result: pass
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/attachment-type-PASS.yaml b/src/validations/constraints/unit-tests/attachment-type-PASS.yaml
index 98e4f563e5..7bfd912339 100644
--- a/src/validations/constraints/unit-tests/attachment-type-PASS.yaml
+++ b/src/validations/constraints/unit-tests/attachment-type-PASS.yaml
@@ -2,7 +2,7 @@
 test-case:
   name: The valid attachment type test.
   description: Test that the specified attachment type is valid.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
   - constraint-id: attachment-type
     result: pass
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/authentication-method-has-remarks-PASS.yaml b/src/validations/constraints/unit-tests/authentication-method-has-remarks-PASS.yaml
index 114dd8e658..ce1162c073 100644
--- a/src/validations/constraints/unit-tests/authentication-method-has-remarks-PASS.yaml
+++ b/src/validations/constraints/unit-tests/authentication-method-has-remarks-PASS.yaml
@@ -3,7 +3,7 @@ test-case:
   description: >-
     This test case validates the behavior of constraint
     authentication-method-has-remarks
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: authentication-method-has-remarks
       result: pass
diff --git a/src/validations/constraints/unit-tests/authorization-type-PASS.yaml b/src/validations/constraints/unit-tests/authorization-type-PASS.yaml
index 9c7eebc8e3..c7bb3f5eab 100644
--- a/src/validations/constraints/unit-tests/authorization-type-PASS.yaml
+++ b/src/validations/constraints/unit-tests/authorization-type-PASS.yaml
@@ -2,7 +2,7 @@
 test-case:
   name: Test Valid Authorization Type Use
   description: Test that the specified authorization type is valid.
-  content: ../content/ssp-all-VALID.xml # the content to run
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml # the content to run
   expectations: # check the constraint result
   - constraint-id: authorization-type
     result: pass
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/categorization-has-correct-system-attribute-PASS.yaml b/src/validations/constraints/unit-tests/categorization-has-correct-system-attribute-PASS.yaml
index c9325952d1..60ffb834ef 100644
--- a/src/validations/constraints/unit-tests/categorization-has-correct-system-attribute-PASS.yaml
+++ b/src/validations/constraints/unit-tests/categorization-has-correct-system-attribute-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for categorization-has-correct-system-attribute
   description: Test that a SSP system-characteristics categorization element has a system attribute equal to "https://doi.org/10.6028/NIST.SP.800-60v2r1".
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: categorization-has-correct-system-attribute
       result: pass
diff --git a/src/validations/constraints/unit-tests/categorization-has-information-type-id-PASS.yaml b/src/validations/constraints/unit-tests/categorization-has-information-type-id-PASS.yaml
index d68778870d..b4ad3b31af 100644
--- a/src/validations/constraints/unit-tests/categorization-has-information-type-id-PASS.yaml
+++ b/src/validations/constraints/unit-tests/categorization-has-information-type-id-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for categorization-has-information-type-id
   description: Test that a SSP system-characteristics categorization element has an information-type-id element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: categorization-has-information-type-id
       result: pass
diff --git a/src/validations/constraints/unit-tests/cia-impact-has-adjustment-justification-PASS.yaml b/src/validations/constraints/unit-tests/cia-impact-has-adjustment-justification-PASS.yaml
index 83c3824d67..076f85f895 100644
--- a/src/validations/constraints/unit-tests/cia-impact-has-adjustment-justification-PASS.yaml
+++ b/src/validations/constraints/unit-tests/cia-impact-has-adjustment-justification-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for cia-impact-has-adjustment-justification
   description: Test that if an SSP system-characteristics system-information information-type (confidentiality-impact/integrity-impact/availability-impact) base element is not equal to the selected element, then an adjustment-justification element exists. If the base element equals the selected element, then it returns true.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: cia-impact-has-adjustment-justification
       result: pass
diff --git a/src/validations/constraints/unit-tests/cia-impact-has-selected-PASS.yaml b/src/validations/constraints/unit-tests/cia-impact-has-selected-PASS.yaml
index abb421c611..1800141800 100644
--- a/src/validations/constraints/unit-tests/cia-impact-has-selected-PASS.yaml
+++ b/src/validations/constraints/unit-tests/cia-impact-has-selected-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for cia-impact-has-selected
   description: Test that an SSP system-characteristics system-information information-type (confidentiality-impact/integrity-impact/availability-impact) element has selected element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: cia-impact-has-selected
       result: pass
diff --git a/src/validations/constraints/unit-tests/cloud-service-model-PASS.yaml b/src/validations/constraints/unit-tests/cloud-service-model-PASS.yaml
index 48a1f5b69e..9b4c7a6161 100644
--- a/src/validations/constraints/unit-tests/cloud-service-model-PASS.yaml
+++ b/src/validations/constraints/unit-tests/cloud-service-model-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Test for cloud-service-model
   description: This test case validates the behavior of constraint cloud-service-model
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: cloud-service-model
       result: pass
diff --git a/src/validations/constraints/unit-tests/component-has-authentication-method-PASS.yaml b/src/validations/constraints/unit-tests/component-has-authentication-method-PASS.yaml
index 76f5b7ef6d..ddd6335267 100644
--- a/src/validations/constraints/unit-tests/component-has-authentication-method-PASS.yaml
+++ b/src/validations/constraints/unit-tests/component-has-authentication-method-PASS.yaml
@@ -3,7 +3,7 @@ test-case:
   description: >-
     This test case validates the behavior of constraint
     component-has-authentication-method
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: component-has-authentication-method
       result: pass
diff --git a/src/validations/constraints/unit-tests/component-has-non-provider-responsible-role-PASS.yaml b/src/validations/constraints/unit-tests/component-has-non-provider-responsible-role-PASS.yaml
index 1ef1f78c26..19dab09735 100644
--- a/src/validations/constraints/unit-tests/component-has-non-provider-responsible-role-PASS.yaml
+++ b/src/validations/constraints/unit-tests/component-has-non-provider-responsible-role-PASS.yaml
@@ -3,7 +3,7 @@ test-case:
   description: >-
     This test case validates the behavior of constraint
     component-has-non-provider-responsible-role
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: component-has-non-provider-responsible-role
       result: pass
diff --git a/src/validations/constraints/unit-tests/component-responsible-role-references-party-PASS.yaml b/src/validations/constraints/unit-tests/component-responsible-role-references-party-PASS.yaml
index 40990f9b83..010623e80e 100644
--- a/src/validations/constraints/unit-tests/component-responsible-role-references-party-PASS.yaml
+++ b/src/validations/constraints/unit-tests/component-responsible-role-references-party-PASS.yaml
@@ -3,7 +3,7 @@ test-case:
   description: >-
     This test case validates the behavior of constraint
     component-has-provider-responsible-role
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: component-has-provider-responsible-role
       result: pass
diff --git a/src/validations/constraints/unit-tests/component-type-PASS.yaml b/src/validations/constraints/unit-tests/component-type-PASS.yaml
index 7b461ec489..25d0f25250 100644
--- a/src/validations/constraints/unit-tests/component-type-PASS.yaml
+++ b/src/validations/constraints/unit-tests/component-type-PASS.yaml
@@ -2,7 +2,7 @@
 test-case:
   name: The valid component type test.
   description: Test that the specified component type is valid.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
   - constraint-id: component-type
     result: pass
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/control-implementation-status-PASS.yaml b/src/validations/constraints/unit-tests/control-implementation-status-PASS.yaml
index 7c02848aed..bba1c533e4 100644
--- a/src/validations/constraints/unit-tests/control-implementation-status-PASS.yaml
+++ b/src/validations/constraints/unit-tests/control-implementation-status-PASS.yaml
@@ -2,7 +2,7 @@
 test-case:
   name: The valid control implementation status test.
   description: Test that the specified control implementation status is valid.
-  content: ../content/ssp-all-VALID.xml
+  content: ../content/ssp-control-implementation-status-VALID.xml
   expectations:
   - constraint-id: control-implementation-status
     result: pass
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/data-center-alternate-PASS.yaml b/src/validations/constraints/unit-tests/data-center-alternate-PASS.yaml
index 1f2cb46ab0..5aae6a85a8 100644
--- a/src/validations/constraints/unit-tests/data-center-alternate-PASS.yaml
+++ b/src/validations/constraints/unit-tests/data-center-alternate-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for data-center-alternate
   description: This test case validates the behavior of constraint data-center-alternate
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: data-center-alternate
       result: pass
diff --git a/src/validations/constraints/unit-tests/data-center-count-PASS.yaml b/src/validations/constraints/unit-tests/data-center-count-PASS.yaml
index 1ecbcdcfe1..79ccc5fe9a 100644
--- a/src/validations/constraints/unit-tests/data-center-count-PASS.yaml
+++ b/src/validations/constraints/unit-tests/data-center-count-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for data-center-count
   description: This test case validates the behavior of constraint data-center-count
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: data-center-count
       result: pass
diff --git a/src/validations/constraints/unit-tests/data-center-country-code-PASS.yaml b/src/validations/constraints/unit-tests/data-center-country-code-PASS.yaml
index 446d658728..09784a9dbb 100644
--- a/src/validations/constraints/unit-tests/data-center-country-code-PASS.yaml
+++ b/src/validations/constraints/unit-tests/data-center-country-code-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for data-center-country-code
   description: This test case validates the behavior of constraint data-center-country-code
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: data-center-country-code
       result: pass
diff --git a/src/validations/constraints/unit-tests/data-center-primary-PASS.yaml b/src/validations/constraints/unit-tests/data-center-primary-PASS.yaml
index 2225fb9e7f..9704731d76 100644
--- a/src/validations/constraints/unit-tests/data-center-primary-PASS.yaml
+++ b/src/validations/constraints/unit-tests/data-center-primary-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for data-center-primary
   description: This test case validates the behavior of constraint data-center-primary
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: data-center-primary
       result: pass
diff --git a/src/validations/constraints/unit-tests/data-center-us-PASS.yaml b/src/validations/constraints/unit-tests/data-center-us-PASS.yaml
index ea5817d968..72492d9f8b 100644
--- a/src/validations/constraints/unit-tests/data-center-us-PASS.yaml
+++ b/src/validations/constraints/unit-tests/data-center-us-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for data-center-us
   description: This test case validates the behavior of constraint data-center-us
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: data-center-us
       result: pass
diff --git a/src/validations/constraints/unit-tests/deployment-model-PASS.yaml b/src/validations/constraints/unit-tests/deployment-model-PASS.yaml
index 276718b66f..d3bdcbf005 100644
--- a/src/validations/constraints/unit-tests/deployment-model-PASS.yaml
+++ b/src/validations/constraints/unit-tests/deployment-model-PASS.yaml
@@ -2,7 +2,7 @@
 test-case:
   name: Test Valid Deployment Model Use
   description: Test that the specified deployment model is valid.
-  content: ../content/ssp-all-VALID.xml # the content to run
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml # the content to run
   expectations: # check the constraint result
   - constraint-id: deployment-model
     result: pass
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/external-system-nature-of-agreement-PASS.yaml b/src/validations/constraints/unit-tests/external-system-nature-of-agreement-PASS.yaml
index 9d62c3fb9b..f8b46cdcc0 100644
--- a/src/validations/constraints/unit-tests/external-system-nature-of-agreement-PASS.yaml
+++ b/src/validations/constraints/unit-tests/external-system-nature-of-agreement-PASS.yaml
@@ -2,7 +2,7 @@
 test-case:
   name: The valid external-system-nature-of-agreement constraint unit test.
   description: Test that the FedRAMP SSP contains valid nature-of-agreement value for an external system.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
   - constraint-id: external-system-nature-of-agreement
     result: pass
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/fedramp-version-PASS.yaml b/src/validations/constraints/unit-tests/fedramp-version-PASS.yaml
index 1dda425dbf..7e84267a4f 100644
--- a/src/validations/constraints/unit-tests/fedramp-version-PASS.yaml
+++ b/src/validations/constraints/unit-tests/fedramp-version-PASS.yaml
@@ -2,7 +2,7 @@
 test-case:
   name: The valid fedramp-version constraint unit test.
   description: Test that the SSP metadata contains the "fedramp-version" property.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
   - constraint-id: fedramp-version
     result: pass
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/fully-operational-date-is-valid-PASS.yaml b/src/validations/constraints/unit-tests/fully-operational-date-is-valid-PASS.yaml
index 2068eff199..8e04b3d1b8 100644
--- a/src/validations/constraints/unit-tests/fully-operational-date-is-valid-PASS.yaml
+++ b/src/validations/constraints/unit-tests/fully-operational-date-is-valid-PASS.yaml
@@ -3,7 +3,7 @@ test-case:
   description: >-
     This test case validates the behavior of constraint
     fully-operational-date-is-valid
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: fully-operational-date-is-valid
       result: pass
diff --git a/src/validations/constraints/unit-tests/fully-operational-date-type-PASS.yaml b/src/validations/constraints/unit-tests/fully-operational-date-type-PASS.yaml
index 1d54c4ef42..00012cf606 100644
--- a/src/validations/constraints/unit-tests/fully-operational-date-type-PASS.yaml
+++ b/src/validations/constraints/unit-tests/fully-operational-date-type-PASS.yaml
@@ -3,7 +3,7 @@ test-case:
   description: >-
     This test case validates the behavior of constraint
     fully-operational-date-type
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: fully-operational-date-type
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-authenticator-assurance-level-PASS.yaml b/src/validations/constraints/unit-tests/has-authenticator-assurance-level-PASS.yaml
index 9fb20e9788..dca5904181 100644
--- a/src/validations/constraints/unit-tests/has-authenticator-assurance-level-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-authenticator-assurance-level-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-authenticator-assurance-level
   description: Test that a SSP system-characteristics element does not have a prop with a name equal to "authenticator-assurance-level".
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-authenticator-assurance-level
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-PASS.yaml b/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-PASS.yaml
index 5640c8da7a..712a0dc182 100644
--- a/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-authorization-boundary-diagram
   description: Test that a SSP system-characteristics element has an authorization-boundary diagram element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-authorization-boundary-diagram
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-caption-PASS.yaml b/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-caption-PASS.yaml
index 23a36c8cc8..8f03a1d555 100644
--- a/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-caption-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-caption-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-authorization-boundary-diagram-caption
   description: Test that a SSP authorization-boundary diagram element has a caption element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-authorization-boundary-diagram-caption
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-description-PASS.yaml b/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-description-PASS.yaml
index 77e2971b11..19bf500071 100644
--- a/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-description-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-description-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-authorization-boundary-diagram-description
   description: Test that a SSP authorization-boundary diagram element has a description element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-authorization-boundary-diagram-description
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-link-PASS.yaml b/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-link-PASS.yaml
index d6a7b7c3b0..82f5de5bd3 100644
--- a/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-link-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-link-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-authorization-boundary-diagram-link
   description: Test that a SSP authorization-boundary diagram element does not have a link element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-authorization-boundary-diagram-link
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-link-href-target-PASS.yaml b/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-link-href-target-PASS.yaml
index ae51624768..3886fdef4f 100644
--- a/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-link-href-target-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-link-href-target-PASS.yaml
@@ -5,7 +5,7 @@ test-case:
     Scenario 1: Tests an @href that references a resource in the back-matter.
     Scenario 2: Tests a link provided directly in the @href.
   content: 
-    - ../content/ssp-all-VALID.xml
+    - ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
     - ../content/ssp-has-authorization-boundary-diagram-link-href-target-VALID-1.xml
   expectations:
     - constraint-id: has-authorization-boundary-diagram-link-href-target
diff --git a/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-link-rel-PASS.yaml b/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-link-rel-PASS.yaml
index df5ff7d683..fb8e9e40e4 100644
--- a/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-link-rel-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-link-rel-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-authorization-boundary-diagram-link-rel
   description: Test that a SSP authorization-boundary diagram link element has a rel attribute.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-authorization-boundary-diagram-link-rel
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-link-rel-allowed-value-PASS.yaml b/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-link-rel-allowed-value-PASS.yaml
index b6b85fec57..339c26d9c6 100644
--- a/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-link-rel-allowed-value-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-authorization-boundary-diagram-link-rel-allowed-value-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-authorization-boundary-diagram-link-rel-allowed-value
   description: Test that a SSP authorization-boundary diagram link rel attribute equals "diagram".
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-authorization-boundary-diagram-link-rel-allowed-value
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-cloud-deployment-model-PASS.yaml b/src/validations/constraints/unit-tests/has-cloud-deployment-model-PASS.yaml
index e1cfaa644b..f817b494a6 100644
--- a/src/validations/constraints/unit-tests/has-cloud-deployment-model-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-cloud-deployment-model-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-cloud-deployment-model
   description: Test that an SSP system-characteristics element has a prop element with a name attribute equal to "cloud-deployment-model".
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-cloud-deployment-model
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-cloud-deployment-model-remarks-PASS.yaml b/src/validations/constraints/unit-tests/has-cloud-deployment-model-remarks-PASS.yaml
index afd3cd1752..31e6e8fa8f 100644
--- a/src/validations/constraints/unit-tests/has-cloud-deployment-model-remarks-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-cloud-deployment-model-remarks-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-cloud-deployment-model-remarks
   description: Test that every SSP system-characteristics prop element with a name attribute equal to "cloud-deployment-model" and a value attribute equal to "hybrid-cloud" has a remarks element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-cloud-deployment-model-remarks
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-cloud-service-model-PASS.yaml b/src/validations/constraints/unit-tests/has-cloud-service-model-PASS.yaml
index ea20d540f9..6a19e37934 100644
--- a/src/validations/constraints/unit-tests/has-cloud-service-model-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-cloud-service-model-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-cloud-service-model
   description: Test that an SSP system-characteristics element has a prop element with a name attribute equal to "cloud-service-model".
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-cloud-service-model
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-cloud-service-model-remarks-PASS.yaml b/src/validations/constraints/unit-tests/has-cloud-service-model-remarks-PASS.yaml
index 92d2776454..3d13b5b95c 100644
--- a/src/validations/constraints/unit-tests/has-cloud-service-model-remarks-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-cloud-service-model-remarks-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-cloud-service-model-remarks
   description: Test that every SSP system-characteristics prop element with a name attribute equal to "cloud-service-model" and a value attribute equal to "other" has a remarks element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-cloud-service-model-remarks
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-configuration-management-plan-PASS.yaml b/src/validations/constraints/unit-tests/has-configuration-management-plan-PASS.yaml
index 9452a2889e..fe8b409157 100644
--- a/src/validations/constraints/unit-tests/has-configuration-management-plan-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-configuration-management-plan-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-configuration-management-plan
   description: Test that a SSP back-matter resource element has a configuration-management-plan element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-configuration-management-plan
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-data-flow-PASS.yaml b/src/validations/constraints/unit-tests/has-data-flow-PASS.yaml
index b8af11e7a6..3e00a85afc 100644
--- a/src/validations/constraints/unit-tests/has-data-flow-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-data-flow-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-data-flow
   description: Test that a SSP system-characteristics element has a data-flow element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-data-flow
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-data-flow-description-PASS.yaml b/src/validations/constraints/unit-tests/has-data-flow-description-PASS.yaml
index 88cad44ea2..7faf1ed84a 100644
--- a/src/validations/constraints/unit-tests/has-data-flow-description-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-data-flow-description-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-data-flow-description
   description: Test that a SSP data-flow element does not have a description element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-data-flow-description
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-data-flow-diagram-PASS.yaml b/src/validations/constraints/unit-tests/has-data-flow-diagram-PASS.yaml
index f639cf067f..a342c05fdc 100644
--- a/src/validations/constraints/unit-tests/has-data-flow-diagram-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-data-flow-diagram-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-data-flow-diagram
   description: Test that a SSP data-flow element has a diagram element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-data-flow-diagram
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-data-flow-diagram-caption-PASS.yaml b/src/validations/constraints/unit-tests/has-data-flow-diagram-caption-PASS.yaml
index 1436c60944..fc4941f663 100644
--- a/src/validations/constraints/unit-tests/has-data-flow-diagram-caption-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-data-flow-diagram-caption-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-data-flow-diagram-caption
   description: Test that a SSP data-flow diagram element has a caption element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-data-flow-diagram-caption
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-data-flow-diagram-description-PASS.yaml b/src/validations/constraints/unit-tests/has-data-flow-diagram-description-PASS.yaml
index 71c0591fe1..f899fd54a7 100644
--- a/src/validations/constraints/unit-tests/has-data-flow-diagram-description-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-data-flow-diagram-description-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-data-flow-diagram-description
   description: Test that a SSP data-flow diagram element has a description element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-data-flow-diagram-description
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-data-flow-diagram-link-PASS.yaml b/src/validations/constraints/unit-tests/has-data-flow-diagram-link-PASS.yaml
index e9ba551c4d..bb492a810c 100644
--- a/src/validations/constraints/unit-tests/has-data-flow-diagram-link-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-data-flow-diagram-link-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-data-flow-diagram-link
   description: Test that a SSP data-flow diagram element has a link element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-data-flow-diagram-link
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-data-flow-diagram-link-href-target-PASS.yaml b/src/validations/constraints/unit-tests/has-data-flow-diagram-link-href-target-PASS.yaml
index 7e4f098abb..1a5a519812 100644
--- a/src/validations/constraints/unit-tests/has-data-flow-diagram-link-href-target-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-data-flow-diagram-link-href-target-PASS.yaml
@@ -5,7 +5,6 @@ test-case:
     Scenario 1: Tests an @href that references a resource in the back-matter.
     Scenario 2: Tests a link provided directly in the @href.
   content: 
-    - ../content/ssp-all-VALID.xml
     - ../content/ssp-has-data-flow-diagram-link-href-target-VALID-1.xml
   expectations:
     - constraint-id: has-data-flow-diagram-link-href-target
diff --git a/src/validations/constraints/unit-tests/has-data-flow-diagram-link-rel-PASS.yaml b/src/validations/constraints/unit-tests/has-data-flow-diagram-link-rel-PASS.yaml
index cf4f1bbd13..ebe34ffcfc 100644
--- a/src/validations/constraints/unit-tests/has-data-flow-diagram-link-rel-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-data-flow-diagram-link-rel-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-data-flow-diagram-link-rel
   description: Test that a SSP data-flow diagram link element has a rel attribute.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-data-flow-diagram-link-rel
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-data-flow-diagram-link-rel-allowed-value-PASS.yaml b/src/validations/constraints/unit-tests/has-data-flow-diagram-link-rel-allowed-value-PASS.yaml
index fee1e089bb..665ccf3618 100644
--- a/src/validations/constraints/unit-tests/has-data-flow-diagram-link-rel-allowed-value-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-data-flow-diagram-link-rel-allowed-value-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-data-flow-diagram-link-rel-allowed-value
   description: Test that a SSP data-flow diagram link rel attribute equals "diagram".
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-data-flow-diagram-link-rel-allowed-value
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-data-flow-diagram-uuid-PASS.yaml b/src/validations/constraints/unit-tests/has-data-flow-diagram-uuid-PASS.yaml
index fdf6e27917..286a1299c7 100644
--- a/src/validations/constraints/unit-tests/has-data-flow-diagram-uuid-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-data-flow-diagram-uuid-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-data-flow-diagram-uuid
   description: Test that a SSP data-flow diagram element has a uuid attribute.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-data-flow-diagram-uuid
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-federation-assurance-level-PASS.yaml b/src/validations/constraints/unit-tests/has-federation-assurance-level-PASS.yaml
index 3bdb7c83c5..d4c48dbbb8 100644
--- a/src/validations/constraints/unit-tests/has-federation-assurance-level-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-federation-assurance-level-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-federation-assurance-level
   description: Test that a SSP system-characteristics element has a prop with a name equal to "federation-assurance-level".
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-federation-assurance-level
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-fully-operational-date-PASS.yaml b/src/validations/constraints/unit-tests/has-fully-operational-date-PASS.yaml
index 68b342103d..bf628ff5cf 100644
--- a/src/validations/constraints/unit-tests/has-fully-operational-date-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-fully-operational-date-PASS.yaml
@@ -3,7 +3,7 @@ test-case:
   description: >-
     This test case validates the behavior of constraint
     has-fully-operational-date
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-fully-operational-date
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-identity-assurance-level-PASS.yaml b/src/validations/constraints/unit-tests/has-identity-assurance-level-PASS.yaml
index 81aafd66c7..f061c8339a 100644
--- a/src/validations/constraints/unit-tests/has-identity-assurance-level-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-identity-assurance-level-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-identity-assurance-level
   description: Test that a SSP system-characteristics element has a prop with a name equal to "identity-assurance-level".
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-identity-assurance-level
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-incident-response-plan-PASS.yaml b/src/validations/constraints/unit-tests/has-incident-response-plan-PASS.yaml
index 94f95701d0..afa1bf1ed1 100644
--- a/src/validations/constraints/unit-tests/has-incident-response-plan-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-incident-response-plan-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-incident-response-plan
   description: Test that a SSP back-matter resource element has an incident-response-plan element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-incident-response-plan
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-information-system-contingency-plan-PASS.yaml b/src/validations/constraints/unit-tests/has-information-system-contingency-plan-PASS.yaml
index 10543f9e65..bc0f40c4ee 100644
--- a/src/validations/constraints/unit-tests/has-information-system-contingency-plan-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-information-system-contingency-plan-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-information-system-contingency-plan
   description: Test that a SSP back-matter resource element has a information-system-contigency-plan element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-information-system-contingency-plan
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-inventory-items-PASS.yaml b/src/validations/constraints/unit-tests/has-inventory-items-PASS.yaml
index 5a9fca33df..1da1ac9b54 100644
--- a/src/validations/constraints/unit-tests/has-inventory-items-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-inventory-items-PASS.yaml
@@ -2,7 +2,7 @@
 test-case:
   name: The valid has-inventory-items constraint unit test.
   description: Test that the FedRAMP SSP contains the two or more inventory items.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
   - constraint-id: has-inventory-items
     result: pass
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/has-network-architecture-PASS.yaml b/src/validations/constraints/unit-tests/has-network-architecture-PASS.yaml
index a009379250..4f92b5b410 100644
--- a/src/validations/constraints/unit-tests/has-network-architecture-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-network-architecture-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-network-architecture
   description: Test that a SSP system-characteristics element has a network-architecture element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-network-architecture
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-network-architecture-diagram-PASS.yaml b/src/validations/constraints/unit-tests/has-network-architecture-diagram-PASS.yaml
index 22c0d8b3ab..31c1c73f31 100644
--- a/src/validations/constraints/unit-tests/has-network-architecture-diagram-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-network-architecture-diagram-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-network-architecture-diagram
   description: Test that a SSP network-architecture element has a diagram element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-network-architecture-diagram
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-network-architecture-diagram-caption-PASS.yaml b/src/validations/constraints/unit-tests/has-network-architecture-diagram-caption-PASS.yaml
index bfb9eda66b..2e73f0c5bb 100644
--- a/src/validations/constraints/unit-tests/has-network-architecture-diagram-caption-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-network-architecture-diagram-caption-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-network-architecture-diagram-caption
   description: Test that a SSP network-architecture diagram element has a caption element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-network-architecture-diagram-caption
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-network-architecture-diagram-description-PASS.yaml b/src/validations/constraints/unit-tests/has-network-architecture-diagram-description-PASS.yaml
index b2f95fe03a..c7b9e09cfc 100644
--- a/src/validations/constraints/unit-tests/has-network-architecture-diagram-description-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-network-architecture-diagram-description-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-network-architecture-diagram-description
   description: Test that a SSP network-architecture diagram element has a description element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-network-architecture-diagram-description
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-network-architecture-diagram-link-PASS.yaml b/src/validations/constraints/unit-tests/has-network-architecture-diagram-link-PASS.yaml
index 372a845509..a83f36cbf5 100644
--- a/src/validations/constraints/unit-tests/has-network-architecture-diagram-link-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-network-architecture-diagram-link-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-network-architecture-diagram-link
   description: Test that a SSP network-architecture diagram element has a link element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-network-architecture-diagram-link
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-network-architecture-diagram-link-href-target-PASS.yaml b/src/validations/constraints/unit-tests/has-network-architecture-diagram-link-href-target-PASS.yaml
index 0de200640b..99aa038b48 100644
--- a/src/validations/constraints/unit-tests/has-network-architecture-diagram-link-href-target-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-network-architecture-diagram-link-href-target-PASS.yaml
@@ -5,7 +5,7 @@ test-case:
     Scenario 1: Tests an @href that references a resource in the back-matter.
     Scenario 2: Tests a link provided directly in the @href.
   content: 
-    - ../content/ssp-all-VALID.xml
+    - ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
     - ../content/ssp-has-network-architecture-diagram-link-href-target-VALID-1.xml
   expectations:
     - constraint-id: has-network-architecture-diagram-link-href-target
diff --git a/src/validations/constraints/unit-tests/has-network-architecture-diagram-link-rel-PASS.yaml b/src/validations/constraints/unit-tests/has-network-architecture-diagram-link-rel-PASS.yaml
index 0adea017a1..64da9b4fe6 100644
--- a/src/validations/constraints/unit-tests/has-network-architecture-diagram-link-rel-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-network-architecture-diagram-link-rel-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-network-architecture-diagram-link-rel
   description: Test that a SSP network-architecture diagram link element has a rel attribute.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-network-architecture-diagram-link-rel
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-network-architecture-diagram-link-rel-allowed-value-PASS.yaml b/src/validations/constraints/unit-tests/has-network-architecture-diagram-link-rel-allowed-value-PASS.yaml
index bb56632526..7631738332 100644
--- a/src/validations/constraints/unit-tests/has-network-architecture-diagram-link-rel-allowed-value-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-network-architecture-diagram-link-rel-allowed-value-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-network-architecture-diagram-link-rel-allowed-value
   description: Test that a SSP network-architecture diagram link rel attribute equals "diagram".
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-network-architecture-diagram-link-rel-allowed-value
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-published-date-PASS.yaml b/src/validations/constraints/unit-tests/has-published-date-PASS.yaml
index 195e7a553b..1dfb77e117 100644
--- a/src/validations/constraints/unit-tests/has-published-date-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-published-date-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-published-date
   description: This test case validates the behavior of constraint has-published-date
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-published-date
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-rules-of-behavior-PASS.yaml b/src/validations/constraints/unit-tests/has-rules-of-behavior-PASS.yaml
index 58f431e4cd..6a99da4cf0 100644
--- a/src/validations/constraints/unit-tests/has-rules-of-behavior-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-rules-of-behavior-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-rules-of-behavior
   description: Test that a SSP back-matter resource element has a rules-of-behavior element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-rules-of-behavior
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-security-impact-level-PASS.yaml b/src/validations/constraints/unit-tests/has-security-impact-level-PASS.yaml
index b3405cea39..0d34d0f581 100644
--- a/src/validations/constraints/unit-tests/has-security-impact-level-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-security-impact-level-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-security-impact-level
   description: Test that an SSP system-characteristics element has a security-impact-level element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-security-impact-level
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-security-sensitivity-level-PASS.yaml b/src/validations/constraints/unit-tests/has-security-sensitivity-level-PASS.yaml
index e6bd7f3e8e..316e91375c 100644
--- a/src/validations/constraints/unit-tests/has-security-sensitivity-level-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-security-sensitivity-level-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-security-sensitivity-level
   description: Test that an SSP system-characteristics element has a security-sensitivity-level element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-security-sensitivity-level
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-separation-of-duties-matrix-PASS.yaml b/src/validations/constraints/unit-tests/has-separation-of-duties-matrix-PASS.yaml
index 70d0b0ce2d..58149ee55c 100644
--- a/src/validations/constraints/unit-tests/has-separation-of-duties-matrix-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-separation-of-duties-matrix-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-separation-of-duties-matrix
   description: Test that a SSP back-matter resource element has a separation-of-duties-matrix element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-separation-of-duties-matrix
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-system-id-PASS.yaml b/src/validations/constraints/unit-tests/has-system-id-PASS.yaml
index 2372e593ed..b48c2aa058 100644
--- a/src/validations/constraints/unit-tests/has-system-id-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-system-id-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-system-id
   description: Test that a SSP system-characteristics system-id identifier-type attribute is equal to 'https://fedramp.gov'.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-system-id
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-system-name-short-PASS.yaml b/src/validations/constraints/unit-tests/has-system-name-short-PASS.yaml
index ff1baa729c..72416f3fd9 100644
--- a/src/validations/constraints/unit-tests/has-system-name-short-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-system-name-short-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-system-name-short
   description: Test that an SSP system-characteristics element has a system-name-short element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-system-name-short
       result: pass
diff --git a/src/validations/constraints/unit-tests/has-user-guide-PASS.yaml b/src/validations/constraints/unit-tests/has-user-guide-PASS.yaml
index 7ceb2c6588..862a942d30 100644
--- a/src/validations/constraints/unit-tests/has-user-guide-PASS.yaml
+++ b/src/validations/constraints/unit-tests/has-user-guide-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for has-user-guide
   description: Test that a SSP back-matter resource element has a user-guide element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: has-user-guide
       result: pass
diff --git a/src/validations/constraints/unit-tests/import-profile-has-available-document-PASS.yaml b/src/validations/constraints/unit-tests/import-profile-has-available-document-PASS.yaml
index 2f4b37c80e..37ec104b79 100644
--- a/src/validations/constraints/unit-tests/import-profile-has-available-document-PASS.yaml
+++ b/src/validations/constraints/unit-tests/import-profile-has-available-document-PASS.yaml
@@ -7,7 +7,7 @@ test-case:
     Scenario 3 tests: a fragment that points to a resolved profile catalog in the back-matter.
     Scenario 4 tests: a fragment that points to a profile in the back-matter.
   content: 
-    - ../content/ssp-all-VALID.xml
+    - ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
     - ../content/ssp-import-profile-resolves-to-fedramp-content-VALID-1.xml
     - ../content/ssp-import-profile-resolves-to-fedramp-content-VALID-2.xml
     - ../content/ssp-import-profile-resolves-to-fedramp-content-VALID-3.xml
diff --git a/src/validations/constraints/unit-tests/import-profile-resolves-to-fedramp-content-PASS.yaml b/src/validations/constraints/unit-tests/import-profile-resolves-to-fedramp-content-PASS.yaml
index 53e5800321..b211b10198 100644
--- a/src/validations/constraints/unit-tests/import-profile-resolves-to-fedramp-content-PASS.yaml
+++ b/src/validations/constraints/unit-tests/import-profile-resolves-to-fedramp-content-PASS.yaml
@@ -7,7 +7,7 @@ test-case:
     Scenario 3 tests: a fragment that points to a resolved profile catalog in the back-matter.
     Scenario 4 tests: a fragment that points to a profile in the back-matter.
   content: 
-    - ../content/ssp-all-VALID.xml
+    - ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
     - ../content/ssp-import-profile-resolves-to-fedramp-content-VALID-1.xml
     - ../content/ssp-import-profile-resolves-to-fedramp-content-VALID-2.xml
     - ../content/ssp-import-profile-resolves-to-fedramp-content-VALID-3.xml
diff --git a/src/validations/constraints/unit-tests/information-type-has-availability-impact-PASS.yaml b/src/validations/constraints/unit-tests/information-type-has-availability-impact-PASS.yaml
index 4dc13de603..5c8c9674b4 100644
--- a/src/validations/constraints/unit-tests/information-type-has-availability-impact-PASS.yaml
+++ b/src/validations/constraints/unit-tests/information-type-has-availability-impact-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for information-type-has-availability-impact
   description: Test that an SSP system-characteristics system-information information-type element has an availability-impact element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: information-type-has-availability-impact
       result: pass
diff --git a/src/validations/constraints/unit-tests/information-type-has-confidentiality-impact-PASS.yaml b/src/validations/constraints/unit-tests/information-type-has-confidentiality-impact-PASS.yaml
index bb8c016821..9c5b360bc2 100644
--- a/src/validations/constraints/unit-tests/information-type-has-confidentiality-impact-PASS.yaml
+++ b/src/validations/constraints/unit-tests/information-type-has-confidentiality-impact-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for information-type-has-confidentiality-impact
   description: Test that an SSP system-characteristics system-information information-type element has a confidentiality-impact element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: information-type-has-confidentiality-impact
       result: pass
diff --git a/src/validations/constraints/unit-tests/information-type-has-integrity-impact-PASS.yaml b/src/validations/constraints/unit-tests/information-type-has-integrity-impact-PASS.yaml
index 0700052f67..8a159528e3 100644
--- a/src/validations/constraints/unit-tests/information-type-has-integrity-impact-PASS.yaml
+++ b/src/validations/constraints/unit-tests/information-type-has-integrity-impact-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for information-type-has-integrity-impact
   description: Test that an SSP system-characteristics system-information information-type element has an integrity-impact element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: information-type-has-integrity-impact
       result: pass
diff --git a/src/validations/constraints/unit-tests/information-type-id-PASS.yaml b/src/validations/constraints/unit-tests/information-type-id-PASS.yaml
index f42f282026..f0157d8fac 100644
--- a/src/validations/constraints/unit-tests/information-type-id-PASS.yaml
+++ b/src/validations/constraints/unit-tests/information-type-id-PASS.yaml
@@ -2,7 +2,7 @@
 test-case:
   name: The valid information-type-800-60-v2r1 constraint unit test.
   description: Test that the SSP "information-type-id" element contains a valid value.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
   - constraint-id: information-type-800-60-v2r1
     result: pass
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/information-type-system-PASS.yaml b/src/validations/constraints/unit-tests/information-type-system-PASS.yaml
index 532e9b0786..b14a4282d2 100644
--- a/src/validations/constraints/unit-tests/information-type-system-PASS.yaml
+++ b/src/validations/constraints/unit-tests/information-type-system-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Test for information-type-system
   description: This test case validates the behavior of constraint information-type-system
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: information-type-system
       result: pass
diff --git a/src/validations/constraints/unit-tests/interconnection-direction-PASS.yaml b/src/validations/constraints/unit-tests/interconnection-direction-PASS.yaml
index 387e91d805..2f3daf2321 100644
--- a/src/validations/constraints/unit-tests/interconnection-direction-PASS.yaml
+++ b/src/validations/constraints/unit-tests/interconnection-direction-PASS.yaml
@@ -2,7 +2,7 @@
 test-case:
   name: The valid interconnection direction test.
   description: Test that the specified interconnection direction is valid.
-  content: ../content/ssp-all-VALID.xml
+  content: ../content/ssp-interconnection-direction-VALID.xml
   expectations:
   - constraint-id: interconnection-direction
     result: pass
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/interconnection-security-PASS.yaml b/src/validations/constraints/unit-tests/interconnection-security-PASS.yaml
index 92350cee1a..9797649891 100644
--- a/src/validations/constraints/unit-tests/interconnection-security-PASS.yaml
+++ b/src/validations/constraints/unit-tests/interconnection-security-PASS.yaml
@@ -2,7 +2,7 @@
 test-case:
   name: The valid interconnection security test.
   description: Test that the specified interconnection security is valid.
-  content: ../content/ssp-all-VALID.xml
+  content: ../content/ssp-interconnection-security-VALID.xml
   expectations:
   - constraint-id: interconnection-security
     result: pass
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/inventory-item-allows-authenticated-scan-PASS.yaml b/src/validations/constraints/unit-tests/inventory-item-allows-authenticated-scan-PASS.yaml
index 3cd58b4143..d5041987d1 100644
--- a/src/validations/constraints/unit-tests/inventory-item-allows-authenticated-scan-PASS.yaml
+++ b/src/validations/constraints/unit-tests/inventory-item-allows-authenticated-scan-PASS.yaml
@@ -2,7 +2,7 @@
 test-case:
   name: The valid authenticated scan test.
   description: Test that the specified authenticated scan is valid.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
   - constraint-id: inventory-item-allows-authenticated-scan
     result: pass
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/inventory-item-public-PASS.yaml b/src/validations/constraints/unit-tests/inventory-item-public-PASS.yaml
index d375d4217b..7562b0acba 100644
--- a/src/validations/constraints/unit-tests/inventory-item-public-PASS.yaml
+++ b/src/validations/constraints/unit-tests/inventory-item-public-PASS.yaml
@@ -2,7 +2,7 @@
 test-case:
   name: The valid public asset test.
   description: Test that the specified public asset is valid.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
   - constraint-id: inventory-item-public
     result: pass
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/inventory-item-virtual-PASS.yaml b/src/validations/constraints/unit-tests/inventory-item-virtual-PASS.yaml
index 21e582b2ee..ca29ef218d 100644
--- a/src/validations/constraints/unit-tests/inventory-item-virtual-PASS.yaml
+++ b/src/validations/constraints/unit-tests/inventory-item-virtual-PASS.yaml
@@ -2,7 +2,7 @@
 test-case:
   name: The valid virtual asset test.
   description: Test that the specified virtual asset is valid.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
   - constraint-id: inventory-item-virtual
     result: pass
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/leveraged-authorization-has-authorization-type-PASS.yaml b/src/validations/constraints/unit-tests/leveraged-authorization-has-authorization-type-PASS.yaml
index fb4222996e..1a9d48b1db 100644
--- a/src/validations/constraints/unit-tests/leveraged-authorization-has-authorization-type-PASS.yaml
+++ b/src/validations/constraints/unit-tests/leveraged-authorization-has-authorization-type-PASS.yaml
@@ -3,7 +3,7 @@ test-case:
   description: >-
     This test case validates the behavior of constraint
     leveraged-authorization-has-authorization-type
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: leveraged-authorization-has-authorization-type
       result: pass
diff --git a/src/validations/constraints/unit-tests/leveraged-authorization-has-impact-level-PASS.yaml b/src/validations/constraints/unit-tests/leveraged-authorization-has-impact-level-PASS.yaml
index f6bd88ccc6..b8fe809654 100644
--- a/src/validations/constraints/unit-tests/leveraged-authorization-has-impact-level-PASS.yaml
+++ b/src/validations/constraints/unit-tests/leveraged-authorization-has-impact-level-PASS.yaml
@@ -3,7 +3,7 @@ test-case:
   description: >-
     This test case validates the behavior of constraint
     leveraged-authorization-has-impact-level
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: leveraged-authorization-has-impact-level
       result: pass
diff --git a/src/validations/constraints/unit-tests/leveraged-authorization-has-system-identifier-PASS.yaml b/src/validations/constraints/unit-tests/leveraged-authorization-has-system-identifier-PASS.yaml
index 5869928738..b45d4175ea 100644
--- a/src/validations/constraints/unit-tests/leveraged-authorization-has-system-identifier-PASS.yaml
+++ b/src/validations/constraints/unit-tests/leveraged-authorization-has-system-identifier-PASS.yaml
@@ -3,7 +3,7 @@ test-case:
   description: >-
     This test case validates the behavior of constraint
     leveraged-authorization-has-system-identifier
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: leveraged-authorization-has-system-identifier
       result: pass
diff --git a/src/validations/constraints/unit-tests/leveraged-authorization-has-valid-impact-level-PASS.yaml b/src/validations/constraints/unit-tests/leveraged-authorization-has-valid-impact-level-PASS.yaml
index 4bedfcc9ac..5e2aa1b4a2 100644
--- a/src/validations/constraints/unit-tests/leveraged-authorization-has-valid-impact-level-PASS.yaml
+++ b/src/validations/constraints/unit-tests/leveraged-authorization-has-valid-impact-level-PASS.yaml
@@ -5,7 +5,7 @@ test-case:
     Scenario 1: Security-sensitivity-level = 'fips-199-moderate' and leveraged-authorization impact-level = 'fips-199-moderate'.
     Scenario 2: Security-sensitivity-level = 'fips-199-moderate' and leveraged-authorization impact-level = 'fips-199-high'.
   content: 
-    - ../content/ssp-all-VALID.xml
+    - ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
     - ../content/ssp-leveraged-authorization-has-valid-impact-level-VALID.xml
   expectations:
     - constraint-id: leveraged-authorization-has-valid-impact-level
diff --git a/src/validations/constraints/unit-tests/leveraged-authorization-nature-of-agreement-PASS.yaml b/src/validations/constraints/unit-tests/leveraged-authorization-nature-of-agreement-PASS.yaml
index ff1e4dbc74..42d6b2282d 100644
--- a/src/validations/constraints/unit-tests/leveraged-authorization-nature-of-agreement-PASS.yaml
+++ b/src/validations/constraints/unit-tests/leveraged-authorization-nature-of-agreement-PASS.yaml
@@ -2,7 +2,7 @@
 test-case:
   name: The valid leveraged-authorization-nature-of-agreement constraint unit test.
   description: Test that the FedRAMP SSP contains valid nature-of-agreement value for an external leveraged system.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
   - constraint-id: leveraged-authorization-nature-of-agreement
     result: pass
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/marking-PASS.yaml b/src/validations/constraints/unit-tests/marking-PASS.yaml
index 1cc26c447c..1e596211f1 100644
--- a/src/validations/constraints/unit-tests/marking-PASS.yaml
+++ b/src/validations/constraints/unit-tests/marking-PASS.yaml
@@ -2,7 +2,7 @@
 test-case:
   name: The valid marking constraint unit test.
   description: Test that the SSP metadata contains the "marking" property.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
   - constraint-id: marking
     result: pass
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/network-component-has-connection-security-prop-PASS.yaml b/src/validations/constraints/unit-tests/network-component-has-connection-security-prop-PASS.yaml
index b9987997dc..0032e1a12e 100644
--- a/src/validations/constraints/unit-tests/network-component-has-connection-security-prop-PASS.yaml
+++ b/src/validations/constraints/unit-tests/network-component-has-connection-security-prop-PASS.yaml
@@ -3,7 +3,7 @@ test-case:
   description: >-
     This test case validates the behavior of constraint
     network-component-has-connection-security-prop
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: network-component-has-connection-security-prop
       result: pass
diff --git a/src/validations/constraints/unit-tests/network-component-has-implementation-point-PASS.yaml b/src/validations/constraints/unit-tests/network-component-has-implementation-point-PASS.yaml
index 414bd38cf1..68be74c584 100644
--- a/src/validations/constraints/unit-tests/network-component-has-implementation-point-PASS.yaml
+++ b/src/validations/constraints/unit-tests/network-component-has-implementation-point-PASS.yaml
@@ -3,7 +3,7 @@ test-case:
   description: >-
     This test case validates the behavior of constraint
     network-component-has-implementation-point
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: network-component-has-implementation-point
       result: pass
diff --git a/src/validations/constraints/unit-tests/non-provider-responsible-role-references-user-PASS.yaml b/src/validations/constraints/unit-tests/non-provider-responsible-role-references-user-PASS.yaml
index 688c8b4d50..f50c3e9916 100644
--- a/src/validations/constraints/unit-tests/non-provider-responsible-role-references-user-PASS.yaml
+++ b/src/validations/constraints/unit-tests/non-provider-responsible-role-references-user-PASS.yaml
@@ -3,7 +3,7 @@ test-case:
   description: >-
     This test case validates the behavior of constraint
     non-provider-responsible-role-references-user
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: non-provider-responsible-role-references-user
       result: pass
diff --git a/src/validations/constraints/unit-tests/party-has-name-PASS.yaml b/src/validations/constraints/unit-tests/party-has-name-PASS.yaml
index e53b9d99eb..95b428f768 100644
--- a/src/validations/constraints/unit-tests/party-has-name-PASS.yaml
+++ b/src/validations/constraints/unit-tests/party-has-name-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for party-has-name
   description: This test case validates the behavior of constraint party-has-name
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: party-has-name
       result: pass
diff --git a/src/validations/constraints/unit-tests/privilege-level-PASS.yaml b/src/validations/constraints/unit-tests/privilege-level-PASS.yaml
index 7bb83b303c..0d97c01b78 100644
--- a/src/validations/constraints/unit-tests/privilege-level-PASS.yaml
+++ b/src/validations/constraints/unit-tests/privilege-level-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for privilege-level
   description: This test case validates the behavior of constraint privilege-level
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: privilege-level
       result: pass
diff --git a/src/validations/constraints/unit-tests/resource-has-base64-or-rlink-PASS.yaml b/src/validations/constraints/unit-tests/resource-has-base64-or-rlink-PASS.yaml
index c2e38a13c5..77d2e214c3 100644
--- a/src/validations/constraints/unit-tests/resource-has-base64-or-rlink-PASS.yaml
+++ b/src/validations/constraints/unit-tests/resource-has-base64-or-rlink-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for resource-has-base64-or-rlink
   description: Test that a SSP back-matter resource element has a base64 or rlink element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: resource-has-base64-or-rlink
       result: pass
diff --git a/src/validations/constraints/unit-tests/resource-has-title-PASS.yaml b/src/validations/constraints/unit-tests/resource-has-title-PASS.yaml
index 5b3a0f0ad3..3d63ed3c73 100644
--- a/src/validations/constraints/unit-tests/resource-has-title-PASS.yaml
+++ b/src/validations/constraints/unit-tests/resource-has-title-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for resource-has-title
   description: Test that a SSP back-matter resource element has a title element.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: resource-has-title
       result: pass
diff --git a/src/validations/constraints/unit-tests/responsible-party-is-person-PASS.yaml b/src/validations/constraints/unit-tests/responsible-party-is-person-PASS.yaml
index 3ec84a2364..7096023f5d 100644
--- a/src/validations/constraints/unit-tests/responsible-party-is-person-PASS.yaml
+++ b/src/validations/constraints/unit-tests/responsible-party-is-person-PASS.yaml
@@ -2,7 +2,7 @@
 test-case:
   name: Positive Test for responsible-party-is-person
   description: This test case validates the behavior of constraint responsible-party-is-person
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: responsible-party-is-person
       result: pass
diff --git a/src/validations/constraints/unit-tests/responsible-party-prepared-by-PASS.yaml b/src/validations/constraints/unit-tests/responsible-party-prepared-by-PASS.yaml
index 3f55f72476..0b1b6b0398 100644
--- a/src/validations/constraints/unit-tests/responsible-party-prepared-by-PASS.yaml
+++ b/src/validations/constraints/unit-tests/responsible-party-prepared-by-PASS.yaml
@@ -3,7 +3,7 @@ test-case:
   description: >-
     This test case validates the behavior of constraint
     responsible-party-prepared-by
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: responsible-party-prepared-by
       result: pass
diff --git a/src/validations/constraints/unit-tests/responsible-party-prepared-by-location-valid-PASS.yaml b/src/validations/constraints/unit-tests/responsible-party-prepared-by-location-valid-PASS.yaml
index f0f790e024..b0ed19cb18 100644
--- a/src/validations/constraints/unit-tests/responsible-party-prepared-by-location-valid-PASS.yaml
+++ b/src/validations/constraints/unit-tests/responsible-party-prepared-by-location-valid-PASS.yaml
@@ -5,7 +5,7 @@ test-case:
     Scenario 1: Tests when a party references a location assembly.
     Scenario 2: Tests when a party has an address assembly embedded.
   content: 
-    - ../content/ssp-all-VALID.xml
+    - ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
     - ../content/ssp-responsible-party-prepared-by-location-valid-VALID-1.xml
   expectations:
     - constraint-id: responsible-party-prepared-by-location-valid
diff --git a/src/validations/constraints/unit-tests/responsible-party-prepared-for-PASS.yaml b/src/validations/constraints/unit-tests/responsible-party-prepared-for-PASS.yaml
index ab3e51306c..95d7ebdb4e 100644
--- a/src/validations/constraints/unit-tests/responsible-party-prepared-for-PASS.yaml
+++ b/src/validations/constraints/unit-tests/responsible-party-prepared-for-PASS.yaml
@@ -3,7 +3,7 @@ test-case:
   description: >-
     This test case validates the behavior of constraint
     responsible-party-prepared-for
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: responsible-party-prepared-for
       result: pass
diff --git a/src/validations/constraints/unit-tests/responsible-party-prepared-for-location-valid-PASS.yaml b/src/validations/constraints/unit-tests/responsible-party-prepared-for-location-valid-PASS.yaml
index 85f418bc82..fda51575f6 100644
--- a/src/validations/constraints/unit-tests/responsible-party-prepared-for-location-valid-PASS.yaml
+++ b/src/validations/constraints/unit-tests/responsible-party-prepared-for-location-valid-PASS.yaml
@@ -5,7 +5,7 @@ test-case:
     Scenario 1: Tests when a party references a location assembly.
     Scenario 2: Tests when a party has an address assembly embedded.
   content: 
-    - ../content/ssp-all-VALID.xml
+    - ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
     - ../content/ssp-responsible-party-prepared-for-location-valid-VALID-1.xml
   expectations:
     - constraint-id: responsible-party-prepared-for-location-valid
diff --git a/src/validations/constraints/unit-tests/role-defined-authorizing-official-poc-PASS.yaml b/src/validations/constraints/unit-tests/role-defined-authorizing-official-poc-PASS.yaml
index bf0446b566..68758640fb 100644
--- a/src/validations/constraints/unit-tests/role-defined-authorizing-official-poc-PASS.yaml
+++ b/src/validations/constraints/unit-tests/role-defined-authorizing-official-poc-PASS.yaml
@@ -2,7 +2,7 @@
 test-case:
   name: The valid role-defined-authorizing-official-poc constraint unit test.
   description: Test that SSP metadata contains the authorizing-official-poc role.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
   - constraint-id: role-defined-authorizing-official-poc
     result: pass
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/role-defined-information-system-security-officer-PASS.yaml b/src/validations/constraints/unit-tests/role-defined-information-system-security-officer-PASS.yaml
index e6400df0a3..5442247c4e 100644
--- a/src/validations/constraints/unit-tests/role-defined-information-system-security-officer-PASS.yaml
+++ b/src/validations/constraints/unit-tests/role-defined-information-system-security-officer-PASS.yaml
@@ -2,7 +2,7 @@
 test-case:
   name: The valid role-defined-information-system-security-officer constraint unit test.
   description: Test that SSP metadata contains the information-system-security-officer role.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
   - constraint-id: role-defined-information-system-security-officer
     result: pass
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/role-defined-prepared-by-PASS.yaml b/src/validations/constraints/unit-tests/role-defined-prepared-by-PASS.yaml
index 20380bce1c..252f5ec49b 100644
--- a/src/validations/constraints/unit-tests/role-defined-prepared-by-PASS.yaml
+++ b/src/validations/constraints/unit-tests/role-defined-prepared-by-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for role-defined-prepared-by
   description: This test case validates the behavior of constraint role-defined-prepared-by
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: role-defined-prepared-by
       result: pass
diff --git a/src/validations/constraints/unit-tests/role-defined-prepared-for-PASS.yaml b/src/validations/constraints/unit-tests/role-defined-prepared-for-PASS.yaml
index af62f26708..5dd6a28e84 100644
--- a/src/validations/constraints/unit-tests/role-defined-prepared-for-PASS.yaml
+++ b/src/validations/constraints/unit-tests/role-defined-prepared-for-PASS.yaml
@@ -3,7 +3,7 @@ test-case:
   description: >-
     This test case validates the behavior of constraint
     role-defined-prepared-for
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: role-defined-prepared-for
       result: pass
diff --git a/src/validations/constraints/unit-tests/role-defined-system-owner-PASS.yaml b/src/validations/constraints/unit-tests/role-defined-system-owner-PASS.yaml
index c93d0ee640..7a53c82b33 100644
--- a/src/validations/constraints/unit-tests/role-defined-system-owner-PASS.yaml
+++ b/src/validations/constraints/unit-tests/role-defined-system-owner-PASS.yaml
@@ -2,7 +2,7 @@
 test-case:
   name: The valid role-defined-system-owner constraint unit test.
   description: Test that SSP metadata contains the system-owner role.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
   - constraint-id: role-defined-system-owner
     result: pass
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/saas-has-leveraged-authorization-PASS.yaml b/src/validations/constraints/unit-tests/saas-has-leveraged-authorization-PASS.yaml
index 4085f0b3bd..14d8c46f14 100644
--- a/src/validations/constraints/unit-tests/saas-has-leveraged-authorization-PASS.yaml
+++ b/src/validations/constraints/unit-tests/saas-has-leveraged-authorization-PASS.yaml
@@ -5,7 +5,7 @@ test-case:
     Scenario 1: SSP does not have a saas cloud service model.
     Scenario 2: SSP has a saas cloud service model.
   content: 
-    - ../content/ssp-all-VALID.xml
+    - ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
     - ../content/ssp-saas-has-leveraged-authorization-VALID.xml
   expectations:
     - constraint-id: saas-has-leveraged-authorization
diff --git a/src/validations/constraints/unit-tests/scan-type-PASS.yaml b/src/validations/constraints/unit-tests/scan-type-PASS.yaml
index 3f456511c1..deb5e61e45 100644
--- a/src/validations/constraints/unit-tests/scan-type-PASS.yaml
+++ b/src/validations/constraints/unit-tests/scan-type-PASS.yaml
@@ -2,7 +2,7 @@
 test-case:
   name: The valid scan type test.
   description: Test that the specified scan type is valid.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
   - constraint-id: scan-type
     result: pass
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/security-level-PASS.yaml b/src/validations/constraints/unit-tests/security-level-PASS.yaml
index 882bcb61a9..df9245cc99 100644
--- a/src/validations/constraints/unit-tests/security-level-PASS.yaml
+++ b/src/validations/constraints/unit-tests/security-level-PASS.yaml
@@ -2,7 +2,7 @@
 test-case:
   name: Test Valid Security Level Use
   description: Test that the specified security level is valid.
-  content: ../content/ssp-all-VALID.xml # the content to run
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml # the content to run
   expectations: # check the constraint result
   - constraint-id: security-level
     result: pass
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/security-sensitivity-level-matches-security-impact-level-PASS.yaml b/src/validations/constraints/unit-tests/security-sensitivity-level-matches-security-impact-level-PASS.yaml
index 691abee1dc..e65133a3fe 100644
--- a/src/validations/constraints/unit-tests/security-sensitivity-level-matches-security-impact-level-PASS.yaml
+++ b/src/validations/constraints/unit-tests/security-sensitivity-level-matches-security-impact-level-PASS.yaml
@@ -2,7 +2,7 @@
 test-case:
   name: The valid security-sensitivity-level-matches-security-impact-level constraint unit test.
   description: Test that the SSP "security-sensitivity-level" element value matches "security-impact-level" values.
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
   - constraint-id: security-sensitivity-level-matches-security-impact-level
     result: pass
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/unique-inventory-item-asset-id-PASS.yaml b/src/validations/constraints/unit-tests/unique-inventory-item-asset-id-PASS.yaml
index 25ce4c0228..7339d64e50 100644
--- a/src/validations/constraints/unit-tests/unique-inventory-item-asset-id-PASS.yaml
+++ b/src/validations/constraints/unit-tests/unique-inventory-item-asset-id-PASS.yaml
@@ -3,7 +3,7 @@ test-case:
   description: >-
     This test case validates the behavior of constraint
     unique-inventory-item-asset-id
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: unique-inventory-item-asset-id
       result: pass
diff --git a/src/validations/constraints/unit-tests/user-authentication-PASS.yaml b/src/validations/constraints/unit-tests/user-authentication-PASS.yaml
index 84eb3a1baf..253f7460ac 100644
--- a/src/validations/constraints/unit-tests/user-authentication-PASS.yaml
+++ b/src/validations/constraints/unit-tests/user-authentication-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for user-authentication
   description: This test case validates the behavior of constraint user-authentication
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: user-authentication
       result: pass
diff --git a/src/validations/constraints/unit-tests/user-has-authorized-privilege-PASS.yaml b/src/validations/constraints/unit-tests/user-has-authorized-privilege-PASS.yaml
index 3964c8422c..8d8ae24709 100644
--- a/src/validations/constraints/unit-tests/user-has-authorized-privilege-PASS.yaml
+++ b/src/validations/constraints/unit-tests/user-has-authorized-privilege-PASS.yaml
@@ -3,7 +3,7 @@ test-case:
   description: >-
     This test case validates the behavior of constraint
     user-has-authorized-privilege
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: user-has-authorized-privilege
       result: pass
diff --git a/src/validations/constraints/unit-tests/user-has-role-id-PASS.yaml b/src/validations/constraints/unit-tests/user-has-role-id-PASS.yaml
index 917dea4263..c77b5ed85e 100644
--- a/src/validations/constraints/unit-tests/user-has-role-id-PASS.yaml
+++ b/src/validations/constraints/unit-tests/user-has-role-id-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for user-has-role-id
   description: This test case validates the behavior of constraint user-has-role-id
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: user-has-role-id
       result: pass
diff --git a/src/validations/constraints/unit-tests/user-has-user-type-PASS.yaml b/src/validations/constraints/unit-tests/user-has-user-type-PASS.yaml
index c13224ed44..2598d44ab4 100644
--- a/src/validations/constraints/unit-tests/user-has-user-type-PASS.yaml
+++ b/src/validations/constraints/unit-tests/user-has-user-type-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for user-has-user-type
   description: This test case validates the behavior of constraint user-has-user-type
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: user-has-user-type
       result: pass
diff --git a/src/validations/constraints/unit-tests/user-privilege-level-PASS.yaml b/src/validations/constraints/unit-tests/user-privilege-level-PASS.yaml
index db272e8575..2845bc3fca 100644
--- a/src/validations/constraints/unit-tests/user-privilege-level-PASS.yaml
+++ b/src/validations/constraints/unit-tests/user-privilege-level-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for user-privilege-level
   description: This test case validates the behavior of constraint user-privilege-level
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: user-privilege-level
       result: pass
diff --git a/src/validations/constraints/unit-tests/user-sensitivity-level-PASS.yaml b/src/validations/constraints/unit-tests/user-sensitivity-level-PASS.yaml
index 582d4cd370..c0496c1358 100644
--- a/src/validations/constraints/unit-tests/user-sensitivity-level-PASS.yaml
+++ b/src/validations/constraints/unit-tests/user-sensitivity-level-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for user-sensitivity-level
   description: This test case validates the behavior of constraint user-sensitivity-level
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: user-sensitivity-level
       result: pass
diff --git a/src/validations/constraints/unit-tests/user-type-PASS.yaml b/src/validations/constraints/unit-tests/user-type-PASS.yaml
index 35c7e51e46..cf649e3ec8 100644
--- a/src/validations/constraints/unit-tests/user-type-PASS.yaml
+++ b/src/validations/constraints/unit-tests/user-type-PASS.yaml
@@ -1,7 +1,7 @@
 test-case:
   name: Positive Test for user-type
   description: This test case validates the behavior of constraint user-type
-  content: ../content/ssp-all-VALID.xml
+  content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
   expectations:
     - constraint-id: user-type
       result: pass