A Governance and Legal Framework for CISO Independence

Executive Summary
Cybersecurity has become one of the defining governance challenges of the digital economy. Current UK guidance treats cyber risk as a board-level responsibility requiring sustained oversight, clear accountability and integration with wider organisational risk management. Regulators increasingly scrutinise not only whether organisations suffered a cyber incident, but whether leadership exercised appropriate oversight before it occurred.
At the centre of this evolution sits the Chief Information Security Officer (CISO).
Over the past two decades, the CISO has transformed from a technical specialist responsible for security controls into a strategic executive tasked with advising boards, informing risk decisions, guiding regulatory compliance, directing incident response, and helping organisations navigate an increasingly complex threat landscape. Current NCSC guidance describes cyber leaders as having a crucial role in communicating and mitigating risks for boards and executive teams. Yet despite the growing importance of the role, governance structures have not evolved at the same pace.
UK government cyber-governance evidence shows that many medium and large organisations still have material gaps in cyber strategy, risk assessment, incident planning and supply-chain assurance. At the same time, security leaders can face personal scrutiny when incident handling or regulatory communications fail, as the Sullivan proceedings demonstrate.
This creates a fundamental governance imbalance.
Organisations increasingly expect CISOs to provide independent assessments of cyber risk, while frequently denying them the independence necessary to perform that function effectively.
The experience of formally designated Data Protection Officers under the GDPR offers a useful but limited comparator. Article 38 protects the independent performance of defined statutory tasks through senior reporting, adequate resources, freedom from instruction and protection against dismissal or penalty for performing those tasks. Those safeguards do not apply automatically to CISOs, whose roles commonly combine advice, assurance and operational responsibility, but they illustrate how function-specific independence can support effective oversight.
Cybersecurity governance has developed sufficiently to justify examining whether function-specific safeguards should support the CISO’s defined cyber-risk reporting and escalation responsibilities.
This article advances a narrower proposition than granting CISOs general immunity or director-equivalent status. It argues that organisations should establish protected independence for defined cyber-risk oversight duties: access to the appropriate board or board committee for defined material risks, freedom to give unfiltered advice, protection for good-faith escalation, and a documented process for decisions that depart from that advice. These safeguards would preserve management’s authority to accept risk while making clear who was informed, what was recommended and who authorised the final decision.
The question is no longer whether cybersecurity belongs in the boardroom.
The question is whether governance structures have evolved sufficiently to support the executives tasked with safeguarding organisational resilience.
Introduction: The Case for Function-Specific CISO Independence and Protected Escalation

