-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/src/validations/constraints/content/ssp-inter-boundary-component-has-direction-INVALID.xml b/src/validations/constraints/content/ssp-inter-boundary-component-has-direction-INVALID.xml
deleted file mode 100644
index 2bb436e61..000000000
--- a/src/validations/constraints/content/ssp-inter-boundary-component-has-direction-INVALID.xml
+++ /dev/null
@@ -1,25 +0,0 @@
-
-
-
-
-
-
- Communication Service System
-
-
A network communication service system.
-
-
-
-
-
-
-
-
-
-
-
-
-
\ 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 2cca026e8..ae4b94bf3 100644
--- a/src/validations/constraints/fedramp-external-constraints.xml
+++ b/src/validations/constraints/fedramp-external-constraints.xml
@@ -552,16 +552,6 @@
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 Incoming Communication Direction Has an IP Address or a URI
-
- Component {@uuid} ({path(.)}) MUST have at least one local ipv4 address, ipv6 address, or a URI to an API.
-
-
- Inter-Boundary Component Has Direction
-
- In an inter-boundary communication component, a FedRAMP SSP MUST have at least one direction property, with no more than one incoming and no more than one outgoing direction.
- Leveraged Authorization Has Authorization Type
diff --git a/src/validations/constraints/unit-tests/inter-boundary-component-direction-incoming-has-ipv-uri-FAIL.yaml b/src/validations/constraints/unit-tests/inter-boundary-component-direction-incoming-has-ipv-uri-FAIL.yaml
deleted file mode 100644
index f74dc0df8..000000000
--- a/src/validations/constraints/unit-tests/inter-boundary-component-direction-incoming-has-ipv-uri-FAIL.yaml
+++ /dev/null
@@ -1,8 +0,0 @@
-# Driver for the invalid inter-boundary-component-direction-incoming-has-ipv-uri constraint unit test.
-test-case:
- name: The invalid inter-boundary-component-direction-incoming-has-ipv-uri constraint unit test.
- description: Test that the FedRAMP SSP inter-boundary incoming communication component does not have a local ipv4 address, ipv6 address, or a URI to an API.
- content: ../content/ssp-inter-boundary-component-direction-incoming-has-ipv-uri-INVALID.xml
- expectations:
- - constraint-id: inter-boundary-component-direction-incoming-has-ipv-uri
- result: fail
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/inter-boundary-component-direction-incoming-has-ipv-uri-PASS.yaml b/src/validations/constraints/unit-tests/inter-boundary-component-direction-incoming-has-ipv-uri-PASS.yaml
deleted file mode 100644
index 9c4fead39..000000000
--- a/src/validations/constraints/unit-tests/inter-boundary-component-direction-incoming-has-ipv-uri-PASS.yaml
+++ /dev/null
@@ -1,8 +0,0 @@
-# Driver for the valid inter-boundary-component-direction-incoming-has-ipv-uri constraint unit test.
-test-case:
- name: The valid inter-boundary-component-direction-incoming-has-ipv-uri constraint unit test.
- description: Test that the FedRAMP SSP inter-boundary incoming communication component has at least one local ipv4 address, ipv6 address, or a URI to an API.
- content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
- expectations:
- - constraint-id: inter-boundary-component-direction-incoming-has-ipv-uri
- result: pass
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/inter-boundary-component-has-direction-FAIL.yaml b/src/validations/constraints/unit-tests/inter-boundary-component-has-direction-FAIL.yaml
deleted file mode 100644
index e17a40820..000000000
--- a/src/validations/constraints/unit-tests/inter-boundary-component-has-direction-FAIL.yaml
+++ /dev/null
@@ -1,8 +0,0 @@
-# Driver for the invalid inter-boundary-component-has-direction constraint unit test.
-test-case:
- name: The invalid inter-boundary-component-has-direction constraint unit test.
- description: Test that the FedRAMP SSP inter-boundary communication component has more than one incoming or outgoing direction.
- content: ../content/ssp-inter-boundary-component-has-direction-INVALID.xml
- expectations:
- - constraint-id: inter-boundary-component-has-direction
- result: fail
\ No newline at end of file
diff --git a/src/validations/constraints/unit-tests/inter-boundary-component-has-direction-PASS.yaml b/src/validations/constraints/unit-tests/inter-boundary-component-has-direction-PASS.yaml
deleted file mode 100644
index b88ce7b02..000000000
--- a/src/validations/constraints/unit-tests/inter-boundary-component-has-direction-PASS.yaml
+++ /dev/null
@@ -1,8 +0,0 @@
-# Driver for the valid inter-boundary-component-has-direction constraint unit test.
-test-case:
- name: The valid inter-boundary-component-has-direction constraint unit test.
- description: Test that the FedRAMP SSP inter-boundary communication component has at least one direction property, with no more than one incoming and no more than one outgoing direction.
- content: ../../../content/rev5/examples/ssp/xml/fedramp-ssp-example.oscal.xml
- expectations:
- - constraint-id: inter-boundary-component-has-direction
- result: pass
\ No newline at end of file