The Blueprint

Governance and people.

How security is led and organised: a senior leader who answers for it, policies people can read, checks and duties for the people who work for you, training and awareness, and keeping leadership informed so they can steer.

GOV 31 requirements

Foundation

RW-GOV-01A senior leader answerable for security

What
Make one member of your senior leadership team accountable for information security, and give them the authority to make decisions about it.
Why
When a named senior person answers for security, it gets attention and money at the level where decisions are made, problems have somewhere to go, and security doesn't quietly become nobody's job.
Protects
Confidentiality · Integrity · Availability

RW-GOV-03Agreed rules for using systems and information

What
Set out in plain terms what staff may and may not do with the organisation's devices, accounts and information, and have every employee and contractor agree to those rules before they are given access.
Why
Clear rules that each person has accepted mean people know where the lines are, such as not forwarding work email to a personal account or signing up to unapproved apps, and give you firm ground to act if someone crosses them.
Protects
Confidentiality · Integrity · Availability

RW-GOV-04Checks before people join

What
Check the identity, right to work and references of every new employee and contractor before they start, as far as the law and the role allow.
Why
Checking people before they are trusted with your systems and information catches false identities and invented histories, which are a common route to fraud and insider misuse and are much harder to deal with once someone is already inside.
Protects
Confidentiality · Integrity

RW-GOV-05Confidentiality duties in every contract

What
Include confidentiality terms that continue after the person leaves in every employment contract, and in the agreements you make with contractors and others who see your information, and review those terms whenever your needs change.
Why
Written confidentiality duties make it clear that your information isn't theirs to share or take with them, and give you a legal remedy if they do, including after they have gone.
Protects
Confidentiality

RW-GOV-06Security awareness training for all

What
Give everyone, including new starters soon after they join, regular training that helps them recognise phishing, fraud attempts and careless handling of information, and tells them how to report anything suspicious.
Why
Most attacks depend on persuading someone to click, pay or share something they shouldn't, so people who know the warning signs become one of your strongest defences instead of the easiest way in.
Protects
Confidentiality · Integrity · Availability

RW-GOV-07Unexpected requests confirmed another way

What
Confirm any unexpected or urgent request for money, information or access by contacting the person through a channel you already know is theirs, such as a phone number on record, before acting on it.
Why
Fraudsters, including those using faked voices, videos or emails, rely on people acting before they check, so confirming through a channel you already know belongs to the real person stops money, information or access reaching them, however genuine the request looks.
Protects
Confidentiality · Integrity

Established

RW-GOV-08Security duties written into roles

What
Write each security responsibility into the description of the role that holds it, including every manager's duty to make sure their staff follow the security policies, so that every security task belongs to someone.
Why
When security duties are part of someone's job description they are planned for, given time and discussed in performance reviews, and tasks such as checking access or applying updates don't fall between people.
Protects
Confidentiality · Integrity · Availability

RW-GOV-09Policies reviewed and refreshed

What
Review the security policy, its supporting topic policies and the procedures your programme relies on, on a regular cycle and whenever something significant changes, and keep a record of each version and who approved it.
Why
Threats, technology and the way you work all change, so regular review stops policies drifting into rules nobody follows or that no longer protect against what you face, and the version records show which rules applied at any time.
Protects
Confidentiality · Integrity · Availability

RW-GOV-10Rules for working away from the office

What
Set rules for working from home, while travelling and in public places, covering matters such as where work may be done, who else may use work devices and how to keep screens and calls private, and make sure everyone who works remotely knows them.
Why
Outside the office, information can be overheard on a train, read over a shoulder or left on a computer the whole family shares, so clear rules help people protect it wherever they happen to be working.
Protects
Confidentiality

RW-GOV-11Conflicting duties kept apart

What
Divide tasks that would let one person commit and hide fraud or a serious error, such as setting up a supplier and approving payments to it, between different people.
Why
When no single person can both carry out a sensitive task and approve or check it, fraud needs two people to collude, and honest mistakes are far more likely to be noticed before they cause harm.
Protects
Integrity

RW-GOV-12Security built into every project

