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.
Home / Services / Cyber Governance Code of Practice
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.
The Code speaks to directors, not to engineers. Each principle comes down to a question the Board should be able to answer.
The Board knows which technology and data the business depends on and what risk it accepts.
Cyber resilience is part of the business strategy and is resourced.
Culture, training, and the Board's own understanding.
A plan exists, has been tested, and the Board takes responsibility for its regulatory obligations, such as reporting.
The Board gains assurance that the controls work and that executives know their regulatory obligations.
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
The Board has been told. It has not been shown.
An answer from operations
Principle E asks for assurance. These four records are what assurance looks like.
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.
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.
Before systems return to production, AuraCore checks servers, virtual machines, and clusters for the backdoors an attacker leaves behind.
A penetration test shows whether the controls the Board has been told about hold against a real attack path.
CISO advisory prepares the papers and sets the cadence: what the Board sees, how often, and what it decides.
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.
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.
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.
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 & advisoryThis page summarises the Code. It is not legal advice. Cyber Governance Code of Practice at gov.uk