TLP:CLEAR · Public page

Leaders learning from leaders.

Independent conversations. Shared experience. Stronger cyber leadership.

An invitation-led community bringing together CISOs, CIOs, CTOs, heads of cybersecurity and senior technology, risk and resilience leaders across critical infrastructure, financial services, energy, healthcare, higher education and global enterprises.

We focus on the critical decisions where cybersecurity, business strategy, regulatory accountability, AI adoption and operational reality intersect: from financial trading platforms and corporate networks to solar farms, wind turbines, battery energy storage systems, oil and gas facilities, water treatment works and connected healthcare environments.

Different sectors. Different threats. Different consequences. One shared responsibility: protecting people, information, operations and business resilience.

No sales pitches. No commercial agenda. Just trusted, practical conversations between leaders who understand the responsibility of making difficult security decisions.

SpotlightAI governance and control · What leaders need to know, in plain terms FreeCoffee with a CISO · 30 minutes on the cyber question on your mind
Ten sectors and AI governance around the Chatham House Rule. Select a sector to open its details. CHATHAM HOUSE RULE Trusted conversations. Candid perspectives. Shared learning. PV BESS WIND H₂O O&G ENT FIN CNI HEALTH EDU AI
Select a sector, or AI, to open its details
Sectors we cover

Different industries. Shared leadership challenges.

An invitation-only peer exchange for CISOs, CIOs, CTOs and senior cyber, technology and risk leaders navigating complex security, regulatory and operational decisions. The Exchange brings together perspectives from enterprise IT, industrial operations, financial services, critical infrastructure and other regulated environments.

No single cybersecurity approach works equally across every sector. Security priorities must reflect the potential consequences for people, business services, physical operations, information and the wider economy.

Across every sector: AI is now the fastest-moving risk leaders are asked about. Open AI governance and control, the first card below.

Applicability: regulatory obligations depend on jurisdiction, operator classification, licensed activities, business model and the relevant legislation. Standards and guidance are listed separately and are not mandatory unless a regulator or contract requires them.

Across every sector · Spotlight

AI governance and control

The fastest-moving risk leaders are asked about: where AI is used, what it can see, what it can do, and who answers for it.

Enable AI with confidence. Keep control of the risk.

AI is now inside email, code, customer service, security operations and, increasingly, operational decisions. The question for leaders is no longer whether the organisation uses AI. It is whether anyone can say where it is used, what data it touches, what it is allowed to do, and who is accountable when it gets something wrong.

AI governance is not a separate programme. It extends the security, data, risk and assurance disciplines leaders already run, with new failure modes to account for.

In plain terms

AI governance answers four questions

Where are we using AI?Every tool, model and supplier feature, including the ones staff found themselves.
What can it see?Which data it can read, and which data must never go into it.
What can it do?Whether it only suggests, or can send, change, buy or switch things on its own.
Who answers for it?A named owner, a way to check it works, and a plan for when it goes wrong.
Layer 1 · Govern

Who decides, and on what basis?

  • Named executive accountability for AI risk
  • AI policy and acceptable use, including external AI tools
  • An inventory of AI systems, models and AI-enabled suppliers
  • Risk appetite and approval thresholds by use case
  • Cross-functional oversight: security, data, legal, risk and the business
Layer 2 · Secure

Can the AI be misused, manipulated or leak data?

  • Data classification and controls on what AI can access
  • Defences against prompt injection and data poisoning
  • Least privilege for AI agents and their tool connections
  • Model, plugin and AI supply chain assurance
  • Logging of prompts, outputs and agent actions
Layer 3 · Assure

How do we know it keeps working as intended?

  • Testing and AI red teaming before release
  • Ongoing monitoring for drift, misuse and abnormal behaviour
  • Human oversight where decisions affect people or safety
  • Internal audit and third-party assurance
  • Board reporting on AI risk and incidents

Control across the AI lifecycle

Controls belong at each stage, not only at launch.

  1. Stage 1

    Intake and approval

    Register the use case, classify its risk and data, and confirm who owns it.

  2. Stage 2

    Build or buy

    Assess models, vendors and data sources. Contract for security, data use and incident notice.

  3. Stage 3

    Test and red team

    Test for prompt injection, data leakage, harmful output and unsafe agent actions.

  4. Stage 4

    Deploy and monitor

    Limit permissions, log activity, watch for drift and misuse, and keep humans in the loop.

  5. Stage 5

    Review and retire

    Reassess as models, data and regulation change. Retire systems cleanly, including their data.

The risks leaders are managing

Sensitive data exposure

Confidential, personal or client data pasted into AI tools, or surfaced by an AI assistant to people who should not see it.

Shadow AI

Staff using unapproved AI services and browser extensions outside security, data protection and contract controls.

Prompt injection and manipulation

Hidden instructions in emails, documents or web pages that hijack an AI system into leaking data or taking actions.

Over-privileged AI agents

