Get the latest cyber news and updates straight to your inbox.
Cyber governance is no longer a "nice to have". It’s a board-level imperative. The UK’s new Cyber Governance Code of Practice outlines the minimum standards that regulators, clients, and insurers expect from boardrooms in medium and large organisations. This Code shifts cyber from IT’s responsibility to the board’s. If you're a COO, compliance lead, or board member, this applies to you now.
Benchmark your alignment with our Cyber Code Readiness Checklist.
Published by the Department for Science, Innovation and Technology (DSIT), this Code sets out clear actions that boards should take to ensure effective oversight and resilience against cyber threats.
It applies to medium and large UK organisations – plus small tech firms – and it complements, but doesn’t replace, standards like Cyber Essentials or ISO 27001.
Many boards still:
The Code is designed to correct that.
Ensure your organisation has a cyber risk register, with clear ownership and defined risk appetite.
Cyber resilience should be built into business planning, budgeting, and outcomes.
Mandate cyber training from the board down. Ensure culture, policies, and behaviours support resilience.
Test incident response plans at least annually. Boards must take responsibility for regulatory reporting and post-incident reviews.
Set quarterly reporting expectations. Integrate cyber into audit plans. Communicate regularly with senior managers on Cyber Security topics.
Boards are increasingly accountable for cyber posture. That means you will be asked questions by auditors, regulators, and clients.
FoxTech helps organisations run board workshops, assess governance maturity, and build cyber resilience from the top down.
Compliance Background: Our client is a small e-commerce business that processes a large volume of credit card transactions daily. They had the critical requirement to comply with the Payment Card Industry Data Security Standard (PCI
A field guide for finance leaders, from our incident response team.
Getting security right at the start of development helps to create systems that are easier to secure and can reduce the need for any costly rework in the future.
