Test and Development Zone A Security Technical Implementation Guide

  • Version/Release: V1R6
  • Published: 2022-04-27
  • Expand All:
  • Severity:
  • Sort:
Compare

Select any two versions of this STIG to compare the individual requirements

View

Select any old version/release of this STIG to view the previous requirements

The Test & Development Zone A STIG is published as a tool to improve the security of Department of Defense (DoD) information systems. Comments or proposed revisions to this document should be sent via e-mail to the following address: disa.stig_spt@mail.mil.
b
Network infrastructure and systems supporting the test and development environment must be documented within the organizations accreditation package.
Medium - V-39344 - SV-51202r1_rule
RMF Control
Severity
Medium
CCI
Version
ENTD0010
Vuln IDs
  • V-39344
Rule IDs
  • SV-51202r1_rule
Up-to-date documentation is essential in assisting with the management, auditing, and security of the network infrastructure used to support the test and development environment. Network diagrams are important because they show the overall layout where devices are physically located within the network infrastructure. Diagrams also show the relationship and connectivity between devices where possible intrusive attacks could take place. Having up-to-date network diagrams will also help show what the security, traffic, and physical impact of adding a system will be on the network.Information Assurance ManagerInformation Assurance OfficerDCHW-1
Checks: C-46619r2_chk

Review the accreditation package documentation to verify the test and development environment is correctly documented within the network diagrams and site security plan. If the organization's accreditation package does not include the test and development infrastructure in the network diagrams and system security plan, this is a finding.

Fix: F-44359r2_fix

Document network infrastructure and systems supporting the test and development environment, then include it with the accreditation package.

b
Network infrastructure and systems supporting the test and development environment must follow DoD certification and accreditation procedures before connecting to a DoD operational network or Internet Service Provider.
Medium - V-39345 - SV-51203r1_rule
RMF Control
Severity
Medium
CCI
Version
ENTD0020
Vuln IDs
  • V-39345
Rule IDs
  • SV-51203r1_rule
Prior to connecting to a live operational network, such as the DISN, systems, at minimum, receive an IATO. A system without an IATO does not show adequate effort to meet IA controls and security requirements and may pose a risk to other computers or systems connecting to the operational network.Information Assurance ManagerInformation Assurance OfficerEBCR-1
Checks: C-46707r5_chk

Review the accreditation package documentation to verify the test and development environment has been granted an IATO to connect to the DISN. If an IATO has not been granted, this is a finding. If the zone environment does not have any connectivity to the DISN or commercial ISP, this requirement is not applicable.

Fix: F-44662r1_fix

Certify and accredit the test and development infrastructure and supporting systems connecting to the DISN. Keep the IATO with the organization's accreditation package.

b
Network infrastructure and systems supporting the test and development environment must be registered in a DoD asset management system.
Medium - V-39433 - SV-51291r1_rule
RMF Control
Severity
Medium
CCI
Version
ENTD0030
Vuln IDs
  • V-39433
Rule IDs
  • SV-51291r1_rule
An asset management system is used to send out notifications on vulnerabilities in commercial and military information infrastructures as they are discovered. If the organization's assets are not registered with an asset management system, administrators will not be notified of important vulnerabilities such as viruses, denial of service attacks, system weaknesses, back doors, and other potentially harmful situations. Additionally, there will be no way to enter, track, or resolve findings during a review.VIVM-1
Checks: C-46812r1_chk

Determine whether all systems and network infrastructure devices supporting the test and development environment are registered in an asset management system. If any systems and network infrastructure devices supporting the test and development environment are not registered in an asset management system, this is a finding.

Fix: F-44446r2_fix

Register the network infrastructure and systems supporting the test and development environment in a DoD asset management program.

b
Network infrastructure and systems supporting the test and development environment must be managed from a management network.
Medium - V-39434 - SV-51292r1_rule
RMF Control
Severity
Medium
CCI
Version
ENTD0040
Vuln IDs
  • V-39434
Rule IDs
  • SV-51292r1_rule
It is important to restrict administrative access to the supporting network infrastructure and systems in the test and development environment, as it reduces the risk of data theft or interception from an attacker on the operational network.ECSC-1
Checks: C-46708r2_chk

Review the network diagrams to determine whether a management network has been established to manage the network infrastructure and systems supporting the test and development environment. If a management network has not been established to manage the test and development environment infrastructure, this is a finding.

Fix: F-44447r2_fix

Engineer a management network solution and document it within the test and development network diagrams.

b
The organization must document impersistent connections to the test and development environment with approval by the organizations Authorizing Official.
Medium - V-39435 - SV-51293r1_rule
RMF Control
Severity
Medium
CCI
Version
ENTD0050
Vuln IDs
  • V-39435
Rule IDs
  • SV-51293r1_rule
An impersistent connection is any temporary connection needed to another test and development environment or DoD operational network where testing is not feasible. As any unvetted connection or device will create additional risk and compromise the entire environment, it is up to the Authorizing Official for the organization to accept the risk of an impersistent connection.EBCR-1, ECSD-1
Checks: C-46709r3_chk

Review documentation for impersistent connections or devices to ensure the risk has been thoroughly assessed and approved by the Authorizing Official. If no documented approval is available for impersistent connections, this is a finding.

Fix: F-44448r4_fix

Create and have on file up-to-date documentation of the authorized risk approval for impersistent connections or devices.

b
Application development must not occur on DoD operational network segments.
Medium - V-39436 - SV-51294r1_rule
RMF Control
Severity
Medium
CCI
Version
ENTD0060
Vuln IDs
  • V-39436
Rule IDs
  • SV-51294r1_rule
To reduce the risk of compromise of DoD operational networks and data, application and system development needs to be limited to systems within a network segment designated for development only.ECSC-1
Checks: C-46711r5_chk

Review the organization's network diagrams to determine whether network segments for development have been established and outlined in the documentation. If application development occurs on DoD operational networks, this is a finding. If there isn't any application development occurring in the zone environment, this requirement is not applicable.

Fix: F-44449r1_fix

Designate network segments for applications and systems development. Document these designated network segments in the network diagrams for the T&D environment.

c
Development systems must have antivirus installed and enabled with up-to-date signatures.
High - V-39437 - SV-51295r1_rule
RMF Control
Severity
High
CCI
Version
ENTD0070
Vuln IDs
  • V-39437
Rule IDs
  • SV-51295r1_rule
Virus scan programs are a primary line of defense against the introduction of viruses and malicious code that can destroy data and even render a computer inoperable. Utilizing the most current virus scan program provides the ability to detect this malicious code before extensive damage occurs. Updated virus scan data files help protect a system, as new malware is identified by the software vendors on a regular basis.ECSC-1, ECVP-1
Checks: C-46712r3_chk

Review development images to determine whether antivirus is installed and configured with current signatures. If antivirus is missing on development systems, this is a finding. If there isn't any application development occurring in the zone environment, this requirement is not applicable.

Fix: F-44450r2_fix

Install antivirus with current signatures on development systems.

b
Development systems must have HIDS or HIPS installed and configured with up-to-date signatures.
Medium - V-39438 - SV-51296r1_rule
RMF Control
Severity
Medium
CCI
Version
ENTD0080
Vuln IDs
  • V-39438
Rule IDs
  • SV-51296r1_rule
A HIDS or HIPS application is a secondary line of defense behind the antivirus. The application will monitor all ports and the dynamic state of a development system. If the application detects irregularities on the system, it will block incoming traffic that may potentially compromise the development system that can lead to a DoS or data theft.ECID-1, ECSC-1
Checks: C-46713r3_chk

Review the development images to determine whether a HIDS or HIPS application is installed and configured. If a HIDS or HIPS application is not installed and configured on the development image, this is a finding. If there isn't any application development occurring in the zone environment, this requirement is not applicable.

