CMMC Level 4

Domain AC: Access Control

Identify and control who and what has access to your systems.

AC.1.001
Limit information system access to authorized users, processes acting on behalf of authorized users, or devices (including other information systems).
AC.1.002
Limit information system access to the types of transactions and functions that authorized users are permitted to execute.
AC.1.003
Verify and control/limit connections to and use of external information systems.
AC.1.004
Control information posted or processed on publicly accessible information systems.
AC.2.005
Provide privacy and security notices consistent with applicable CUI rules.
AC.2.006
Limit use of portable storage devices on external systems.
AC.2.007
Employ the principle of least privilege, including for specific security functions and privileged accounts.
AC.2.008
Use non-privileged accounts or roles when accessing nonsecurity functions.
AC.2.009
Limit unsuccessful logon attempts.
AC.2.010
Use session lock with pattern-hiding displays to prevent access and viewing of data after a period of inactivity.
AC.2.011
Authorize wireless access prior to allowing such connections.
AC.3.012
Protect wireless access using authentication and encryption.
AC.2.013
Monitor and control remote access sessions.
AC.3.014
Employ cryptographic mechanisms to protect the confidentiality of remote access sessions.
AC.2.015
Route remote access via managed access control points.
AC.2.016
Control the flow of CUI in accordance with approved authorizations.
AC.3.017
Separate the duties of individuals to reduce the risk of malevolent activity without collusion.
AC.3.018
Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs.
AC.3.019
Terminate (automatically) user sessions after a defined condition.
AC.3.020
Control connection of mobile devices.
AC.3.021
Authorize remote execution of privileged commands and remote access to security-relevant information.
AC.3.022
Encrypt CUI on mobile devices and mobile computing platforms.
AC.4.023
Control information flows between security domains on connected systems.
AC.4.025
Periodically review and update CUI program access permissions.
AC.4.032
Restrict remote network access based on organizationally defined risk factors such as time of day, location of access, physical location, network connection state, and measured properties of the current user and role.

Domain AM: Asset Management

Managing all devices and services which store, process, transmit or access your data. These assets may be on your network, but they may hosted or in the cloud.

AM.3.036
Define procedures for the handling of CUI data.
AM.4.226
Employ a capability to discover and identify systems with specific component attributes (e.g., firmware level, OS type) within your inventory.

Domain AT: Awareness and Training

Establish a program to continuously educate your staff, vendors, and contractors about how you safeguard your data, and the threats you face.

AT.2.056
Ensure that managers, system 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.2.057
Ensure that personnel are trained to carry out their assigned information security-related duties and responsibilities.
AT.3.058
Provide security awareness training on recognizing and reporting potential indicators of insider threat.
AT.4.059
Provide awareness training 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.4.060
Include practical exercises in awareness training that are aligned with current threat scenarios and provide feedback to individuals involved in the training.

Domain AU: Audit and Accountability

Practices and capabilities which relate to creating, storing, and reviewing audit trails of user and system activity.

AU.2.041
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.2.042
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.2.043
Provide a system capability that compares and synchronizes internal system clocks with an authoritative source to generate time stamps for audit records.
AU.2.044
Review audit logs.
AU.3.045
Review and update logged events.
AU.3.046
Alert in the event of an audit logging process failure.
AU.3.048
Collect audit information (e.g., logs) into one or more central repositories.
AU.3.049
Protect audit information and audit logging tools from unauthorized access, modification, and deletion.
AU.3.050
Limit management of audit logging functionality to a subset of privileged users.
AU.3.051
Correlate audit record review, analysis, and reporting processes for investigation and response to indications of unlawful, unauthorized, suspicious, or unusual activity.
AU.3.052
Provide audit record reduction and report generation to support on-demand analysis and reporting.
AU.4.053
Automate analysis of audit logs to identify and act on critical indicators (TTPs) and/or organizationally defined suspicious activity.
AU.4.054
Review audit information for broad activity in addition to per-machine activity.

Domain CA: Security Assessment

The organization will need to periodically conduct assessments and tests to ensure that practices are in place and working as expected.

CA.2.157
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.
CA.2.158
Periodically assess the security controls in organizational systems to determine if the controls are effective in their application.
CA.2.159
Develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems.
CA.3.161
Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls.
CA.3.162
Employ a security assessment of enterprise software that has been developed internally, for internal use, and that has been organizationally defined as an area of risk.
CA.4.163
Create, maintain, and leverage a security roadmap for improvement.
CA.4.164
Conduct penetration testing periodically, leveraging automated scanning tools and ad hoc tests using human experts.
CA.4.227
Periodically perform red teaming against organizational assets in order to validate defensive capabilities.

Domain CM: Configuration Management