Scope and method
This paper is a governance and legal-policy analysis rather than jurisdiction-specific legal advice. It draws principally on the UK GDPR and EU GDPR, NIS2, selected United States disclosure and enforcement developments, regulator guidance and relevant governance practice. Because employment protection, directors’ duties, privilege, whistleblowing law and regulatory liability differ by jurisdiction and sector, each proposal should be tested against the law applicable to the organisation, its regulated entities and the individual office-holder.
Authorities
The analysis draws principally on Article 38 of the UK GDPR and EU GDPR, Article 20 of Directive (EU) 2022/2555, the SEC’s 2023 cybersecurity-disclosure rules and the Ninth Circuit’s amended 2025 opinion in United States v Sullivan. Regulator guidance is used to explain supervisory expectations and is distinguished from binding legislation, rules and judicial authority.
Introduction
For much of the internet era, cybersecurity was viewed primarily as a technical matter.
Security leaders were expected to deploy controls, maintain infrastructure, and respond to incidents. Risk decisions were often implicit rather than formally assessed, and board engagement was limited.
Those assumptions are now obsolete. Digital transformation has made technology inseparable from business operations: revenue generation, customer engagement, supply-chain management, product delivery and strategic growth increasingly depend on digital systems. Cyber incidents can therefore affect financial performance, corporate reputation, regulatory compliance and long-term enterprise value.
Today’s organisations operate in an environment that ENISA’s 2025 threat landscape, the NCSC Cyber Security Toolkit for Boards and the 2025 Verizon Data Breach Investigations Report characterise through ransomware, state-aligned activity, software and supplier dependencies, internet-exposed services, emerging AI use and expanding regulatory obligations:
- Sophisticated ransomware campaigns.
- State-sponsored cyber operations.
- Software supply chain compromise.
- Cloud dependency.
- Artificial intelligence-driven threats.
- Complex third-party ecosystems.
- Expanding regulatory obligations.
The consequences of cyber incidents extend far beyond technology disruption.
A significant cybersecurity event can disrupt business continuity, weaken competitiveness, damage customer trust and threaten financial stability. For public companies, the SEC also recognises that cybersecurity incidents can cause significant losses to companies and investors. The resulting legal, financial and reputational consequences may persist beyond the immediate operational disruption.
Accordingly, cyber risk has become a business risk rather than merely a technology risk.
Boards increasingly recognise cybersecurity as an enterprise risk involving strategy, investment, resilience, people, systems, processes and technology. Security leaders therefore operate at the intersection of technology, business strategy, law, governance and enterprise risk management.
The CISO’s role has fundamentally changed.
What has not changed sufficiently are the governance arrangements surrounding the role.
The governance principle is simple: no executive should be held responsible for identifying material cyber risk while lacking the independence to report it, the authority to escalate it or protection from retaliation for doing so. Organisations should therefore consider contractual independence, protected escalation routes, direct access to the appropriate board committee for defined material risks and protection from retaliation for good-faith reporting. These measures may draw on the governance principle illustrated by Article 38, but they must be designed for the CISO’s distinct operational and advisory responsibilities. They would neither transfer business decisions to the CISO nor make the role immune from accountability; they would help ensure that material risks reach the appropriate decision-makers, departures from professional advice are recorded and responsibility for accepting risk remains with those empowered to do so.
Across industries, CISOs may be expected to safeguard organisations against severe cyber threats while lacking formal rights to escalate material concerns independently of their management line. By contrast, Article 38 of the UK GDPR and Article 38 of the EU GDPR require a Data Protection Officer to report directly to the highest management level, to receive no instructions regarding the exercise of the DPO’s statutory tasks, and not to be dismissed or penalised for performing those tasks. These are function-specific safeguards, not general job security or an unrestricted right of board access.
The governance gap is now clear. Organisations increasingly depend on CISOs to provide candid assessments of threats, control weaknesses and residual risk, yet many have not created the structural safeguards needed for that advice to reach the board intact. The issue is not executive privilege; it is whether decision-makers receive reliable risk information and whether responsibility remains with those authorised to accept the risk.
Responsibility Without Authority

One of the oldest principles of effective management is that responsibility and authority should remain aligned.
In many organisational models, a CISO may have responsibility for assessing and reporting cyber risk without controlling the business, investment, product, procurement or operational decisions that determine whether recommended mitigations are implemented.
A typical CISO may be accountable for:
- Security strategy.
- Cyber resilience.
- Incident response.
- Regulatory compliance.
- Third-party assurance.
- Board reporting.
- Risk management.
- Security awareness.
- Breach notification support.
However, they frequently lack authority over:
- Business investment decisions.
- Product-release schedules.
- Procurement decisions.
- Vendor selection.
- Enterprise architecture.
- Operational priorities.
- Project funding.
This asymmetry would be recognised as problematic in most governance contexts. Organisations generally seek to align authority with responsibility. Where responsibility exceeds authority, accountability becomes blurred and governance quality deteriorates.
The problem becomes particularly acute when CISOs are expected to challenge the decisions of executives who influence their performance reviews, resources, promotion opportunities or continued employment.
The CISO may identify risks, recommend mitigations and escalate concerns, yet possess little ability to compel action. Business leaders retain the authority to accept, defer, or ignore recommendations while the security function often remains exposed to criticism when those decisions result in adverse outcomes.
In effect, organisations frequently hold CISOs accountable for risks they do not fully control.
A mature governance model should identify and address any material mismatch between the CISO’s assigned responsibilities, decision rights and escalation authority.
The Expanding Personal Accountability of Security Leaders

