United States

NIST SP 800-184 Guide for Cybersecurity Event Recovery

21 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.

21 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
1Purpose, scope and audience0
2.1aPlan to operate in a diminished capacity and restore services in priority order0
2.1bIdentify the key recovery personnel and make sure they know their roles0
2.1cKeep a complete inventory of mission-enabling assets and their dependencies, including hosted services0
2.1dCategorise assets by importance and map interdependencies to set the restoration sequence0
2.2aIdentify critical systems and model threats before an event to produce a dependency map0
2.2bProtect the recovery plan like a system security plan and contain resources that need not touch key assets0
2.2cUnderstand the roots of trust: identities and boundaries, management access control and data integrity0
2.3.1Document a recovery plan covering agreements, authority, team, procedures, communications, off-site storage and workarounds0
2.3.2aDevelop recovery processes as a staged playbook with exit criteria plus automated technical procedures0
2.3.2bSet continuity requirements with stakeholders, weigh cost against resilience and involve the privacy team0
2.3.3Define invocation conditions, authority, notification, milestones, termination criteria and planning assumptions0
2.4Plan recovery communications for every stakeholder, with contacts, reporting lines, sharing rules and alternate channels0
2.5Share recovery insights with other organisations after setting sharing goals and rules0
3.1aGather feedback on recovery plans from everyone with a recovery role0
3.1bRun recovery exercises and tests at a set frequency, with realistic objectives and roles, and review the results0
3.2Learn from real recoveries to improve recovery, operations and security posture, documenting issues as they arise0
4Decide in advance which recovery metrics to collect, make them an automated by-product, and control their sharing0
5aExecute the tactical recovery playbook through initiation, execution and termination0
5bRun the strategic phase: improvement plan, continued communications and review of milestones and metrics0
6Example scenarios, checklist and Cybersecurity Framework mapping0

Tell me when NIST SP 800-184 Guide for Cybersecurity Event Recovery 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 NIST SP 800-184 Guide for Cybersecurity Event Recovery, 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