Agents connected to email, files, code or business systems with more access and autonomy than the task needs.

AI supply chain

Third-party models, plugins and AI features added to existing software, often without a fresh risk assessment.

Unreliable output in decisions

Confident but wrong answers feeding financial, clinical, legal or operational decisions without adequate checks.

AI-enabled attacks

Deepfake voice and video fraud, convincing phishing at scale, and faster vulnerability discovery by attackers.

AI near operational technology

AI-driven optimisation or analytics connected to control systems, where an unsafe recommendation or action has physical consequences.

Legally binding

Regulation and law

What applies, and when.
European Union · AI Act
  • Prohibited AI practices and AI literacy duties: applying since February 2025
  • General-purpose AI model obligations: applying since August 2025
  • Transparency obligations (Article 50): applying from 2 August 2026
  • High-risk AI (Annex III): deferred to 2 December 2027 by the Digital Omnibus on AI, in force since 27 July 2026
  • High-risk AI in regulated products (Annex I): deferred to 2 August 2028
United Kingdom
  • No AI-specific statute: existing law and sector regulators apply
  • UK GDPR, Data Protection Act 2018 and the Data (Use and Access) Act 2025, including automated decision-making
  • Equality, consumer protection and sector rules, including FCA expectations for regulated firms
Elsewhere
  • A growing patchwork of national, state and sector rules. Check each jurisdiction you operate in.
Voluntary, unless required by contract or regulator

Standards and guidance

How to build and evidence good practice.
Management systems and risk
ISO/IEC 42001 (AI management system)ISO/IEC 23894 (AI risk management)NIST AI RMF and Generative AI Profile
AI security
UK AI Cyber Security Code of PracticeETSI EN 304 223NCSC and partners' guidelines for secure AI developmentOWASP Top 10 for LLM ApplicationsMITRE ATLAS
Data protection
ICO guidance on AI and data protection

Same principles, different stakes by sector

Enterprise and technology

Copilots and assistants with broad access to email and files. Data access controls and labelling matter more than the model itself.

Financial services

Model risk management, explainability, fair treatment of customers and resilience of AI-dependent important business services.

Energy and OT

AI may advise, but safety-relevant changes to control systems need engineering approval, fail-safe design and human authority.

Healthcare and higher education

Patient and student data, research integrity, clinical safety and academic openness, often with limited central control.

What leaders must decide

  1. Who is accountable for AI risk, and does the board know?
  2. Do we know every AI system and AI-enabled supplier we rely on?
  3. Which data must never enter external AI services?
  4. Which decisions can AI make alone, and which always need a human?
  5. What can an AI agent do without approval, and how is that limited?
  6. How do we test AI for manipulation before it goes live?
  7. Can we detect and investigate misuse of an AI system?
  8. How do we assess AI features quietly added to existing software?
  9. Where is AI allowed near operational technology, and under whose authority?
  10. How will we evidence compliance as AI regulation changes?

The leadership principle

Banning AI pushes it into the shadows. Allowing it without control moves risk faster than the organisation can see it.

The goal is governed adoption: clear accountability, controlled data, bounded autonomy and evidence that it works as intended.

Sector 01 · Renewable energy · OT

Solar PV

Large, distributed and often unmanned generation environments.

Solar farms rely on inverters, power plant controllers, SCADA, telecommunications infrastructure and third-party operations and maintenance providers. Growing connectivity adds cyber risk through remote access, cloud monitoring, suppliers and interfaces with grid operations.

What's at stake

Generation availability, grid-code compliance, remote operational control, commercial performance and third-party access.

Typical systems
Solar invertersPower plant controllersSCADARemote terminal unitsRemote-access gatewaysGrid interface systemsOEM monitoring platforms
Regulatory obligations and oversight
  • UK NIS Regulations 2018, where applicable
  • Relevant Ofgem and electricity-sector requirements
  • EU NIS2 and national implementing legislation, where applicable
  • Applicable national energy-sector cybersecurity obligations
Standards and guidance
NCSC CAFIEC 62443IEC 62443-2-4 (service providers)IEC 62351ISO 27001

Leadership questionWho owns the cyber risk when remote access to critical generation assets is controlled by an OEM or maintenance contractor?

Sector 02 · Energy storage · OT

Battery energy storage (BESS)

Increasingly important to modern electricity systems.

BESS environments combine battery management, energy management, power conversion, industrial controllers, grid connectivity and commercial optimisation platforms. Cybersecurity must consider both digital compromise and the physical consequences of unauthorised control.

What's at stake

Thermal and electrical safety, asset availability, grid services, revenue, operational control and the integrity of OEM-managed technology.

Typical systems
Battery management (BMS)Energy management (EMS)Power conversion (PCS)SCADAFire and safety monitoringGrid control systemsTrading and optimisationRemote OEM support
Regulatory obligations and oversight
  • UK NIS Regulations, where the operator and activities are in scope
  • Applicable electricity licensing and grid obligations
  • Relevant battery, electrical and fire safety requirements
  • EU NIS2, where applicable
  • National energy infrastructure requirements