At the same time, the UK Cyber Governance Code of Practice, NIS2, DORA and the SEC’s cybersecurity-disclosure rules illustrate the expanding expectations placed on management bodies and boards in relation to cyber risk, resilience and disclosure.
Across Europe and the United States, current regulatory and governance frameworks increasingly require or encourage organisations to demonstrate:
- Effective cyber governance.
- Appropriate board oversight.
- Timely incident disclosure.
- Risk-management processes.
- Operational resilience capabilities.
- Executive accountability.
Taken together, these developments show a growing emphasis on cyber governance, resilience, disclosure and management-body oversight, although their legal scope and consequences differ by jurisdiction and sector.
Cybersecurity is no longer treated solely as an operational matter delegated to IT departments. It is increasingly addressed as a governance issue requiring active senior-management and board engagement.
This trend creates an important question.
If society expects security leaders to shoulder increasing personal accountability, should those same individuals possess protected independence when advising boards and executives about cyber risk?
Increasingly, the answer appears to be yes.
Lessons from Corporate Failures

Official breach research, threat-landscape analysis and public enforcement records include incidents involving vulnerabilities, delayed remediation, supplier dependencies and governance weaknesses. The evidential record varies by incident, so the defensible conclusion is not that every failure was foreseeable, but that governance arrangements should ensure material warnings are recorded, tested and presented to the people authorised to accept the resulting risk.
Where material vulnerabilities, control deficiencies or remediation delays were known before an event, the governance question is whether that information reached the people authorised to assess and accept the risk, whether competing technical and operational constraints were understood, and whether the resulting decision was properly recorded.
In many cases:
- Vulnerabilities were known.
- Risks were documented.
- Concerns had been raised.
- Investments had been deferred.
- Remediation had been postponed.
Where material warning signs existed before an incident, the failure may have involved technical understanding, prioritisation, resourcing, escalation or decision-making, either separately or in combination.
Where warning signs were available but did not produce an effective response, the failure may have involved governance as well as technical, operational or resource constraints.
In some incidents, executives or boards may not have received a complete account of the risk; in others, they may have accepted risk on the basis of incomplete analysis, competing priorities or an inaccurate understanding of the possible consequences.
An independent and empowered CISO cannot eliminate such failures. However, clearer communication between cyber leaders, senior executives and boards can improve the likelihood that risks are understood, managed and mitigated. This distinction is critically important.
The purpose of independence is not to make better decisions on behalf of management.
It is to ensure management makes better-informed decisions.
The Joe Sullivan Prosecution: A Case Study in Individual Criminal Exposure

While the facts of the case were unusual, its significance extends far beyond its individual circumstances.
Sullivan’s prosecution was exceptional and should not be treated as establishing general criminal liability for CISOs following a breach. A federal jury convicted him in 2022 of obstruction of Federal Trade Commission proceedings and misprision of a felony; he was sentenced in 2023 to three years’ probation and a US$50,000 fine. The Ninth Circuit affirmed the convictions in an opinion filed in March 2025 and issued an amended opinion in November 2025 when it denied rehearing en banc. The case turned on its particular evidential and procedural context, including Uber’s existing FTC investigation and the conduct used to conceal the 2016 incident. Its governance lesson is therefore narrower but important: authority, disclosure duties, legal advice and escalation decisions should be explicit before an incident, not improvised during one.
The case demonstrates that an individual security executive may incur personal criminal exposure where the evidence establishes the elements of an offence such as obstruction of Federal Trade Commission proceedings or misprision of a felony. It does not establish a general doctrine of personal liability for cybersecurity outcomes, nor does it make organisational and individual liability legally interchangeable.
Where legal regimes or enforcement actions expose individual security executives to scrutiny for defined conduct, there is a stronger governance case for ensuring that their reporting and escalation responsibilities are clearly authorised and protected.
Should those individuals also be afforded legally protected independence when communicating risk?
The broader importance of protected challenge and assurance is reflected in established frameworks for corporate governance and internal control, DPO independence and whistleblowing protection, although their legal bases and scope differ.
External auditors are subject to formal independence requirements, while internal audit, compliance, company-secretarial, DPO and money-laundering reporting functions operate under different statutory, regulatory and organisational arrangements. Their common relevance is more limited: each may depend on sufficient authority, access and freedom from inappropriate influence to provide effective challenge.
The Sullivan case supports a more limited conclusion: organisations should define incident authority, preserve independent legal advice, identify applicable notification and disclosure duties, and document who makes material decisions. It does not by itself establish that CISOs require statutory independence, although it provides a concrete example of the personal exposure that can arise when incident governance and regulatory communications fail.
The GDPR DPO Framework by way of Comparison

