The Blueprint

The core.

The core sits beneath all eleven areas and applies to every organisation, whatever its tier. It sets out how the rest of the framework is applied: under a security policy that leadership approves, in proportion to your risks, from a risk register that every organisation keeps, with a recorded decision on which requirements apply. All seven core requirements are Foundation.

CORE 7 requirements, all Foundation

The proportionality principle

The Blueprint says what to achieve, not how far to take it. Each organisation meets each requirement in a way that matches its size, the information it holds and the risks in its register. A five-person firm might meet RW-RES-04 (restores tried out) by restoring a few files each quarter, while a larger organisation rehearses whole rebuilds.

Proportionality decides how far you go with a requirement, never whether you meet one that applies. If a requirement applies but you decide not to meet it yet, record that as a risk with an owner, so leadership can accept it knowingly. A requirement is left out only when it genuinely doesn't apply, and the reason is recorded.

Core requirements

RW-CORE-01A risk register with an owner for every risk

What
Identify the main information security risks to your organisation and record each one in a risk register, with a named owner who is responsible for it.
Why
Writing down the most likely ways you could be harmed, each with someone responsible for it, means they are known and being dealt with rather than noticed only after something has gone wrong, and the register becomes the basis for every other decision in this framework.
Protects
Confidentiality · Integrity · Availability

Read the guide: The information security risk register: what goes in it, and how to keep it useful

RW-CORE-03An agreed appetite for risk

What
Have senior leadership agree and write down how much information security risk the organisation is prepared to accept.
Why
Without an agreed limit, choices about which risks to fix and which to live with depend on whoever happens to be asked, whereas a written appetite lets people make consistent decisions that leadership will stand behind.
Protects
Confidentiality · Integrity · Availability

Read the guide: The information security risk register: what goes in it, and how to keep it useful

RW-CORE-04A decision for every significant risk

What
Decide how each risk above your agreed appetite will be dealt with, whether by reducing, avoiding, transferring or accepting it, have senior leadership approve any decision to accept one, and follow each agreed action through until it is done.
Why
Recording a clear decision, and leadership's approval where a risk above the appetite is kept, turns the register into action, so serious risks are either brought down or carried knowingly by the people accountable for them rather than left open by default.
Protects
Confidentiality · Integrity · Availability

Read the guide: The information security risk register: what goes in it, and how to keep it useful

RW-CORE-05The register kept up to date

What
Review the risk register regularly, and whenever something significant changes, so that every risk, its assessment and the decision about it stay current.
Why
Threats, systems and the business all change, so a register that isn't revisited soon describes risks you no longer face and misses the ones you now do.
Protects
Confidentiality · Integrity · Availability

Read the guide: The information security risk register: what goes in it, and how to keep it useful

RW-CORE-06Applicable requirements decided and recorded

What
Decide which Blueprint requirements apply to your organisation, in light of what you do and the risks you face, and record how you meet each one that applies and why each of the others does not.
Why
Not every requirement fits every organisation, so deciding deliberately which ones apply keeps your effort on what protects you, and a written reason for each exclusion shows customers and auditors that a gap was a considered choice rather than something overlooked.
Protects
Confidentiality · Integrity · Availability

RW-CORE-07A security policy everyone can read

What
Write a short information security policy that sets out how the organisation protects its information, have senior leadership approve it, publish it where all staff can find it, and share it with the customers, suppliers and others who need to know it.
Why
A policy that leadership has signed off tells everyone that security matters and what is expected of them, and gives every other rule and decision something to point back to, so people aren't left to guess.
Protects
Confidentiality · Integrity · Availability