Standards and guidance
NCSC CAFIEC 62443IEC 62351IEC 62933 seriesISO 27001

Leadership questionIf a cyber incident affects battery control or remote monitoring, who determines the safe operational state, and who has authority to act?

Sector 03 · Renewable energy · OT

Onshore and offshore wind

Turbine controllers, substations and extensive OEM relationships.

Wind generation depends on industrial control systems, turbine controllers, remote monitoring, substations and OEM service relationships. Offshore sites add physical access, connectivity and recovery challenges.

What's at stake

Fleet availability, personnel safety, generation output, grid compliance, remote access and supply chain dependency.

Typical systems
Turbine controllersWind farm SCADASubstation automationIEC 61850 communicationsCondition monitoringOEM management platformsRemote maintenance
Regulatory obligations and oversight
  • UK NIS Regulations, where applicable
  • Relevant UK electricity-sector obligations
  • EU NIS2, where applicable
  • Applicable regional energy-sector cybersecurity requirements
Standards and guidance
NCSC CAFIEC 62443IEC 62351IEC 61400-25ISO 27001

Leadership questionHow do you maintain effective monitoring and response when assets are remote, the OEM controls key systems and physical intervention may take hours or days?

Sector 04 · Utilities · OT

Water and wastewater

Essential public health and environmental services.

Treatment works, pumping stations and distribution systems rely on SCADA, telemetry, PLCs and widely dispersed operational assets.

What's at stake

Drinking water quality, wastewater management, public safety, environmental protection and continuity of essential services.

Typical systems
SCADAPLCsRemote telemetry unitsChemical dosingPump controlWater quality monitoringIndustrial communications
Regulatory obligations and oversight
  • UK NIS Regulations for qualifying operators
  • Drinking Water Inspectorate oversight in England and Wales, where applicable
  • Relevant environmental regulation
  • EU NIS2, where applicable
  • Sector-specific national resilience requirements
Standards and guidance
NCSC CAFIEC 62443ISO 27001NIST SP 800-82

Leadership questionHow should security leaders respond when a simple containment action could interrupt water treatment or pumping?

Sector 05 · Process industry · OT

Oil and gas

Complex plant where safety and environmental protection come first.

Production facilities, pipelines, gas control environments and processing plants often rely on long-lived industrial control systems.

What's at stake

Process safety, environmental impact, production continuity, infrastructure resilience and protection of legacy systems.

Typical systems
Distributed control (DCS)Safety instrumented systems (SIS)PLCsPipeline SCADAGas control systemsIndustrial historiansRemote engineering access
Regulatory obligations and oversight
  • UK NIS Regulations, where applicable
  • Relevant HSE and major accident hazard legislation
  • Applicable offshore and onshore safety requirements
  • EU NIS2, where applicable
  • Relevant national oil and gas cybersecurity requirements
Standards and guidance
IEC 62443IEC 61511NCSC CAFHSE OG86NIST SP 800-82

Leadership questionWhen an industrial cyber incident threatens operations, how do security teams coordinate with process safety and engineering authorities without creating further risk?

Sector 06 · Global enterprise · IT

Enterprise and technology

People, identities, applications, data and suppliers, all connected.

Cloud adoption, digital transformation, AI, hybrid working and third-party integration create complex security dependencies.

What's at stake

Business continuity, intellectual property, customer information, financial transactions, identity compromise and enterprise resilience.

Typical systems
Active Directory and Entra IDCloud infrastructureSaaSERPEmail and collaborationEndpointsData platformsAI-enabled applications
Regulatory obligations and oversight
  • UK GDPR and Data Protection Act 2018
  • Applicable sector-specific legal requirements
  • UK NIS Regulations for qualifying digital service providers
  • EU NIS2, where applicable
  • EU Cyber Resilience Act for relevant products and economic operators, subject to its phased dates
Standards and guidance
ISO 27001 and 27002NIST CSF 2.0Cyber Essentials PlusISO 22301ISO 27017ISO 27018

Leadership questionHow can leaders balance digital transformation, cloud, AI innovation and growth against increasingly complex security and regulatory obligations?

Sector 07 · Regulated financial services · IT

Banking, hedge funds, investment management and fintech

Confidentiality, transaction integrity and market confidence are critical.

Cybersecurity is inseparable from financial resilience, third-party dependencies, fraud prevention and business trust.

What's at stake

Client assets, market confidence, operational resilience, data confidentiality, transaction integrity, regulatory compliance and financial stability.

Typical systems
Trading platformsOrder managementPortfolio managementPayment infrastructureMarket dataFinancial messagingPrivileged accessCloud and SaaS
Regulatory obligations and oversight
  • Applicable FCA and PRA requirements
  • UK operational resilience rules for in-scope firms
  • EU DORA for in-scope EU financial entities
  • UK GDPR and Data Protection Act 2018
  • UK critical third parties regime, where applicable