Implementing practices for creating standard configurations, approving changes, and monitoring for unapproved changes.

CM.2.061
Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles.
CM.2.062
Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities.
CM.2.063
Control and monitor user-installed software.
CM.2.064
Establish and enforce security configuration settings for information technology products employed in organizational systems.
CM.2.065
Track, review, approve, or disapprove, and log changes to organizational systems.
CM.2.066
Analyze the security impact of changes prior to implementation.
CM.3.067
Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems.
CM.3.068
Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.
CM.3.069
Apply deny-by-exception (deny-listing) policy to prevent the use of unauthorized software -OR- deny-all, permit-by-exception (allow-listing) policy to allow the execution of authorized software.
CM.4.073
Employ application whitelisting and an application vetting process for systems identified by the organization.

Domain IA: Identification and Authentication

Closely tied to Access Control, this Domain contains practices to ensure that only the person assigned to a user account is the one using it.

IA.1.076
Identify information system users, processes acting on behalf of users, or devices.
IA.1.077
Authenticate (or verify) the identities of those users, processes, or devices, as a prerequisite to allowing access to organizational information systems.
IA.2.078
Enforce a minimum password complexity and change of characters when new passwords are created.
IA.2.079
Prohibit password reuse for a specified number of generations.
IA.2.080
Allow temporary password use for system logons with an immediate change to a permanent password.
IA.2.081
Store and transmit only cryptographically-protected passwords.
IA.2.082
Obscure feedback of authentication information.
IA.3.083
Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts.
IA.3.084
Employ replay-resistant authentication mechanisms for network access to privileged and non-privileged accounts.
IA.3.085
Prevent the reuse of identifiers for a defined period.
IA.3.086
Disable identifiers after a defined period of inactivity.

Domain IR: Incident Response

Develop a plan to prepare for a security incident before it occurs.

IR.2.092
Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recover, and user response activities.
IR.2.093
Detect and report events.
IR.2.094
Analyze and triage events to support event resolution and incident declaration.
IR.2.096
Develop and implement responses to declared incidents according to predefined procedures.
IR.2.097
Perform root cause analysis on incidents to determine underlying causes.
IR.3.098
Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization.
IR.3.099
Test the organizational incident response capability.
IR.4.100
Use knowledge of attacker tactics, techniques, and procedures in incident response planning and execution.
IR.4.101
Establish and maintain a security operations center capability that facilitates a 24/7 response capability.

Domain MA: Maintenance

100% of computer systems will fail, eventually. These practices define a strategy to limit opportunities which may expose critical data and services to intentional, or unintentional, misconfiguration, malicious code, and outages.

MA.2.111
Perform maintenance on organizational systems.
MA.2.112
Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance.
MA.2.113
Require multifactor authentication to establish non-local maintenance sessions via external network connections and terminate such connections when nonlocal maintenance is complete.
MA.2.114
Supervise the maintenance activities of personnel without required access authorization.
MA.3.115
Ensure equipment removed for off-site maintenance is sanitized of any CUI.
MA.3.116
Check media containing diagnostic and test programs for malicious code before the media are used in organizational systems.

Domain MP: Media Protection

Safeguard data stored on removable media, such as a USB drive, or even on paper.

MP.1.118
Sanitize or destroy information system media containing Federal Contract Information before disposal or release for reuse.
MP.2.119
Protect (i.e., physically control and securely store) system media containing CUI, both paper and digital.
MP.2.120
Limit access to CUI on system media to authorized users.
MP.2.121
Control the use of removable media on system components.
MP.3.122
Mark media with necessary CUI markings and distribution limitations.
MP.3.123
Prohibit the use of portable storage devices when such devices have no identifiable owner.
MP.3.124
Control access to media containing CUI and maintain accountability for media during transport outside of controlled areas.
MP.3.125
Implement cryptographic mechanisms to protect the confidentiality of CUI stored on digital media during transport unless otherwise protected by alternative physical safeguards.

Domain PE: Physical Protection

You must protect physical access to your facility and data, as a breach of physical security can be used to quickly override logical security practices.

PE.1.131
Limit physical access to organizational information systems, equipment, and the respective operating environments to authorized individuals.
PE.1.132
Escort visitors and monitor visitor activity.
PE.1.133
Maintain audit logs of physical access.
PE.1.134
Control and manage physical access devices.
PE.2.135
Protect and monitor the physical facility and support infrastructure for organizational systems.
PE.3.136
Enforce safeguarding measures for CUI at alternate work sites.

Domain PS: Personnel Security

Practices for screening individuals before allowing access to systems, and protecting those systems when an individual is terminated or transferred.

PS.2.127
Screen individuals prior to authorizing access to organizational systems containing CUI.
PS.2.128
Ensure that organizational systems containing CUI are protected during and after personnel actions such as terminations and transfers.

