Zone B network connections (all incoming/outgoing traffic) are not strictly controlled via network infrastructure devices to include the establishment of a VPN, VLAN or TACLANE.

Part of Zone B network not controlled/restricted.

Associated with IA controls: EBCR-1

SV-14993r1_rule Zone B network connections (all incoming/outgoing traffic) are not strictly controlled via network infrastructure devices to include the establishment of a VPN, VLAN or TACLANE.

Vulnerability discussion

The systems that reside in Zone B require external access utilizing a DoD network as the transport mechanism. Logical access control mechanisms will be utilized at the network boundary such as strictly controlled ACLs with no ingress traffic origination and established sessions only. Test or development traffic will be isolated/separated from production traffic. Downloading software from the Internet is acceptable in Zone B, however, a DMZ with gateway must be established for such purposes.

Check content

Work with the network reviewer to determine compliance. All Zone B traffic that needs to traverse a Zone A, DISN, or Enclave network boundary must be isolated and/or segregated from any DoD production traffic.

Fix text

The IAO will ensure all incoming/outgoing network connections are strictly controlled via network infrastructure devices to include the establishment of a VPN, VLAN or TACLANE.

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.