Standards and guidance
ISO 27001NIST CSF 2.0CBEST, where applicableTIBER-EU

Leadership questionWhen controls protect sensitive transactions but may affect trading availability or important business services, how should leaders balance security, resilience and business impact?

Sector 08 · National resilience · IT and OT

Critical national infrastructure

Services whose disruption affects national security and society.

Critical infrastructure includes transport, telecommunications, energy, water and other nationally significant services, where disruption could affect national security, economic stability or public wellbeing.

What's at stake

National resilience, essential service continuity, public safety, cascading failures, supply chain dependencies and nation-state threats.

Typical systems
Industrial control systemsSCADATelecoms infrastructureTransport and signallingNetwork managementOperational communications
Regulatory obligations and oversight
  • UK NIS Regulations for in-scope entities
  • Telecommunications (Security) Act 2021, where applicable
  • EU NIS2 and national implementation
  • Australian SOCI Act, where applicable
  • NERC CIP in North American bulk electric system environments
Standards and guidance
NCSC CAFIEC 62443NIST CSFNIST SP 800-82AESCSF

Leadership questionHow should an organisation assess cyber risk when an incident could affect essential services beyond its own commercial operations?

Sector 09 · Regulated healthcare · IT, devices and OT

Healthcare and life sciences

Patient safety, sensitive data, clinical technology and manufacturing.

Healthcare and life sciences combine sensitive information, essential services, clinical technology, research and pharmaceutical manufacturing. Failures can directly affect patient care, safety and public trust.

What's at stake

Patient safety, continuity of care, sensitive health information, medicine production, clinical availability and research integrity.

Typical systems
Electronic patient recordsClinical applicationsMedical devicesLaboratory systemsResearch environmentsPharmaceutical manufacturing
Regulatory obligations and oversight
  • UK GDPR and Data Protection Act 2018
  • NHS Data Security and Protection Toolkit, where applicable
  • UK NIS Regulations for qualifying healthcare operators
  • Relevant medical-device regulation
  • Pharmaceutical manufacturing and quality requirements
  • EU NIS2, where applicable
Standards and guidance
ISO 27001IEC 80001-1IEC 62443 (industrial)NCSC CAF, where applicable

Leadership questionHow should security teams contain a threat when isolating a connected clinical device or system could affect patient care?

Sector 10 · Research and education · IT

Universities and higher education

Open, collaborative and complex by design.

Universities support large numbers of users, decentralised technology, valuable research, cloud platforms and international collaboration.

What's at stake

Research intellectual property, student and staff data, teaching continuity, institutional reputation and academic collaboration.

Typical systems
Identity and accessStudent recordsResearch computing and HPCCloud collaborationLearning managementLaboratory technology
Regulatory obligations and oversight
  • UK GDPR and Data Protection Act 2018
  • Research security and export controls, where applicable
  • Relevant contractual and funding requirements
  • EU NIS2 only where national law brings an institution into scope
Standards and guidance
ISO 27001Cyber Essentials PlusNCSC guidanceTrusted ResearchNIST CSF

Leadership questionHow can a university keep academic openness and research collaboration while protecting sensitive information and staying resilient?

Background · Cybersecurity across IT and OT

One security discipline. Different operational consequences.

Corporate IT and operational technology increasingly share identities, networks, cloud infrastructure, suppliers and attack paths. Yet the consequences of an incident, and the actions needed to contain it, can be fundamentally different.

Corporate information technology

Protecting identities, data, transactions and business services.

Corporate security protects information, people, business applications, communications and critical enterprise processes.

Incidents may cause
Data lossFinancial fraudRansomware disruptionBusiness interruptionRegulatory exposureReputational damageLoss of transaction integrity

Response may include endpoint containment, account suspension, credential revocation, network isolation and controlled recovery, subject to business impact and approval.

Operational technology

Protecting physical processes, safety and operational continuity.

OT security protects the industrial systems behind electricity generation, energy storage, gas distribution, manufacturing, water treatment and other physical processes.

Incidents may cause
Equipment damageLoss of generation or productionSafety incidentsEnvironmental harmLoss of visibilityUnauthorised control changesDisruption of essential services

Response needs coordination with engineering, operations and safety teams. Disconnecting a controller or blocking communications can itself introduce operational risk.

