The NCSC CAF: outcomes, profiles and who is measured against it
The Cyber Assessment Framework is the UK’s outcome-based framework for organisations whose services matter to the nation: operators of essential services, central government departments, the NHS and, under the Cyber Security and Resilience Bill, a widening set of regulated entities. It is assessed not by ticking controls but by judging whether each outcome is achieved. This guide explains the structure, the scoring, the profiles regulators set and how to produce evidence an assessor will accept.
The CAF describes what good looks like without prescribing how to get there. Each contributing outcome, such as “you have identified and documented your essential functions and the systems that support them”, comes with indicators of good practice at the achieved and partially achieved levels, and indicators that would mark it not achieved. An assessor reads your evidence against those indicators and makes a judgement.
Regulators turn the framework into obligations through profiles: a set of outcomes and the level each must reach for a given sector or risk tier. The NIS competent authorities each publish one, GovAssure uses baseline and enhanced profiles for government systems, and the NHS toolkit maps its own requirements to CAF outcomes. The same self-assessment therefore serves several regulators once the profiles are known.
The four objectives and fourteen principles
Objective A: Managing security risk
A1 Governance, A2 Risk management, A3 Asset management, A4 Supply chain. Board-level ownership, a risk process that drives decisions, knowing what supports your essential functions, and managing the security of suppliers.
Objective B: Protecting against cyber attack
B1 Service protection policies and processes, B2 Identity and access control, B3 Data security, B4 System security, B5 Resilient networks and systems, B6 Staff awareness and training. The bulk of the technical outcomes, from privileged access and secure configuration to backups and segregation.
Objective C: Detecting cyber security events
C1 Security monitoring, C2 Proactive security event discovery. Logging that covers the essential functions, monitoring that would detect an attack, and threat hunting proportionate to the risk.
Objective D: Minimising the impact of incidents
D1 Response and recovery planning, D2 Lessons learned. Tested incident plans, the ability to restore essential functions, and a process that turns incidents into improvements.
The three outcome levels
- Not achieved. One or more of the “not achieved” indicators applies, or the organisation cannot show the outcome is met.
- Partially achieved. The partially achieved indicators are met, typically meaning the outcome is addressed but not consistently, completely or with evidence of effectiveness.
- Achieved. All achieved indicators are met with evidence. Profiles name which outcomes must reach this level; for high-risk functions, most of Objective B and C.
Who it applies to
Operators of essential services in energy, transport, water, health and digital infrastructure under the NIS Regulations; central government departments and arm’s-length bodies through GovAssure; NHS trusts and other health organisations through the DSPT; and, as the Cyber Security and Resilience Bill is enacted, managed service providers, data centres and a wider range of regulated entities. Suppliers to all of these are asked for CAF-aligned evidence through the supply-chain principle.
From scope to evidence, in one system
Outcomes and indicators as the assessment structure
The CAF is a native framework in the GRCorb library: each of the 41 contributing outcomes carries its indicators of good practice, an achieved / partially achieved / not achieved judgement, the rationale and the evidence, which is the form regulators and GovAssure reviewers expect to read.
Profiles as scoped targets
Apply the profile your regulator publishes, or the GovAssure or DSPT mapping, and the gap view shows which outcomes fall short of the required level and which controls close them.
Evidence for Objectives B and C from your estate
Adapters for Microsoft 365, Entra ID, Intune, Defender, CrowdStrike, AWS, Azure, Kubernetes and your SIEM collect identity, configuration, backup, logging and monitoring evidence on a schedule, so technical outcomes are judged on current data.
Supply chain (A4) as a vendor programme
Suppliers are tiered, assessed and monitored in the third-party module, with the assurance evidence the principle expects.
Crosswalk to ISO 27001, Cyber Essentials and NIST CSF
CAF outcomes are mapped to ISO 27001 controls, the five Cyber Essentials controls and NIST CSF 2.0 subcategories, so an ISO-certified organisation starts with much of Objective B evidenced, and a group reporting to a US parent can present the same evidence as a CSF profile.
Frequently asked questions
CAF or ISO 27001?
Different purposes. ISO 27001 certifies a management system; the CAF is how UK regulators judge whether essential functions are protected. Regulated organisations usually need the CAF and find ISO 27001 helps them evidence Objective B. Nobody is certified to the CAF; they are assessed against a profile.
What is a CAF profile?
A regulator’s statement of which outcomes must be achieved or partially achieved for a given type of organisation or function. Without a profile the CAF is a reference; with one it is a set of obligations.
How does the NHS DSPT use it?
From 2024/25 the toolkit for NHS trusts and similar bodies is built on CAF outcomes, with the DSPT setting the required level for each. Suppliers and smaller organisations continued on the older question-based toolkit for a transition period; check the current year’s requirements.
What will the Cyber Security and Resilience Bill change?
It is intended to update the NIS Regulations: bringing managed service providers, data centres and more sectors into scope, strengthening incident reporting and giving regulators more powers, with the CAF as the assessment basis. Treat the current CAF as the target now; details depend on the final Act and regulations.
Related frameworks
Reviewed November 2026. This guide is general information about the published framework and is not legal advice; always check the current official text from the publisher before relying on it.