For organisations required to designate a Data Protection Officer under Article 37 of the UK GDPR or EU GDPR, privacy regulation provides an instructive example of how lawmakers have addressed a defined oversight function. Where an organisation voluntarily designates a DPO within the statutory framework, the relevant DPO requirements also apply; the distinction is therefore between a formally designated DPO and privacy personnel who do not hold that role.
ICO guidance explains that DPOs monitor compliance, advise on data-protection obligations and DPIAs, and act as a contact point for individuals and the regulator. The role’s effectiveness would be compromised if those performing it could be instructed how to act or penalised for carrying out their statutory tasks.
Article 38 of the UK GDPR and Article 38 of the EU GDPR require the DPO to be involved properly and in a timely manner in matters relating to personal-data protection, to receive the resources and access necessary to perform the role, and to report directly to the highest management level of the controller or processor. They also provide that the DPO must not receive instructions regarding the exercise of those tasks and must not be dismissed or penalised for performing them. Although the provisions are materially aligned, the two regimes are legally distinct and should be cited separately where the analysis addresses both UK and EU organisations.
The GDPR framework reflects a deliberate legislative judgment: a DPO cannot provide effective oversight if management may direct the exercise of the role’s statutory tasks or penalise the individual for performing them. Article 38 therefore combines access, resources, senior reporting and protection from instruction or retaliation as function-specific safeguards for independent privacy oversight.
The DPO’s minimum statutory tasks include: informing and advising the controller, processor and relevant employees; monitoring compliance; advising on data-protection impact assessments when requested; cooperating with the supervisory authority; and acting as its contact point.
These responsibilities would be compromised if a DPO could be instructed how to perform the role’s statutory tasks, denied appropriate access or resources, subjected to a conflict of interests, or dismissed or penalised for performing those tasks. Management may decide not to follow the DPO’s advice, but responsibility for the organisation’s compliance decisions remains with the controller or processor.
Accordingly, GDPR established several protections designed to preserve independence.
Article 38 requires the controller or processor to involve the DPO properly and in a timely manner in personal-data protection matters, provide the resources and access needed for the Article 39 tasks, ensure that the DPO reports directly to the highest management level, give no instructions regarding the exercise of those tasks, prevent conflicts arising from other duties, and refrain from dismissing or penalising the DPO for performing the role’s tasks.
These safeguards support the effective performance of the DPO’s statutory tasks and protect the integrity of the oversight function. Their practical benefits extend to controllers, processors, supervisory authorities and data subjects.
The framework therefore treats independence as a condition supporting effective performance of the DPO’s defined oversight tasks.
Current ICO guidance describes the DPO as independent, adequately resourced and accountable to the highest management level, and states that the DPO must not be penalised for performing the role’s duties. The ICO notes that this guidance is under review following the Data (Use and Access) Act 2025. Article 38 of the UK GDPR remains the primary authority for the underlying obligations.
These provisions illustrate a governance principle that may be relevant beyond privacy: where legislation assigns an individual an independent oversight function, the legal framework may protect the exercise of that function from management instruction or retaliation. Whether an analogous principle should apply to CISOs is a policy and governance question; it is not a rule presently established by the UK GDPR, EU GDPR or general company law.
These principles have profound implications for cybersecurity.
Although CISO and DPO mandates differ, the roles may involve some comparable governance activities, including advising senior leadership, assessing regulated risk, escalating concerns and supporting oversight. The comparison is functional rather than legal: a CISO commonly retains operational responsibility for security delivery, whereas a DPO performs defined statutory tasks under the applicable data-protection regime.
- Advise senior leadership.
- Assess risk.
- Challenge business decisions.
- Escalate concerns.
- Interface with regulators.
- Support governance processes.
- Provide independent assurance.
The GDPR framework therefore offers a useful but limited comparator for cybersecurity governance. It demonstrates that defined oversight tasks may require protection from inappropriate influence, but it does not establish that CISO duties, reporting rights or employment protections should mirror those of a DPO.
The analogy is persuasive but not complete. Privacy and cybersecurity involve different statutory mandates, operating models and lines of accountability. The relevant question is therefore not whether the two roles are identical, but whether the same governance principle applies when an organisation relies on an officer to provide independent challenge on a material regulated risk.
The Governance-Law Asymmetry

