United States

CISA Cyber Resilience Review (CRR) v4.0

42 controls. 0 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

42 controls 0 frameworks share controls with it United States verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

No measured overlap with another framework in the corpus.

Every control

CodeControlAlso in
AM.1Services are identified and prioritised0
AM.2Assets are inventoried with authority and responsibility established0
AM.3The relationship between assets and the services they support is established0
AM.4The asset inventory is managed0
AM.5Access to assets is managed0
AM.6Information assets are categorised and managed for sustainment and protection0
AM.7Facility assets supporting the critical service are prioritised and managed0
CCM.1The lifecycle of assets is managed0
CCM.2The integrity of technology and information assets is managed0
CCM.3Asset configuration baselines are established0
CM.1Control objectives are established0
CM.2Controls are implemented0
CM.3Control designs are analysed to ensure they satisfy control objectives0
CM.4The internal control system is assessed to ensure control objectives are met0
EDM.1External dependencies are identified and prioritised to ensure operation of high-value services0
EDM.2Risks due to external dependencies are identified and managed0
EDM.3Relationships with external entities are formally established and maintained0
EDM.4Performance of external entities is managed0
EDM.5Dependencies on public services and infrastructure service providers are identified0
IM.1A process for identifying, analysing, responding to and learning from incidents is established0
IM.2A process for detecting, reporting, triaging and analysing events is established0
IM.3Incidents are declared0
IM.4A process for responding to and recovering from incidents is established0
IM.5Post-incident lessons learned are translated into improvement strategies0
RM.1A strategy for identifying, analysing and mitigating risks is developed0
RM.2Risk tolerances are identified and the focus of risk management activities is established0
RM.3Risks are identified0
RM.4Risks are analysed and assigned a disposition0
RM.5Risks to assets and services are mitigated and controlled0
SA.1Threat monitoring is performed0
SA.2The requirements for communicating threat information are established0
SA.3Threat information is communicated0
SCM.1Service continuity plans for high-value services are developed0
SCM.2Service continuity plans are reviewed to resolve conflicts between plans0
SCM.3Service continuity plans are tested to ensure they meet their stated objectives0
SCM.4Service continuity plans are executed and reviewed0
TA.1Cybersecurity awareness and training programmes are established0
TA.2Awareness and training activities are conducted0
VM.1Preparation for vulnerability analysis and resolution0
VM.2A process for identifying and analysing vulnerabilities is established and maintained0
VM.3Exposure to identified vulnerabilities is managed0
VM.4The root causes of vulnerabilities are addressed0

Tell me when CISA Cyber Resilience Review (CRR) v4.0 files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for CISA Cyber Resilience Review (CRR) v4.0, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition