Attachment J.27 - CSF Mapping Disclaimer.xlsx
XLSX spreadsheet 26 KB Posted
- Attached to
- Health Care Benefits Services Contract - Request For Proposal (RFP) Federal contract opportunity
- Solicitation number
- 1145PC22R0001
- Issued by
- Peace Corps
About this file
This document provides a mapping between the security requirements in NIST Special Publication 800-171 and subcategories in the Cybersecurity Framework. The mapping shows equivalencies between the two publications in whole or in part. However, the publications have different scopes: SP 800-171 focuses on protecting controlled unclassified information in non-federal systems, while the CSF addresses cybersecurity more broadly. Some SP 800-171 requirements are not mapped to CSF subcategories due to differences in scope and objectives between the publications. The document notes limitations in using the mapping to satisfy all requirements in SP 800-171 or the CSF. It also identifies several SP 800-171 requirements that could not be logically mapped to any CSF subcategory.
View the file
Other files for this federal contract opportunity
Show all 35
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
CSF to SP 800-171 Mapping
| CSF to SP 800-171 Mapping Disclaimer |
| This documents provides a mapping between the Cybersecurity Framework (CSF) Subcategories and the Controlled Unclassified Information (CUI) Requirements in NIST Special Publication (SP) 800-171. The intent of the mappings included in this document show an equivalency of requirements (in whole or in part) between the two publications. It is important to consider the different scope between the two publications when reviewing and using this mapping. |
NIST SP 800-171 focuses on protecting the confidentiality of Controlled Unclassified Information (CUI) in nonfederal systems and organizations, and recommends specific security requirements to achieve that objective. The requirements recommended for use in SP 800-171 are derived from FIPS Publication 200 and the moderate security control baseline in NIST Special Publication 800-53 and are based on the CUI regulation (32 CFR Part 2002, Controlled Unclassified Information). The tailoring criteria applied to the FIPS Publication 200 security requirements and the NIST Special Publication 800-53 security controls is not an endorsement for the elimination of those requirements and controls—rather, the tailoring criteria focuses on the protection of CUI from unauthorized disclosure in nonfederal systems and organizations.
Since the security requirements are derivative from the NIST publications listed above, organizations should not assume that satisfying those particular requirements will automatically satisfy the security requirements and controls in FIPS Publication 200 and Special Publication 800-53. In addition to the security objective of confidentiality, the objectives of integrity and availability remain a high priority for organizations that are concerned with establishing and maintaining a comprehensive information security program. While the primary purpose of SP 800-171 is to define requirements to protect the confidentiality of CUI, there is a close relationship between confidentiality and integrity since many of the underlying security mechanisms at the system level support both security objectives.
Some SP 800-171 security requirements are not mapped to any CSF subcategories due to the scoping of SP 800-171 which is focused solely on protecting the confidentiality of CUI in nonfederal systems (i.e., security requirements supporting availability and integrity are not addressed in SP 800-171) and assumes some security best practices to be routinely satisfied by nonfederal organizations as part of conducting business (see SP 800-171 Appendix E). Note also that some CSF subcategories are not mapped to SP 800-171 CUI security requirements for similar reasons or because the SP 800-171 requirements are aligned with specific federal requirements needed to protect CUI. The following are the SP 800-171 security requirements that could not logically be mapped to CSF subcategories: 3.1.22; 3.10.6; and 3.13.14.
| Function | CSF Subcategory | CUI Requirement | CUI Requirement Description |
| IDENTIFY (ID) | ID.AM-1 | 3.4.1 | Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles. |
| ID.AM-2 | 3.4.1 | Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles. | |
| ID.AM-3 | 3.1.3 | Control the flow of CUI in accordance with approved authorizations. | |
| ID.AM-3 | 3.13.1 | Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems. | |
| ID.AM-4 | 3.1.20 | Verify and control/limit connections to and use of external systems. | |
| ID.AM-4 | 3.1.21 | Limit use of organizational portable storage devices on external systems. | |
| ID.AM-5 | No mapping; see Mapping Disclaimer. | ||
| ID.AM-6 | No mapping; see Mapping Disclaimer. | ||
| ID.BE-1 | No mapping; see Mapping Disclaimer. | ||
| ID.BE-2 | No mapping; see Mapping Disclaimer. | ||
| ID.BE-3 | No mapping; see Mapping Disclaimer. | ||
| ID.BE-4 | No mapping; see Mapping Disclaimer. | ||
| ID.BE-5 | No mapping; see Mapping Disclaimer. | ||
| ID.GV-1 | No mapping; see Mapping Disclaimer. | ||
| ID.GV-2 | No mapping; see Mapping Disclaimer. | ||
| ID.GV-3 | No mapping; see Mapping Disclaimer. | ||
| ID.GV-4 | No mapping; see Mapping Disclaimer. | ||
| ID.RA-1 | 3.11.1 | Periodically assess the risk to organizational operations (including mission, functions, image, or reputation), organizational assets, and individuals, resulting from the operation of organizational systems and the associated processing, storage, or transmission of CUI. | |
| ID.RA-1 | 3.11.2 | Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting the system are identified. | |
| ID.RA-1 | 3.12.1 | Periodically assess the security controls in organizational systems to determine if the controls are effective in their application. | |
| ID.RA-1 | 3.12.3 | Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls. | |
| ID.RA-1 | 3.14.1 | Identify, report, and correct information and system flaws in a timely manner. | |
| ID.RA-1 | 3.14.3 | Monitor system security alerts and advisories and take actions in response. | |
| ID.RA-1 | 3.14.6 | Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks. | |
| ID.RA-1 | 3.14.7 | Identify unauthorized use of organizational systems. | |
| ID.RA-2 | 3.14.1 | Identify, report, and correct information and system flaws in a timely manner. | |
| ID.RA-2 | 3.14.3 | Monitor system security alerts and advisories and take actions in response. | |
| ID.RA-3 | 3.11.1 | Periodically assess the risk to organizational operations (including mission, functions, image, or reputation), organizational assets, and individuals, resulting from the operation of organizational systems and the associated processing, storage, or transmission of CUI. | |
| ID.RA-3 | 3.14.1 | Identify, report, and correct information and system flaws in a timely manner. | |
| ID.RA-3 | 3.14.3 | Monitor system security alerts and advisories and take actions in response. | |
| ID.RA-4 | 3.11.1 | Periodically assess the risk to organizational operations (including mission, functions, image, or reputation), organizational assets, and individuals, resulting from the operation of organizational systems and the associated processing, storage, or transmission of CUI. | |
| ID.RA-5 | 3.11.1 | Periodically assess the risk to organizational operations (including mission, functions, image, or reputation), organizational assets, and individuals, resulting from the operation of organizational systems and the associated processing, storage, or transmission of CUI. | |
| ID.RA-6 | No mapping; see Mapping Disclaimer. | ||
| ID.RM-1 | No mapping; see Mapping Disclaimer. | ||
| ID.RM-2 | No mapping; see Mapping Disclaimer. | ||
| ID.RM-3 | No mapping; see Mapping Disclaimer. | ||
| PR.AC-1 | 3.5.1 | Identify system users, processes acting on behalf of users, and devices. | |
| PR.AC-1 | 3.5.2 | Authenticate (or verify) the identities of those users, processes, or devices, as a prerequisite to allowing access to organizational systems. | |
| PR.AC-1 | 3.5.5 | Prevent reuse of identifiers for a defined period. | |
| PR.AC-1 | 3.5.6 | Disable identifiers after a defined period of inactivity. | |
| PR.AC-1 | 3.5.7 | Enforce a minimum password complexity and change of characters when new passwords are created. | |
| PR.AC-1 | 3.5.8 | Prohibit password reuse for a specified number of generations. | |
| PR.AC-1 | 3.5.9 | Allow temporary password use for system logons with an immediate change to a permanent password. | |
| PR.AC-1 | 3.5.10 | Store and transmit only cryptographically-protected passwords. | |
| PR.AC-1 | 3.5.11 | Obscure feedback of authentication information. | |
| PR.AC-2 | 3.10.1 | Limit physical access to organizational systems, equipment, and the respective operating environments to authorized individuals. | |
| PR.AC-2 | 3.10.2 | Protect and monitor the physical facility and support infrastructure for organizational systems. | |
| PR.AC-2 | 3.10.3 | Escort visitors and monitor visitor activity. | |
| PR.AC-2 | 3.10.4 | Maintain audit logs of physical access. | |
| PR.AC-2 | 3.10.5 | Control and manage physical access devices. | |
| PR.AC-3 | 3.1.1 | Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems). | |
| PR.AC-3 | 3.1.2 | Limit system access to the types of transactions and functions that authorized users are permitted to execute. | |
| PR.AC-3 | 3.1.14 | Route remote access via managed access control points. | |
| PR.AC-3 | 3.1.15 | Authorize remote execution of privileged commands and remote access to security-relevant information. | |
| PR.AC-3 | 3.1.18 | Control connection of mobile devices. | |
| PR.AC-3 | 3.1.20 | Verify and control/limit connections to and use of external systems. | |
| PR.AC-3 | 3.13.9 | Terminate network connections associated with communications sessions at the end of the sessions or after a defined period of inactivity. | |
| PR.AC-3 | 3.13.12 | Prohibit remote activation of collaborative computing devices and provide indication of devices in use to users present at the device. | |
| PR.AC-4 | 3.1.1 | Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems). | |
| PR.AC-4 | 3.1.2 | Limit system access to the types of transactions and functions that authorized users are permitted to execute. | |
| PR.AC-4 | 3.1.4 | Separate the duties of individuals to reduce the risk of malevolent activity without collusion. | |
| PR.AC-4 | 3.1.5 | Employ the principle of least privilege, including for specific security functions and privileged accounts. | |
| PR.AC-4 | 3.1.6 | Use non-privileged accounts or roles when accessing nonsecurity functions. | |
| PR.AC-4 | 3.1.7 | Prevent non-privileged users from executing privileged functions and audit the execution of such functions. | |
| PR.AC-4 | 3.1.8 | Limit unsuccessful logon attempts. | |
| PR.AC-4 | 3.1.10 | Use session lock with pattern-hiding displays to prevent access and viewing of data after period of inactivity. | |
| PR.AC-4 | 3.1.11 | Terminate (automatically) a user session after a defined condition. | |
| PR.AC-4 | 3.5.3 | Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts. | |
| PR.AC-4 | 3.5.4 | Employ replay-resistant authentication mechanisms for network access to privileged and non-privileged accounts. | |
| PR.AC-4 | 3.13.3 | Separate user functionality from system management functionality. | |
| PR.AC-4 | 3.13.4 | Prevent unauthorized and unintended information transfer via shared system resources. | |
| PR.AC-5 | 3.1.3 | Control the flow of CUI in accordance with approved authorizations. | |
| PR.AC-5 | 3.13.1 | Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems. | |
| PR.AC-5 | 3.13.2 | Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems. | |
| PR.AC-5 | 3.13.5 | Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. | |
| PR.AC-5 | 3.13.6 | Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception). | |
| PR.AC-5 | 3.13.7 | Prevent remote devices from simultaneously establishing non-remote connections with organizational systems and communicating via some other connection to resources in external networks. (i.e. split tunneling). | |
| PR.AT-1 | 3.2.1 | Ensure that managers, systems administrators, and users of organizational systems are made aware of the security risks associated with their activities and of the applicable policies, standards, and procedures related to the security of those systems. | |
| PR.AT-1 | 3.2.2 | Ensure that organizational personnel are adequately trained to carry out their assigned information security-related duties and responsibilities. | |
| PR.AT-1 | 3.2.3 | Provide security awareness training on recognizing and reporting potential indicators of insider threat. | |
| PR.AT-2 | 3.2.1 | Ensure that managers, systems administrators, and users of organizational systems are made aware of the security risks associated with their activities and of the applicable policies, standards, and procedures related to the security of those systems. | |
| PR.AT-2 | 3.2.2 | Ensure that organizational personnel are adequately trained to carry out their assigned information security-related duties and responsibilities. | |
| PR.AT-3 | No mapping; see Mapping Disclaimer. | ||
| PR.AT-4 | 3.2.1 | Ensure that managers, systems administrators, and users of organizational systems are made aware of the security risks associated with their activities and of the applicable policies, standards, and procedures related to the security of those systems. | |
| PR.AT-4 | 3.2.2 | Ensure that organizational personnel are adequately trained to carry out their assigned information security-related duties and responsibilities. | |
| PR.AT-5 | 3.2.1 | Ensure that managers, systems administrators, and users of organizational systems are made aware of the security risks associated with their activities and of the applicable policies, standards, and procedures related to the security of those systems. | |
| PR.AT-5 | 3.2.2 | Ensure that organizational personnel are adequately trained to carry out their assigned information security-related duties and responsibilities. | |
| PR.DS-1 | 3.1.19 | Encrypt CUI on mobile devices and mobile computing platforms. | |
| PR.DS-1 | 3.8.1 | Protect (i.e., physically control and securely store) system media containing CUI, both paper and digital. | |
| PR.DS-1 | 3.8.9 | Protect the confidentiality of backup CUI at storage locations. | |
| PR.DS-1 | 3.13.10 | Establish and manage cryptographic keys for cryptography employed in organizational systems. | |
| PR.DS-1 | 3.13.16 | Protect the confidentiality of CUI at rest. | |
| PR.DS-2 | 3.1.13 | Employ cryptographic mechanisms to protect the confidentiality of remote access sessions. | |
| PR.DS-2 | 3.1.17 | Protect wireless access using authentication and encryption. | |
| PR.DS-2 | 3.8.5 | Control access to media containing CUI and maintain accountability for media during transport outside of controlled areas. | |
| PR.DS-2 | 3.13.8 | Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards. | |
| PR.DS-2 | 3.13.10 | Establish and manage cryptographic keys for cryptography employed in organizational systems. | |
| PR.DS-3 | 3.4.1 | Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles. | |
| PR.DS-3 | 3.8.1 | Protect (i.e., physically control and securely store) system media containing CUI, both paper and digital. | |
| PR.DS-3 | 3.8.2 | Limit access to CUI on system media to authorized users. | |
| PR.DS-3 | 3.8.3 | Sanitize or destroy system media containing CUI before disposal or release for reuse. | |
| PR.DS-3 | 3.8.5 | Control access to media containing CUI and maintain accountability for media during transport outside of controlled areas. | |
| PR.DS-4 | No mapping; see Mapping Disclaimer. | ||
| PR.DS-5 | 3.1.4 | Separate the duties of individuals to reduce the risk of malevolent activity without collusion. | |
| PR.DS-5 | 3.1.13 | Employ cryptographic mechanisms to protect the confidentiality of remote access sessions. | |
| PR.DS-5 | 3.2.3 | Provide security awareness training on recognizing and reporting potential indicators of insider threat. | |
| PR.DS-5 | 3.9.2 | Ensure that CUI and organizational systems containing CUI are protected during and after personnel actions such as terminations and transfers. | |
| PR.DS-5 | 3.13.1 | Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems. | |
| PR.DS-5 | 3.13.5 | Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. | |
| PR.DS-5 | 3.13.6 | Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception). | |
| PR.DS-5 | 3.13.7 | Prevent remote devices from simultaneously establishing non-remote connections with organizational systems and communicating via some other connection to resources in external networks. (i.e. split tunneling). | |
| PR.DS-5 | 3.13.8 | Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards. | |
| PR.DS-5 | 3.13.11 | Employ FIPS-validated cryptography when used to protect the confidentiality of CUI. | |
| PR.DS-5 | 3.13.16 | Protect the confidentiality of CUI at rest. | |
| PR.DS-5 | 3.14.6 | Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks. | |
| PR.DS-6 | No mapping; see Mapping Disclaimer. | ||
| PR.DS-7 | No mapping; see Mapping Disclaimer. | ||
| PR.IP-1 | 3.4.1 | Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles. | |
| PR.IP-1 | 3.4.2 | Establish and enforce security configuration settings for information technology products employed in organizational systems. | |
| PR.IP-1 | 3.4.6 | Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities. | |
| PR.IP-1 | 3.4.7 | Restrict, disable, and prevent the use of nonessential, functions, ports, protocols, or services. | |
| PR.IP-1 | 3.4.8 | Apply deny-by-exception (blacklist) policy to prevent the use of unauthorized software or deny- all, permit-by-exception (whitelisting) policy to allow the execution of authorized software. | |
| PR.IP-2 | No mapping; see Mapping Disclaimer. | ||
| PR.IP-3 | 3.4.3 | Track, review, approve or disapprove, and audit changes to organizational systems. | |
| PR.IP-3 | 3.4.4 | Analyze the security impact of changes prior to implementation. | |
| PR.IP-3 | 3.4.5 | Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational system. | |
| PR.IP-4 | No mapping; see Mapping Disclaimer. | ||
| PR.IP-5 | No mapping; see Mapping Disclaimer. | ||
| PR.IP-6 | 3.8.3 | Sanitize or destroy system media containing CUI before disposal or release for reuse. | |
| PR.IP-7 | No mapping; see Mapping Disclaimer. | ||
| PR.IP-8 | No mapping; see Mapping Disclaimer. | ||
| PR.IP-9 | 3.6.1 | Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities. | |
| PR.IP-9 | 3.6.2 | Track, document, and report incidents to appropriate organizational officials and/or authorities. | |
| PR.IP-10 | 3.6.3 | Test the organizational incident response capability. | |
| PR.IP-11 | 3.9.1 | Screen individuals prior to authorizing access to organizational systems containing CUI. | |
| PR.IP-11 | 3.9.2 | Ensure that CUI and organizational systems containing CUI are protected during and after personnel actions such as terminations and transfers. | |
| PR.IP-12 | 3.11.2 | Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting the system are identified. | |
| PR.IP-12 | 3.11.3 | Remediate vulnerabilities in accordance with assessments of risk. | |
| PR.IP-12 | 3.12.2 | Develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems. | |
| PR.IP-12 | 3.12.3 | Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls. | |
| PR.IP-12 | 3.14.1 | Identify, report, and correct system flaws in a timely manner. | |
| PR.IP-12 | 3.14.2 | Provide protection from malicious code at appropriate locations within organizational systems. | |
| PR.IP-12 | 3.14.3 | Monitor system security alerts and advisories and take actions in response. | |
| PR.MA-1 | 3.7.1 | Perform maintenance on organizational systems. | |
| PR.MA-1 | 3.7.2 | Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance. | |
| PR.MA-1 | 3.7.3 | Ensure equipment removed for off-site maintenance is sanitized of any CUI. | |
| PR.MA-1 | 3.7.4 | Check media containing diagnostic and test programs for malicious code before the media are used in organizational systems. | |
| PR.MA-1 | 3.7.6 | Supervise the maintenance activities of maintenance personnel without required access authorization. | |
| PR.MA-2 | 3.7.5 | Require multifactor authentication to establish nonlocal maintenance sessions via external network connections and terminate such connections when nonlocal maintenance is complete. | |
| PR.PT-1 | 3.3.1 | Create and retain system audit records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful, unauthorized, or inappropriate system activity. | |
| PR.PT-1 | 3.3.2 | Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions. | |
| PR.PT-1 | 3.3.3 | Review and update audited events. | |
| PR.PT-1 | 3.3.4 | Alert in the event of an audit process failure. | |
| PR.PT-1 | 3.3.5 | Correlate audit review, analysis, and reporting processes for investigation and response to indications of inappropriate, suspicious, or unusual activity. | |
| PR.PT-1 | 3.3.6 | Provide audit reduction and report generation to support on-demand analysis and reporting. | |
| PR.PT-1 | 3.3.7 | Provide a system capability that compares and synchronizes internal system clocks with an authoritative source to generate time stamps for audit records. | |
| PR.PT-1 | 3.3.8 | Protect audit information and audit tools from unauthorized access, modification, and deletion. | |
| PR.PT-1 | 3.3.9 | Limit management of audit functionality to a subset of privileged users. | |
| PR.PT-2 | 3.8.1 | Protect (i.e., physically control and securely store) system media containing CUI, both paper and digital. | |
| PR.PT-2 | 3.8.2 | Limit access to CUI on system media to authorized users. | |
| PR.PT-2 | 3.8.3 | Sanitize or destroy system media containing CUI before disposal or release for reuse. | |
| PR.PT-2 | 3.8.4 | Mark media with necessary CUI markings and distribution limitations. | |
| PR.PT-2 | 3.8.5 | Control access to media containing CUI and maintain accountability for media during transport outside of controlled areas. | |
| PR.PT-2 | 3.8.6 | Implement cryptographic mechanisms to protect the confidentiality of CUI stored on digital media during transport outside of controlled areas unless otherwise protected by alternative physical safeguards. | |
| PR.PT-2 | 3.8.7 | Control the use of removable media on system components. | |
| PR.PT-2 | 3.8.8 | Prohibit the use of portable storage devices when such devices have no identifiable owner. | |
| PR.PT-3 | 3.1.1 | Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems). | |
| PR.PT-3 | 3.1.2 | Limit system access to the types of transactions and functions that authorized users are permitted to execute. | |
| PR.PT-3 | 3.4.6 | Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities. | |
| PR.PT-3 | 3.4.7 | Restrict, disable, and prevent the use of nonessential, functions, ports, protocols, or services. | |
| PR.PT-3 | 3.4.8 | Apply deny-by-exception (blacklist) policy to prevent the use of unauthorized software or deny- all, permit-by-exception (whitelisting) policy to allow the execution of authorized software. | |
| PR.PT-4 | 3.1.16 | Authorize wireless access prior to allowing such connections. | |
| PR.PT-4 | 3.1.17 | Protect wireless access using authentication and encryption. | |
| PR.PT-4 | 3.13.1 | Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems. | |
| PR.PT-4 | 3.13.2 | Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems. | |
| PR.PT-4 | 3.13.5 | Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. | |
| PR.PT-4 | 3.13.6 | Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception). | |
| PR.PT-4 | 3.13.7 | Prevent remote devices from simultaneously establishing non-remote connections with organizational systems and communicating via some other connection to resources in external networks. (i.e. split tunneling). | |
| PR.PT-4 | 3.13.15 | Protect the authenticity of communications sessions. | |
| DETECT (DE) | DE.AE-1 | No mapping; see Mapping Disclaimer. | |
| DE.AE-2 | 3.3.1 | Create and retain system audit records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful, unauthorized, or inappropriate system activity. | |
| DE.AE-2 | 3.3.2 | Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions. | |
| DE.AE-2 | 3.3.5 | Correlate audit review, analysis, and reporting processes for investigation and response to indications of inappropriate, suspicious, or unusual activity. | |
| DE.AE-2 | 3.6.1 | Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities. | |
| DE.AE-2 | 3.14.6 | Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks. | |
| DE.AE-2 | 3.14.7 | Identify unauthorized use of organizational systems. | |
| DE.AE-3 | 3.3.5 | Correlate audit review, analysis, and reporting processes for investigation and response to indications of inappropriate, suspicious, or unusual activity. | |
| DE.AE-4 | 3.11.1 | Periodically assess the risk to organizational operations (including mission, functions, image, or reputation), organizational assets, and individuals, resulting from the operation of organizational systems and the associated processing, storage, or transmission of CUI. | |
| DE.AE-5 | 3.6.1 | Establish an operational incident-handling capability for organizational systems that includes adequate preparation, detection, analysis, containment, recovery, and user response activities. | |
| DE.AE-5 | 3.6.2 | Track, document, and report incidents to appropriate organizational officials and/or authorities. | |
| DE.CM-1 | 3.13.1 | Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems. | |
| DE.CM-1 | 3.14.6 | Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks. | |
| DE.CM-1 | 3.14.7 | Identify unauthorized use of organizational systems. | |
| DE.CM-2 | 3.10.2 | Protect and monitor the physical facility and support infrastructure for organizational systems. | |
| DE.CM-2 | 3.10.3 | Escort visitors and monitor visitor activity. | |
| DE.CM-3 | 3.1.12 | Monitor and control remote access sessions. | |
| DE.CM-3 | 3.3.1 | Create, protect, and retain system audit records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful, unauthorized, or inappropriate system activity. | |
| DE.CM-3 | 3.3.2 | Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions. | |
| DE.CM-3 | 3.4.9 | Control and monitor user-installed software. | |
| DE.CM-4 | 3.14.1 | Identify, report, and correct system flaws in a timely manner. | |
| DE.CM-4 | 3.14.2 | Provide protection from malicious code at appropriate locations within organizational systems. | |
| DE.CM-4 | 3.14.3 | Monitor system security alerts and advisories and take actions in response. | |
| DE.CM-4 | 3.14.4 | Update malicious code protection mechanisms when new releases are available. | |
| DE.CM-4 | 3.14.5 | Perform periodic scans of organizational systems and real-time scans of files from external sources as files are downloaded, opened, or executed. | |
| DE.CM-5 | 3.13.13 | Control and monitor the use of mobile code. | |
| DE.CM-6 | 3.14.6 | Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks. | |
| DE.CM-6 | 3.14.7 | Identify unauthorized use of organizational systems. | |
| DE.CM-7 | 3.1.12 | Monitor and control remote access sessions. | |
| DE.CM-7 | 3.3.1 | Create, protect, and retain system audit records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful, unauthorized, or inappropriate system activity. | |
| DE.CM-7 | 3.10.2 | Protect and monitor the physical facility and support infrastructure for organizational systems. | |
| DE.CM-7 | 3.10.3 | Escort visitors and monitor visitor activity. | |
| DE.CM-7 | 3.14.6 | Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks. | |
| DE.CM-7 | 3.14.7 | Identify unauthorized use of organizational systems. | |
| DE.CM-8 | 3.11.2 | Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting the system are identified. | |
| DE.DP-1 | No mapping; see Mapping Disclaimer. | ||
| DE.DP-2 | 3.12.1 | Periodically assess the security controls in organizational systems to determine if the controls are effective in their application. | |
| DE.DP-2 | 3.12.3 | Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls. | |
| DE.DP-2 | 3.14.6 | Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks. | |
| DE.DP-2 | 3.14.7 | Identify unauthorized use of organizational systems. | |
| DE.DP-3 | 3.10.4 | Maintain audit logs of physical access. | |
| DE.DP-3 | 3.12.1 | Periodically assess the security controls in organizational systems to determine if the controls are effective in their application. | |
| DE.DP-3 | 3.12.3 | Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls. | |
| DE.DP-4 | No mapping; see Mapping Disclaimer. | ||
| DE.DP-5 | No mapping; see Mapping Disclaimer. | ||
| RS.RP-1 | 3.6.2 | Track, document, and report incidents to appropriate organizational officials and/or authorities. | |
| RS.CO-1 | 3.6.3 | Test the organizational incident response capability. | |
| RS.CO-2 | 3.6.2 | Track, document, and report incidents to appropriate organizational officials and/or authorities. | |
| RS.CO-3 | No mapping; see Mapping Disclaimer. | ||
| RS.CO-4 | 3.6.1 | Establish an operational incident-handling capability for organizational systems that includes adequate preparation, detection, analysis, containment, recovery, and user response activities. | |
| RS.CO-5 | No mapping; see Mapping Disclaimer. | ||
| RS.AN-1 | 3.3.5 | Correlate audit review, analysis, and reporting processes for investigation and response to indications of inappropriate, suspicious, or unusual activity. | |
| RS.AN-1 | 3.6.1 | Establish an operational incident-handling capability for organizational systems that includes adequate preparation, detection, analysis, containment, recovery, and user response activities. | |
| RS.AN-1 | 3.6.2 | Track, document, and report incidents to appropriate organizational officials and/or authorities. | |
| RS.AN-2 | 3.11.1 | Periodically assess the risk to organizational operations (including mission, functions, image, or reputation), organizational assets, and individuals, resulting from the operation of organizational systems and the associated processing, storage, or transmission of CUI. | |
| RS.AN-3 | No mapping; see Mapping Disclaimer. | ||
| RS.AN-4 | 3.6.1 | Establish an operational incident-handling capability for organizational systems that includes adequate preparation, detection, analysis, containment, recovery, and user response activities. | |
| RS.AN-4 | 3.6.2 | Track, document, and report incidents to appropriate organizational officials and/or authorities. | |
| RS.MI-1 | 3.6.1 | Establish an operational incident-handling capability for organizational systems that includes adequate preparation, detection, analysis, containment, recovery, and user response activities. | |
| RS.MI-1 | 3.6.2 | Track, document, and report incidents to appropriate organizational officials and/or authorities. | |
| RS.MI-2 | 3.6.1 | Establish an operational incident-handling capability for organizational systems that includes adequate preparation, detection, analysis, containment, recovery, and user response activities. | |
| RS.MI-2 | 3.6.2 | Track, document, and report incidents to appropriate organizational officials and/or authorities. | |
| RS.MI-3 | 3.11.1 | Periodically assess the risk to organizational operations (including mission, functions, image, or reputation), organizational assets, and individuals, resulting from the operation of organizational systems and the associated processing, storage, or transmission of CUI. | |
| RS.MI-3 | 3.11.2 | Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting the system are identified. | |
| RS.MI-3 | 3.11.3 | Remediate vulnerabilities in accordance with assessments of risk. | |
| RS.MI-3 | 3.12.2 | Develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems. | |
| RS.MI-3 | 3.12.4 | Develop, document, and periodically update system security plans that describe system boundaries, system environments of operation, how security requirements are implemented, and the relationships with or connections to other systems. | |
| RS.MI-3 | 3.14.1 | Identify, report, and correct information and system flaws in a timely manner. | |
| RS.IM-1 | 3.6.1 | Establish an operational incident-handling capability for organizational systems that includes adequate preparation, detection, analysis, containment, recovery, and user response activities. | |
| RS.IM-1 | 3.6.2 | Track, document, and report incidents to appropriate organizational officials and/or authorities. | |
| RS.IM-2 | 3.6.2 | Track, document, and report incidents to appropriate organizational officials and/or authorities. | |
| RC.RP-1 | 3.6.1 | Establish an operational incident-handling capability for organizational systems that includes adequate preparation, detection, analysis, containment, recovery, and user response activities. | |
| RC.RP-1 | 3.6.2 | Track, document, and report incidents to appropriate organizational officials and/or authorities. | |
| RC.IM-1 | 3.6.1 | Establish an operational incident-handling capability for organizational systems that includes adequate preparation, detection, analysis, containment, recovery, and user response activities. | |
| RC.IM-1 | 3.6.2 | Track, document, and report incidents to appropriate organizational officials and/or authorities. | |
| RC.IM-2 | 3.6.1 | Establish an operational incident-handling capability for organizational systems that includes adequate preparation, detection, analysis, containment, recovery, and user response activities. | |
| RC.IM-2 | 3.6.2 | Track, document, and report incidents to appropriate organizational officials and/or authorities. | |
| RC.CO-1 | No mapping; see Mapping Disclaimer. | ||
| RC.CO-2 | No mapping; see Mapping Disclaimer. | ||
| RC.CO-3 | 3.6.1 | Establish an operational incident-handling capability for organizational systems that includes adequate preparation, detection, analysis, containment, recovery, and user response activities. | |
| RC.CO-3 | 3.6.2 | Track, document, and report incidents to appropriate organizational officials and/or authorities. |
File details come from the government source that posted it. Updated .