Operational Resilience

CERT-RMM — CERT Resilience Management Model

CERT-RMM framework badge
Summarize with
ClaudeChatGPTPerplexityGoogle AI Mode
In this article
At a Glance
CERT Resilience Management Model (CERT-RMM) v1.2
  • Classification
    Category
    Operational Resilience
    Domain
    Operational Resilience
    Framework Family
    Other
  • Regulatory Context
    Type
    Framework
    Legal Instrument
    Process improvement model
    Sector
    Cross-Sector
    Industry
    Cross-Industry
  • Region / Publisher
    Region
    North America
    Region Detail
    United States
    Publisher
    Carnegie Mellon University Software Engineering Institute (SEI)
  • Versioning
    Version
    Version 1.2
    Effective Date
    February 2016
    Issue Date
    February 15, 2016
  • Adoption
    Adoption Model
    Voluntary
    Implementation Complexity
    High
  • Official Reference
License Information

License included / downloadable: No

The SEI publishes CERT-RMM Version 1.2 free to download under a Carnegie Mellon University copyright. It may be reproduced in its entirety without modification, and other external or commercial use needs the SEI's permission, so the text is not included with the platform.

Framework text is licensed by its publisher and is included only where stated above.

Official Resources
CERT-RMM Version 1.2
Provides comprehensive guidance for implementing the CERT Resilience Management Model.
Key takeaways
  • CERT-RMM v1.2 is the Software Engineering Institute's process improvement model for operational resilience, published in February 2016.
  • It defines 26 process areas in four categories for protecting and sustaining the services and assets that support an organization's mission.
  • Use is voluntary, it is not a certification scheme, and it does not bind an organization legally.
  • Organizations identify mission services, the people, information, technology, and facilities each depends on, and set resilience requirements for those assets.
  • SmartSuite holds the process areas, the critical services and assets, resilience requirements, and the evidence for each practice.

Overview

The CERT Resilience Management Model (CERT-RMM) Version 1.2 is the Software Engineering Institute's process improvement model for operational resilience management. It defines 26 process areas that an organization uses to protect and sustain the services and assets that matter to its mission, and to judge how mature its practices are. Version 1.2 was published in February 2016.

Carnegie Mellon University's Software Engineering Institute (SEI), through its CERT Program, publishes the model. Using it is voluntary, it is not a certification scheme, and it does not bind an organization legally. The SEI defines operational resilience as the emergent property of an organization that can continue to carry out its mission in the presence of operational stress and disruption that does not exceed its operational limit.

Organizations implement it by identifying the services that support their mission, defining the people, information, technology and facilities each service depends on, setting resilience requirements for those assets, and then applying the process areas, with generic goals that show whether each practice is managed and defined.

Why does it matter?

CERT-RMM treats security, business continuity and IT operations as one discipline: managing the resilience of services and the assets they depend on. Each of its 26 process areas states a purpose, introductory notes, specific goals with practices, and the generic goals used to judge institutionalization.

Key benefits include:

  • One model for three disciplines

Security, business continuity and IT operations management are described by shared process areas instead of separate programs.

  • Asset-based thinking

Assets are people, information, technology and facilities, each with an owner and custodian, and resilience requirements are set for each asset to support a service (Asset Definition and Management).

  • Maturity shown by generic goals

Generic goals GG1 to GG3 distinguish achieving the specific goals from managing and defining the process, so maturity is measured per process area.

  • Dependencies are in scope

External Dependencies Management applies controls to services and assets that third parties own or operate.

  • Improvement loop built in

Measurement and Analysis, Monitoring and Organizational Process Focus keep the resilience management system under review.

How does it work?

Version 1.2 organizes its 26 process areas into four categories. Enterprise Management has seven: Communications, Compliance, Enterprise Focus, Financial Resource Management, Human Resource Management, Organizational Training and Awareness, and Risk Management. Engineering has six: Asset Definition and Management, Controls Management, Resilience Requirements Development, Resilience Requirements Management, Resilient Technical Solution Engineering, and Service Continuity.

Operations has nine: Access Management, Environmental Control, External Dependencies Management, Identity Management, Incident Management and Control, Knowledge and Information Management, People Management, Technology Management, and Vulnerability Analysis and Resolution. Process Management has four: Measurement and Analysis, Monitoring, Organizational Process Definition, and Organizational Process Focus.

Each process area uses specific goals (for example CTRL:SG1 Establish Control Objectives and CTRL:SG2 Establish Controls) and the generic goals GG1 Achieve Specific Goals, GG2 Institutionalize a Managed Process and GG3 Institutionalize a Defined Process. The SEI's version 1.2 document supplies the process areas, generic goals and practices, glossary and acronyms.

Key Elements

  • Enterprise Focus and Risk Management (EF, RISK)

Enterprise Focus establishes strategic objectives and critical success factors that resilience activities support. Risk Management identifies, analyzes and responds to risks to organizational assets that could adversely affect the operation and delivery of services.

  • Asset Definition and Management (ADM)

Identifies, documents and manages organizational assets through their life cycle to ensure sustained productivity for services. Assets are people, information, technology and facilities, and high-value assets have owners and custodians.

  • Resilience requirements (RRD, RRM)