DimensionCorporate ITOperational technology
Core objectiveProtect data, transactions and business servicesProtect safety, physical processes and operational continuity
Typical assetsEndpoints, servers, identities, cloud, SaaSPLC, RTU, DCS, SCADA, BMS, EMS, SIS
MonitoringEDR, identity telemetry, cloud and application logsIndustrial network monitoring, protocol analysis, asset visibility and process context
ThreatsCredential theft, ransomware, malware, data exfiltrationUnauthorised commands, engineering changes, controller compromise, remote-access abuse
PatchingRegular change-controlled maintenanceEngineering-tested changes in approved maintenance windows
ContainmentEndpoint, account or workload isolation where authorisedSite-aware actions coordinated with operational and safety authorities
Incident ownershipSecurity and IT service ownersSecurity, engineering, site operations and safety teams
Success measureReduced business risk and service restorationSafe operation, process integrity and controlled recovery

The leadership challenge

Neither environment has a universal priority order. Confidentiality, integrity, availability and safety must be weighed against the consequences of failure for each system.

The goal is not to choose between corporate IT security and OT security. It is a coordinated strategy that recognises different operational constraints while keeping accountability clear.

Security operations · Detection · Response · Resilience

One threat landscape. Two very different monitoring challenges.

A 24/7 SOC is only as effective as what it can see, understand and safely respond to. Collecting logs, deploying a SIEM or outsourcing alert management does not by itself create an effective detection and response capability. Corporate IT and OT need different telemetry, detection logic, operational understanding and response authority.

Operating models leaders weigh
Internal SOCMSSPMDRDedicated OT monitoringHybrid SOCConverged IT/OT operationsSpecialist incident response
Corporate SOC

Identities, data, applications and enterprise services

Detecting threats across users, endpoints, cloud services, networks and business applications.

What it monitors
Identity and privileged accessEndpoints and serversEmail and collaborationCloud and SaaSData loss and insider threatLateral movementInternet-facing assetsThird-party accessRansomware and malware
Technologies
SIEMEDRXDRIdentity threat detectionDLPSOARNDRCloud security monitoring

What good looks like: analysts correlate activity across identities, endpoints, networks, data and cloud, understand business impact, and take authorised containment action before an incident becomes a material disruption.

OT SOC

Industrial processes, continuity and physical safety

Judging whether activity is abnormal, unauthorised or potentially dangerous for a process, not only whether it is suspicious.

What it monitors
SCADA communicationsPLC and RTU interactionsIndustrial networksEngineering workstationsLogic and configuration changesIndustrial protocol commandsOEM and contractor accessIT/OT boundary trafficUnexpected process behaviour
Technologies
OT network detectionPassive asset discoveryProtocol inspectionIndustrial firewall loggingRemote-access monitoringEngineering change monitoringProcess-aware detection

What good looks like: analysts use industrial context, validate consequences with engineering and operations, and respond through approved procedures that protect people, process integrity and continuity.

Important distinction

Traditional IT monitoring tools must not be deployed automatically into sensitive OT environments. Active scanning, endpoint agents, automated isolation and uncontrolled response actions need compatibility assessment, operational authorisation and suitable safeguards.

Converged IT/OT security operations: one coordinated response, different operational rules

A converged model brings together threat intelligence, identity security, endpoint detection, OT network visibility, engineering expertise and incident coordination. It does not mean treating industrial controllers like corporate laptops.

Corporate SOC

IdentityEndpointEmailCloudDataNetwork

OT SOC

SCADAPLCBMSEMSIndustrial networksRemote access

Converged security operations

Shared intelligenceCorrelated detectionCoordinated escalationIncident command
Supported by engineering · security · operations · business leadership
One governance model. Different operational safeguards.

MSSP, MDR or in-house SOC? Outsourcing monitoring does not outsource accountability.

The right model depends on operational complexity, business criticality, geography, internal capability and cost.

In-house SOC

Internal teams own monitoring, investigation and response directly.

Specialist expertiseStaffing24/7 capabilityCostDetection engineeringScalability

MSSP

Providers deliver managed monitoring, correlation, escalation and other contracted services.

Service boundariesLog coverageInvestigation qualityEscalationSLAsIncident ownershipVendor dependency

MDR

Deeper investigation, threat hunting and response support, within the contract and technical scope.

Real response capabilityEndpoint and identity coverageAuthority to actEvidence handlingBusiness context

Dedicated OT SOC

Specialist monitoring of industrial control systems, networks and OT-specific threats.

Protocol expertiseSite understandingEngineering integrationSafe responseOEM access

Hybrid or converged SOC

Internal security leadership combined with external monitoring and specialist OT capability.

Clear ownershipIntegrated visibilityOperational response authorityCross-domain escalationSupplier governanceCoverage and resilience

What leaders must decide

  1. Are we buying log monitoring, investigation, response or measurable protection?
  2. Can our SOC detect an attacker moving from a compromised corporate identity into OT remote access?
  3. Do we have visibility of OEM connections and industrial control changes?
  4. Can our MSSP tell normal industrial communications from suspicious activity?
  5. Who can authorise containment if stopping a system could affect safety or production?
  6. Which services need 24/7 monitoring, and which need specialist on-call escalation?
  7. How do we validate that detections work in practice?
  8. Are the SOC and engineering teams ready to respond together?
  9. What happens if the MSSP or its technology becomes unavailable?
  10. How do we report monitoring effectiveness to the board?