Fix: F-44451r2_fix

Install and configure a HIDS or HIPS application on development system images.

b
Development systems must have a firewall installed, configured, and enabled.
Medium - V-39439 - SV-51297r1_rule
RMF Control
Severity
Medium
CCI
Version
ENTD0090
Vuln IDs
  • V-39439
Rule IDs
  • SV-51297r1_rule
A firewall provides a line of defense against malicious attacks. To be effective, it must be enabled and properly configured.ECSC-1
Checks: C-46714r3_chk

Review the development images to determine whether the OS or a third party firewall has been installed, configured, and enabled. If a firewall is not installed, configured, and enabled, this is a finding. If there isn't any application development occurring in the zone environment, this requirement is not applicable.

Fix: F-44452r2_fix

Install, configure, and enable either the OS or a third party firewall on the development system.

c
Development systems must be part of a patch management solution and all systems must be up to date.
High - V-39440 - SV-51298r1_rule
RMF Control
Severity
High
CCI
Version
ENTD0100
Vuln IDs
  • V-39440
Rule IDs
  • SV-51298r1_rule
Major software vendors release security patches and hotfixes to their products when security vulnerabilities are discovered. It is essential that these updates be applied in a timely manner to prevent unauthorized individuals from exploiting identified vulnerabilities.ECSC-1, VIVM-1
Checks: C-46715r3_chk

Determine whether the organization has a patch management solution in place to apply security patches released by the vendor, and that all systems are up to date. If a patch management solution has not been implemented and is not functioning to update development systems with the latest patches, or all systems are not up to date, this is a finding.

Fix: F-44453r2_fix

Implement a patch management solution to keep development systems up to date with the latest security patches released by the vendor.

b
A change management policy must be implemented for application development.
Medium - V-39441 - SV-51299r1_rule
RMF Control
Severity
Medium
CCI
Version
ENTD0110
Vuln IDs
  • V-39441
Rule IDs
  • SV-51299r1_rule
Change management is the formal review process that ensures that all changes made to a system or application receives formal review and approval. Change management reduces impacts from proposed changes that could possibly have interruptions to the services provided. Recording all changes for applications will be accomplished by a configuration management policy. The configuration management policy will capture the actual changes to software code and anything else affected by the change.DCII-1, DCPR-1
Checks: C-46716r3_chk

Interview the ISSM/ISSO to determine whether a current Change Control Management policy has been implemented in the organization. If a change management policy has not been created and implemented for the organization, this is a finding. If there isn't any application development occurring in the zone environment, this requirement is not applicable.

Fix: F-44454r2_fix

Create a change management policy for the organization for application and system development.

b
The organization must document and gain approval from the Change Control Authority prior to migrating data to DoD operational networks.
Medium - V-39611 - SV-51469r1_rule
RMF Control
Severity
Medium
CCI
Version
ENTD0120
Vuln IDs
  • V-39611
Rule IDs
  • SV-51469r1_rule
Without the approval of the Change Control Authority, data moved from the test and development network into an operational network could pose a risk of containing malicious code or cause other unintended consequences to live operational data. Data moving into operational networks from final stage preparation must always be vetted and approved.ECSC-1, ECSD-1, ECSD-2
Checks: C-46796r3_chk

Review the change control documentation for the environment to determine whether the organization has prior approval to move data from the test and development environment to the operational network after final testing. If the organization does not keep a change control log or the log exists but is not current, this is a finding. If there isn't any application development occurring in the zone environment, this requirement is not applicable.

Fix: F-44627r2_fix

Create a policy to document all finalized projects to gain approval by the Change Control Authority prior to deploying finalized projects to a DoD operational network.

b
Application code must go through a code review prior to deployment into DoD operational networks.
Medium - V-39614 - SV-51472r1_rule
RMF Control
Severity
Medium
CCI
Version
ENTD0130
Vuln IDs
  • V-39614
Rule IDs
  • SV-51472r1_rule