Domain RE: Recovery

Practices to securely backup and protect your data.

RE.2.137
Regularly perform and test data backups.
RE.2.138
Protect the confidentiality of backup CUI at storage locations.
RE.3.139
Regularly perform complete, comprehensive, and resilient data backups, as organizationally defined.

Domain RM: Risk Management

Create practices to monitor, manage, and remediate risks to your systems and data.

RM.2.141
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.
RM.2.142
Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified.
RM.2.143
Remediate vulnerabilities in accordance with risk assessments.
RM.3.144
Periodically perform risk assessments to identify and prioritize risks according to the defined risk categories, risk sources, and risk measurement criteria.
RM.3.146
Develop and implement risk mitigation plans.
RM.3.147
Manage non-vendor-supported products (e.g., end of life) separately and restrict as necessary to reduce risk.
RM.4.148
Develop and update as required, a plan for managing supply chain risks associated with the IT supply chain.
RM.4.149
Catalog and periodically update threat profiles and adversary TTPs.
RM.4.150
Employ threat intelligence to inform the development of the system and security architectures, selection of security solutions, monitoring, threat hunting, and response and recovery activities.
RM.4.151
Perform scans for unauthorized ports available across perimeter network boundaries over the organization’s Internet network boundaries and other organizationally defined boundaries.

Domain SA: Situational Awareness

Practices for using threat monitoring and intelligence gathering from external data sources to inform and advance internal detection capabilities.

SA.3.169
Receive and respond to cyber threat intelligence from information sharing forums and sources and communicate to stakeholders.
SA.4.171
Establish and maintain a cyber-threat hunting capability to search for indicators of compromise in organizational systems and detect, track, and disrupt threats that evade existing controls.
SA.4.173
Design network and system security capabilities to leverage, integrate, and share indicators of compromise.

Domain SC: Systems and Communications Protection

Secure your network boundaries and communications.

SC.1.175
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 information systems.
SC.1.176
Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.
SC.3.177
Employ FIPS-validated cryptography when used to protect the confidentiality of CUI.
SC.2.178
Prohibit remote activation of collaborative computing devices and provide indication of devices in use to users present at the device.
SC.2.179
Use encrypted sessions for the management of network devices.
SC.3.180
Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.
SC.3.181
Separate user functionality from system management functionality.
SC.3.182
Prevent unauthorized and unintended information transfer via shared system resources.
SC.3.183
Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception).
SC.3.184
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.3.185
Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards.
SC.3.186
Terminate network connections associated with communications sessions at the end of the sessions or after a defined period of inactivity.
SC.3.187
Establish and manage cryptographic keys for cryptography employed in organizational systems.
SC.3.188
Control and monitor the use of mobile code.
SC.3.189
Control and monitor the use of Voice over Internet Protocol (VoIP) technologies.
SC.3.190
Protect the authenticity of communications sessions.
SC.3.191
Protect the confidentiality of CUI at rest.
SC.3.192
Implement Domain Name System (DNS) filtering services.
SC.3.193
Implement a policy restricting the publication of CUI on externally-owned, publicly accessible websites (e.g., forums, LinkedIn, Facebook, Twitter).
SC.4.197
Employ physical and logical isolation techniques in the system and security architecture and/or where deemed appropriate by the organization.
SC.4.199
Utilize threat intelligence to proactively block DNS requests from reaching malicious domains.
SC.4.202
Employ mechanisms to analyze executable code and scripts (e.g., sandbox) traversing Internet network boundaries or other organizationally defined boundaries.
SC.4.228
Isolate administration of organizationally defined high-value critical network infrastructure components and servers.
SC.4.229
Utilize a URL categorization service and implement techniques to enforce URL filtering of websites that are not approved by the organization.

Domain SI: System and Information Integrity

Protect your network from malicious code execution by applying security patches in a timely manner and using anti-malware software.

SI.1.210
Identify, report, and correct information system flaws in a timely manner.
SI.1.211
Provide protection from malicious code at appropriate locations within organizational information systems.
SI.1.212
Update malicious code protection mechanisms when new releases are available.
SI.1.213
Perform periodic scans of information systems and real-time scans of files from external sources as files are downloaded, opened, or executed.
SI.2.214
Monitor system security alerts and advisories and take action in response.
SI.2.216
Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks.
SI.2.217
Identify unauthorized use of organizational systems.
SI.3.218
Employ spam protection mechanisms at information system access entry and exit points.
SI.3.219
Implement email forgery protections.
SI.3.220
Utilize sandboxing to detect or block potentially malicious email.
SI.4.221
Use threat indicator information relevant to the information and systems being protected and effective mitigations obtained from external organizations to inform intrusion detection and threat hunting.