What
Assess the security needs of each project when it starts, design what it delivers to your agreed security design principles, and check both have been met before it goes live.
Why
Security that is planned in from the beginning costs less and works better than fixes made afterwards, and a check before go-live stops new systems and processes from opening gaps that nobody intended.
Protects
Confidentiality · Integrity · Availability

RW-GOV-13Measurable security objectives

What
Set a small number of measurable security objectives each year that support what the organisation is trying to achieve.
Why
Objectives give security work a direction and a way of telling whether it is succeeding, so effort goes to the improvements that matter most to the business rather than to whatever seems most urgent that week.
Protects
Confidentiality · Integrity · Availability

RW-GOV-14Enough resources for security

What
Give security the budget, people and time it needs to carry out the agreed plan and policies.
Why
Plans and policies protect nothing unless someone has the time and money to put them into practice, and setting resources aside deliberately avoids the gaps that open when security is only funded after something has gone wrong.
Protects
Confidentiality · Integrity · Availability

RW-GOV-15Leadership kept informed

What
Report to senior leadership at regular intervals on the state of security, covering changes in risks, incidents, audit findings and progress against objectives, using a few agreed measures, and record the decisions they make in response.
Why
Regular, consistent reports let leadership see whether risks are rising or falling and step in early, and recorded decisions show that security is being steered rather than left to run on its own.
Protects
Confidentiality · Integrity · Availability

RW-GOV-16Improvements tracked to completion

What
Keep a single list of the security improvements found by risk assessments, audits, incidents, tests and reviews, each with an owner and a target date, find the cause of each problem, and follow every item through until it is done.
Why
Findings are only useful if they are acted on, and one tracked list stops the lessons of one review being forgotten before the next, so the same weaknesses don't keep coming back.
Protects
Confidentiality · Integrity · Availability

RW-GOV-17Consequences for breaking security rules

What
Make sure your disciplinary process covers breaches of security policy, and tell staff that it does.
Why
People take rules more seriously when they know that a deliberate or reckless breach has consequences, and a fair process that everyone knows about lets you respond consistently instead of improvising when it happens.
Protects
Confidentiality · Integrity

RW-GOV-18Training matched to the role

What
Decide what skills each role with particular security duties needs, such as security staff, administrators, developers and finance staff, and give people in those roles the training to gain them.
Why
General awareness training doesn't teach an administrator to set systems up safely or a finance clerk to spot a faked invoice, so training aimed at the role closes the gaps where a mistake would do the most damage.
Protects
Confidentiality · Integrity · Availability

RW-GOV-19Contacts ready for the authorities

What
Keep a current list of the authorities you might need to contact about a security matter, such as regulators, the police and your national cyber security agency, noting when and how to reach each one.
Why
During an incident there is little time to find out who to call, so having the right contacts and triggers ready means you get help sooner and are more likely to meet any reporting deadlines.
Protects
Confidentiality · Integrity · Availability

RW-GOV-20Learning from security communities

What
Join and take an active part in at least one trusted security group, industry forum or professional body that is relevant to your work.
Why
Organisations in the same sector often see the same threats first, so belonging to a trusted group gives you early warning and practical advice that you wouldn't get on your own.
Protects
Confidentiality · Integrity · Availability

RW-GOV-21Written procedures for key tasks

What
Write down step-by-step procedures for the security and IT tasks that must be done the same way every time, such as setting up new systems or restoring data, and keep them where the people who carry them out can find them.
Why
Written procedures mean important tasks are done correctly whoever is on duty, reduce mistakes under pressure, and stop your security depending on what one person happens to remember.
Protects
Confidentiality · Integrity · Availability

RW-GOV-22What your security programme covers

What
Decide and write down which parts of the organisation, which locations and which systems and services your security programme covers, with the reason for anything left out.
Why
Being clear about what's covered stops important systems falling between teams unnoticed, and lets everyone, including auditors and customers, see exactly what your security claims apply to.
Protects
Confidentiality · Integrity · Availability

RW-GOV-23Management body trained in security

What
Give the members of your management body, meaning the board or whoever directs the organisation, regular training in security risk that suits their part in overseeing it.
Why
Leaders who understand the threats, and what good protection looks like, can ask sharper questions, judge the reports they receive and make better-informed decisions about risk and spending.
Protects
Confidentiality · Integrity · Availability

