Each non-authorized leveraged service must be expressed as a "service" component.
+
+
+
+
\ No newline at end of file
diff --git a/src/validations/constraints/fedramp-external-constraints.xml b/src/validations/constraints/fedramp-external-constraints.xml
index a468b8655..856cad3df 100644
--- a/src/validations/constraints/fedramp-external-constraints.xml
+++ b/src/validations/constraints/fedramp-external-constraints.xml
@@ -585,7 +585,7 @@
-
+ Authentication Method Has Remarks
@@ -603,7 +603,7 @@
Container Image Has Checksum Property
-
+ In a FedRAMP SSP, a component that describes a container or operating system image MUST define a checksum property.
@@ -611,11 +611,21 @@
In a FedRAMP SSP, each information type property in a component MUST categorize the class of data flow as incoming to the system, outgoing from the system, or both.
+
+ Inter-Boundary Component Has Information Type
+
+ An inter-boundary communication component {@uuid} ({path(.)}) MUST have at least one information-type property.
+ Inventory Item and Component Has PublicIn a FedRAMP SSP, each inventory item and internal service component MUST state if they are public-facing.
+
+ Inventory Item or Component Has Asset ID
+
+ In a FedRAMP SSP, each inventory item and software image component MUST include the asset ID.
+ Leveraged Authorization Has Authorization Type
@@ -659,16 +669,6 @@
-
-
-
-
- Inventory Item or Component Has Asset ID
-
- In a FedRAMP SSP, each inventory item and software image component MUST include the asset ID.
-
-
-
@@ -681,7 +681,7 @@
Authenticated Scan No Has Remarks
- FedRAMP requires CSPs to provide justification for any high or moderate impact system inventory item that does not support authenticated scans.
+ A FedRAMP SSP MUST provide justification for any high or moderate impact system inventory item that does not support authenticated scans.High Impact Inventory Item Has Asset Owner
@@ -796,6 +796,7 @@
'sc-1_smt.a' : 'at least one procedure that addresses System and Communications Protection MUST be associated with SC-1 part a.',
'si-1_smt.a' : 'at least one procedure that addresses System and Information Integrity MUST be associated with SI-1 part a.',
'sr-1_smt.a' : 'at least one procedure that addresses Supply Chain Risk Management MUST be associated with SR-1 part a.'}"/>
+ Has Policy
@@ -806,6 +807,11 @@
In a FedRAMP SSP, {$procedure-messages(./@statement-id)}
+
+ Statement Has This System Component
+
+ In a FedRAMP SSP, each control implementation statement MUST have one "this-system" by-component.
+
@@ -825,17 +831,6 @@
-
-
-
-
-
- Statement Has This System Component
-
- In a FedRAMP SSP, each control implementation statement MUST have one "this-system" by-component.
-
-
-
diff --git a/src/validations/constraints/unit-tests/inter-boundary-component-has-information-type-FAIL.yaml b/src/validations/constraints/unit-tests/inter-boundary-component-has-information-type-FAIL.yaml
new file mode 100644
index 000000000..e148e6f8d
--- /dev/null
+++ b/src/validations/constraints/unit-tests/inter-boundary-component-has-information-type-FAIL.yaml
@@ -0,0 +1,8 @@
+# Driver for the invalid inter-boundary-component-has-information-type constraint unit test.
+test-case:
+ name: The invalid inter-boundary-component-has-information-type constraint unit test.
+ description: Test that the FedRAMP SSP inter-boundary communication component does not have the "information-type" property.
+ content: ../content/ssp-inter-boundary-component-has-information-type-INVALID.xml
+ expectations:
+ - constraint-id: inter-boundary-component-has-information-type
+ result: fail
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/inter-boundary-component-has-information-type-PASS.yaml b/src/validations/constraints/unit-tests/inter-boundary-component-has-information-type-PASS.yaml
new file mode 100644
index 000000000..6bb761964
--- /dev/null
+++ b/src/validations/constraints/unit-tests/inter-boundary-component-has-information-type-PASS.yaml
@@ -0,0 +1,8 @@
+# Driver for the valid inter-boundary-component-has-information-type constraint unit test.
+test-case:
+ name: The valid inter-boundary-component-has-information-type constraint unit test.
+ description: Test that the FedRAMP SSP inter-boundary communication component has at least one "information-type" property.
+ content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
+ expectations:
+ - constraint-id: inter-boundary-component-has-information-type
+ result: pass
\ No newline at end of file