CMMC v1.0 Domains & Practices

AC - Access Control

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

AC.L1-3.1.1
Limit information system access to authorized users, processes acting on behalf of authorized users, or devices (including other information systems).
AC.L2-3.1.10
Use session lock with pattern-hiding displays to prevent access and viewing of data after a period of inactivity.
AC.L2-3.1.11
Terminate (automatically) user sessions after a defined condition.
AC.L2-3.1.12
Monitor and control remote access sessions.
AC.L2-3.1.13
Employ cryptographic mechanisms to protect the confidentiality of remote access sessions.
AC.L2-3.1.14
Route remote access via managed access control points.
AC.L2-3.1.15
Authorize remote execution of privileged commands and remote access to security-relevant information.
AC.L2-3.1.16
Authorize wireless access prior to allowing such connections.
AC.L2-3.1.17
Protect wireless access using authentication and encryption.
AC.L2-3.1.18
Control connection of mobile devices.
AC.L2-3.1.19
Encrypt CUI on mobile devices and mobile computing platforms.
AC.L1-3.1.2
Limit information system access to the types of transactions and functions that authorized users are permitted to execute.
AC.L1-3.1.20
Verify and control/limit connections to and use of external information systems.
AC.L2-3.1.21
Limit use of portable storage devices on external systems.
AC.L1-3.1.22
Control information posted or processed on publicly accessible information systems.
AC.L2-3.1.3
Control the flow of CUI in accordance with approved authorizations.
AC.L2-3.1.4
Separate the duties of individuals to reduce the risk of malevolent activity without collusion.
AC.L2-3.1.5
Employ the principle of least privilege, including for specific security functions and privileged accounts.
AC.L2-3.1.6
Use non-privileged accounts or roles when accessing nonsecurity functions.
AC.L2-3.1.7
Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs.
AC.L2-3.1.8
Limit unsuccessful logon attempts.
AC.L2-3.1.9
Provide privacy and security notices consistent with applicable CUI rules.

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.

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.L2-3.2.1
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.L2-3.2.2
Ensure that personnel are trained to carry out their assigned information security-related duties and responsibilities.
AT.L2-3.2.3
Provide security awareness training on recognizing and reporting potential indicators of insider threat.

AU - Audit and Accountability

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

AU.L2-3.3.1
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
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
Review and update logged events.
AU.L2-3.3.4
Alert in the event of an audit logging process failure.
AU.L2-3.3.5
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
Provide audit record reduction and report generation to support on-demand analysis and reporting.
AU.L2-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.
AU.L2-3.3.8
Protect audit information and audit logging tools from unauthorized access, modification, and deletion.
AU.L2-3.3.9
Limit management of audit logging functionality to a subset of privileged users.

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.L2-3.12.1
Periodically assess the security controls in organizational systems to determine if the controls are effective in their application.
CA.L2-3.12.2
Develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems.
CA.L2-3.12.3
Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls.
CA.L2-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.

CM - Configuration Management

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

CM.L2-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.
CM.L2-3.4.2
Establish and enforce security configuration settings for information technology products employed in organizational systems.
CM.L2-3.4.3
Track, review, approve, or disapprove, and log changes to organizational systems.
CM.L2-3.4.4
Analyze the security impact of changes prior to implementation.
CM.L2-3.4.5
Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems.
CM.L2-3.4.6
Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities.
CM.L2-3.4.7
Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.
CM.L2-3.4.8
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.L2-3.4.9
Control and monitor user-installed software.

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.L1-3.5.1
Identify information system users, processes acting on behalf of users, or devices.
IA.L2-3.5.10
Store and transmit only cryptographically-protected passwords.
IA.L2-3.5.11
Obscure feedback of authentication information.
IA.L1-3.5.2
Authenticate (or verify) the identities of those users, processes, or devices, as a prerequisite to allowing access to organizational information systems.
IA.L2-3.5.3
Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts.
IA.L2-3.5.4
Employ replay-resistant authentication mechanisms for network access to privileged and non-privileged accounts.
IA.L2-3.5.5
Prevent the reuse of identifiers for a defined period.
IA.L2-3.5.6
Disable identifiers after a defined period of inactivity.
IA.L2-3.5.7
Enforce a minimum password complexity and change of characters when new passwords are created.
IA.L2-3.5.8
Prohibit password reuse for a specified number of generations.
IA.L2-3.5.9
Allow temporary password use for system logons with an immediate change to a permanent password.

