START HERE
What you will learn
- Explain the six CSF functions without treating them as a rigid sequence.
- Describe a current situation and a more useful target.
- Assign evidence and decisions to a small security improvement plan.
Before you start: No framework experience required. Choose one service or project you are responsible for.
Reference edition: NIST Cybersecurity Framework 2.0. Sources checked 2026-11-11.
What are the six functions?
NIST is the US National Institute of Standards and Technology. CSF 2.0 organises cybersecurity outcomes into Govern, Identify, Protect, Detect, Respond and Recover. Governance establishes direction and responsibilities; the other functions cover understanding risk, applying safeguards, noticing problems, handling incidents and restoring operations.
These functions work together. You should prepare recovery and incident decisions before an incident, while protection and detection continue during normal operation. The framework’s structure is not an instruction to finish one function and leave it behind.
Use outcomes to make the next decision clearer
An outcome describes a condition you want to achieve. For an independent operator, that might include knowing which credentials can change a service and having a tested way to restore an acceptable version. The implementation depends on the actual service and its consequences.
A current profile describes selected outcomes as they stand today; a target profile describes where you intend to get. Keep scope and evidence with the comparison. The CSF does not itself supply a universal list of product settings or turn a completed worksheet into a certification.
Step-by-step process
Choose a service and accountable owner
State what is in scope, who depends on it and who can decide how much risk to accept. For a personal project, the owner may be you.
Describe the current position
Identify important data, identities, dependencies, controls and incident arrangements. Record uncertainty instead of presenting an assumed control as established.
Choose target outcomes
Specify a useful improvement in terms someone can observe, such as a documented and tested recovery path for the service.
Prioritise gaps and assign decisions
Consider the effects of failure and existing constraints. Give each action an owner, evidence expectation and review point.
Exercise response and recovery
Walk through a realistic failure using a safe rehearsal or tabletop discussion. Check who can act, what evidence is needed and how service restoration would be verified.
Review the position as the service changes
Reassess after new integrations, identities or incidents. Keep detection, response and recovery connected with ongoing protection work.
FOLLOW ONE EXAMPLE
Worked scenario
An independent operator preparing a customer portal
In a fictional project, the operator has a working portal and a backup job but has not tested restoration or decided who handles a suspected credential exposure.
- The current position records what the backup covers, who owns the credential and what remains unverified. It does not mark recovery complete simply because a backup file exists.
- The target is a tested restoration procedure and a documented incident decision path. The operator assigns a safe restore exercise and records the result.
- A later integration adds a new cloud identity. The operator revisits the relevant outcomes rather than assuming the earlier review covers the additional authority.
What this shows: The framework helps organise decisions, gaps and evidence. It does not select or validate every technical control automatically.
The process at a glance
Read Mermaid diagram source
flowchart TD G[Govern - direction and responsibilities] --> I[Identify - understand risk] G --> P[Protect - apply safeguards] G --> D[Detect - notice problems] G --> R[Respond - handle incidents] G --> C[Recover - restore operations] I --> L[Shared evidence and improvement decisions] P --> L D --> L R --> L C --> L L --> G
What you should have at the end
- A scoped current-and-target comparison.
- Owned actions with a clear evidence expectation.
- A rehearsed incident and restoration decision path.
Common mistakes and how to avoid them
Treating the functions as a one-way checklist
Governance and operational preparation must continue as the service changes.
Equating a purchased tool with an achieved outcome
Check whether the required behaviour actually works in your service.
Leaving recovery until an incident
Rehearse the authority, information and access required before you need them.
APPLY THE IDEA
Try it yourself
Your task: Choose a service you own and write one question under each of the six functions. Mark answers you can support and gaps you cannot yet establish.
What to produce: A one-page improvement plan naming the owner, next action, evidence and review date for the most important gap.
Check your understanding: Could someone tell what improved from the evidence, rather than from the fact that a document was completed?
Key terms in plain English
- Framework function
- A high-level grouping of related security outcomes.
- Profile
- A description of selected outcomes for a particular context or target.
- Governance
- The decisions, responsibilities and oversight guiding the work.
- Tabletop exercise
- A discussion-based rehearsal of how people would handle a scenario.