The leadership principle

The objective is not one SOC for everything. It is one accountable security operating model with the right visibility, expertise and response authority for every environment.

The technology may be connected. The risks are not identical. Understanding both is a leadership responsibility.

Discussion themes

Eight themes across IT, OT and executive leadership.

Our discussions concentrate on the issues security leaders must understand, defend, fund and take accountability for. Every roundtable is built around practical decisions, lived experience and competing priorities.

Theme 01

Regulation and regulatory change

What applies to us, and who enforces it?

United Kingdom

NIS Regulations 2018Cyber Security and Resilience Bill (proposed, Oct 2026)NCSC CAFOfgemDrinking Water InspectorateHSEUK GDPR and DPA 2018FCA and PRATelecoms security legislationPSTI Act 2022

European Union

NIS2 and national lawsDORACyber Resilience Act (phased)GDPR

North America

NERC CIPSector and state requirements

Australia

SOCI ActAESCSF
Discussion questions
  • How do you align NIS2, NERC CIP and SOCI controls without running disconnected programmes?
  • How do obligations differ between corporate entities and operational asset operators?
  • How should organisations prepare for proposed legislation?
  • What do regulators, insurers and legal advisers expect after a significant incident?
  • How should leaders manage cross-border reporting and accountability?
Theme 02

Security maturity and risk assessment

Where do we actually stand today?
Approaches
NCSC CAFIEC 62443 risk assessmentNIST CSF 2.0C2M2OT asset and network reviewsArchitecture assessmentsVulnerability managementPenetration testingThreat-led testingSupplier risk assessments
Discussion questions
  • How do you assess an organisation running both IT and OT?
  • How can you test industrial security safely?
  • What does a realistic maturity assessment look like?
  • How do you prioritise investment when every team says its risks are critical?
  • How do you show progress beyond a maturity score?
Theme 03

Assurance and control effectiveness

How do we prove controls are working?
Mechanisms
ISO 27001 certificationCyber Essentials PlusSOC 2ISAE 3402Internal auditThree lines modelControl testingThird-party assuranceBoard assuranceRegulatory reporting
Discussion questions
  • When does certification give meaningful assurance?
  • What evidence shows a control is effective?
  • How do you assess OT that cannot be tested conventionally?
  • Which assurance reports should you require from critical suppliers?
  • How do you tell compliance from resilience?
Theme 04

Security operations and threat detection

Who's watching, what can they see and who can respond?
Operating models
Corporate SOCOT SOCConverged IT/OT SOCMSSPMDRSIEM and SOAROT network monitoringThreat intelligenceIR retainersDetection engineering
Discussion questions
  • Should the SOC be internal, outsourced or hybrid?
  • Does an MSSP have the skills to monitor industrial control systems?
  • What must the MSSP contract include?
  • How do you measure detection coverage and response quality?
  • Who can approve industrial containment when an incident spans IT and OT?
Theme 05

Supply chain and third-party risk

Who else holds the keys?
Practices
Supplier due diligenceContractual security requirementsOngoing monitoringOEM remote accessCloud dependenciesSoftware supply chainSBOMsFourth-party riskConcentration riskExit planning
Discussion questions
  • How much due diligence is enough before signing?
  • How should OEMs be granted access to turbines, inverters and batteries?
  • Who owns the risk created by external OT providers?
  • What do you do when a critical supplier fails an assessment?
  • What if a critical cloud or managed security provider becomes unavailable?
Theme 06

Board governance and cyber investment

Does the board understand the risk it is carrying?
Leadership tools
Enterprise risk registersRisk appetite and tolerancesKey risk indicatorsCyber risk quantificationFinancial exposure modellingBoard reportingAudit committeeBusiness casesCyber insuranceDirectors' dutiesUK Corporate Governance Code, Provision 29
Discussion questions
  • How do you translate technical findings into business risk?
  • Which three metrics should a CISO present to a board?
  • Can cyber risk be expressed credibly in financial terms?
  • How do you justify cybersecurity investment?
  • How should boards evaluate the effectiveness of material controls?
Theme 07

AI, data and emerging technology

How do we enable innovation without losing control? See also AI governance and control.
Topics
AI governanceAI system securityGenerative AIShadow AISensitive data exposureData classificationDLPInsider riskPrivacyModel governanceAI third-party riskCloud and architecture
Discussion questions
  • Who is accountable for AI risk in an organisation?
  • How do you govern confidential data in AI systems?
  • What safeguards are needed before allowing autonomous security actions?
  • How do you separate useful AI investment from unnecessary complexity?
  • How should organisations govern staff use of external AI services?
Theme 08

Cyber resilience and crisis leadership

