Home / Services / Cyber Governance Code of Practice

Five principles. Twenty-two actions. All of them addressed to the Board.

The UK Cyber Governance Code of Practice: what it asks of directors and how to evidence it.

The Code is voluntary. It is also the government's written view of what a board should do about cyber risk. Identiqa supplies the evidence behind the answers: backups no stolen admin account can delete, servers checked for intruders, and a response the Board has seen rehearsed.

The Department for Science, Innovation and Technology published the Cyber Governance Code of Practice with the NCSC on 8 April 2025. It is aimed at boards and directors of medium and large organisations and sets out five principles and 22 actions. The principles are risk management, strategy, people, incident planning, response and recovery, and assurance and oversight. It was launched as a voluntary tool.

Five principles, and the evidence each one calls for.

The Code speaks to directors, not to engineers. Each principle comes down to a question the Board should be able to answer.

A · 5 ACTIONS
Risk management

The Board knows which technology and data the business depends on and what risk it accepts.

RISK PICTURE
B · 4 ACTIONS
Strategy

Cyber resilience is part of the business strategy and is resourced.

PLAN AND BUDGET
C · 4 ACTIONS
People

Culture, training, and the Board's own understanding.

TRAINING RECORD
D · 4 ACTIONS
Incident planning, response and recovery

A plan exists, has been tested, and the Board takes responsibility for its regulatory obligations, such as reporting.

TESTED RECOVERY
E · 5 ACTIONS
Assurance and oversight

The Board gains assurance that the controls work and that executives know their regulatory obligations.

INDEPENDENT EVIDENCE
8 April 2025Published by DSIT with the NCSC
5 principlesFrom risk management to assurance
22 actionsAcross the five principles
VoluntaryLaunched as a voluntary tool

Assurance means being shown.

Principles D and E are where boards most often lack evidence: a recovery that has never been tested and controls nobody independent has checked.

An answer on paper

  1. Backup policy approved
  2. Incident plan filed
  3. Last test: not recorded

The Board has been told. It has not been shown.

An answer from operations

  1. Lock record of the backup
  2. Record of the last recovery test
  3. Penetration test with proven paths
  4. Reporting line rehearsed

Principle E asks for assurance. These four records are what assurance looks like.

The Code doesn't change directors' duties. It makes them easier to measure.

Section 174 of the Companies Act 2006 already requires a director to exercise reasonable care, skill and diligence. The Code adds no new duty. What it adds is a published list of actions against which a board's conduct can be judged after an incident.

What Identiqa puts in front of the Board.

A backup the Board can vouch for

AuraLink locks every snapshot in the storage controller of its own 2U hardware, outside your domain. The lock record is something the Board can see, not something it must take on trust.

PRINCIPLE D · AURALINK

Recovery that has been checked

Before systems return to production, AuraCore checks servers, virtual machines, and clusters for the backdoors an attacker leaves behind.

PRINCIPLE D · AURACORE

Independent testing

A penetration test shows whether the controls the Board has been told about hold against a real attack path.

PRINCIPLE E · PENETRATION TEST

Reporting written for directors

CISO advisory prepares the papers and sets the cadence: what the Board sees, how often, and what it decides.

PRINCIPLES A AND E · CISO ADVISORY

Common questions

Is the Cyber Governance Code of Practice mandatory?

No. The government launched it as a voluntary tool. In its response to the call for views it added that, if uptake is limited, it will look into firmer levers, which may include legislation or public procurement requirements.

Who is the Code written for?

For boards and directors of medium and large organisations, in the public and the private sector. It is not written for the people who run security day to day. Smaller organisations are encouraged to apply it too.

How does the Code relate to incident reporting law?

The Code asks boards to take responsibility for their regulatory obligations, such as reporting. Those obligations sit elsewhere. Under the NIS Regulations 2018, operators of essential services notify an incident without undue delay and no later than 72 hours after becoming aware of it. The Cyber Security and Resilience Bill, introduced to Parliament on 12 November 2025, would add an initial notification within 24 hours once it becomes law and its secondary legislation is made.

See what your Board could evidence today.

In the architecture briefing we take principles D and E and check them against your systems: which records exist, which are missing, and what to do first.

Architecture briefing & advisory

This page summarises the Code. It is not legal advice. Cyber Governance Code of Practice at gov.uk