IR - Incident Response

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

IR.L2-3.6.1
Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recover, and user response activities.
IR.L2-3.6.2
Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization.
IR.L2-3.6.3
Test the organizational incident response capability.

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.L2-3.7.1
Perform maintenance on organizational systems.
MA.L2-3.7.2
Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance.
MA.L2-3.7.3
Ensure equipment removed for off-site maintenance is sanitized of any CUI.
MA.L2-3.7.4
Check media containing diagnostic and test programs for malicious code before the media are used in organizational systems.
MA.L2-3.7.5
Require multifactor authentication to establish non-local maintenance sessions via external network connections and terminate such connections when nonlocal maintenance is complete.
MA.L2-3.7.6
Supervise the maintenance activities of personnel without required access authorization.

MP - Media Protection

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

MP.L2-3.8.1
Protect (i.e., physically control and securely store) system media containing CUI, both paper and digital.
MP.L2-3.8.2
Limit access to CUI on system media to authorized users.
MP.L1-3.8.3
Sanitize or destroy information system media containing Federal Contract Information before disposal or release for reuse.
MP.L2-3.8.4
Mark media with necessary CUI markings and distribution limitations.
MP.L2-3.8.5
Control access to media containing CUI and maintain accountability for media during transport outside of controlled areas.
MP.L2-3.8.6
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
Control the use of removable media on system components.
MP.L2-3.8.8
Prohibit the use of portable storage devices when such devices have no identifiable owner.
MP.L2-3.8.9
Protect the confidentiality of backup CUI at storage locations.

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.L1-3.10.1
Limit physical access to organizational information systems, equipment, and the respective operating environments to authorized individuals.
PE.L2-3.10.2
Protect and monitor the physical facility and support infrastructure for organizational systems.
PE.L1-3.10.3
Escort visitors and monitor visitor activity.
PE.L1-3.10.4
Maintain audit logs of physical access.
PE.L1-3.10.5
Control and manage physical access devices.
PE.L2-3.10.6
Enforce safeguarding measures for CUI at alternate work sites.

PS - Personnel Security

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

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

RA - Risk Assesment

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

RA.L2-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.
RA.L2-3.11.2
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
Remediate vulnerabilities in accordance with risk assessments.

RE - Recovery

Practices to securely backup and protect your data.

SA - Situational Awareness

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

SC - Systems and Communications Protection

Secure your network boundaries and communications.

SC.L1-3.13.1
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.L2-3.13.10
Establish and manage cryptographic keys for cryptography employed in organizational systems.
SC.L2-3.13.11
Employ FIPS-validated cryptography when used to protect the confidentiality of CUI.
SC.L2-3.13.12
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
Control and monitor the use of mobile code.
SC.L2-3.13.14
Control and monitor the use of Voice over Internet Protocol (VoIP) technologies.
SC.L2-3.13.15
Protect the authenticity of communications sessions.
SC.L2-3.13.16
Protect the confidentiality of CUI at rest.
SC.L2-3.13.2
Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.
SC.L2-3.13.3
Separate user functionality from system management functionality.
SC.L2-3.13.4
Prevent unauthorized and unintended information transfer via shared system resources.
SC.L1-3.13.5
Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.
SC.L2-3.13.6
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
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
Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards.
SC.L2-3.13.9
Terminate network connections associated with communications sessions at the end of the sessions or after a defined period of inactivity.

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.L1-3.14.1
Identify, report, and correct information system flaws in a timely manner.
SI.L1-3.14.2
Provide protection from malicious code at appropriate locations within organizational information systems.
SI.L2-3.14.3
Monitor system security alerts and advisories and take action in response.
SI.L1-3.14.4
Update malicious code protection mechanisms when new releases are available.
SI.L1-3.14.5
Perform periodic scans of information systems and real-time scans of files from external sources as files are downloaded, opened, or executed.
SI.L2-3.14.6
Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks.
SI.L2-3.14.7
Identify unauthorized use of organizational systems.