The analogy with the DPO should not be overstated. A DPO performs functions defined by legislation, whereas a CISO commonly combines independent assurance with operational responsibility for security delivery. Giving the CISO an unrestricted statutory veto could blur accountability, inhibit proportionate risk-taking and create conflicts between assurance and execution. The stronger model is therefore functional rather than status-based: protection should attach when the CISO is assessing, reporting or escalating material cyber risk in good faith, while ordinary accountability should continue to apply to competence, conduct, delivery and the management of delegated responsibilities.
One of the most compelling arguments for enhanced CISO protections is that modern regulation increasingly treats cybersecurity as a governance function.
Article 20 of NIS2 requires the management bodies of in-scope entities to approve cybersecurity risk-management measures, oversee their implementation and undertake relevant training; Member States must also ensure that management bodies can be held liable for infringements by the entity in accordance with national law. The precise consequences depend on domestic implementation, the entity’s status and the applicable liability regime. NIS2 therefore strengthens the case for reliable board-level cyber reporting, but it does not itself create a uniform employment-protection regime for CISOs.
For issuers subject to the relevant US federal securities-reporting requirements, the Securities and Exchange Commission’s cybersecurity rules require disclosure of material cybersecurity incidents and annual disclosure concerning cybersecurity risk-management processes, management’s role and the board’s oversight. The rules regulate issuer disclosure; they do not prescribe a particular reporting line for the CISO, require boards to appoint a cybersecurity expert or create employment protections for security executives.
This creates what may be described as a governance-law asymmetry.
On one hand, legislators and regulators increasingly expect boards to oversee cybersecurity in much the same way they oversee financial, operational and compliance risk.
On the other hand, the executive primarily responsible for informing those decisions often lacks the protections traditionally associated with independent governance functions.
The contradiction is increasingly difficult to defend.
This is not merely a cybersecurity problem. It is a governance problem.
The Impact of NIS2

The NIS2 Directive requires the management bodies of in-scope essential and important entities to approve cybersecurity risk-management measures, oversee their implementation and undertake relevant training. Article 20 also requires Member States to ensure that management bodies can be held liable for infringements of that Article by the entity, subject to national law. The Directive therefore strengthens management-level responsibility, but the identity of the persons exposed, the applicable standard and the available sanctions depend on national transposition and the entity’s legal form.
NIS2 prevents an in-scope entity’s management body from treating cybersecurity solely as a technical function: the management body must approve the relevant risk-management measures and oversee their implementation. Operational activities may be delegated, but the extent to which individual directors or other office-holders retain legal responsibility depends on the Member State’s implementing law, the organisation’s constitutional arrangements and the facts of the alleged infringement.
If an in-scope management body is required to approve cybersecurity risk-management measures and oversee their implementation, it needs reliable information on which to perform those functions. That requirement naturally raises questions about the authority and reporting position of the individuals responsible for providing cyber-risk information.
Why Independence Matters

The argument for enhanced protections is frequently misunderstood. Critics sometimes portray independence as an attempt to elevate the status of cybersecurity professionals or insulate them from performance management.
Neither objective is desirable.
Effective CISOs should remain accountable for their competence, judgement and execution.
The real purpose of independence is different. Independent governance and assurance arrangements are intended to improve the quality of challenge and decision-making. Boards rely on audit, risk and internal-control frameworks for objective assurance; organisations rely on legal counsel for legal advice; and whistleblowing law protects qualifying disclosures.
Boards rely on cyber leaders to explain and mitigate cyber risks in terms that support executive decision-making. Without formal protections, organisational pressures may affect reporting behaviours.
Security leaders may become reluctant to:
- Delay strategic initiatives.
- Challenge executive decisions.
- Escalate compliance concerns.
- Report deteriorating risk positions.
- Highlight resource deficiencies.
The result is not necessarily deliberate concealment. Organisational pressures may instead appear as self-censorship, normalisation of elevated risk or overly optimistic reporting; this is an analytical governance risk rather than a universal empirical finding.
If these reporting behaviours suppress or distort material information, they can impair decision-making during significant cyber events.
The objective should therefore be to create governance structures that encourage transparency rather than conformity.
The Strategic Business Case