Can the organisation operate through a serious incident?
Topics
Incident responseCrisis managementBusiness continuityDisaster recoveryOperational resilienceExecutive decision-makingTabletop exercisesRansomware responseIT/OT coordinationRegulatory notificationRecovery testing
Discussion questions
  • Who commands a cyber crisis spanning IT and OT?
  • When does incident response become a business crisis?
  • Can critical operations continue without central IT?
  • How do you decide with incomplete information?
  • How do you establish that recovery is safe and sustainable?
What makes the Exchange different

The hard part is rarely the technical control.

Most cybersecurity events concentrate on threats, products and tooling. Ours concentrate on judgement: the difficult decisions leaders face when cyber risk collides with operational safety, financial performance, regulatory expectations, technical limits and business priorities.

Each session begins with a realistic leadership decision. Participants explore how different organisations and sectors would respond, which assumptions shape their choices and which consequences matter.

A financial services CISO, an energy-sector security leader and a technology executive may reach different conclusions. That is the value of bringing different experience together.

We are not here to agree one universal answer. We are here to improve the quality of leadership decisions.

Example session · Incident 0106:40 · Monday morning

The attacker crossed the boundary. Who makes the next decision?

A renewable energy operator finds ransomware in its corporate IT environment. The SOC sees suspicious authentication from a remote-access account used by a third-party maintenance provider, and unusual traffic toward OT supporting three wind farms and a battery storage site. There is no confirmed malicious controller activity. Generation continues, but the team cannot tell whether the attacker has reached operational systems.

  • Security operationsDoes the corporate SOC have enough OT visibility to tell suspicious connectivity from genuine compromise?
  • Engineering and safetyCan the remote-access path be isolated without disrupting safe operations, monitoring or maintenance support?
  • Regulatory responseWhich reporting obligations may apply, what evidence is needed, and which deadlines have started?
  • Executive leadershipWho approves containment: the CISO, incident commander, engineering lead or accountable executive?
  • Business continuityIf central monitoring is lost, can sites run safely under local control, and for how long?
  • The boardWhat should directors hear in the first hour: what is confirmed, what is uncertain, and which decisions need approval?
The roundtable questionWould you isolate the IT/OT connection immediately, or keep controlled connectivity while you investigate? What evidence, safeguards and authority would you need first?

There is no single correct answer without understanding the architecture, operational dependencies and safety consequences.

Three programmes

One exchange. Three ways to take part.

Three independent, non-commercial programmes, all built on professional contribution, practical experience and mutual respect.

Programme one

CISO Roundtable

Leaders learning from leaders

Private, cross-industry peer discussions for established cybersecurity and technology leaders. Bring decisions you are facing, share lessons learned and test your thinking with peers who have managed similar challenges.

Who
CISOs, CIOs, CTOs, heads of cybersecurity, and senior GRC, risk and resilience leaders
Size
6–8 participants per session
Format
90 minutes, online, built around a practical scenario or leadership theme
Frequency
Scheduled during the pilot around participant availability
Cost
Free
Discussion areas
Cyber strategyRegulation and assuranceIT/OT securitySOC and MSSP modelsSupply chain riskAI and data governanceBoard reportingResilience and crisis
Programme two

The Next CISO

Mentoring future cybersecurity leaders

One-to-one mentoring for cybersecurity professionals preparing for senior leadership: the move from technical specialist or security manager to a leader responsible for people, strategy, budgets, governance and business outcomes.

Who
Aspiring and newly appointed cybersecurity leaders
Format
One-to-one mentoring
Duration
Three sessions over about three months
Cost
Free
Mentoring themes
Executive presenceCommunicating cyber riskBuilding a strategyGovernance and regulationSecurity operating modelsFrom delivery to leadershipBudgets and stakeholdersJudgement and confidence

Mentoring offers experience-based guidance, not guaranteed employment, certification or career advancement.

Programme three

Coffee with a CISO

A free 30-minute conversation about the cyber question on your mind

Not every question needs a programme or a consultant. Some need half an hour with someone who has faced it before. Bring one question and leave with a clearer view of your options and a sensible next step.

Good questions to bring
A decision you're weighingPreparing for a board or regulatorNIS2, CAF or DORA: where to startSOC or MSSP choicesIT/OT securityAI governanceSupplier riskStepping into a CISO role

Coffee with a CISO offers experience-based perspective, not consultancy, legal advice or a security assessment. There is no sales follow-up.

Who
Security leaders, business owners, board members and anyone facing a cyber or risk question
Length
30 minutes, online
Cost
Free
Pay it forward, if you like

If the conversation helped, donate to a charity of your choice or one Nathan recommends, or buy him a coffee. Entirely optional.

TLP:AMBER+STRICT · How sessions are handled

Trust makes the conversation possible.

The Exchange runs on confidentiality, independence, respectful participation and professional responsibility. These rules apply equally to the founder and host.

Chatham House Rule

Use what you learn, but never disclose the identity or organisation of speakers or other participants.

No recording or AI transcription

