The Cybersecurity Capability Maturity Model (C2M2) Version 2.0 (V2.0) was released today, the 21st of July 2021. The update addresses emerging technologies and the...
The Cybersecurity Capability Maturity Model (C2M2) contains a set of common cybersecurity practices that can be used to evaluate, prioritize, and improve cybersecurity capabilities. As a maturity model, C2M2 includes practices that range from foundational ones that are considered basic cybersecurity activities to those that are more advanced in terms of either technical sophistication or consistency and repeatability. This enables use of C2M2 to understand the current state of a cybersecurity program and track growth over time.
The C2M2 that is available today from the C2M2 Program of the United States Department of Energy’s Office of Cybersecurity, Energy Security, and Emergency Response website1 is a derivative of the Electricity Subsector Cybersecurity Capability Maturity Model (ES-C2M2) Version 1.0, which was first published in 2012. ES-C2M2 Version 1.0 was developed in support of a White House initiative to improve the cybersecurity of critical infrastructure organizations. The development project was led by the United States Department of Energy in partnership with the Department of Homeland Security and in collaboration with cybersecurity and maturity model experts from across the energy sector.
The model was built upon and tied together a number of existing cybersecurity resources and initiatives. Additional input to the model content was based on a review of cyber threats to the electricity subsector that the development team conducted to help ensure the model’s relevance. The initial draft of the model was revised after feedback was received from more than 40 industry experts and 17 pilot evaluations. The electricity subsector widely adopted the model and provided more feedback for improvements. Version 1.1 of ES-C2M2 was published in February 2014. The first derivative of the ES-C2M2, the Oil and Natural Gas Subsector C2M2, was developed along a similar timeline by replacing the Electricity–Subsector-focused examples with ONG-specific ones. The United States Department of Energy developed the next derivative of the ES-C2M2, the Cybersecurity Capability Maturity Model, by removing sector-specific references and terminology.
C2M2 is available for free in the Axio360 platform. Interested? Sign up at learn.axio.com/free-tool
The C2M2 is a maturity model, that is, it is “a set of characteristics, attributes, indicators, or patterns that represent capability and progression in a particular discipline.”2 These are some of the elements and concepts that make the C2M2 a maturity model:
See the “Maturity Models” section of the C2M2 document for more details about the maturity model aspects of C2M2.
The model is organized into 10 domains, which are logical groupings of cybersecurity practices.
These are the domains in the current version of the model:
Within domains, cybersecurity practices are organized into groupings of related practices called objectives. The objectives in the Asset, Change, and Configuration Management domain, for example, are Manage Asset Inventory, Manage Asset Configuration, and Manage Changes to Assets. One of the objectives in each domain is called “Management Activities”; it contains practices that describe institutionalization activities. Those practices are similar across domains.
Within objectives, practices are grouped by maturity indicator levels (MILs). In Management Activities objectives, MILs define a progression of institutionalization; in the other objectives, MIL progression means that the practices become more complete in their implementation or more advanced in the way they are performed.
These are the four MILs in C2M2:

Attaining MIL1 in all 10 C2M2 domains is a reasonable goal for development of a cybersecurity program. Beyond that, a target of MIL2 or MIL3 can be set for each domain based on an understanding of the organization’s risk tolerance and threat environment, and also on an evaluation of the anticipated benefits of implementing the practices that would be required to achieve the target. In Axio360, a target MIL can be set for each practice.
The United States Department of Energy created the C2M2 for energy sector and other critical infrastructure organizations, and the model has had wide adoption among such organizations. However, C2M2 Version 1.1 practices are written in a style and at a level of abstraction that enables them to be easily interpreted for any type of organization, including those of any structure and size.
Cybersecurity leaders can easily be consumed by the constant firefighting inherent to the cybersecurity trade—both incident-driven and project-related. You may be committed to implementing a proactive strategy for your cybersecurity program but be constantly thwarted by never-ending distractions. An effective way to quickly develop your strategy and get the wheels in motion is what’s needed to enable you to focus on what matters most and maybe even have some time to think about what’s next.
You can implement C2M2 using a planning technique called Scripts and Rhythms to quickly plan your cyber program activities and make sure those activities actually happen.
To learn more about the C2M2, view a demo of the Axio360 platform and see C2M2 in action.
[1] The United States Department of Energy Cybersecurity Capability Maturity Model
https://www.energy.gov/ceser/energy-security/cybersecurity-capability-maturity-model-c2m2-program
[2] The United States Department of Energy Cybersecurity Capability Maturity Model
https://www.energy.gov/ceser/energy-security/cybersecurity-capability-maturity-model-c2m2-program
C2M2 is available for free in the Axio360 platform. Interested? Sign up at learn.axio.com/free-tool
The Cybersecurity Capability Maturity Model (C2M2) Version 2.0 (V2.0) was released today, the 21st of July 2021. The update addresses emerging technologies and the...
This piece was written by Axio cyber risk experts Pamela Curtis, Vice President of Process Engineering and John Fry, Director of Cyber Risk Engineering.