The argument for CISO independence is often framed as an employment issue. In reality, it is primarily a governance issue.
Effective cyber governance can improve prioritisation, investment decisions, resilience, compliance and stakeholder confidence. Boards benefit from access to clear assessments of cyber risk, while executives are better positioned to allocate resources when they receive decision-useful analysis.
Moreover, the existence of protected escalation mechanisms may help organisations avoid the gradual normalisation of elevated risk.
Public enforcement actions and post-incident reviews include cases in which warning signs preceded a crisis, concerns were raised and risks were documented. Those records may reveal failures in decision-making or governance, but the causes and evidential record differ by incident.
An independent CISO cannot guarantee perfect outcomes. However, independence increases the probability that critical information reaches decision-makers in an accurate and timely form.
A Governance Framework for Protected Cyber-Risk Escalation
Rather than waiting for statutory reform, organisations can create a contractual and governance framework for protected cyber-risk escalation. The framework should define the matters that qualify as material, identify the executives and board committees authorised to accept them, prescribe the evidence required for a risk-acceptance decision, protect good-faith escalation, and retain an auditable record of advice, challenge and decision. Legislation could later establish minimum safeguards, but organisations do not need to defer these core controls.
The framework should establish protected cyber-risk escalation through defined reporting routes, decision rights, documentation requirements and good-faith protection.
Under such a model, CISOs would possess formally documented rights to:

Material cyber risks should be capable of escalation directly to relevant board committees where necessary.
This does not circumvent executive authority. Rather, it ensures transparency in situations involving significant organisational exposure.

Where executive management chooses to accept cyber risks against professional advice, CISOs should be permitted to formally record dissenting positions.
Formal recording of challenge and risk decisions is consistent with the emphasis that the UK Corporate Governance Code places on board decision-making, risk management, internal control and transparent explanation, although practices differ by sector and jurisdiction.

CISOs should not face adverse employment consequences for honestly escalating a reasonably held cyber-risk concern through an authorised channel, even if the concern or underlying belief later proves mistaken. Under this proposed model, reasonable belief should be assessed against the information available at the time, the grounds for the concern and the urgency of the circumstances, not with the benefit of hindsight. The assessment should be made by a designated reviewer independent of the disputed decision and anyone implicated in the concern, with appropriate legal and technical advice. Where that independence cannot be secured internally, an unconflicted board committee should appoint an external reviewer. The CISO should have an opportunity to explain the basis for the concern and respond to any challenge. Contractual terms should define the protected activities, reporting routes and review process, while preserving fair management of competence, conduct and performance. Protection should not extend to knowingly false or deliberately misleading statements or excuse unrelated misconduct. These safeguards should operate alongside applicable whistleblowing, employment, regulatory-reporting and fiduciary duties, without restricting disclosures independently protected by law.

Significant cyber-risk acceptance decisions should be formally documented, including:
- Relevant risks.
- Potential impacts.
- Recommended controls.
- Responsible decision-makers.
- Rationales for acceptance.

Such measures would enhance accountability rather than reduce it.
For organisations required to designate a DPO under Article 37, or those that appoint one voluntarily and bring the role within the GDPR framework, Article 38 provides a useful but limited governance analogy. It protects the exercise of defined data-protection tasks; it does not create a general model of executive independence or establish that the same safeguards apply automatically to cybersecurity roles.
The Role of General Counsel

For General Counsel, the immediate task is to convert principle into an operating model. The legal function should define the CISO’s mandate; map reporting lines and reserved matters; align cyber escalation with whistleblowing, disclosure and incident-response protocols; specify who may accept material risk; and ensure that minutes and risk records distinguish professional advice from the ultimate business decision. Privilege should be analysed separately for each communication: involving lawyers, copying legal on a record or labelling a document privileged does not by itself establish legal-advice or litigation privilege. Employment terms should protect good-faith escalation without preventing legitimate performance management, and indemnification and directors’ and officers’ insurance should be reviewed under the applicable jurisdiction and policy wording rather than assumed to respond to every investigation or allegation.
General Counsel should play a central role in this discussion.
The issue extends beyond cybersecurity. It concerns governance, accountability, evidence and regulatory defensibility.
By helping create robust reporting structures, escalation procedures and documentation practices, legal teams can strengthen the organisation’s ability to demonstrate informed decision-making.
Well-designed reporting, escalation and decision records can help an organisation explain how material cyber risk was identified, challenged and accepted. They do not provide a safe harbour, cure deficient controls or remove disclosure obligations. Their value lies in evidencing a disciplined process, preserving institutional memory and enabling legal and regulatory scrutiny to focus on the quality of the decision rather than reconstructing an undocumented chain of events.
Implications for Boards

