Zone C systems are not tightly restricted and/or controlled via network resources to avoid T&D systems traffic or data from entering the DoD network.

From Enclave - Zone C Checklist

Part of Zone C systems not controlled by network devices.

Associated with IA controls: ECSC-1

SV-15086r1_rule Zone C systems are not tightly restricted and/or controlled via network resources to avoid T&D systems traffic or data from entering the DoD network.

Vulnerability discussion

Zone C T&D environments are specific in nature to those facilities that have a mission to communicate with another testing facility (e.g., DISA JITC). In Zone C, the network may be completed closed and isolated or connected only to another testing facility or to another subnet with a point-to-point network (dedicated circuit) or end-to-end VPN tunnel. Traffic is isolated and restricted via source and destination IP addresses or host names. If an external testing facility is not required, these networks may also be totally contained in racks physically located within a lab environment. There are no direct external (DoD or Internet) connections to these networks. The network connectivity to another testing facility may be accomplished via tunneling mechanisms such as VPNs, private circuit (preferred method), TACLANE, MPLS, or other means of complete traffic isolation. At no time will the Zone C system data be commingled with the General Business Enclave LAN or with DoD network traffic. Security requirements of Zone C systems are at the discretion of the Testing Facility IAM. If the IAM deems that testing requires STIG compliance, than the systems will be assessed, loaded into VMS, and any discrepancies will be corrected. The requirement for STIG compliancy on development systems remains. This does not imply that, although the systems may be STIG compliant, they are permitted to have external connectivity to a DoD network. The very nature of the Closed Network Test environment precludes network connectivity to any other network outside of the secondary testing facility.

Check content

Review the connection approval documentation to determine how the Zone C environment is isolated from the rest of the networking activity. Work with the network reviewer to determine if there are tight controls of the Zone C network traffic from all other DoD traffic (VPN, MPLS, point to point circuit, etc.).

Fix text

The IAO will ensure Zone C systems are tightly restricted and controlled via network resources to avoid T&D system traffic or data from entering the DoD network.

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.

Powered by sagemincer