Prior to release of the application receiving an IATO for deployment into a DoD operational network, the application will have a thorough code review. Along with the proper testing, the code review will specify flaws causing security, compatibility, or reliability concerns that may compromise the operational network.DCSQ-1, ECSC-1, ECSD-1, ECSD-2
Checks: C-46813r2_chk

Determine whether there is a policy in place for code review prior to applications being deployed into a DoD operational network. If a code review policy has not been established, this is a finding. If there isn't any application development occurring in the zone environment, this requirement is not applicable.

Fix: F-44666r1_fix

Implement a code review policy for applications before deployment into DoD operational networks.

b
Access to source code during application development must be restricted to authorized users.
Medium - V-39619 - SV-51477r1_rule
RMF Control
Severity
Medium
CCI
Version
ENTD0140
Vuln IDs
  • V-39619
Rule IDs
  • SV-51477r1_rule
Restricting access to source code and the application to authorized users will limit the risk of source code theft or other potential compromise.ECAN-1, ECCD-1, ECLP-1
Checks: C-46797r3_chk

Review the organization's site security plan and documentation to determine whether there is a list of current authorized users. If a current list of authorized users is missing from the site security plan for the test and development environment, this is a finding. If there isn't any application development occurring in the zone environment, this requirement is not applicable.

Fix: F-44630r2_fix

Document all authorized users with access to the development environment and access to source code. If the documentation exists but is not current, bring the documentation up to date.

b
The organization must sanitize data transferred to test and development environments from DoD operational networks for testing to remove personal and sensitive information exempt from the Freedom of Information Act.
Medium - V-39621 - SV-51479r2_rule
RMF Control
Severity
Medium
CCI
Version
ENTD0150
Vuln IDs
  • V-39621
Rule IDs
  • SV-51479r2_rule
If DoD production data is transferred to a test and development environment and personal or sensitive information has not been sanitized from the data, personal or sensitive information could be exposed or compromised.
Checks: C-46799r3_chk

Determine the data type on systems within the test and development environment. Interview the ISSM or ISSO regarding the connection approval process for housing DoD live operational data or Privacy Act information on any test or development system. If the test and development environment is using live DoD data or Privacy Act information, this is a finding.

Fix: F-44637r2_fix

Create organizational policies and procedures to prohibit the use of any live operational DoD data or Privacy Act information in the test and development environment.

b
The test and development infrastructure must use a gateway to separate access to DoD operational networks.
Medium - V-39627 - SV-51485r1_rule
RMF Control
Severity
Medium
CCI
Version
ENTD0160
Vuln IDs
  • V-39627
Rule IDs
  • SV-51485r1_rule
Acting as the first hop into a test and development environment, the gateway can implement proper routing and provide a first layer of defense against attacks and other unintentional compromise or spillage of sensitive information into the operational network.DCSP-1, ECSC-1
Checks: C-46800r2_chk

Review the network diagrams and physically check to see whether the organization has a gateway implemented for the test and development environment. If the organization has not documented or implemented a gateway for the test and development environment, this is a finding.

Fix: F-44639r2_fix

Install a gateway to separate the test and development environment from the DoD operational network. Document it in the test and development network diagrams.

b
Ports, protocols, and services visible to DoD operational networks or ISPs must follow DoDI 8551.1 policy.
Medium - V-39629 - SV-51487r1_rule
RMF Control
Severity
Medium
CCI
Version
ENTD0170
Vuln IDs
  • V-39629
Rule IDs
  • SV-51487r1_rule
In accordance with the DoD 8551.1 policy, the test and development environment may require external access to live operational data to perform final stage testing. All network connections for the test and development environment must make use of the PPS CAL at the appropriate boundaries.DCPP-1
Checks: C-46801r2_chk

Review the latest version of the PPS CAL for those ports, protocols, and services visible to DoD-managed components. If the organization is using ports, protocols, or services deemed not acceptable by the PPS CAL or requiring Authorization Official approval without proper documentation, this is a finding.