For directors, the debate is ultimately about information quality.
Current UK government guidance clarifies expectations for board accountability in cyber-risk governance. That accountability is meaningful only where boards possess reliable information regarding the risks they oversee.
Boards should therefore view CISO independence not as a concession to the security function but as an investment in governance capability.
The strongest boards are not those that avoid hearing difficult messages. They are those that create systems encouraging honest dialogue about risk.
The CISO as a Governance Officer

Several governance and control functions derive value from their ability to provide objective challenge, although the source and degree of independence differ materially by role, sector and jurisdiction. The UK Corporate Governance Code 2024, for example, addresses board leadership, division of responsibilities, audit, risk and internal control, while the legal foundations of other functions arise from their own statutory, regulatory or professional frameworks:
- External auditors
- Internal audit
- Compliance officers
- Company secretaries
- Data Protection Officers
- Money Laundering Reporting Officers
Their shared relevance is not a uniform legal status or identical degree of independence. It is that each may require sufficient authority, access and freedom from inappropriate influence to provide effective challenge or assurance within its particular mandate.
NCSC guidance describes cyber leaders as playing a crucial role in explaining and mitigating cyber risks for boards and executive teams. In practice, the modern CISO may contribute by:
- identifying enterprise risks;
- challenging management assumptions;
- informing board decision-making;
- providing assurance regarding organisational resilience;
- facilitating regulatory compliance.
The CISO should not automatically be treated as a corporate officer in the company-law sense; that status depends on jurisdiction, constitutional arrangements and the substance of the role. The more defensible proposition is that certain CISO activities have a governance character because they inform board oversight, regulatory compliance and enterprise-risk decisions. Protection should attach to those defined activities without obscuring the CISO’s separate operational accountabilities.
Why Boards Should Support This Model

Some directors may fear that increased CISO independence could complicate governance structures. The proposed model instead aims to improve the information and assurance available to boards, consistent with the NCSC’s emphasis on embedding cyber resilience and risk management throughout the organisation. Potential benefits include:
- Improved Information Quality: Independent reporting reduces the risk of filtered or sanitised risk assessments.
- Stronger Governance Evidence: Greater independence may provide boards with clearer evidence of challenge and risk acceptance. That evidence may assist an organisation in explaining its governance process, but it does not establish due diligence, create a regulatory defence or compensate for inadequate controls, resources, disclosure or remediation.
- Better Decision-Making: Transparent risk reporting enables more effective allocation of resources and risk capital.
- Enhanced Organisational Resilience: Organisations respond more effectively to emerging threats when leadership receives accurate information.
Boards should test the model through evidence rather than titles or reporting lines alone. Useful indicators include the age and value of accepted material risks; the proportion of overdue remediation owned outside the security function; the frequency of direct CISO sessions with the board or risk committee; whether significant dissent is recorded and resolved; whether incident exercises test legal, disclosure and escalation decisions; and whether the CISO can demonstrate access to adequate expertise, budget and operational data. These measures convert independence from an organisational aspiration into an assurance question.
The beneficiaries are therefore not security teams alone.
The primary beneficiaries are boards and the organisations they serve.
The Future of Cyber Governance

Cybersecurity regulation and official guidance continue to evolve. Current regimes place increasing emphasis on resilience, accountability and governance effectiveness; the UK Corporate Governance Code 2024, for example, strengthened expectations around material internal controls and board reporting.
As that evolution continues, policymakers may increasingly ask whether cybersecurity warrants governance arrangements similar to those already established for privacy, audit and compliance functions.
The GDPR model offers a credible starting point. It recognises that oversight functions require structural independence if they are to fulfil their intended purpose.
Cybersecurity governance has developed sufficiently to justify examining whether function-specific independence safeguards should accompany the CISO’s defined oversight responsibilities.
Conclusion

