CMMC Practices

PracticeID Practice
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.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.L1-3.1.22 Control information posted or processed on publicly accessible information systems.
AC.L2-3.1.9 Provide privacy and security notices consistent with applicable CUI rules.
AC.L2-3.1.21 Limit use of portable storage devices on external systems.
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.8 Limit unsuccessful logon attempts.
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.16 Authorize wireless access prior to allowing such connections.
AC.L2-3.1.12 Monitor and control remote access sessions.
AC.L2-3.1.14 Route remote access via managed access control points.
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.7 Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs.
AC.L2-3.1.11 Terminate (automatically) user sessions after a defined condition.
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.13 Employ cryptographic mechanisms to protect the confidentiality of remote access sessions.
AC.L2-3.1.15 Authorize remote execution of privileged commands and remote access to security-relevant information.
AC.L2-3.1.19 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.
AC.5.024 Identify and mitigate risk associated with unidentified wireless access points connected to the network.
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.
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.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.7 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.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.3.048 Collect audit information (e.g., logs) into one or more central repositories.
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.
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.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.
AU.5.055 Identify assets not reporting audit logs and assure appropriate organizationally defined systems are logging.
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.
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.
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.6 Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities.
CM.L2-3.4.9 Control and monitor user-installed software.
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.7 Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.
CM.L2-3.4.8 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.4.073 Employ application whitelisting and an application vetting process for systems identified by the organization.
CM.5.074 Verify the integrity and correctness of security critical or essential software as defined by the organization (e.g., roots of trust, formal verification, or cryptographic signatures).
IA.L1-3.5.1 Identify information system users, processes acting on behalf of users, or devices.
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.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.
IA.L2-3.5.10 Store and transmit only cryptographically-protected passwords.
IA.L2-3.5.11 Obscure feedback of authentication information.
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.
IR.L2-3.6.1 Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, 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 pre-defined procedures.
IR.2.097 Perform root cause analysis on incidents to determine underlying causes.
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.
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.
IR.5.106 In response to cyber incidents, utilize forensic data gathering across impacted systems, ensuring the secure transfer and protection of forensic data.
IR.5.102 Use a combination of manual and automated, real-time responses to anomalous activities that match incident patterns.
IR.5.108 Establish and maintain a cyber incident response team that can investigate an issue physically or virtually at any location within 24 hours.
IR.5.110 Perform unannounced operational exercises to demonstrate technical and procedural responses.
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.5 Require multifactor authentication to establish nonlocal 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.
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.
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.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.L2-3.8.7 Control the use of removable media on system components.
MP.L2-3.8.4 Mark media with necessary CUI markings and distribution limitations.
MP.L2-3.8.8 Prohibit the use of portable storage devices when such devices have no identifiable owner.
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.
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.
PE.L1-3.10.1 Limit physical access to organizational information systems, equipment, and the respective operating environments to authorized individuals.
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.2 Protect and monitor the physical facility and support infrastructure for organizational systems.
PE.L2-3.10.6 Enforce safeguarding measures for CUI at alternate work sites.
RE.2.137 Regularly perform and test data back-ups.
MP.L2-3.8.9 Protect the confidentiality of backup CUI at storage locations.
RE.3.139 Regularly perform complete, comprehensive, and resilient data back-ups as organizationally defined.
RE.5.140 Ensure information processing facilities meet organizationally defined information security continuity, redundancy, and availability requirements.
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.
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.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.
RM.4.148 Develop and update as required, a plan for managing supply chain risks associated with the IT supply chain.
RM.5.152 Utilize an exception process for non-whitelisted software that includes mitigation techniques.
RM.5.155 Analyze the effectiveness of security solutions at least annually to address anticipated risk to the system and the organization based on current and accumulated threat intelligence.
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.
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.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 strategy and roadmap for organizational cybersecurity 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.
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.
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 the information systems.
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.12 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.L2-3.13.11 Employ FIPS-validated cryptography when used to protect the confidentiality of CUI.
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.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.
SC.L2-3.13.10 Establish and manage cryptographic keys for cryptography employed in organizational systems.
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.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.228 Isolate administration of organizationally defined high-value critical network infrastructure components and servers.
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.229 Utilize a URL categorization service and implement techniques to enforce URL filtering of websites that are not approved by the organization.
SC.5.198 Configure monitoring systems to record packets passing through the organization's Internet network boundaries and other organizationally defined boundaries.
SC.5.230 Enforce port and protocol compliance.
SC.5.208 Employ organizationally defined and tailored boundary protections in addition to commercially available solutions.
SI.L1-3.14.1 Identify, report, and correct information and 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.L1-3.14.4 Update malicious code protection mechanisms when new releases are available.
SI.L1-3.14.5 Perform periodic scans of the information system and real-time scans of files from external sources as files are downloaded, opened, or executed.
SI.L2-3.14.3 Monitor system security alerts and advisories and take action in response.
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.
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.
SI.5.222 Analyze system behavior to detect and mitigate execution of normal system commands and scripts that indicate malicious actions.
SI.5.223 Monitor individuals and system components on an ongoing basis for anomalous or suspicious behavior.