Fix: F-44640r2_fix

Configure all ports, protocols, and services visible to DoD-managed components as described in the DoDI 8551.1 PPSM policy.

c
The test and development infrastructure must use a firewall for traffic inspection to and from DoD operational networks.
High - V-39636 - SV-51494r1_rule
RMF Control
Severity
High
CCI
Version
ENTD0180
Vuln IDs
  • V-39636
Rule IDs
  • SV-51494r1_rule
A firewall is necessary to inspect traffic as it flows into and out of the test and development environment. Without a firewall present, traffic could flow freely between the operational network and test and development environment, allowing malicious or other unintended traffic and unauthorized access, compromising a system or environment.DCSP-1, EBBD-1, EBBD-2, EBBD-3, ECSC-1
Checks: C-46802r2_chk

Install and configure a firewall to separate DoD operational and test and development environments.

Fix: F-44643r2_fix

Install and configure a firewall to separate DoD operational and test and development environments.

a
Access control lists between development and testing network segments within a test and development environment must be in a deny-by-default posture.
Low - V-39662 - SV-51529r1_rule
RMF Control
Severity
Low
CCI
Version
ENTD0230
Vuln IDs
  • V-39662
Rule IDs
  • SV-51529r1_rule
To prevent malicious or accidental leakage of information between test and development environments, organizations must implement a deny-by-default security posture. All traffic not explicitly permitted must be denied. Such rule sets prevent many malicious exploits or accidental leakage by regulating the ports, protocols, or services necessary between network segments within the test and development environment.ECSC-1
Checks: C-46817r1_chk

Determine whether a deny-by-default security posture has been implemented for both ingress and egress traffic for the test and development environment. If the organization is not using a deny-by-default security posture for ingress and ingress traffic for the test and development environment, this is a finding.

Fix: F-44670r1_fix

Implement a deny-by-default security posture for both ingress and egress traffic between network segments in the test and development environment.

c
Access control lists between the test and development environment and DoD operational networks must be in a deny-by-default posture.
High - V-39663 - SV-51530r1_rule
RMF Control
Severity
High
CCI
Version
ENTD0240
Vuln IDs
  • V-39663
Rule IDs
  • SV-51530r1_rule
To prevent malicious or accidental leakage of traffic between test and development environments and operational networks, organizations must implement a deny-by-default security posture. Perimeter routers, boundary controllers, or firewalls must deny incoming and outgoing traffic not expressly permitted. Such rule sets prevent many malicious exploits or accidental leakage by regulating the ports, protocols, or services necessary to the enclave.ECSC-1
Checks: C-46818r1_chk

Determine whether a deny-by-default security posture has been implemented for both ingress and egress traffic between the test and development environment and DoD operational networks. If the organization is not using a deny-by-default security posture for traffic between the test and development environment and DoD operational networks, this is a finding.

Fix: F-44671r1_fix

Implement a deny-by-default security posture for both ingress and egress traffic between the test and development environment and DoD operational networks.

b
Access control lists between the test and development environments must be in a deny-by-default posture.
Medium - V-39664 - SV-51531r1_rule
RMF Control
Severity
Medium
CCI
Version
ENTD0250
Vuln IDs
  • V-39664
Rule IDs
  • SV-51531r1_rule
To prevent malicious or accidental leakage of traffic, organizations must implement a deny-by-default security posture between test and development environments. All ingress and egress traffic not explicitly permitted between test and development environments must be denied. Such rule sets prevent many malicious exploits or accidental leakage by regulating the ports, protocols, or services necessary to each environment.ECSC-1
Checks: C-46819r1_chk

Determine whether a deny-by-default security posture has been implemented for both ingress and egress traffic between the test and development environments. If the organization is not using a deny-by-default security posture for traffic between the test and development environments, this is a finding.

Fix: F-44672r1_fix

Implement a deny-by-default security posture for both ingress and egress traffic between test and development environments.