RW-GOV-26Threats understood and used in judging risk

What
Gather information about the threats most likely to target organisations like yours, such as criminal groups, fraud or misuse by insiders and attacks through suppliers, from trusted sources such as your national cyber security agency, and use it whenever you identify and assess risks.
Why
Risks judged without knowing who is likely to attack, and how, are scored on guesswork. Knowing the threats that actually target organisations like yours shows which risks are most likely to happen and where your protection needs to be strongest.
Protects
Confidentiality · Integrity · Availability

RW-GOV-27What shapes your security written down

What
Write down the outside and inside factors that shape your security, and the people and bodies with a stake in it, such as customers, regulators, staff, suppliers and insurers, with what each expects of you, and review this at least once a year.
Why
Security has to fit your situation: the market you work in, the laws and contracts you're under and what customers and regulators expect of you. Writing these down keeps the programme aimed at the right things, and shows that it is.
Protects
Confidentiality · Integrity · Availability

RW-GOV-28A security plan agreed by leadership

What
Write a plan for the next one to three years that sets out how security will support the organisation's aims and bring its risks within the agreed appetite, have senior leadership approve it, and check progress against it at least once a year.
Why
Without a plan, security work tends to follow whatever happened last. A plan that leadership has agreed ties the work and the budget to the organisation's aims and its appetite for risk, and shows everyone whether it's on track.
Protects
Confidentiality · Integrity · Availability

RW-GOV-29Exceptions recorded and time-limited

What
Allow an exception to a security policy or requirement only when its risk has been assessed and an agreed person has approved it, and record each one with the reason and an end date so it is reviewed before that date rather than left in place.
Why
Exceptions are sometimes needed, but each one leaves a gap in your protection. Approving them knowingly, and giving each an end date, stops temporary gaps from quietly becoming permanent.
Protects
Confidentiality · Integrity · Availability

Read the guide: Post-quantum cryptography: the questions to ask your suppliers

RW-GOV-31Topic policies for the requirements you meet

What
Back the security policy with topic policies that set out how you meet the Blueprint requirements that apply to you, such as one for each area of the Blueprint, each with an owner and approved by senior leadership.
Why
A single top-level policy says what the organisation intends, but not how it will meet each requirement. Topic policies turn that intention into rules people can follow, and following the Blueprint's areas means each policy covers a known set of requirements, so it's easy to see that none has been left without one.
Protects
Confidentiality · Integrity · Availability

RW-GOV-32Security communication planned

What
Decide what you need to tell staff, customers, suppliers, regulators and others about security, who tells them, and when and how.
Why
Security depends on people knowing what is expected of them and what is happening, and customers and regulators expect to hear from you at the right moments. Deciding this in advance means the right people hear the right things, from the right person, rather than nothing or too much.
Protects
Confidentiality · Integrity · Availability

Advanced

RW-GOV-24Deeper checks for high-trust roles

What
Identify the roles that could do serious harm if misused, and screen the people in them more thoroughly before they start and again at set intervals.
Why
People in the most trusted roles can cause the greatest damage, and circumstances can change after someone joins, so deeper and repeated checks reduce the chance of a serious insider problem going unnoticed.
Protects
Confidentiality · Integrity

RW-GOV-25Awareness measured and acted on

What
Measure whether your awareness programme is changing how people behave, for example by how often and how quickly people report suspicious messages and what lies behind recent incidents, and adjust the programme based on what you find.
Why
Completion records only show that people sat the training, whereas measuring behaviour shows whether it works, so you can focus effort on the teams and topics where people still need help.
Protects
Confidentiality · Integrity

RW-GOV-30Insider concerns handled together

What
Agree how HR, legal and security will share concerns about the conduct of people inside the organisation and work together to look into suspected misuse.
Why
People inside the organisation already have access, so misuse by them is hard to spot from security alerts alone. HR, legal and security each hold part of the picture, and agreeing in advance how to share it means concerns are looked into fairly, lawfully and in time.
Protects
Confidentiality · Integrity