Sessions are not recorded, livestreamed or automatically transcribed. AI notetakers and meeting assistants are not permitted.

Protect sensitive information

Do not share confidential information, personal data, credentials, operationally sensitive details or unreported vulnerabilities without authority. Sanitise scenarios.

No commercial solicitation

Not a lead-generation forum: no product demos, recruitment, unsolicited approaches or sales pitches.

Respect professional boundaries

Respect employment duties, contractual confidentiality, data protection law, regulatory obligations and conflicts of interest.

Nothing identifiable is published

Names, affiliations and identifiable experiences are never published without explicit permission. Anonymised lessons are reviewed for indirect identification risk.

Equal contribution

Discussion favours thoughtful contribution, professional experience and respectful challenge.

Independent and non-commercial

The Exchange sells no consultancy, assessments, certifications or managed services. Participation is free, and discussions do not replace professional advice.

Founding pilot · UK-based · Winter 2026–27

Starting small on purpose.

The first 90 days are a quiet founding pilot with a small UK-based group, focused on trust, relevance, quality of discussion and usefulness. If the model proves valuable, participation may expand to Europe, the Middle East and other regions.

  1. Phase 01 · now

    Founding conversations

    Personal invitations to a small number of experienced leaders, to understand shared challenges and the topics that matter.

  2. Phase 02

    Two roundtables

    Two private sessions of six to eight participants, each built around one realistic scenario.

  3. Phase 03

    Mentoring begins

    Two aspiring leaders join The Next CISO, with three sessions each over about three months.

  4. Phase 04

    90-day review

    • Were the discussions useful?
    • Did people feel able to speak openly?
    • Did they gain insight they could apply?
    • Would they take part again?

Contribution over volume. Quality over visibility. Trust over promotion.

Founder and host

Nathan Piratheepan

Global Cybersecurity Executive · CISO and Digital Transformation Leader · Financial Services · Critical Infrastructure · Enterprise IT and OT

Nathan brings experience across global cybersecurity leadership, financial services and hedge funds, renewable energy, utilities, critical infrastructure, higher education and multinational enterprises.

His career includes a decade in the hedge fund industry, alongside senior cybersecurity leadership spanning corporate IT, industrial control systems, cloud, enterprise technology and operational resilience. He pairs strategic CISO leadership with CTO-level experience in technology modernisation and digital transformation.

He has led cybersecurity transformation, developed global SOC and security operating models, strengthened governance and assurance programmes, and supported the security of complex IT and OT environments across the UK, Europe, the Americas and Asia-Pacific.

Cybersecurity should not be measured simply by the controls deployed or technology purchased, but by the business value protected, the resilience achieved and the quality of decisions made under pressure.
Why he founded the Exchange

Effective leadership is about more than individual achievement. It means sharing experience, challenging assumptions, helping others succeed and strengthening the profession for the next generation. The Exchange is an independent, non-commercial community where leaders contribute without expectation of commercial reward.

Outside work, Nathan enjoys competitive cycling, HYROX and mountain hiking, including summiting Mount Kilimanjaro.

Areas of expertise
Strategy and transformationGlobal CISO leadershipFinancial services securityEnterprise security architectureIT/OT convergenceICS and SCADAGlobal SOC operating modelsManaged security and detection engineeringGovernance, risk and complianceExecutive and board reportingIncident and crisis managementOperational resilienceSupply chain securityData protection and privacyInsider risk and DLPAI security and governanceCloud securityDigital transformation
Regulatory and framework experience
NIS2NERC CIPSOCINCSC CAFISO 27001NIST CSFIEC 62443Financial services operational resilienceCyber Essentials Plus
Sector experience
Financial services and hedge fundsRenewable energyOil and gasUtilitiesCritical national infrastructureHigher educationGlobal enterprise
A decision worth discussing

The difficult decisions rarely have one obvious answer.

Why it matters

Different sectors. Different risks. Stronger leadership through shared experience.

Cybersecurity leadership is not simply about technology. It means balancing business objectives, regulatory accountability, operational constraints, human judgement and the consequences of failure.

A cyber incident can mean financial disruption at a bank, lost generation at a wind farm, equipment damage at a battery site, compromised water treatment or the loss of essential clinical services. The risks differ. The leadership responsibility remains.

Cyber Leadership Exchange exists to help leaders make better decisions, learn from one another and strengthen the next generation of cybersecurity leadership.

Founding seats open

Request an invitation.

Membership is by invitation during the founding pilot. We are starting with a small group of leaders who value practical knowledge, independent thinking and respectful discussion.

To express interest, connect with Nathan on LinkedIn and send a short message with:

  1. Your current role and sector
  2. Which programme interests you: CISO Roundtable, The Next CISO or Coffee with a CISO
  3. One leadership decision or topic you would like to explore

Places are limited to keep discussion and mentoring quality high. Participation is free.

linkedin.com/in/npiratheepan