Cyber risk is established as a board-level concern in current UK government guidance, while NIS2, DORA and the SEC’s disclosure rules reflect related regulatory expectations in their respective scopes.
The remaining question is whether organisations can credibly expect independent cyber-risk assurance from executives who lack meaningful structural independence.
For formally designated DPOs, Article 38 establishes safeguards for the independent performance of defined data-protection tasks. That framework informs the policy debate about cyber-risk reporting, but NIS2 does not create an equivalent CISO role or a corresponding set of independence protections.
The practical question for boards and General Counsel is not whether the CISO should be insulated from accountability. It is whether the organisation can prove that material cyber advice reaches the right decision-makers, that dissent can be raised without retaliation, that risk acceptance is authorised and recorded, and that operational responsibility remains clear. Organisations should review those arrangements now through board mandates, employment terms, escalation protocols and assurance testing. Statutory reform may ultimately establish minimum protections, but governance leaders already possess the tools to close much of the gap.
Doing so would not reduce accountability. It would strengthen it.
References (much more here)
Legislation, Regulation and Judicial Authorities
- European Parliament and Council. Regulation (EU) 2016/679 (General Data Protection Regulation), particularly Articles 37–39.
- UK Parliament. UK GDPR, Article 37: Designation of the Data Protection Officer.
- UK Parliament. UK GDPR, Article 38: Position of the Data Protection Officer.
- European Parliament and Council. Directive (EU) 2022/2555 (NIS2), particularly Article 20.
- European Parliament and Council. Regulation (EU) 2022/2554 on digital operational resilience for the financial sector (DORA).
- US Securities and Exchange Commission. Cybersecurity Risk Management, Strategy, Governance, and Incident Disclosure (2023).
- US Securities and Exchange Commission. Erik Gerding, Cybersecurity Disclosure (14 December 2023).
- US Court of Appeals for the Ninth Circuit. United States v Sullivan, No. 23-927, amended opinion (12 November 2025).
- US Department of Justice. Former Chief Security Officer of Uber convicted on federal charges for covering up data breach (5 October 2022).
- US Department of Justice. Former Chief Security Officer of Uber sentenced to three years’ probation (4 May 2023).
Official Guidance, Governance Frameworks and Evidence
- Information Commissioner’s Office. Data protection officers.
- Information Commissioner’s Office. Data (Use and Access) Act 2025.
- National Cyber Security Centre. Cyber Governance for Boards.
- National Cyber Security Centre. Cyber Governance Code of Practice.
- National Cyber Security Centre. Cyber Security Toolkit for Boards.
- National Cyber Security Centre. Board-level cyber discussions: communicating clearly.
- National Cyber Security Centre. NCSC Annual Review 2025.
- UK Government. Cyber Security Breaches Survey 2025/2026.
- UK Government. Whistleblowing guidance for workers.
- Financial Reporting Council. UK Corporate Governance Code 2024.
- European Union Agency for Cybersecurity. ENISA Threat Landscape 2025.
- 2025 Data Breach Investigations Report.
Further Reading
The following sources extend the article’s legal, governance and executive analysis. Official and institutional materials are listed first, followed by peer-reviewed scholarship and expert commentary.
- World Economic Forum. Elevating Cybersecurity: Ensuring Strategic and Sustainable Impact for CISOs (2025). A current executive-level treatment of the CISO’s mandate, organisational relationships and board empowerment.
- World Economic Forum. Principles for Board Governance of Cyber Risk (2021). Six consensus principles for directors overseeing cyber risk.
- World Economic Forum. Global Cybersecurity Outlook 2025. Analysis of geopolitical risk, supply-chain interdependence, AI and cyber resilience.
- Kiesow Cortez, E. and Dekker, M. “A Corporate Governance Approach to Cybersecurity Risk Disclosure”, European Journal of Risk Regulation, 13(3), 443–463 (2022). Peer-reviewed analysis of information asymmetry, disclosure and the CISO perspective.
- Ishikawa, T. and Kryvoi, Y. (eds). Public and Private Governance of Cybersecurity: Challenges and Potential(Cambridge University Press, 2023). An interdisciplinary legal and international-relations account of cyber governance.
- Fisher, S. R. and Check, T. A., Jr. “What Is a Cybersecurity Legal Practice, 2.0?”, Lawfare (2026). A practical roadmap for General Counsel and cybersecurity legal teams.
- Hakmeh, J. “The UK must prioritise cybersecurity or be left dangerously exposed”, Chatham House (2025). Expert commentary connecting escalating threats with national and organisational resilience.
- Carnegie Endowment for International Peace. Cyber and Digital Policy. A continuing collection of policy research on cyber threats, cloud security, norms and systemic technological risk.

Leave a Reply