The test and development infrastructure must use a DMZ to import and export data between test and development environments and DoD operational networks.

From Test and Development Zone B Security Technical Implementation Guide

Part of ENTD0190 - Data is not transported through a DMZ.

Associated with IA controls: DCSP-1, ECSC-1, EBBD-2, EBBD-1, EBBD-3

SV-51525r1_rule The test and development infrastructure must use a DMZ to import and export data between test and development environments and DoD operational networks.

Vulnerability discussion

Most systems that reside in the test and development environment require external access using a DoD network as the transport mechanism. Logical access control mechanisms, such as strictly controlled ACLs for both ingress and egress traffic, must be utilized at the environment boundary. The permissible activities for test and development 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 for the environment; however, establish a DMZ for such purposes.

Check content

Determine whether there is a DMZ properly configured for traffic entering and leaving the test and development environment. If a DMZ for traffic entering and leaving the test and development environment is not implemented, this is a finding.

Fix text

Configure and implement a DMZ for traffic entering and leaving the test and development environment.

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.