The CMMC framework is spread over 17 cybersecurity domains and associated 43 cybersecurity capabilities (combination of processes, skills, knowledge, tools and behaviors) which should be accomplished by an organization for each level of maturity (Level 1, 2, 3, 4 or 5) in successfully protecting FCI and CUI, if the associated cybersecurity practices are deployed and managed appropriately. See below the CMMC framework by cybersecurity levels.
Level 1Level 2Level 3Level 4Level 5
Basic cyber hygiene
CMMC level 1 is the most basic level of cyber maturity, it forms the initial building block for basic cybersecurity. The focus of CMMC level 1 controls are to support any organization implement basic cybersecurity hygiene, addressing the need to protect Federal Contract information (FCI). Defined as ‘Information provided by or generated for the Government under contract not intended for public release’. Level 1 requires an organization to demonstrates that it performs the control procedures required at Level 1. As identified in FAR 48 CFR § 52.204-21 – (Basic Safeguarding of Covered Contractor Information Systems), equivalent to 17 practices identified in NIST 800-171 r2, listed in the table . Demonstrating that it has applied the practices. By demonstrating that level 1 practices are being performed the organization is adopting basic cyber security hygiene, for the protection of FCI information which it manages on behalf of the government.
| Processes: Performed | Level 1 requires that an organization performs the specified practices. Because the organization may only be able to perform these practices in an ad-hoc manner and may or may not rely on documentation, process maturity is not assessed for Level 1. |
| Practices: Basic cyber hygiene | Level 1 focuses on the protection of FCI and consists only of practices that correspond to the basic safeguarding requirements specified in 48 CFR 52.204-21 (“Basic Safeguarding of Covered Contractor Information Systems”) |
CMMC Level 1 consist of 6 security domains addressing 9 capabilities with 17 security practices.
| Domain | Capability | Control | Control Description |
| Access Control (AC) | C001 Establish system access requirements | AC.1.001 | Limit information system access to authorized users, processes acting on behalf of authorized users or devices (including other information systems). |
| C002 Control internal system access | AC.1.002 | Limit information system access to the types of transactions and functions that authorized users are permitted to execute. | |
| C004 Limit data access to authorized users and processes | 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. | ||
| Identification & Authentication (IA) | C015 Grant access to authenticated entities | 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. | ||
| Media Protection (MP) | C024 Sanitize media | MP.1.118 | Sanitize or destroy information system media containing Federal Contract Information (FCI) before disposal or release for reuse. |
| Physical Protection (PE) | C028 Limit physical access | 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. | ||
| System and Communications Protection (SC) | C039 Control communications at system boundaries | SC.1.175 | Monitor, control and protect organizational communications (e.g., information transmitted or received by organizational information systems) at the external boundaries and key internal boundaries of the information systems. |
| SC.1.176 | Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. | ||
| System & Information Integrity (SI) | C040 Identify and manage information system flaws | SI.1.210 | Identify, report and correct information and information system flaws in a timely manner. |
| C041 Identify malicious content | 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 the information system and real-time scans of files from external sources as files are downloaded, opened or executed. |
Intermediate cyber hygiene
CMMC Level 2 adds a further 55 security controls practices to those of level 1 (17). Increasing the total number of controls under evaluation, to 72 (17+55) controls. Level 2 includes the 17 controls identified at level 1, 48 additional practices from NIST 800-171 r1 (now r2) and a further 7 controls from other sources. Level 2 compliance requires an organization to both demonstrate Level 1 practice compliance (control procedures are performed across all 72 controls) and demonstrate Level 2 process compliance demonstrating practices are documented in policies and procedures to guide the implementation of Level 2.
By demonstrating that Level 2 control procedures are being performed and are documented the organization will develop its cyber security maturity, for the protection of Federal Contract Information (FCI).
| Processes: Documented | Level 2 requires that an organization establish and document practices and policies to guide the implementation of their CMMC efforts. The documentation of practices enables individuals to perform them in a repeatable manner. Organizations develop mature capabilities by documenting their processes and then practicing them as documented. |
| Practices: Intermediate cyber hygiene | Level 2 serves as a progression from Level 1 to Level 3 and consists of a subset of the security requirements specified in NIST SP 800-171 [4] as well as practices from other standards and references. Because this level represents a transitional stage, a subset of the practices reference the protection of CUI. |
CMMC Level 2 consist of 15 security domains addressing 28 capabilities with additional 55 security controls.
| Domain | Capability | Control | Control description |
| Access Control (AC) | C001 Establish system access requirements | AC.2.005 | Provide privacy and security notices consistent with applicable Controlled Unclassified Information (CUI) rules. |
| AC.2.006 | Limit use of portable storage devices on external systems. | ||
| C002 Control internal system access | 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 non-security 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. | ||
| C003 Control remote system access | AC.2.013 | Monitor and control 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. | ||
| Audit & Accountability (AU) | C007 Define audit requirements | 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. |
| C008 Perform auditing | 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. | ||
| C010 Review and manage audit logs | AU.2.044 | Review audit logs. | |
| Awareness & Training (AT) | C011 Conduct security awareness activities | 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. |
| C012 Conduct training | AT.2.057 | Ensure that personnel are trained to carry out their assigned information security- related duties and responsibilities. | |
| Configuration Management (CM) | C013 Establish configuration baselines | 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. | ||
| C014 Perform configuration and change management | 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. | ||
| Identification & Authentication (IA) | C015 Grant access to authenticated entities | 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. | ||
| Incident Response (IR) | C016 Plan incident response | IR.2.092 | Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery and user response activities. |
| C017 Detect and report events | IR.2.093 | Detect and report events. | |
| IR.2.094 | Analyze and triage events to support event resolution and incident declaration. | ||
| C018 Develop and implement a response to a declared incident | IR.2.095 | Develop and implement responses to declared incidents according to pre- defined procedures. | |
| C019 Perform post incident reviews | IR.2.097 | Perform root cause analysis on incidents to determine underlying causes. | |
| Maintenance (MA) | C021 Manage maintenance | 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 nonlocal 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. | ||
| Media Protection (MP) | C023 Protect and control media | MP.2.119 | Protect (e.g., physically control and securely store) system media containing Federal Contract Information, 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. | ||
| Personnel Security (PS) | C026 Screen personnel | PS.2.127 | Screen individuals prior to authorizing access to organizational systems containing CUI. |
| C027 Protect federal contract information during personnel actions | PS.2.128 | Ensure that organizational systems containing CUI are protected during and after personnel actions such as terminations and transfers. | |
| Physical Protection (PE) | C028 Limit physical access | PE.2.135 | Protect and monitor the physical facility and support infrastructure for organizational systems. |
| Recovery (RE) | C029 Manage back-ups | RE.2.137 | Regularly perform and test data back-ups. |
| RE.2.138 | Protect the confidentiality of backup CUI at storage locations. | ||
| Risk Management (RM) | C031 Identify and evaluate risk | 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. | ||
| C032 Manage risk | RM.2.143 | Remediate vulnerabilities in accordance with risk assessments. | |
| Security Assessment (CA) | C034 Develop and manage a system security plan | CA.2.157 | Develop, document and periodically update System Security Plans (SSPs) that describe system boundaries, system environments of operation, how security requirements are implemented and the relationships with or connections to other systems. |
| C035 Define and manage controls | 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 (e.g., POA&M) designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems. | ||
| System & Communications Protection (SC) | C038 Define security requirements for systems and communications | 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. | ||
| System & Information Integrity (SI) | CO40 Identify and manage information system flaws | SI.2.214 | Monitor system security alerts and advisories and take action in response. |
| C042 Perform network and system monitoring | 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. |
Good cyber hygiene
CMMC level 3 increases the number of security controls required at level 1 and level 2 by 58 controls (45 from NIST 800-171r2 and 13 from other sources). Bringing the total number of practices to maintain Level 3 compliance to 130, this includes the controls defined at Level 1 (17) and Level 2 (55). Level 3 compliance will require an organization to apply the compliance processes identified at Level 1 and Level 2 (practiced and documented) to Level 3 practices. In addition the organization will have to establish, maintaining and resource a plan to demonstrate that it is managing the activities for practice implementation. By demonstrating that Level 3 control procedures are being performed, documented and managed the organization will develop its cybersecurity maturity, for the protection of Controlled Unclassified Information (CUI).
| Processes: Managed | Level 3 requires that an organization establish, maintain, and resource a plan demonstrating the management of activities for practice implementation. The plan may include information on missions, goals, project plans, resourcing, required training, and involvement of relevant stakeholders. |
| Practices: Good Cyber Hygiene | Level 3 focuses on the protection of CUI and encompasses all of the security requirements specified in NIST SP 800-171 [4] as well as additional practices from other standards and references to mitigate threats. It is noted that DFARS clause 252.204-7012 (“Safeguarding of Covered Defense Information and Cyber Incident Reporting”) [5] specifies additional requirements beyond the NIST SP 800-171 security requirements such as incident reporting. |
CMMC Level 3 consist of 16 security domains addressing 27 capabilities with an additional 58 security controls.
| Domain | Capability | Control | Control Description |
| Access Control (AC) | C002 Control internal system access | AC.3.012 | Protect wireless access using authentication and encryption. |
| 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. | ||
| C003 Control remote system access | AC.3.014 | Employ cryptographic mechanisms to protect the confidentiality of remote access sessions. | |
| AC.3.021 | Authorize remote execution of privileged commands and remote access to security-relevant information. | ||
| C004 Limit data access to authorized users and processes | AC.3.022 | Encrypt CUI on mobile devices and mobile computing platforms. | |
| Asset Management (AM) | C005 Identify and document assets | AM.3.036 | Define procedures for the handling of CUI data. |
| Audit & Accountability (AU) | C007 Define Audit requirements | AU.3.045 | Review and update logged events. |
| AU.3.046 | Alert in the event of an audit logging process failure. | ||
| C008 Perform Audit | AU.3.048 | Collect audit information (e.g., logs) into one or more central repositories. | |
| C009 Identify and protect audit information | 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. | ||
| C010 Review and manage audit logs | 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. | ||
| Awareness & Training (AT) | C011 Conduct security awareness activities | AT.3.058 | Provide security awareness training on recognizing and reporting potential indicators of insider threat. |
| Configuration Management (CM) | C014 Perform configuration and change management | 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 (blacklisting) policy to prevent the use of unauthorized software or deny-all, permit-by-exception (whitelisting) policy to allow the execution of authorized software. | ||
| Identification & Authentication (IA) | C015 Grant access to authenticated entities | IA.3.083 | Use multi-factor 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. | ||
| Incident Response (IR) | C018 Develop and implement a response to a declared incident | IR.3.098 | Track, document and report incidents to designated officials and/or authorities both internal and external to the organization. |
| C020 Test incident response | IR.3.099 | Test the organizational incident response capability. | |
| Maintenance (MA) | C021 Manage maintenance | 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. | ||
| Media Protection (MP) | C022 Identify and mark media | 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. | ||
| C025 Protect media during transport | 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. | ||
| Physical Protection (PE) | C028 Limit physical access | PE.3.136 | Enforce safeguarding measures for CUI at alternate work sites. |
| Recovery (RE) | C029 Manage back-ups | RE.3.139 | Regularly perform complete, comprehensive and resilient data backups as organizationally-defined. |
| Risk Management (RM) | C031 Identify and evaluate risk | RM.3.144 | Periodically perform risk assessments to identify and prioritize risks according to the defined risk categories, risk sources and risk measurement criteria. |
| C032 Manage risk | 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. | ||
| Security Assessment (CA) | C035 Define and manage controls | CA.3.161 | Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls. |
| C036 Perform code reviews | 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. | |
| Situational Awareness (SA) | C037 Implement threat monitoring | SA.3.169 | Receive and respond to cyber threat intelligence from information sharing forums and sources and communicate to stakeholders. |
| System & Communications Protection (SC) | C038 Define security requirements for systems and communications | SC.3.177 | Employ FIPS-validated cryptography when used to protect the confidentiality of CUI. |
| 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 (e.g., 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 (e.g., 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. | ||
| C039 Control communications at system boundaries | 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, etc.). | ||
| System & Information Integrity (SI) | C042 Perform network and system monitoring | SI.3.218 | Employ spam protection mechanisms at information system access entry and exit points. |
| C043 Implement advanced email protections | SI.3.219 | Implement email forgery protections | |
| SI.3.220 | Utilize email sandboxing to detect or block potentially malicious email. |
Proactive cyber
CMMC level 4 increases the number of security controls in scope by 26, 11 controls from NIST SP 800-171B and 15 from other sources. In addition to those controls identified at Level 1 (17), Level 2 (55) and Level 3 (58), a total of 156 controls at Level 4. Compliance will require an organization to apply the compliance processes identified at Level 1, 2 and 3 (practiced, documented and managed) to Level 4 controls. In addition the organization will have to implement the necessary processes to review and measure practices to demonstrate their effectiveness, taking corrective action and informing senior management when control procedures fail to meet the required level of effectiveness.
By demonstrating that Level 4 control procedures are being performed, documented, managed, reviewed and measured the organization will develop its cyber security maturity, for the protection of Controlled Unclassified Information (CUI).
| Processes: Reviewed | Level 4 requires that an organization review and measure practices for effectiveness. In addition to measuring practices for effectiveness, organizations at this level are able to take corrective action when necessary and inform higher level management of status or issues on a recurring basis. |
| Practices: Proactive | Level 4 focuses on the protection of CUI from APTs and encompasses a subset of the enhanced security requirements from Draft NIST SP 800-171B [6] as well as other cybersecurity best practices. These practices enhance the detection and response capabilities of an organization to address and adapt to the changing tactics, techniques, and procedures (TTPs) used by APTs. |
CMMC Level 4 consist of 11 security domains addressing 16 capabilities with 26 security controls.
| Domain | Capability | Control | Control Description |
| Access Control (AC) | C002 Control internal system access | AC.4.023 | Control information flows between security domains on connected systems. |
| AC.4.025 | Periodically review and update CUI program access permissions. | ||
| C003 Control remote system access | AC.4.032 | Restrict remote network access based on organizational 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. | |
| Asset Management (AM) | C006 Manage asset inventory | AM.4.226 | Employ automated capability to discover and identify systems with specific component attributes (e.g., firmware level, OS type) within your inventory. |
| Audit & Accountability (AU) | C010 Review and manage audit logs | 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. | ||
| Awareness & Training (AT) | C011 Conduct security awareness activities | 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. | ||
| Configuration Management (CM) | C014 Perform configuration and change management | CM.4.073 | Employ application whitelisting and an application vetting process for systems identified by the organization. |
| Incident Response (IR) | C016 Plan incident response | IR.4.100 | Use knowledge of attacker tactics, techniques and procedures in incident response planning and execution. |
| C018 Develop and implement a response to a declared incident | IR.4.101 | Establish and maintain a Security Operations Center (SOC) capability that facilitates a 24/7 response capability. | |
| Risk Management (RM) | C031 Identify and evaluate risk | RM.4.149 | Catalog and periodically update threat profiles and adversary Tactics, Techniques & Procedures (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 boundaries and other organization-defined boundaries. | ||
| C033 Manage supply chain risk | RM.4.148 | Develop and update as required, a plan for managing supply chain risks associated with the IT supply chain. | |
| Security Assessment (CA) | C034 Develop and manage a system security plan | CA.4.163 | Create, maintain and leverage a security strategy and roadmap for organizational cybersecurity improvement. |
| C035 Define and manage controls | 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 | ||
| Situational Awareness (SA) | C037 Implement threat monitoring | SA.4.171 | Establish and maintain a cyber threat hunting capability to search for Indicators of Compromise (IoC) 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 (IoC). | ||
| System & Communications Protection (SC) | C038 Define security requirements for systems and communications | SC.4.197 | Employ physical and logical isolation techniques in the system and security architecture and/or and where deemed appropriate by the organization. |
| SC.4.228 | Isolate administration of organizationally-defined high-value critical network infrastructure components and servers. | ||
| C039 Control communications at system boundaries | 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. | ||
| System & Information Integrity (SI) | C040 Identify and manage information system flaws | 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. |
Advanced cyber
CMMC level 5 is the final level of cyber security maturity. The number of security controls added at level 5 is 15, 4 controls from NIST SP 800 – 171B and 11 from other sources. In addition to those controls identified at Level 1(17), Level 2(55), Level 3(58) and Level 4(26), a total of 171 in scope controls at Level 5. Compliance will require an organization to apply the compliance processes identified at Level 1, 2, 3 and 4 (performed, documented, managed, reviewed and measured ) to Level 5 practices. In addition the organization will have to implement the necessary processes to standardize and optimize control procedures to demonstrate their consistency, effectiveness and efficiency across the organization.
By demonstrating that Level 5 control procedures are being performed, documented, managed, reviewed, measured standardised and optimised the organization will demonstrate that it is taking a practice approach to the development and maintain its cybersecurity maturity, for the protection of Controlled Unclassified Information (CUI).
| Processes: Optimizing | Level 5 requires an organization to standardize and optimize process implementation across the organization. |
| Practices: Advanced/ Proactive | Level 5 focuses on the protection of CUI from APTs. The additional practices increase the depth and sophistication of cybersecurity capabilities. |
CMMC Level 1 consist of 8 security domains addressing 12 capabilities with 15 security controls.
| Domain | Capability | Control | Control description |
| Access Control (AC) | C002 Control internal system access | AC.5.024 | Identify and mitigate risk associated with unidentified wireless access points connected to the network. |
| Audit & Accountability (AU) | C008 Perform auditing | AU.5.055 | Identify assets not reporting audit logs and assure appropriate organizationally defined systems are logging. |
| Configuration Management (CM) | C014 Perform configuration and change management | 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). |
| Incident Response (IR) | C016 Plan incident response | IR.5.106 | In response to cyber incidents, utilize forensic data gathering across impacted systems, ensuring the secure transfer and protection of forensic data. |
| C018 Develop and implement a response to a declared incident | IR.5.102 | Use a combination of manual and automated, real-time response to anomalous activities that match incident patterns. | |
| IR.5.108 | Establish and maintain a Cyber Incident Response Team (CIRT) that can investigate an issue physically or virtually at any location within 24 hours. | ||
| C020 Test incident response | IR.5.110 | Perform unannounced operational exercises to demonstrate technical and procedural responses. | |
| Recovery (RE) | C030 Manage information security continuity | RE.5.140 | Ensure information processing facilities meet organizationally-defined information security continuity, redundancy and availability requirements. |
| Risk Management (RM) | C032 Manage risk | 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. | ||
| System & Communications Protection (SC) | C038 Define security requirements for systems and communications | SC.5.198 | Configure monitoring systems to record packets passing through the organization’s Internet network boundaries and other organizational-defined boundaries. |
| SC.5.230 | Enforce port and protocol compliance. | ||
| C039 Control communications at system boundaries | SC.5.208 | Employ organizationally-defined and tailored boundary protections in addition to commercially-available solutions. | |
| System & Information Integrity (SI) | C041 Identify malicious content | SI.5.222 | Analyze system behavior to detect and mitigate execution of normal system commands and scripts that indicate malicious actions. |
| C042 Perform network and system monitoring | SI.5.223 | Monitor individuals and system components on an ongoing basis for anomalous or suspicious behavior. |
Recent Comments