b
Remote access into the test and development environment must use an encryption mechanism approved for the classification level of the network.
Medium - V-39667 - SV-51534r1_rule
RMF Control
Severity
Medium
CCI
Version
ENTD0280
Vuln IDs
  • V-39667
Rule IDs
  • SV-51534r1_rule
Remote access to the environment using unapproved encryption mechanism is inherently dangerous because anyone with a packet sniffer and access to the network can acquire the device's account and password information. With this intercepted information, a malicious user could gain access to the device, cause denial of service attacks, intercept sensitive information, or perform other destructive actions.EBRU-1, ECCT-1, ECCT-2
Checks: C-46822r1_chk

Determine whether the proper encryption standard is deployed for the classification of the network where remote access is performed. Unclassified/FOUO or any need-to-know data will need to use a FIPS 140-2 validated cryptographic module. Classified traffic must use an NSA approved encryption standard. If the proper encryption standard is not in use for remote access, this is a finding.

Fix: F-44675r1_fix

Implement an approved encryption mechanism for the classification of the network for remote access. Unclassified/FOUO or any need-to-know data will need to use a FIPS 140-2 validated cryptographic module. Classified traffic must use an NSA approved encryption standard.

b
Remote access VPNs must prohibit the use of split tunneling on VPN connections.
Medium - V-39669 - SV-51536r1_rule
RMF Control
Severity
Medium
CCI
Version
ENTD0300
Vuln IDs
  • V-39669
Rule IDs
  • SV-51536r1_rule
The VPN software on a host can be configured in either of two modes. It can be set to encrypt all IP traffic originating from that host, and send all of that traffic to the remote IP address of the network gateway. This configuration is called “tunnel-all” mode, because all IP traffic from the host must traverse the VPN tunnel to the remote system, where it will either be processed or further forwarded to additional IP addresses after decryption. Alternately, the VPN software can be set only to encrypt traffic that is specifically addressed to an IP at the other end of the VPN tunnel. All other IP traffic bypasses the VPN encryption and routing process, and is handled by the host as if the VPN relationship did not exist. This configuration is called “split-tunnel” mode, because the IP traffic from the host is split between encrypted packets sent across the VPN tunnel and unencrypted packets sent to all other external addresses. There are security and operational implications in the decision of whether to use split-tunnel or tunnel-all mode. Placing a host in tunnel-all mode makes it appear to the rest of the world as a node on the connected logical (VPN-connected) network. It no longer has an identity to the outside world based on the local physical network. In tunnel-all mode, all traffic between the remote host and any other host can be subject to inspection and processing by the security policy devices of the remote VPN-linked network. This improves the security aspects of the connected network, since it can enforce all security policies on the VPN-connected computer.ECSC-1
Checks: C-46824r1_chk

Determine whether split tunneling is prohibited for remote access VPNs connecting to the test and development environment. If the VPN policy allows split tunneling, this is a finding.

Fix: F-44677r1_fix

Configure VPNs to prohibit split tunneling when connecting to the test and development environment.

a
Installation of operating systems on systems and devices in the test and development environment must be logically separated to prohibit access to any operational network.
Low - V-39671 - SV-51538r1_rule
RMF Control
Severity
Low
CCI
Version
ENTD0320
Vuln IDs
  • V-39671
Rule IDs
  • SV-51538r1_rule
Systems are most vulnerable to attack during the installation of an operating system because no security controls have been put in place to protect the system. It is very important to block all access to a system while the operating system is being installed and configured until such time that security controls can be implemented.ECSC-1
Checks: C-46826r1_chk

Determine whether the organization has a connection approval policy on the installation of operating systems within the test and development environment. The policy must include either physically disconnecting or blocking the system at the firewall in order to achieve complete isolation from any network traffic. If no connection approval policy has been developed, this is a finding.

Fix: F-44679r1_fix

Create a policy to ensure the test or development system is physically disconnected or blocked at the firewall from any external network during the installation of an operating system.

