The Chief Information Security Officer role has changed more in the past few years than in the decade before. The driver is not mainly technology, although the threats have moved on too. It is regulation. The Digital Operational Resilience Act (DORA) has applied across EU financial services since 17 January 2025. The NIS2 Directive has widened cyber obligations to far more sectors and organisations across EU member states. The FCA and PRA operational resilience rules reached their full compliance deadline on 31 March 2025, and a new UK incident and third-party reporting regime is now on the way. Taken together, these frameworks have moved the CISO from head of a technology function to a board-facing role with direct regulatory exposure in a growing number of businesses.
This guide is written for boards, CEOs and HR leaders who are hiring or replacing a CISO under the current rules. It covers what DORA, NIS2 and the UK operational resilience framework actually ask of the security function, what is coming next in UK law and regulation, how all of this changes the candidate profile, what drives pay now that the role carries regulatory weight, and the mistakes that most often undermine CISO appointments. If you are ready to start a search, our CISO recruitment service sets out how we run these mandates.
What DORA requires — and what it means for the CISO
DORA is an EU regulation that applies to financial entities operating in the EU — banks, insurers, investment firms, payment and e-money institutions, crypto-asset service providers and others — and, through a separate oversight framework, to ICT third-party providers designated as critical. It has applied since 17 January 2025. It is not UK law. A UK-only firm with no EU presence is not in scope. But a UK group with an EU-authorised subsidiary, or a UK firm that provides services into the EU through a regulated EU entity, will have DORA obligations in that entity, and UK technology suppliers to EU financial firms will find DORA terms written into their contracts.
DORA is built around five pillars, and every one of them lands on the CISO’s desk:
- ICT risk management. A documented ICT risk management framework, approved and overseen by the management body and reviewed at least annually.
- Incident management and reporting. Major ICT-related incidents must be classified and reported to the competent authority on a fixed timetable: an initial notification within four hours of classifying an incident as major and no later than 24 hours after becoming aware of it, an intermediate report within 72 hours of the initial notification, and a final report within one month of the latest intermediate report.
- Digital operational resilience testing. A testing programme proportionate to the firm, with threat-led penetration testing at least every three years for the larger entities identified by their supervisors.
- ICT third-party risk. A register of information covering ICT contracts, mandatory contractual terms, due diligence and exit planning for key providers.
- Information sharing. Voluntary arrangements for sharing cyber threat intelligence between financial entities.
The CISO implications are direct. DORA puts the management body — in practice, the board — in charge of defining, approving and overseeing the ICT risk management framework, and makes it ultimately responsible for ICT risk. Members of the management body are also expected to keep their own knowledge of ICT risk up to date. The practical consequence is that the CISO has to brief the board on ICT risk in terms that let directors exercise that responsibility properly. A CISO who produces technical reports that the board cannot follow is not just failing an internal communication standard; at a DORA-subject firm, they are leaving the board unable to show it is meeting a regulatory obligation. That is why CISO hires at these firms are a different exercise from hires where cyber sits further down the organisation.
The incident timetable deserves particular attention at interview. Four hours from classification is not long. It assumes the firm already has classification criteria agreed, an on-call escalation route, pre-drafted notification templates and a clear decision-maker. A candidate who has run a regulated incident process will talk about those things unprompted. A candidate who has not will tend to talk about detection tooling instead.
What NIS2 changes — and how it extends the CISO’s reach
The NIS2 Directive replaced the original EU NIS Directive, with a transposition deadline for member states of October 2024. Where NIS1 focused on operators of essential services in sectors such as energy, transport, water, health and digital infrastructure, NIS2 reaches a much broader set of sectors, including postal and courier services, waste management, food production and distribution, manufacturing of certain products and a wider range of digital services. It also applies, as a rule, to medium and large organisations in those sectors, rather than only to those individually designated as critical.
NIS2 is an EU directive and the UK is not transposing it. UK organisations need to think about it only where they have entities operating in EU member states that fall within scope, and those entities will be subject to the national law of the relevant member state. Because transposition has been uneven across the EU, a UK group with operations in several member states may face slightly different requirements in each one. The UK has its own regime, the Network and Information Systems Regulations 2018, which is now being updated through the Cyber Security and Resilience Bill (covered below).
The most significant change NIS2 brings for CISO hiring is its approach to management accountability. Management bodies of essential and important entities must approve the cyber risk management measures, oversee their implementation and undergo training, and member states must be able to hold them liable for breaches. Supervisors also have the power, in some circumstances, to seek a temporary ban on individuals exercising managerial functions. This pulls cyber accountability up to the C-suite and board in a way NIS1 did not. The CISO who owns the cyber risk programme has to understand that accountability chain and be able to give the board the evidence it needs to show it is discharging its duties.
Hiring a CISO for a regulated business?
Exec Capital assesses CISO candidates on board communication, incident leadership and regulatory knowledge as well as technical depth, across permanent, interim and fractional appointments.
FCA operational resilience — what changed at the March deadline
The UK operational resilience framework, introduced by the FCA in PS21/3 and by the PRA alongside it, requires in-scope firms to identify their important business services, set impact tolerances for the maximum tolerable disruption to each, map the people, processes, technology, facilities and third parties those services depend on, and test their ability to stay within tolerance in severe but plausible scenarios. Firms had until 31 March 2025 to show they could actually remain within those tolerances. Since that date, the question from supervisors has changed from “have you done the mapping?” to “can you prove you would stay within tolerance, and what have you fixed?”. The FCA’s published insights and observations on operational resilience set out what it has seen firms do well and badly.
For the CISO, the framework creates three specific responsibilities that were much less clearly defined before 2021:
- Credible mapping. Important business services must be mapped to the underlying technology and third-party dependencies in enough detail that the impact tolerance analysis stands up. The security function usually holds much of that knowledge.
- Cyber scenario testing. A severe cyber incident, such as ransomware across core systems or the loss of a key cloud provider, is one of the most obvious severe but plausible scenarios. The CISO should own the cyber dimension of that testing and the remediation that follows.
- Board reporting. The board has to approve the self-assessment. The CISO must report the firm’s cyber resilience in a way that supports that approval rather than simply reassuring.
The supervisory direction is clear even where enforcement is still developing: boards that cannot show active engagement with operational resilience, including cyber resilience, are exposed. A CISO who treats this as a documentation exercise rather than a real governance function is not equipped for the role as it now stands.
FCA incident and third-party reporting — the next deadline
The next major change for UK financial services is already published. In March 2026 the FCA issued PS26/2 on operational incident and third party reporting, with the PRA and Bank of England publishing aligned policy at the same time. The rules apply from 18 March 2027, giving firms a twelve-month implementation window.
The incident reporting rules apply to a wide population, including all firms with a Part 4A permission and payment service providers. They set thresholds for when an operational incident must be reported and introduce standard and enhanced reports. In broad terms, a standard report goes in within 24 hours of determining that a threshold has been met; larger firms and dual-regulated firms make enhanced reports, with an initial report within 24 hours, updates as significant developments occur and a final report after the incident is resolved. The third-party element applies to a narrower group, including enhanced SM&CR firms, banks, building societies, Solvency II firms and authorised payment and e-money institutions. Those firms will need to notify the FCA of new material third-party arrangements or significant changes to them, keep a register of material arrangements and submit it annually.
For a firm hiring a CISO now, this matters because the person appointed will almost certainly be the one building the classification criteria, reporting workflow and third-party register before March 2027. That is a concrete delivery task, and it is a good test of a candidate: ask how they would scope it, who they would need, and what they would have in place by the end of their first six months.
Critical third parties and the supply chain
Since 1 January 2025, the UK has had a regime for critical third parties to the financial sector, set out in PS24/16. HM Treasury designates the third parties — typically large cloud and technology providers — whose failure could threaten financial stability or confidence, and the Bank of England, PRA and FCA then oversee them directly. The regulators are explicit, however, that designation does not move responsibility away from the firms that use those providers. Firms remain accountable for their own operational resilience and for managing their suppliers under the existing outsourcing and operational resilience rules.
This is where many CISOs are tested hardest. Concentration on a small number of cloud, software and managed service providers means that a firm’s cyber resilience increasingly depends on contracts, assurance and exit plans as much as on its own controls. A strong CISO candidate can explain how they have assessed supplier security, what contractual rights they negotiated, how they test a supplier’s recovery claims, and what the firm would actually do if a key provider failed. Those conversations often need the CISO to work closely with procurement, legal and the Chief Operating Officer, and the best candidates are comfortable in all three rooms.
The UK Cyber Security and Resilience Bill
Outside financial services, the biggest UK change is the Cyber Security and Resilience (Network and Information Systems) Bill, which updates the NIS Regulations 2018. The Bill was carried over into the current parliamentary session and, by early November 2026, had completed its Lords stages and was returning to the Commons for consideration of Lords amendments. It is not yet law, and the detail could still change before Royal Assent, with much of the operational detail expected to follow in secondary legislation and regulator guidance.
As it currently stands, the Bill brings managed service providers and data centres into the NIS regime, gives regulators powers to designate critical suppliers, and tightens incident reporting, including duties on certain providers to keep affected customers informed after a reportable incident. For a CISO in an organisation that is, or supplies, an operator of essential services or a relevant digital service provider, this means new reporting duties and closer scrutiny from sector regulators. For a CISO in a business that buys managed services, it means suppliers will be under clearer legal obligations, which should improve the assurance a CISO can obtain from them.
The hiring point is straightforward. Organisations in or near the expanded scope should look for CISO candidates who have already worked under a regulatory reporting regime, whether NIS, DORA or the FCA’s, because the habits transfer: clear classification, fast escalation, accurate notification and disciplined follow-up.
Data protection: the Information Commission and the Data (Use and Access) Act
Personal data breaches remain one of the most common ways a security incident becomes a regulatory matter. Two recent changes affect how CISOs and data protection officers work together. The Data (Use and Access) Act 2025 received Royal Assent in June 2025 and amends parts of UK data protection law, with its provisions being brought into force in stages. Under that Act, the Information Commissioner’s Office was replaced on 30 September 2026 by the Information Commission, a body corporate with a board of executive and non-executive members. The regulator’s role, responsibilities and powers are unchanged.
For the CISO, the practical requirement is unchanged too: a personal data breach that is likely to result in a risk to individuals must be reported to the regulator within 72 hours of the organisation becoming aware of it. What has changed is the number of parallel clocks. A single incident at a financial services firm could trigger a data breach report, an FCA operational incident report and, in an EU entity, a DORA notification, each with its own thresholds and timings. A CISO who has built a single incident process that feeds all of them is far more valuable than one who treats each regime separately.
How the regulatory environment changes the candidate profile
The combined effect of DORA, NIS2, UK operational resilience, the new reporting rules and the Cyber Security and Resilience Bill is to move the CISO from a technical leader who provides assurance to the board to part of the governance chain a regulator will examine after a material incident. That changes the specification in four concrete ways.
Board communication is a real requirement, not a nice-to-have. A CISO who is technically outstanding but cannot brief a board of non-technical directors in a way that lets them exercise their responsibility is not right for a regulated business. This needs to be assessed directly in the process, not assumed from seniority or job title.
Regulatory literacy is baseline competence. In financial services and other regulated sectors, a CISO should arrive understanding the incident reporting duties, operational resilience expectations and third-party rules that apply to the firm. One who needs to be briefed on what DORA or PS26/2 require is behind before they start.
Incident leadership at the regulatory interface is an experience criterion. Managing a material incident now means classification decisions, regulator notification, board briefings and customer and media communication, often within hours. The timelines leave no room for a CISO who is learning the process during the incident itself. Ask for the detail of the last significant incident a candidate led: what happened, how they found out, what they told the CEO and the board, and what changed afterwards.
Third-party and supply chain judgement. With so much critical capability outsourced, the CISO must be able to assess, contract for and test supplier resilience, and to work with the second-line risk function on how that risk is reported. In larger firms this is often shared with a dedicated information security risk officer, and the split of responsibilities should be agreed before the hire, not after it.
For a broader view of how to run the process itself — specification, assessment and offer — see our guide on how to hire a Chief Information Security Officer.
Where the CISO sits in the senior management structure
Under the Senior Managers and Certification Regime there is no specific senior management function for the CISO. In most FCA-regulated firms the CISO is not an approved senior manager, although they may be in scope of the Certification Regime depending on the firm and the role. Accountability for operational resilience is normally allocated to a senior manager, often the Chief Operations function holder (SMF24) in firms that have one, and the CISO’s work feeds that individual’s accountability. That makes the relationship between the CISO and the COO of a regulated firm one of the most important in the business.
The CISO also needs a working relationship with the risk function. The Chief Risk Officer will want independent challenge of cyber risk, and the board’s risk or audit committee will expect to hear from the CISO directly. Where the CISO reports through the CTO or CIO, the firm should be confident that the reporting line does not filter what the board hears. Many regulated firms give the CISO a direct line to the risk committee chair for exactly that reason.
Market rate — CISO, UK
We do not publish salary bands on this page, because CISO pay varies widely and any single table quickly goes out of date. What we can say is what moves the number. Once a CISO role carries regulatory accountability, the pool of credible candidates narrows sharply, and pay reflects that scarcity more than job title does.
- Regulatory scope. Roles at firms subject to DORA, PRA supervision or the enhanced PS26/2 reporting tier attract a premium over similar-sized unregulated businesses.
- Board exposure. A CISO who reports to the board or a board committee and owns the resilience self-assessment input is paid differently from one who reports into a technology function.
- Incident record. Candidates who have led a regulated firm through a material incident and its aftermath are in short supply and know it.
- Team and estate size. The size of the security team, the complexity of the technology estate and the number of jurisdictions all push the package up.
- Equity and stage. Growth-stage and pre-regulated technology companies often trade lower base salary for equity, which suits some candidates and rules out others.
When we take on a CISO mandate, we give the client a current view of pay for that specific role, sector and location, drawn from the live conversations we are having with candidates rather than a generic survey.
The most common mistakes in CISO appointments
Hiring for technical depth without testing board communication. This is the most frequent mistake in regulated sectors. Technical depth is necessary but not sufficient. The process should include at least one exercise in which the candidate briefs a non-technical director on a serious cyber risk or incident scenario. The quality of that briefing tells you more than any technical question.
Assuming regulatory knowledge from sector experience. Ten years in a bank does not mean a candidate has run an incident notification or contributed to an operational resilience self-assessment. Regulatory literacy should be tested directly, with scenarios drawn from the regimes that actually apply to your firm.
Placing the role too far below the board. If the CISO reports to the CTO, who reports to the CEO, and the board’s view of cyber risk comes through two layers of management, the firm will struggle to show a supervisor that the management body is actively engaged in ICT risk governance. In most regulated firms the CISO should have direct board access, either through a formal reporting line or regular attendance at the risk or audit committee.
Writing a specification that tries to cover everything. Some briefs ask for a hands-on security architect, a regulatory specialist, a board-level communicator and a transformation leader in one person. Few people are all four. Decide which two matter most for the next three years and build the team around the rest.
Leaving the role vacant during a regulatory deadline. A long permanent search during a DORA implementation, an operational resilience remediation or the run-up to March 2027 can leave the firm exposed. An interim CISO can hold the programme while the permanent search runs.
Permanent, interim or fractional CISO?
Not every organisation needs a full-time permanent CISO from day one. A large regulated firm almost always does. A smaller payment institution, a growing fintech or a mid-sized business entering a regulated market may be better served by a fractional CISO who provides senior leadership, board reporting and regulatory oversight for a set number of days a month, supported by an internal security manager or a managed service. Our fractional C-suite practice places senior leaders on exactly that basis.
Interim CISOs suit a different need: a vacancy after a departure, a remediation programme following an incident or supervisory finding, or a fixed implementation task such as building a PS26/2 reporting process. A good interim arrives with the experience to act quickly and leaves behind a function a permanent hire can take on. We place interim leaders through our interim executive recruitment service, and an interim engagement can also give a firm time to decide what the permanent role should look like. Whichever model you choose, our CISO search team can advise on how the regulatory context should shape the brief.
Frequently asked questions
Does DORA apply to UK firms?
Only where they operate in the EU. DORA applies to EU financial entities, so a UK group’s EU-authorised subsidiaries are in scope, as are some UK firms serving EU clients through EU entities. A UK-only firm is not directly in scope, though UK suppliers to EU financial firms will see DORA requirements in their contracts.
Is the UK adopting NIS2?
No. NIS2 is an EU directive and the UK is not transposing it. The UK is updating its own NIS Regulations 2018 through the Cyber Security and Resilience Bill, which was in its final parliamentary stages in November 2026.
When do the FCA’s new incident reporting rules start?
PS26/2 was published in March 2026 and the rules apply from 18 March 2027. Firms should already be building classification thresholds, reporting workflows and, where in scope, a register of material third-party arrangements.
Is the CISO a senior manager function under SMCR?
No. There is no CISO senior manager function. Operational resilience accountability usually sits with a senior manager, often the SMF24 Chief Operations function holder where the firm has one, and the CISO supports that individual and reports to the board or its committees.
What happened to the ICO?
On 30 September 2026 the Information Commissioner’s Office was replaced by the Information Commission under the Data (Use and Access) Act 2025. Its powers and responsibilities are unchanged, and personal data breach reporting duties still apply.
Should a smaller regulated firm hire a fractional CISO?
Often, yes. A fractional CISO can provide board reporting, regulatory oversight and programme leadership for a few days a month, alongside an internal security manager or managed service, at a cost that suits a smaller firm. As the firm grows or its regulatory scope widens, the role can move to full-time.
Need a CISO who is ready for the regulator?
Exec Capital places permanent, interim and fractional CISOs and security leaders across financial services and other regulated sectors. Tell us about the role and the regulatory context, and we will come back with a clear view of the market.
Related Security and Technology Leadership Services
Exec Capital places CISOs, technology leaders and the senior risk and operations roles that work alongside them, on permanent, interim and fractional terms. Every search is run by our specialist team, with Adrian Lawrence FCA overseeing each mandate.
PRACTICE AREA
CISO & Security Leadership
Permanent, interim and fractional CISOs and information security risk leaders for regulated and growing businesses.
→ Information Security Risk Officer
PRACTICE AREA
Technology Leadership
CTOs and technology executives whose platforms and suppliers the CISO has to secure.
→ Technology & Digital Leadership
PRACTICE AREA
Operational Resilience & Risk
COOs and CROs at regulated firms who hold the accountability the CISO’s work supports.
PRACTICE AREA
Regulated Firm Appointments
Senior hires at banks, insurers, payment firms and other FCA-regulated businesses.
→ FCA Regulated Firm Recruitment
→ Financial Services Executive Search
Every search is run by our specialist team, with Adrian Lawrence FCA overseeing each mandate.
About the author
Adrian Lawrence FCA is the founder of Exec Capital. He is a Chartered Accountant holding an ICAEW practising certificate in his own name, with more than 25 years’ experience operating at C-suite level. His background spans private equity-backed businesses, owner-managed companies and listed environments, giving Exec Capital a practitioner’s understanding of what senior leadership hires actually require. View Adrian’s ICAEW profile.