|AC.L1-b.1.i||1||Access Control||Authorized Access Control (FCI)|
Limit information system access to authorized users, processes acting on behalf of authorized users, or devices (including other information systems).
|AC.L1-b.1.ii||1||Access Control||Transaction & Function Control (FCI)|
Limit information system access to the types of transactions and functions that authorized users are permitted to execute.
|AC.L1-b.1.iii||1||Access Control||External Connections (FCI)|
Verify and control/limit connections to and use of external information systems.
|AC.L1-b.1.iv||1||Access Control||Control Public Information (FCI)|
Control information posted or processed on publicly accessible information systems.
|IA.L1-b.1.v||1||Identification and Authentication||Identification (FCI)|
Identify information system users, processes acting on behalf of users, or devices.
|IA.L1-b.1.vi||1||Identification and Authentication||Authentication (FCI)|
Authenticate (or verify) the identities of those users, processes, or devices, as a prerequisite to allowing access to organizational information systems.
|MP.L1-b.1.vii||1||Media Protection||Media Disposal (FCI)|
Sanitize or destroy information system media containing Federal Contract Information before disposal or release for reuse.
|PE.L1-b.1.ix||1||Physical Protection||Manage Visitors & Physical Access (FCI)|
Escort visitors and monitor visitor activity; maintain audit logs of physical access; and control and manage physical access devices.
|PE.L1-b.1.viii||1||Personnel Security||Limit Physical Access (FCI)|
Limit physical access to organizational information systems, equipment, and the respective operating environments to authorized individuals.
|SC.L1-b.1.x||1||System and Communications Protection||Boundary Protection (FCI)|
Monitor, control, and protect organizational communications (i.e., information transmitted or received by organizational information systems) at the external boundaries and key internal boundaries of the information systems.
|SC.L1-b.1.xi||1||System and Communications Protection||Public-Access System Separation (FCI)|
Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.
|SI.L1-b.1.xii||1||System and Information Integrity||Flaw Remediation (FCI)|
Identify, report, and correct information and information system flaws in a timely manner.
|SI.L1-b.1.xiii||1||System and Information Integrity||Malicious Code Protection (FCI)|
Provide protection from malicious code at appropriate locations within organizational information systems.
|SI.L1-b.1.xiv||1||Access Control||Update Malicious Code Protection (FCI)|
Update malicious code protection mechanisms when new releases are available.
|SI.L1-b.1.xv||1||System and Information Integrity||System & File Scanning (FCI)|
Perform periodic scans of the information system and real-time scans of files from external sources as files are downloaded, opened, or executed.
|AC.L2-3.1.1||2||Access Control||Authorized Access Control (CUI)|
Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems).
|AC.L2-3.1.2||2||Access Control||Transaction & Function Control|
Limit system access to the types of transactions and functions that authorized users are permitted to execute.
|AC.L2-3.1.3||2||Access Control||Control CUI Flow|
Control the flow of CUI in accordance with approved authorizations.
|AC.L2-3.1.4||2||Access Control||Separation of Duties|
Separate the duties of individuals to reduce the risk of malevolent activity without collusion.
|AC.L2-3.1.5||2||Access Control||Least Privilege|
Employ the principle of least privilege, including for specific security functions and privileged accounts.
|AC.L2-3.1.6||2||Access Control||Non-Privileged Account Use|
Use non-privileged accounts or roles when accessing nonsecurity functions.
|AC.L2-3.1.7||2||Access Control||Privileged Functions|
Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs.
|AC.L2-3.1.8||2||Access Control||Unsuccessful Logon Attempts|
Limit unsuccessful logon attempts.
|AC.L2-3.1.9||2||Access Control||Privacy & Security Notices|
Provide privacy and security notices consistent with applicable CUI rules.
|AC.L2-3.1.10||2||Access Control||Session Lock|
Use session lock with pattern-hiding displays to prevent access and viewing of data after a period of inactivity.
|AC.L2-3.1.11||2||Access Control||Session Termination|
Terminate (automatically) a user session after a defined condition.
|AC.L2-3.1.12||2||Access Control||Control Remote Access|
Monitor and control remote access sessions.
|AC.L2-3.1.13||2||Access Control||Remote Access Confidentiality|
Employ cryptographic mechanisms to protect the confidentiality of remote access sessions.
|AC.L2-3.1.14||2||Access Control||Remote Access Routing|
Route remote access via managed access control points.
|AC.L2-3.1.15||2||Access Control||Privileged Remote Access|
Authorize remote execution of privileged commands and remote access to security-relevant information.
|AC.L2-3.1.16||2||Access Control||Wireless Access Authorization|
Authorize wireless access prior to allowing such connections.
|AC.L2-3.1.17||2||Access Control||Wireless Access Protection|
Protect wireless access using authentication and encryption.
|AC.L2-3.1.18||2||Access Control||Mobile Device Connection|
Control connection of mobile devices.
|AC.L2-3.1.19||2||Access Control||Encrypt CUI on Mobile|
Encrypt CUI on mobile devices and mobile computing platforms.
|AC.L2-3.1.20||2||Access Control||External Connections|
Verify and control/limit connections to and use of external systems.
|AC.L2-3.1.21||2||Access Control||Portable Storage Use|
Limit use of portable storage devices on external systems.
|AC.L2-3.1.22||2||Access Control||Control Public Information|
Control CUI posted or processed on publicly accessible systems.
|AT.L2-3.2.1||2||Awareness and Training||Role-Based Risk Awareness|
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.
|AT.L2-3.2.2||2||Awareness and Training||Role-Based Training|
Ensure that personnel are trained to carry out their assigned information security-related duties and responsibilities.
|AT.L2-3.2.3||2||Awareness and Training||Insider Threat Awareness|
Provide security awareness training on recognizing and reporting potential indicators of insider threat.
|AU.L2-3.3.1||2||Audit and Accountability||System Auditing|
Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity.
|AU.L2-3.3.2||2||Audit and Accountability||User Accountability|
Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions.
|AU.L2-3.3.3||2||Audit and Accountability||Event Review|
Review and update logged events.
|AU.L2-3.3.4||2||Audit and Accountability||Audit Failure Alerting|
Alert in the event of an audit logging process failure.
|AU.L2-3.3.5||2||Audit and Accountability||Audit Correlation|
Correlate audit record review, analysis, and reporting processes for investigation and response to indications of unlawful, unauthorized, suspicious, or unusual activity.
|AU.L2-3.3.6||2||Audit and Accountability||Reduction & Reporting|
Provide audit record reduction and report generation to support on-demand analysis and reporting.
|AU.L2-3.3.7||2||Audit and Accountability||Authoritative Time Source|
Provide a system capability that compares and synchronizes internal system clocks with an authoritative source to generate time stamps for audit records.
|AU.L2-3.3.8||2||Audit and Accountability||Audit Protection|
Protect audit information and audit logging tools from unauthorized access, modification, and deletion.
|AU.L2-3.3.9||2||Audit and Accountability||Audit Management|
Limit management of audit logging functionality to a subset of privileged users.
|CA.L2-3.12.1||2||Security Assessment||Security Control Assessment|
Periodically assess the security controls in organizational systems to determine if the controls are effective in their application.
|CA.L2-3.12.2||2||Security Assessment||Plan of Action|
Develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems.
|CA.L2-3.12.3||2||Security Assessment||Security Control Monitoring|
Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls.
|CA.L2-3.12.4||2||Security Assessment||System Security Plan|
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.
|CM.L2-3.4.1||2||Configuration Management||System Baselining|
Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles.
|CM.L2-3.4.2||2||Configuration Management||Security Configuration Enforcement|
Establish and enforce security configuration settings for information technology products employed in organizational systems.
|CM.L2-3.4.3||2||Configuration Management||System Change Management|
Track, review, approve or disapprove, and log changes to organizational systems.
|CM.L2-3.4.4||2||Configuration Management||Security Impact Analysis|
Analyze the security impact of changes prior to implementation.
|CM.L2-3.4.5||2||Configuration Management||Access Restrictions for Change|
Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems.
|CM.L2-3.4.6||2||Configuration Management||Least Functionality|
Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities.
|CM.L2-3.4.7||2||Configuration Management||Nonessential Functionality|
Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.
|CM.L2-3.4.8||2||Configuration Management||Application Execution Policy|
Apply deny-by-exception (blacklisting) policy to prevent the use of unauthorized software or deny-all, permit-by-exception (whitelisting) policy to allow the execution of authorized software.
|CM.L2-3.4.9||2||Configuration Management||User-Installed Software|
Control and monitor user-installed software.
|IA.L2-3.5.1||2||Identification and Authentication||Identification|
Identify system users, processes acting on behalf of users, and devices.
|IA.L2-3.5.2||2||Identification and Authentication||Authentication|
Authenticate (or verify) the identities of users, processes, or devices, as a prerequisite to allowing access to organizational systems.
|IA.L2-3.5.3||2||Identification and Authentication||Multifactor Authentication|
Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts.
|IA.L2-3.5.4||2||Identification and Authentication||Replay-Resistant Authentication|
Employ replay-resistant authentication mechanisms for network access to privileged and non-privileged accounts.
|IA.L2-3.5.5||2||Identification and Authentication||Identifier Reuse|
Prevent reuse of identifiers for a defined period.
|IA.L2-3.5.6||2||Identification and Authentication||Identifier Handling|
Disable identifiers after a defined period of inactivity.
|IA.L2-3.5.7||2||Identification and Authentication||Password Complexity|
Enforce a minimum password complexity and change of characters when new passwords are created.
|IA.L2-3.5.8||2||Identification and Authentication||Password Reuse|
Prohibit password reuse for a specified number of generations.
|IA.L2-3.5.9||2||Identification and Authentication||Temporary Passwords|
Allow temporary password use for system logons with an immediate change to a permanent password.
|IA.L2-3.5.10||2||Identification and Authentication||Cryptographically-Protected Passwords|
Store and transmit only cryptographically-protected passwords.
|IA.L2-3.5.11||2||Identification and Authentication||Obscure Feedback|
Obscure feedback of authentication information.
|IR.L2-3.6.1||2||Incident response||Incident Handling|
Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities.
|IR.L2-3.6.2||2||Incident response||Incident Reporting|
Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization.
|IR.L2-3.6.3||2||Incident response||Incident Response Testing|
Test the organizational incident response capability.
Perform maintenance on organizational systems.
|MA.L2-3.7.2||2||Maintenance||System Maintenance Control|
Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance.
Ensure equipment removed for off-site maintenance is sanitized of any CUI.
Check media containing diagnostic and test programs for malicious code before the media are used in organizational systems.
Require multifactor authentication to establish nonlocal maintenance sessions via external network connections and terminate such connections when nonlocal maintenance is complete.
Supervise the maintenance activities of maintenance personnel without required access authorization.
|MP.L2-3.8.1||2||Media Protection||Media Protection|
Protect (i.e., physically control and securely store) system media containing CUI, both paper and digital.
|MP.L2-3.8.2||2||Media Protection||Media Access|
Limit access to CUI on system media to authorized users.
|MP.L2-3.8.3||2||Media Protection||Media Disposal|
Sanitize or destroy system media containing CUI before disposal or release for reuse.
|MP.L2-3.8.4||2||Media Protection||Media Markings|
Mark media with necessary CUI markings and distribution limitations.
|MP.L2-3.8.5||2||Media Protection||Media Accountability|
Control access to media containing CUI and maintain accountability for media during transport outside of controlled areas.
|MP.L2-3.8.6||2||Media Protection||Portable Storage Encryption|
Implement cryptographic mechanisms to protect the confidentiality of CUI stored on digital media during transport unless otherwise protected by alternative physical safeguards.
|MP.L2-3.8.7||2||Media Protection||Removable Media|
Control the use of removable media on system components.
|MP.L2-3.8.8||2||Media Protection||Shared Media|
Prohibit the use of portable storage devices when such devices have no identifiable owner.
|MP.L2-3.8.9||2||Media Protection||Protect Backups|
Protect the confidentiality of backup CUI at storage locations.
|PE.L2-3.10.1||2||Physical Protection||Limit Physical Access (CUI)|
Limit physical access to organizational systems, equipment, and the respective operating environments to authorized individuals.
|PE.L2-3.10.2||2||Physical Protection||Monitor Facility|
Protect and monitor the physical facility and support infrastructure for organizational systems.
|PE.L2-3.10.3||2||Physical Protection||Escort Visitors (CUI)|
Escort visitors and monitor visitor activity.
|PE.L2-3.10.4||2||Physical Protection||Physical Access Logs (CUI)|
Maintain audit logs of physical access.
|PE.L2-3.10.5||2||Physical Protection||Manage Physical Access (CUI)|
Control and manage physical access devices.
|PE.L2-3.10.6||2||Physical Protection||Alternative Work Sites|
Enforce safeguarding measures for CUI at alternate work sites.
|PS.L2-3.9.1||2||Personnel Security||Screen Individuals|
Screen individuals prior to authorizing access to organizational systems containing CUI.
|PS.L2-3.9.2||2||Personnel Security||Personnel Actions|
Ensure that organizational systems containing CUI are protected during and after personnel actions such as terminations and transfers.
|RA.L2-3.11.1||2||Risk Assessment||Risk Assessments|
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.
|RA.L2-3.11.2||2||Risk Assessment||Vulnerability Scan|
Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified.
|RA.L2-3.11.3||2||Risk Assessment||Vulnerability Remediation|
Remediate vulnerabilities in accordance with risk assessments.
|SC.L2-3.13.1||2||System and Communications Protection||Boundary Protection (CUI)|
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.
|SC.L2-3.13.2||2||System and Communications Protection||Security Engineering|
Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.
|SC.L2-3.13.3||2||System and Communications Protection||Role Separation|
Separate user functionality from system management functionality.
|SC.L2-3.13.4||2||System and Communications Protection||Shared Resource Control|
Prevent unauthorized and unintended information transfer via shared system resources.
|SC.L2-3.13.5||2||System and Communications Protection||Public-Access System Separation (CUI)|
Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.
|SC.L2-3.13.6||2||System and Communications Protection||Network Communication by Exception|
Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception).
|SC.L2-3.13.7||2||System and Communications Protection||Split Tunneling|
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).
|SC.L2-3.13.8||2||System and Communications Protection||Data in Transit|
Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards.
|SC.L2-3.13.9||2||System and Communications Protection||Connections Termination|
Terminate network connections associated with communications sessions at the end of the sessions or after a defined period of inactivity.
|SC.L2-3.13.10||2||System and Communications Protection||Key Management|
Establish and manage cryptographic keys for cryptography employed in organizational systems.
|SC.L2-3.13.11||2||System and Communications Protection||CUI Encryption|
Employ FIPS-validated cryptography when used to protect the confidentiality of CUI.
|SC.L2-3.13.12||2||System and Communications Protection||Collaborative Device Control|
Prohibit remote activation of collaborative computing devices and provide indication of devices in use to users present at the device.
|SC.L2-3.13.13||2||System and Communications Protection||Mobile Code|
Control and monitor the use of mobile code.
|SC.L2-3.13.14||2||System and Communications Protection||Voice over Internet Protocol|
Control and monitor the use of Voice over Internet Protocol (VoIP) technologies.
|SC.L2-3.13.15||2||System and Communications Protection||Communications Authenticity|
Protect the authenticity of communications sessions.
|SC.L2-3.13.16||2||System and Communications Protection||Data at Rest|
Protect the confidentiality of CUI at rest.
|SI.L2-3.14.1||2||System and Information Integrity||Flaw Remediation (CUI)|
Identify, report, and correct system flaws in a timely manner.
|SI.L2-3.14.2||2||System and Information Integrity||Malicious Code Protection (CUI)|
Provide protection from malicious code at designated locations within organizational systems.
|SI.L2-3.14.3||2||System and Information Integrity||Security Alerts & Advisories|
Monitor system security alerts and advisories and take action in response.
|SI.L2-3.14.4||2||System and Information Integrity||Update Malicious Code Protection (CUI)|
Update malicious code protection mechanisms when new releases are available.
|SI.L2-3.14.5||2||System and Information Integrity||System & File Scanning (CUI)|
Perform periodic scans of organizational systems and real-time scans of files from external sources as files are downloaded, opened, or executed.
|SI.L2-3.14.6||2||System and Information Integrity||Monitor Communications for Attacks|
Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks.
|SI.L2-3.14.7||2||System and Information Integrity||Identify Unauthorized Use|
Identify unauthorized use of organizational systems.
|AC.L3-3.1.2e||3||Access Control||Organizationally Controlled Assets|
Restrict access to systems and system components to only those information resources that are owned, provisioned, or issued by the organization.
|AC.L3-3.1.3e||3||Access Control||Secured Information Transfer|
Employ secure information transfer solutions to control information flows between security domains on connected systems.
|AT.L3-3.2.1e||3||Awareness and Training||Advanced Threat Awareness|
Provide awareness training upon initial hire, following a significant cyber event, and at least annually, focused on recognizing and responding to threats from social engineering, advanced persistent threat actors, breaches, and suspicious behaviors; update the training at least annually or when there are significant changes to the threat.
|AT.L3-3.2.2e||3||Awareness and Training||Practical Training Exercises|
Include practical exercises in awareness training for all users, tailored by roles, to include general users, users with specialized roles, and privileged users, that are aligned with current threat scenarios and provide feedback to individuals involved in the training and their supervisors.
|CA.L3-3.12.1e||3||Security Assessment||Penetration Testing|
Conduct penetration testing at least annually or when significant security changes are made to the system, leveraging automated scanning tools and ad hoc tests using subject matter experts.
|CM.L3-3.4.1e||3||Configuration Management||Authoritative Repository|
Establish and maintain an authoritative source and repository to provide a trusted source and accountability for approved and implemented system components.
|CM.L3-3.4.2e||3||Configuration Management||Automated Detection & Remediation|
Employ automated mechanisms to detect misconfigured or unauthorized system components; after detection, remove the components or place the components in a quarantine or remediation network to facilitate patching, re-configuration, or other mitigations.
|CM.L3-3.4.3e||3||Configuration Management||Automated Inventory|
Employ automated discovery and management tools to maintain an up-to-date, complete, accurate, and readily available inventory of system components.
|IA.L3-3.5.1e||3||Identification and Authentication||Bidirectional Authentication|
Identify and authenticate systems and system components, where possible, before establishing a network connection using bidirectional authentication that is cryptographically based and replay resistant.
|IA.L3-3.5.3e||3||Identification and Authentication||Block Untrusted Assets|
Employ automated or manual/procedural mechanisms to prohibit system components from connecting to organizational systems unless the components are known, authenticated, in a properly configured state, or in a trust profile.
|IR.L3-3.6.1e||3||Incident response||Security Operations Center|
Establish and maintain a security operations center capability that operates 24/7, with allowance for remote/on-call staff.
|IR.L3-3.6.2e||3||Incident response||Cyber Incident Response Team|
Establish and maintain a cyber incident response team that can be deployed by the organization within 24 hours.
|PS.L3-3.9.2e||3||Personnel Security||Adverse Information|
Ensure that organizational systems are protected if adverse information develops or is obtained about individuals with access to CUI.
|RA.L3-3.11.1e||3||Risk Assessment||Threat-Informed Risk Assessment|
Employ threat intelligence, at a minimum from open or commercial sources, and any DoD-provided sources, as part of a risk assessment to guide and inform the development of organizational systems, security architectures, selection of security solutions, monitoring, threat hunting, and response and recovery activities.
|RA.L3-3.11.2e||3||Risk Assessment||Threat Hunting|
Conduct cyber threat hunting activities on an on-going aperiodic basis or when indications warrant, to search for indicators of compromise in organizational systems and detect, track, and disrupt threats that evade existing controls.
|RA.L3-3.11.3e||3||Risk Assessment||Advanced Risk Identification|
Employ advanced automation and analytics capabilities in support of analysts to predict and identify risks to organizations, systems, and system components.
|RA.L3-3.11.4e||3||Risk Assessment||Security Solution Rationale|
Document or reference in the system security plan the security solution selected, the rationale for the security solution, and the risk determination.
|RA.L3-3.11.5e||3||Risk Assessment||Security Solution Effectiveness|
Assess the effectiveness of security solutions at least annually or upon receipt of relevant cyber threat information, or in response to a relevant cyber incident, to address anticipated risk to organizational systems and the organization based on current and accumulated threat intelligence.
|RA.L3-3.11.6e||3||Risk Assessment||Supply Chain Risk Response|
Assess, respond to, and monitor supply chain risks associated with organizational systems and system components.
|RA.L3-3.11.7e||3||Risk Assessment||Supply Chain Risk Plan|
Develop a plan for managing supply chain risks associated with organizational systems and system components; update the plan at least annually, and upon receipt of relevant cyber threat information, or in response to a relevant cyber incident.
|SC.L3-3.13.4e||3||System and Communications Protection||Isolation|
Employ physical isolation techniques or logical isolation techniques or both in organizational systems and system components.
|SI.L3-3.14.1e||3||System and Information Integrity||Integrity Verification|
Verify the integrity of security critical and essential software using root of trust mechanisms or cryptographic signatures.
|SI.L3-3.14.3e||3||System and Information Integrity||Specialized Asset Security|
Ensure that specialized assets including IoT, IIoT, OT, GFE, Restricted Information Systems and test equipment are included in the scope of the specified enhanced security requirements or are segregated in purpose-specific networks.
|SI.L3-3.14.6e||3||System and Information Integrity||Threat-Guided Intrusion Detection|
Use threat indicator information and effective mitigations obtained from, at a minimum, open or commercial sources, and any DoD-provided sources, to guide and inform intrusion detection and threat hunting.