From Enclave - Zone B Checklist
Part of Ingress network connections permitted.
Associated with IA controls: ECSC-1
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. The guidance for Zone B systems is restricted to unclassified DoD networks; it does not apply to other DoD networks such as the Defense Research and Engineering Network (DREN). Test or development traffic will be isolated/separated from production traffic. The permissible activities for Zone B environments include, but are not limited to, user functional acceptance of a product, final stage testing, and Development. Downloading software from the Internet is acceptable in Zone B, however, a DMZ with gateway must be established for such purposes.
Work with the network reviewer to determine if any connections are allowed from the external interface to the Zone B environment. No external initiated connection should be allowed to enter the environment. Due to the nature of the test environment, SAs may believe it is acceptable to allow inbound traffic to certain systems. This is strictly forbidden as there may be other systems that reside within the same environment that may be compromised.
The IAO will ensure no external to internal (ingress) network initiated connections are permitted (denied by default).
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