Resilience Requirements Development establishes enterprise and asset resilience requirements for services, and Resilience Requirements Management keeps them current. A resilience requirement is a characteristic or capability an asset must have to remain viable to support a service.

  • Controls, service continuity and engineering (CTRL, SC, RTSE)

Controls Management defines control objectives and controls. Service Continuity plans for service continuity and sets standards for it. Resilient Technical Solution Engineering builds resilience into software and systems.

  • Operations process areas (AM, EDM, IMC, VAR and others)

Operations covers access and identity, environmental control, external dependencies, incident management and control (identify and analyze events, detect incidents and determine the response), knowledge and information, people, technology, and vulnerability analysis and resolution.

  • Process management (MA, MON, OPD, OPF)

Measurement and Analysis, Monitoring, Organizational Process Definition and Organizational Process Focus provide the feedback and standard processes that raise maturity. Monitoring collects, records and distributes information about the operational resilience management system on a timely basis.

What does it cover?

CERT-RMM applies to any organization that wants to manage the resilience of the services and assets that support its mission, public or private. It is a model that organizations apply across the 26 process areas, and it can be applied to a whole enterprise or to selected services.

What are its objectives?

CERT-RMM aims to define the practices needed to manage operational resilience and to help organizations improve them.

Define the essential organizational practices that manage operational resilience.

Let an organization determine its capability to manage resilience and set goals and targets.

Identify and prioritize the services and assets that need protection and sustainment.

Set resilience requirements for assets and keep them current.

Develop plans to close the gaps between current and target capability.

Framework in Context

CERT-RMM is a process view of resilience, in the tradition of capability maturity models. It sits beside control frameworks such as ISO/IEC 27001, NIST CSF and the ISO business continuity standards by describing how well an organization manages the underlying processes, not only which controls it has.

Common Framework Mappings

Organizations map CERT-RMM process areas to control and management-system standards to reuse evidence, align programs and simplify audits.

Mapped frameworks include:

C2M2 (Cybersecurity Capability Maturity Model)

COBIT 2019

ISO 22301

ISO/IEC 27001

NIST Cybersecurity Framework

NIST SP 800-53

SMARTSUITE

How SmartSuite Supports CERT-RMM v1.2

SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting.

Use Operational Resilience & Business Continuity and Enterprise Risk Management records to hold the process areas, the critical services and assets they protect, resilience requirements and the evidence for each practice.

Process Area Library

Load the 26 process areas with their specific goals and practices, each carrying an owner and a target generic goal level.

Services, Assets and Resilience Requirements

Link each service to the people, information, technology and facilities it depends on and record the resilience requirements for each asset.

Incident and Continuity Management

Track events, incidents, service continuity plans and recovery tests against the Incident Management and Control and Service Continuity areas.

Appraisal and Improvement Plans

Record self-appraisal results per process area, then turn gaps into improvement tasks with owners and due dates.

Evidence for Generic Goals

Attach documents showing a process is managed and defined: policies, plans, training and monitoring results.

Resilience Readiness Reporting

Report readiness, gaps and maturity by process area and by critical service for leadership.

Related frameworks

COBIT 2019

COBIT 2019 is ISACA's framework for governing and managing enterprise IT, with 40 objectives in five domains, six governance principles and 11 design factors.

EU DORA

DORA (Regulation (EU) 2022/2554) requires EU financial entities to manage ICT risk, report major incidents, test resilience and control ICT third-party risk, applying from January 17, 2025.

ISO 22301

ISO 22301:2019 specifies requirements for a business continuity management system to protect against, prepare for, respond to and recover from disruptions.

ISO 27001:2022

ISO/IEC 27001:2022 specifies requirements for an information security management system: Clauses 4 to 10, risk treatment, the Statement of Applicability and 93 Annex A controls.

NIST CSF 2.0

NIST CSF 2.0 (CSWP 29, February 26, 2024) is the voluntary cybersecurity framework with six Functions including Govern, 22 Categories, 106 Subcategories, Profiles and Tiers.

NIST 800-53 Rev.5

NIST SP 800-53 Rev. 5 is the NIST catalog of security and privacy controls in 20 families, mandatory for federal systems under OMB A-130 and FISMA; Release 5.2.0 issued August 27, 2025.

FAQ

Frequently Asked Questions For CERT-RMM (CERT Resilience Management Model)

CERT-RMM is the Software Engineering Institute's process improvement model for operational resilience management. Organizations use it to determine their capability to manage resilience, set goals and targets, and plan to close gaps in how they protect and sustain services and assets.

Twenty-six, in four categories: Enterprise Management (7), Engineering (6), Operations (9) and Process Management (4). Each has a purpose, specific goals and practices, and generic goals.

No. It is a voluntary model published by Carnegie Mellon University's Software Engineering Institute. It is a model for self-improvement, not a certification scheme, and nothing in it makes it a legal requirement.

GG1 is Achieve Specific Goals, GG2 is Institutionalize a Managed Process and GG3 is Institutionalize a Defined Process. They are applied to every process area to judge how well a practice is embedded, rather than whether it exists.

Organizational assets are people, information, technology and facilities. High-value assets have owners and custodians, and resilience requirements are set for each asset to support the service that depends on it.

Put this framework to work in SmartSuite

Manage controls, risks, evidence, and audits in one platform designed for modern governance, risk, and compliance.