b
Virtual machines used for application development and testing must not share the same physical host with DoD operational virtual machines.
Medium - V-39672 - SV-51539r1_rule
RMF Control
Severity
Medium
CCI
Version
ENTD0330
Vuln IDs
  • V-39672
Rule IDs
  • SV-51539r1_rule
Attacks on virtual machines from other VMs through denial of service and other attacks potentially stealing sensitive data such as source code used in application development. It is imperative to keep DoD operational virtual machines on physically separate platforms from test and development virtual machines.ECSC-1
Checks: C-46827r1_chk

Review the system plan to determine whether physical hosts are sharing DoD operational and test and development virtual machines.

Fix: F-44680r2_fix

Engineer a solution to use separate physical hosts for DoD operational and T&D virtual machines.

b
Data used for testing and development must be downloaded through a secure connection to an IA-compliant system for vulnerability scanning prior to deployment in the test and development environment.
Medium - V-41494 - SV-54070r1_rule
RMF Control
Severity
Medium
CCI
Version
ENTD0360
Vuln IDs
  • V-41494
Rule IDs
  • SV-54070r1_rule
It is mandatory that data from an untrusted network or website that is to be used in a testing and development environment be downloaded through a secure perimeter. Bringing data directly from an untrusted network or downloaded from a personal computer or home Internet connection must be prohibited. Scanning data is crucial to ensure the integrity of the information prior to deployment for T&D processes. While not an all-inclusive list, data in this situation includes OS patches, application updates, operating systems, development tools, and test data. In the T&D environment, there will typically be one or more IA-compliant systems accessing a secure Internet connection. If a secure Internet connection is not available, such as in Zone D, a connection in another zone can be used and the data moved by approved physical media into the zone. Scanning the data with an anti-virus program will reduce the risk of exploits and of having vulnerable systems in the T&D environment taken over. Downloading data from a single workstation for all zone environments is acceptable. Organizations with NIPRNet connections must download all data through their NIPR connection for scanning at the IAPs. Contractors or other DoD organizations without any direct NIPRNet connectivity will need to use a secure Internet connection following all applicable DoD IA policy and STIG requirements.
Checks: C-48011r6_chk

1. Verify an IA-compliant system has been deployed to scan downloaded data prior to deployment into the T&D environment. Also, review the zone diagrams to ensure the workstation is documented appropriately. 2. Determine if the organization has a NIPRNet connection. A. If the organization has a NIPRNet connection; data must be downloaded through the DoD IAP. B. If the organization does not have a NIPRNet connection, data must be downloaded through a secure, IA-compliant connection. If the organization does not download and scan the downloaded data to a dedicated IA-system and secure IA-compliant connection, this is a finding.

Fix: F-46950r4_fix

1. Deploy an IA-compliant system to download data. 2. Configure the IA-compliant system to download data through a secure, IA-compliant connection. A. If your organization has a NIPRNet or connection; data must be downloaded through the DoD IAP. B. If your organization does not have a NIPRNet or connection, data must be downloaded through a secure, IA-compliant connection.

b
The organization must create a policy and procedures document for proper handling and transport of data entering (physically or electronically) the test and development environment.
Medium - V-43317 - SV-56070r1_rule
RMF Control
Severity
Medium
CCI
Version
ENTD0370
Vuln IDs
  • V-43317
Rule IDs
  • SV-56070r1_rule
Without policies and procedures in place, the organization will not have the authority to hold personnel accountable for improperly handling or transporting data into the test and development environment. The documents need to include guidance for both physical and electronic data migration.
Checks: C-49290r2_chk

Review the organization's policies and procedures document to ensure proper handling of data being transported into the test and development environment. This document must include information for physical and electronic migration of data. If the organization does not have a policy and procedures document created or available for review, this is a finding.

Fix: F-48944r1_fix

Create a policy for, and document the procedure of, proper handling of data transported into the test and development environment. This document must include information for physical and electronic handling and migration of data.