A structured discipline for identifying, assessing, prioritising, and treating risks to information systems, data assets, and digital infrastructure arising from threats such as malicious actors, system vulnerabilities, and operational failures. Cybersecurity risk management integrates threat modelling, vulnerability assessment, control selection, and residual risk acceptance into a repeatable governance cycle aligned with organisational risk appetite. Frameworks such as NIST CSF, ISO 27005, and FAIR provide structured methodologies. It bridges technical security practice with executive governance and regulatory compliance.
Semantic Classification
Content
Compositional Relationships (Components)
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:hasPart security:ThreatModelling))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:hasPart security:VulnerabilityAssessment))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:hasPart security:RiskAssessment))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:hasPart security:RiskRegister))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:hasPart security:ContinuousMonitoring))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:hasPart security:IncidentResponse))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:hasPart security:ControlMapping))
Dependency Relationships
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:requires security:SecurityOperations))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:requires security:ThreatDetection))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:requires security:SecurityOperationsCentre))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:dependsOn security:SIEM))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:dependsOn security:SOAR))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:dependsOn security:ThreatIntelligence))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:dependsOn security:VulnerabilityDatabase))
Capability Relationships
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:enables security:CyberResilience))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:enables security:OperationalResilience))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:enables security:ComplianceMonitoring))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:enables security:BoardLevelRiskReporting))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:enables security:RegulatoryCompliance))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:enables security:ResidualRiskAcceptance))
Implementation Relationships
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:implements security:NISTCybersecurityFramework))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:implements security:ISO27001))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:implements security:FAIRQuantitativeModel))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:implements security:RiskAssessmentMethodology))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:implements security:ZeroTrustArchitecture))
Reduction Relationships
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:reducesTo security:RiskAssessment))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:reducesTo security:ControlSelection))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:reducesTo security:ResidualRiskAcceptance))
Governance Relationships
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:supports security:Governance))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:supports security:Accountability))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:bridges security:InformationSecurityManagement))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:bridges security:EnterpriseRiskManagement))
Contrastive Relationships
SubClassOf(security:CybersecurityRiskManagement
ObjectAllValuesFrom(security:contrasts-with security:AISafety))
SubClassOf(security:CybersecurityRiskManagement
ObjectAllValuesFrom(security:contrasts-with security:PhysicalSecurity))
Regulatory Relationships
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:standardizedBy security:NISTCybersecurityFramework))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:standardizedBy security:ISO27001))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:standardizedBy security:NCSCCAF))
SubClassOf(security:CybersecurityRiskManagement
ObjectSomeValuesFrom(security:complianceWith security:NIS2Directive))
About
Cybersecurity Risk Management is the systematic, evidence-based practice of understanding, quantifying, and mitigating threats to the confidentiality, integrity, and availability of information systems and the data they process. Unlike ad hoc security patching or perimeter-focused defence, it provides a structured governance layer that connects technical Security Operations with organisational strategy: every control investment is justified by a documented risk reduction, and every accepted risk is signed off by an accountable risk owner. The discipline has matured considerably since the early 2000s, moving from binary compliance checklists (pass/fail against prescribed standards) toward risk-based and outcomes-based approaches that accommodate the continuously evolving threat landscape. The CIA triad — Confidentiality, Integrity, and Availability — remains the foundational definitional framework for what cybersecurity risk management seeks to protect, and almost all risk taxonomies and control catalogues trace their categorisation logic back to these three properties.
The economics of cybersecurity risk management are distinctive. Unlike physical safety risks where failure modes are usually well-characterised and probability distributions empirically grounded in historical incident data (engineering reliability data, insurance actuarial tables), cyber risk is shaped by adaptive adversaries who actively probe for and exploit weaknesses in controls. This adversarial dynamic means that historical incident frequencies may systematically underestimate future risk as attackers innovate, and that the effectiveness of a control can degrade rapidly once adversaries develop evasion techniques. Anderson’s foundational 2001 paper on the economics of information security identified three systemic distortions: (1) misaligned incentives, where those who build insecure systems do not bear the full cost of their failures; (2) information asymmetry, where vendors conceal vulnerability information; and (3) externalities, where security failures in one organisation impose costs on others through network effects. These distortions justify regulatory intervention — mandatory incident disclosure, minimum security standards, certification schemes — precisely because market mechanisms alone produce persistent underinvestment in cybersecurity Resilience.
The discipline is organised around a management cycle that parallels ISO general management system structures. In the Plan phase, organisations define the scope of the Risk Assessment, identify assets and their owners, map the threat landscape (internal threats, external adversaries, environmental risks), and select a risk assessment methodology. In the Do phase, risk assessments are executed — threats enumerated via Threat Modelling, vulnerabilities identified via Vulnerability Assessment and Penetration Testing, likelihood and impact estimated, and risks scored and ranked. In the Check phase, risk treatment plans are implemented (controls deployed, configurations hardened, policies updated, insurance procured), and their effectiveness verified through testing, audit, and Continuous Monitoring. In the Act phase, findings from monitoring, incidents, and external intelligence feed back into the next assessment cycle, updating the Risk Register and informing governance reporting. This PDCA cycle underpins ISO 27001 certification and ISO 27005 risk management practice alike.
The conceptual core of cybersecurity risk management is a four-phase cycle — identify, assess, treat, monitor — which is variously formalised across frameworks. NIST CSF 2.0 (released February 2024) expanded the original five-function model (Identify, Protect, Detect, Respond, Recover) by adding a sixth function, Govern, making explicit that cybersecurity strategy, policy, and risk management are executive responsibilities rather than purely operational ones. ISO/IEC 27005:2022 provides complementary guidance on implementing an information security risk management process compatible with ISO/IEC 27001:2022, and explicitly accommodates both qualitative and semi-quantitative analysis methods. The FAIR (Factor Analysis of Information Risk) model layers financial quantification onto this cycle, expressing cyber risk in monetary loss expectancy terms that align with finance and audit language, enabling prioritisation of controls by return on security investment.
A critical dimension of modern cybersecurity risk management is supply chain and third-party risk. Sophisticated threat actors — nation states and organised criminal groups alike — increasingly target organisations indirectly through their software vendors, managed service providers, and hardware suppliers. The SolarWinds (2020), Kaseya (2021), and MOVEit Transfer (2023) incidents each demonstrated how a compromise in a trusted supplier can propagate laterally across thousands of downstream organisations. Risk managers now routinely conduct vendor risk assessments, apply tiered supplier classifications, and require supply chain organisations to achieve Cyber Essentials certification as a baseline hygiene standard. The UK NCSC’s 2025 Annual Review recorded a record 204 nationally significant cyber incidents in the year to September 2025 — more than double the previous year’s 89 — reinforcing the urgency of systematic risk management practice.
Components / Architecture
Threat Modelling
-
Structured enumeration of adversary profiles, attack surfaces, and likely kill chains
-
Methodologies: STRIDE (Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, Elevation of Privilege); PASTA (Process for Attack Simulation and Threat Analysis, seven-stage attacker-centric framework); OCTAVE (Operationally Critical Threat, Asset, and Vulnerability Evaluation); ATT&CK-aligned modelling using MITRE ATT&CK framework
-
Outputs: data-flow diagrams annotated with threat categories, adversary capability assessments, prioritised attack scenarios
Vulnerability Assessment and Management
-
Continuous discovery of exploitable weaknesses in assets, configurations, code, and third-party components
-
Tools: authenticated network scanning (Tenable Nessus, Qualys VMDR, Rapid7 InsightVM); dynamic application security testing (Burp Suite DAST); static analysis (Checkmarx SAST, Semgrep); software composition analysis (Snyk, Dependabot, Black Duck)
-
Scoring via CVSS v3.1 and CVSS v4.0 (Common Vulnerability Scoring System); contextualisation via CISA KEV (Known Exploited Vulnerabilities catalogue) prioritises patching based on observed exploitation in the wild
-
EPSS (Exploit Prediction Scoring System) supplements CVSS by providing probability estimates of exploitation within 30 days, enabling more nuanced prioritisation beyond base severity
-
Vulnerability management metrics: Mean Time to Remediate (MTTR) by severity class; Patch Coverage Rate; Critical Vulnerability Exposure Window
-
Cloud configuration management: CSPM (Cloud Security Posture Management) tools (Prisma Cloud, Wiz, Orca Security) continuously assess cloud infrastructure for misconfigurations — a leading cause of cloud data breaches
-
Feeds directly into risk treatment prioritisation: high-CVSS vulnerabilities on internet-facing assets with active exploit code in KEV receive emergency patching priority (SLA: 24-48 hours)
Risk Assessment and Quantification
-
Qualitative matrices mapping likelihood × impact (5×5 heat maps) for executive communication
-
Semi-quantitative ordinal scales (ISO 27005:2022 approach) providing ranked risk lists
-
Quantitative FAIR analysis: decomposing risk into Threat Event Frequency, Vulnerability, and Loss Magnitude (Primary Loss and Secondary Loss) to produce Monte Carlo probability distributions of annualised loss expectancy (ALE)
-
Output: prioritised risk register with treatment options (accept, mitigate, transfer, avoid) and cost-benefit analysis
Control Framework Mapping
-
CIS Controls v8.1 (18 control families, 153 safeguards); NIST SP 800-53 Rev. 5 (over 1,000 controls across 20 control families); ISO 27002:2022 (93 controls across 4 themes and 11 clauses)
-
Mapping identified risks to specific control identifiers enables structured evidence collection, gap analysis, and audit readiness
-
Compensating control documentation required for cases where primary controls are technically or operationally infeasible (e.g. legacy OT systems that cannot be patched)
-
Control inheritance: cloud customers inherit controls from cloud service providers under shared responsibility models; these must be explicitly documented and evidenced in compliance programmes
-
SCF (Secure Controls Framework) provides a unified control catalogue mapping across 100+ frameworks enabling simultaneous compliance with ISO 27001, NIST CSF, SOC 2, PCI DSS, and HIPAA from a single control set
-
Control testing cadence: preventive controls tested annually; detective controls tested quarterly; corrective controls tested per incident; continuous controls validated by automated compliance scanning
Continuous Monitoring and Detection
-
SIEM platforms (Splunk, Microsoft Sentinel, IBM QRadar) aggregate logs from network devices, endpoints, cloud services, and applications; apply correlation rules and ML-based anomaly detection
-
SOAR platforms (Palo Alto XSOAR, Splunk SOAR) automate response playbooks: endpoint isolation, credential rotation, firewall rule updates — reducing mean time to respond (MTTR) to under minutes
-
Threat intelligence feeds (MISP, TAXII/STIX, commercial threat intel) enrich detection rules with adversary indicators of compromise (IoCs) and tactics, techniques, and procedures (TTPs)
Governance and Reporting
-
Quarterly risk committee reporting: Risk Register status (open, in-treatment, accepted, closed risks), control effectiveness metrics, overdue remediation actions, and emerging threat briefings
-
Board-level cybersecurity dashboards translating technical findings into financial and strategic risk language aligned with enterprise risk management (ERM) risk appetite statements
-
Regulatory reporting obligations: NIS2 Directive (significant incident notification within 24 hours initial warning, 72 hours detailed report for EU-service entities); ICO/UK GDPR breach notification (72 hours from awareness); Cyber Security and Resilience Bill obligations for UK CNI operators; SEC cybersecurity disclosure rules (material incident disclosure within 4 business days for US-listed entities)
-
Risk appetite statements approved by board: quantitative tolerances for maximum acceptable downtime, maximum tolerable data loss (RPO/RTO), and maximum annualised loss expectancy by business unit and risk category
-
Cyber insurance integration: risk quantification outputs (FAIR ALE distributions) inform cyber insurance coverage decisions; insurers increasingly require evidence of risk management maturity (MFA deployment, EDR coverage, patch cadence) as underwriting conditions
-
Three Lines of Defence model: Line 1 — operational security controls owned by business units; Line 2 — second-line risk and compliance function providing oversight and frameworks; Line 3 — internal audit providing independent assurance to the board
-
Key Risk Indicators (KRIs): metrics providing leading-indicator signals of deteriorating risk posture — e.g. phishing click rates, mean time to patch critical vulnerabilities, percentage of endpoints with current EDR, number of unresolved high-severity findings
Risk Register Management
-
The Risk Register is the central artefact of cybersecurity risk management: a structured, live document (or platform record) capturing all identified risks with their owner, current rating, treatment status, and acceptance decision
-
Standard fields: Risk ID; Description; Asset(s) at risk; Threat source; Vulnerability exploited; Likelihood (qualitative or ALE probability); Impact (qualitative or financial £/$); Inherent risk rating; Control(s) applied; Residual risk rating; Risk owner; Treatment decision (mitigate/accept/transfer/avoid); Target treatment date; Review date; Status
-
Risk register reviews typically: monthly operational review (action progress, new risks emerging from incident or threat intelligence); quarterly risk committee (control effectiveness, risk trend analysis, budget implications); annual board presentation (risk appetite alignment, strategic risk posture)
-
GRC platform tooling: ServiceNow GRC, Archer, LogicGate, 6clicks, Vanta — provide integrated risk register management with control evidence collection, workflow automation, and regulatory mapping
Zero Trust Integration
-
Classical perimeter defences assume a trusted internal network; Zero Trust Architecture (ZTA) assumes breach and enforces micro-segmentation, least-privilege access, continuous identity verification, and device health attestation
-
Risk management informs ZTA policy: assets carrying the highest-risk data receive the strictest access controls; lateral movement is restricted by dynamic policy engines
-
SIEM + SOAR + ZTA convergence enables automated risk-responsive enforcement: when SIEM detects anomalous credential behaviour, SOAR triggers ZTNA policy engine to revoke session in real time
-
ZTA implementation risk: overly aggressive microsegmentation can create availability risks; risk management must balance security control strength against operational continuity requirements
Major Threat Families and Risk Taxonomy
Cybersecurity risk management operates against a structured taxonomy of threat categories, each requiring distinct assessment and treatment approaches.
Social Engineering and Phishing
-
Business Email Compromise (BEC) and spear phishing represent the highest-frequency, high-impact threat vector for most organisations — NCSC data shows phishing remains the initial access method in the majority of significant incidents
-
Vishing (voice phishing) and smishing (SMS phishing) extend the attack surface beyond email
-
AI-generated deepfake audio and video are increasingly used in sophisticated BEC campaigns — a threat vector specifically highlighted in the NCSC 2025 Annual Review
-
Risk treatment: security awareness training, email authentication controls (DMARC, DKIM, SPF), anti-phishing email gateways, multi-factor authentication to limit credential compromise impact
-
Residual risk monitoring: phishing simulation programmes, click-rate KRIs, reported phishing volume metrics
Ransomware and Extortion
-
Ransomware-as-a-Service (RaaS) groups (LockBit, BlackCat/ALPHV, Clop) operate affiliate models enabling low-sophistication actors to deploy enterprise-grade ransomware
-
Double-extortion model: data exfiltration precedes encryption, enabling ransom demand even if backups prevent service disruption
-
Triple-extortion extends to DDoS against victims who refuse to pay, and threatening victims’ customers/partners
-
Critical risk treatment controls: offline immutable backups tested quarterly; EDR (Endpoint Detection and Response) with behavioural detection on all endpoints; network segmentation limiting lateral movement; incident response playbook with tested recovery procedure
-
UK NCSC guidance recommends against ransom payment as it does not guarantee data recovery and funds criminal ecosystems
Supply Chain and Third-Party Compromise
-
Software supply chain attacks target build pipelines, code repositories, and CI/CD systems — compromising a trusted software update mechanism propagates malware to all downstream customers
-
Notable incidents: SolarWinds SUNBURST (2020), Kaseya VSA (2021), MOVEit Transfer (2023) each affected thousands of organisations through single vendor compromises
-
Hardware supply chain risks: counterfeit components, implanted hardware backdoors in imported equipment — relevant for CNI and defence procurement
-
Risk treatment: software bill of materials (SBOM) for all deployed software; vendor tiering with proportionate security assessment depth; Supply Chain Security contractual requirements; continuous monitoring of vendor security posture via attack surface management tools
-
NCSC Cyber Essentials certification required as minimum for Tier 3 suppliers; full ISO 27001 or SOC 2 for Tier 1 suppliers with sensitive data access
Insider Threats
-
Malicious insiders (disgruntled employees, compromised accounts with excessive privileges) pose disproportionate risk because they already possess trusted access
-
Negligent insiders (accidental data exposure, misconfiguration, falling for phishing) cause the majority of data breaches by frequency
-
Risk treatment: least-privilege access principles; privileged access management (PAM) systems; user and entity behaviour analytics (UEBA) within SIEM; data loss prevention (DLP) tooling; joiners-movers-leavers identity lifecycle processes
-
Insider threat monitoring must balance security monitoring obligations with employee privacy rights under UK GDPR — a legal tension requiring documented legitimate interest assessments
Nation-State and Advanced Persistent Threat (APT) Actors
-
State-sponsored groups (categorised by MITRE ATT&CK as specific APT groups: APT28/Fancy Bear attributed to Russia GRU; Lazarus Group attributed to North Korea; APT41 attributed to China MSS) target CNI, defence, finance, and technology sectors
-
TTPs: spear phishing for initial access; living-off-the-land (LoTL) techniques using legitimate system tools for lateral movement; persistent backdoors; long dwell times (months to years) before impact
-
Risk treatment for high-risk targets: defence-in-depth with multiple independent detection layers; deception technology (honeypots, honeytokens); threat hunting by skilled analysts rather than sole reliance on automated detection; privileged access workstations (PAWs); just-in-time privileged access
-
NCSC provides sector-specific threat intelligence briefings to CNI operators and regulated sectors via its CISP (Cyber Security Information Sharing Partnership) platform
Cloud and API Security Risks
-
Cloud misconfiguration is the leading cause of cloud data breaches — exposed S3 buckets, overpermissioned IAM roles, publicly accessible development databases
-
API security risks: broken object-level authorisation (BOLA), broken authentication, excessive data exposure — the OWASP API Security Top 10 provides the canonical risk taxonomy
-
Shadow IT and unmanaged cloud services expand the attack surface outside the visibility of central security teams
-
Risk treatment: CSPM tools for continuous cloud posture monitoring; Infrastructure-as-Code (IaC) scanning in CI/CD pipelines; API gateway with authentication enforcement and rate limiting; cloud-native SIEM integration (AWS Security Hub, Azure Sentinel, GCP Security Command Centre)
Use Cases / Major Families
Enterprise Security Programme Governance
-
Large organisations (financial services, healthcare, energy, defence) use cybersecurity risk management as the governance backbone of their information security programmes
-
Quarterly board risk packs translate technical risk register data into executive risk language, using financial loss estimates and regulatory consequence framing
-
Annual ISO 27001 audit cycle generates evidence of risk assessment execution, treatment plan completion, and monitoring programme operation
-
Enterprise risk management (ERM) integration: cyber risks carried alongside financial, operational, and reputational risk categories in the enterprise risk register, enabling cross-risk prioritisation and board-level holistic risk oversight
Cloud Migration Risk Assessment
-
Cloud migration projects require risk assessments addressing shared responsibility boundaries (AWS/Azure/GCP security of the cloud vs customer security in the cloud), data residency and sovereignty requirements, identity federation risks, and misconfiguration threat surfaces unique to cloud environments
-
Risk management gates embedded in DevSecOps pipelines via Infrastructure-as-Code (IaC) scanning tools (Checkov, Terrascan, tfsec) prevent insecure configurations from reaching production
-
Cloud risk assessment output: RACI matrix clarifying which controls the CSP owns, which are customer-owned, and which are shared — critical for audit evidence completeness
-
Data classification drives cloud security control selection: highly sensitive data categories (health, financial, legal) require encryption at rest and in transit, tokenisation or pseudonymisation where feasible, and access limited to specific geographic regions
AI System Risk Gating
-
Organisations deploying AI models — particularly high-risk AI under the EU AI Act classification — require threat modelling of AI-specific attack surfaces: adversarial input attacks, model inversion (extracting training data from model outputs), membership inference (determining whether specific data was in the training set), prompt injection for LLM-based systems, and data poisoning of training pipelines
-
Cybersecurity risk management provides the methodological backbone extended by AI-specific risk taxonomies from NIST AI RMF and the EU AI Act risk classification system
-
AI risk register entries capture: model source and version; training data provenance; fine-tuning and RLHF details; known capability limitations; adversarial robustness test results; incident response plan for model misbehaviour
Third-Party and Supply Chain Risk
-
Vendor risk assessment programmes classify suppliers by data access tier: Tier 1 (access to sensitive personal data — full security questionnaire, on-site audit, penetration test requirements); Tier 2 (system access, no personal data — questionnaire and evidence review); Tier 3 (no system or data access — Cyber Essentials certification only)
-
Continuous monitoring of vendor cyber posture via attack surface management (ASM) tools supplements periodic point-in-time assessments — tracking exposed services, detected vulnerabilities, and dark web exposure for all critical suppliers
-
Contract security schedules specify minimum security standards, right-to-audit clauses, incident notification obligations, and liability allocation for supplier-caused breaches
Operational Technology (OT) and Critical Infrastructure
-
Industrial control systems, SCADA networks, and IoT-heavy environments in energy, water, and transport sectors apply adapted frameworks: IEC 62443 for industrial cybersecurity, NCSC CAF for UK CNI operators
-
Safety-critical consequences of availability disruption (power outage, water system contamination, transportation system failure) require integrated safety and security risk assessment
-
Patching legacy OT systems without operational downtime is a chronic risk management challenge — compensating controls (network segmentation, unidirectional security gateways, enhanced monitoring) substitute for direct patching where technically infeasible
-
IT/OT convergence driven by Industry 4.0 connectivity expands the cyber attack surface into previously air-gapped systems, requiring integrated IT/OT risk management approaches
Regulatory Compliance and Audit Readiness
-
ISO 27001 certification requires documented risk assessment methodology, risk treatment plans, and evidence of ongoing monitoring — all core outputs of cybersecurity risk management; annual surveillance audits and triennial recertification audits assess continuous operation
-
UK financial services firms regulated by the FCA and PRA: DORA (Digital Operational Resilience Act) requirements applicable to firms serving EU markets mandate formal risk-based impact tolerance testing and scenario-based resilience testing
-
Cyber insurance underwriting increasingly requires evidence of specific cybersecurity control maturity: multi-factor authentication deployment rates, EDR coverage, backup immutability, and risk assessment currency are standard underwriting requirements
Academic Context
The theoretical foundations of cybersecurity risk management draw from multiple disciplines: information security engineering, risk theory, decision science, economics, and organisational behaviour. Information security risk management formalised in the late 1990s through governmental frameworks: the US Department of Defense developed the DIACAP and later the Risk Management Framework (RMF) processes for federal systems; NIST published SP 800-30 (Guide for Conducting Risk Assessments) in 2002, updated 2012. The Orange Book (DoD Trusted Computer System Evaluation Criteria, 1983) provided early formal security evaluation methodology. Bruce Schneier’s work throughout the 2000s popularised risk-thinking in security practice, articulating the distinction between security theatre (compliance without risk reduction) and genuine security improvement.
Ross Anderson’s foundational 2001 paper “Why Information Security is Hard — An Economic Perspective” (ACSAC 2001) introduced the economic lens: incentive misalignment (developers bear no cost for insecure code; users bear the cost), information asymmetry (vendors conceal vulnerability data from customers), and externality problems (breaches impose costs on third parties not party to the vendor-customer relationship) each explain chronic underinvestment in security. Anderson and Moore’s 2006 Science paper “The Economics of Information Security” expanded this analysis to cover signalling, moral hazard, and adverse selection in security markets — providing the theoretical justification for mandatory disclosure and minimum standards regulation.
Hubbard and Seiersen’s “How to Measure Anything in Cybersecurity Risk” (2016) provided the methodological basis for FAIR-style quantitative analysis, applying established actuarial and engineering risk techniques — calibrated probability estimation, Monte Carlo simulation, Bayesian updating — to cyber domains where data is sparse. Their core argument — that calibrated uncertainty (well-calibrated 90% confidence intervals) is epistemically superior to false precision (3-decimal-place CVSS scores from 5×5 matrices) — has driven the quantitative risk management movement.
Academic attention has turned increasingly to adversarial machine learning risk (Biggio and Roli, 2018 Wild Patterns survey; Papernot et al., 2016 practical black-box attacks) and to AI system risk management as a distinct subdiscipline (NIST AI RMF 1.0, 2023; ISO/IEC 42001:2023; EU AI Act risk classification). Research groups at University College London (Information Security Group led by Prof. Angela Sasse — foundational usable security and human factors research), Royal Holloway (Information Security Group — 25-year applied security research tradition), University of Edinburgh (Security & Privacy research — formal verification and privacy-enhancing technologies), and Imperial College London (Computing Security — systems security and cryptography) contribute to both technical and governance dimensions of cybersecurity risk management. Internationally, Carnegie Mellon’s CyLab (Pittsburgh), MIT CSAIL, and Stanford’s Security Lab produce the most cited foundational research.
The ISADM framework (Zalewski, Boneh et al., 2024; arXiv:2512.18751) proposed an integrated STRIDE, ATT&CK, and D3FEND model, synthesising threat modelling, adversary behaviour cataloguing, and defensive countermeasure mapping into a unified analytical structure aligned with real-world adversary TTPs observed in operational threat intelligence — a significant methodological advance over using these frameworks in isolation.
Behavioural cybersecurity is an emerging academic subdiscipline examining how cognitive biases, organisational culture, and incentive structures shape security decision-making. Research by Beautement, Sasse, and Wonham on the Compliance Budget model demonstrates that security policies generate a psychological and practical burden, and that when this burden exceeds users’ capacity, they develop workarounds that create new risk — a critical insight for risk-based proportionality in control selection.
Current Landscape (2026)
The 2026 cybersecurity risk management landscape is characterised by four converging forces:
AI-Augmented Attack and Defence
-
The NCSC’s AI to 2027 threat assessment warned that AI is expanding attack volume and sophistication: more targeted spear phishing at scale; automated vulnerability scanning; AI-generated malware with polymorphic evasion; deepfake-based social engineering
-
Defensive AI: LLM-powered alert triage within SIEM stacks (reducing tier-1 analyst alert fatigue); anomaly detection using unsupervised ML (UEBA); AI-generated threat hunting hypotheses; automated incident summarisation
-
AI assistants are now embedded in enterprise GRC tools, drafting risk statements, mapping controls to regulatory requirements, and generating board-level risk narratives from structured risk register data
Regulatory Convergence and Expansion
-
NIST CSF 2.0 (February 2024): added Govern function; published Implementation Examples and Community Profiles for healthcare, financial services, and CNI; explicitly positioned CSF as a universal framework for all organisation types, not just US critical infrastructure
-
UK Cyber Security and Resilience Bill (2025-2026): expands NIS regulations scope; strengthens incident reporting (24-hour notification windows); extends powers to regulate digital infrastructure suppliers; reinforces board accountability
-
NCSC CAF 4.0: updated assessment framework underpinning regulatory inspections for 13 UK CNI sectors; provides the language for regulator conversations with CNI operators about cyber risk posture
-
EU AI Act (effective August 2026 for GPAI obligations): mandates cybersecurity robustness testing for high-risk AI systems — expanding the risk management remit into AI system security
Zero Trust and Cloud Convergence
-
Cloud-first architectures have rendered classical network perimeters obsolete; Zero Trust Architecture (identity-centric, device-health-gated, microsegmented) is now the dominant enterprise network security paradigm
-
NIST SP 800-207 (Zero Trust Architecture) provides the risk-based implementation framework; CISA Zero Trust Maturity Model 2.0 provides staged adoption guidance for US federal agencies (adopted voluntarily by many UK enterprises)
-
Converged XDR (Extended Detection and Response) platforms unify endpoint, network, cloud, and identity telemetry into a single detection and response surface — simplifying risk monitoring across complex hybrid environments
AI System Risk Integration
-
ISO/IEC 42001:2023 (AI Management System Standard) and NIST AI RMF 1.0 (2023) establish governance frameworks for AI systems that are increasingly cited alongside ISO 27001 and NIST CSF in enterprise risk governance programmes
-
Organisations developing or deploying AI Governance-scope AI must maintain AI-specific risk registers capturing model risk, data lineage risk, inference attack risk, and systemic risks from AI supply chain components
-
The EU AI Act’s conformity assessment requirements for high-risk AI create a new category of cybersecurity risk assessment obligation: demonstrating robustness against adversarial inputs as a prerequisite for market access
UK Context
The United Kingdom maintains a sophisticated national cybersecurity governance ecosystem through the National Cyber Security Centre (NCSC), an arm of GCHQ established in 2016 and headquartered in Victoria, London. The NCSC serves as the UK’s national technical authority on cybersecurity, publishing authoritative guidance, operating the Active Cyber Defence programme (ACD), managing national-level incident response, and operating the Cyber Security Information Sharing Partnership (CISP) platform for private sector threat intelligence sharing. The NCSC publishes the Cyber Assessment Framework (CAF), now at version 4.0, which provides structured outcomes-based assessment guidance for operators of UK Critical National Infrastructure spanning 13 regulated sectors including energy, water, transport, healthcare, and communications. The Cyber Essentials and Cyber Essentials Plus certification schemes provide baseline cybersecurity hygiene standards for smaller organisations; Cyber Essentials certification is required for all UK government suppliers handling personal data, and is increasingly specified as a minimum supply chain security condition in larger enterprise procurement frameworks.
The UK Cyber Security and Resilience Bill, announced in the 2024 King’s Speech and progressing through Parliament in 2025-2026, represents the most significant expansion of UK cyber regulation since the 2018 NIS Regulations. The Bill expands the scope of regulated entities to cover a broader range of digital infrastructure and service providers; strengthens mandatory incident reporting requirements with reduced notification windows; extends Secretary of State powers to set minimum security standards for high-impact digital service suppliers; and reinforces board accountability for cyber risk governance with explicit accountability expectations. While the UK no longer directly adopts EU regulation post-Brexit, organisations providing services to EU essential entities, operating as managed service providers for EU customers, or as UK subsidiaries of EU parents remain subject to NIS2, creating dual regulatory obligations that UK risk management programmes must accommodate.
The NCSC’s 2025 Annual Review reported a record 204 nationally significant cyber incidents, more than doubling the prior year’s 89, with ransomware, state-sponsored intrusions against CNI, and AI-accelerated attack techniques as the dominant threat categories. The UK government responded by writing directly to FTSE 350 boards reinforcing personal accountability for cyber risk governance, and by publishing the Cyber Governance Code of Practice (2024) providing structured board-level guidance on cybersecurity responsibilities — a direct parallel to the corporate governance responsibilities under the UK Corporate Governance Code.
UK academia plays a prominent role in cybersecurity risk research. Royal Holloway (University of London) operates one of the UK’s largest information security research groups and runs the NCSC-certified MSc Information Security programme, producing approximately 150 graduates annually who form a significant part of the UK’s senior security talent pipeline. University College London’s Information Security Group (Prof. Angela Sasse, Prof. Steven Murdoch, and colleagues) conducts foundational research on usable security, privacy-enhancing technologies, and security economics — work directly cited in NCSC guidance on proportionate control design. Lancaster University’s Security Lancaster research institute is a designated NCSC Academic Centre of Excellence in Cyber Security Research (ACE-CSR), with strengths in network security and formal verification. The University of Edinburgh’s Security and Privacy research group contributes to formal methods for security assurance. The Alan Turing Institute, as the UK national institute for data science and AI (based in the British Library, London), contributes to AI-specific security risk research with growing relevance to cybersecurity risk management practice.
In Northern England, the cybersecurity academic and commercial ecosystem is rapidly developing. The University of Manchester — home to the UK’s first computing pioneer Alan Turing and site of the Manchester Mark 1 (1948) — maintains an active cybersecurity research group within the School of Computer Science, with particular strengths in network security and data privacy. The University of Leeds operates the Centre for Doctoral Training (CDT) in Cyber Security and works with Yorkshire-based financial services and healthcare organisations on applied risk management research. The University of Sheffield’s Computer Science department contributes to security verification and applied cryptography research. Newcastle University (NCSC ACE-CSR designated) focuses on hardware security, side-channel attacks, and security for embedded systems — expertise relevant to the North East’s automotive and advanced manufacturing sectors. The University of York contributes to real-time systems security relevant to the rail and aerospace sectors prominent in the Yorkshire economy.
The UK’s cybersecurity commercial ecosystem is concentrated in London (particularly Tech City / Shoreditch and the Westminster government cluster) but extends to regional hubs: Manchester’s MediaCityUK and digital corridor along the Oxford Road; Edinburgh’s Silicon Glen; Bristol’s aerospace and defence sector; and Cambridge’s high-tech cluster spanning Arm Holdings (chip security), Darktrace (AI-based threat detection — Cambridge-founded, now London-listed), and a dense ecosystem of security startups. The UK Cybersecurity Council, established 2021, is developing a professional competency framework for cybersecurity practitioners analogous to medical or legal professional regulation — a significant initiative for raising the quality and accountability of cybersecurity risk management practice nationally.
Future Directions (2026-2030)
Quantitative risk management at scale
-
As FAIR methodology matures and tooling integrates with SIEM telemetry, automated continuous risk quantification will replace periodic point-in-time assessments
-
Risk registers will carry real-time annualised loss expectancy (ALE) values updated by threat intelligence feeds, enabling dynamic control investment decisions
-
Automated FAIR analysis will be triggered by new CVE disclosures, threat intelligence reports, and control failures, providing near-real-time risk posture updates
-
Cyber risk aggregation models — comparable to actuarial catastrophe models in property insurance — will quantify correlated tail risks across interconnected systems
AI-native risk management platforms
-
Dedicated AI risk management capabilities will be embedded in GRC (Governance, Risk, and Compliance) platforms, applying LLM-driven natural language risk analysis to audit findings, policy documents, and incident reports
-
Automated Threat Modelling from code repositories and architecture diagrams: AI-powered tools will parse system designs and generate STRIDE-annotated data-flow diagrams and threat catalogues without manual analyst input
-
AI-generated remediation playbooks will map identified risks to specific control implementations with configuration-level detail, reducing the analyst expertise barrier for control selection
-
The boundary between AI Governance and cybersecurity risk management will blur as AI systems become pervasive risk subjects requiring their own sub-registers within enterprise risk frameworks
Post-quantum cryptographic risk
-
NIST standardised post-quantum cryptographic algorithms in 2024 (FIPS 203 — ML-KEM/CRYSTALS-Kyber; FIPS 204 — ML-DSA/CRYSTALS-Dilithium; FIPS 205 — SLH-DSA/SPHINCS+), triggering enterprise cryptographic migration planning
-
Quantum threat assessment — estimating when cryptographically-relevant quantum computers (CRQCs) will break RSA-2048 and ECC-256 — will become a standard component of cybersecurity risk registers alongside conventional threat categories
-
Cryptographic inventory management (cataloguing all deployed cryptographic algorithms, key lengths, and certificate expiry) will emerge as a distinct risk management subdiscipline, requiring automated discovery tools
-
“Harvest now, decrypt later” attacks — where adversaries collect encrypted data today intending to decrypt it once quantum computers are available — are already relevant for long-lived sensitive data (national security, medical records, trade secrets)
OT/IT convergence and cyber-physical risk
-
Smart grid, Industry 4.0 manufacturing, connected medical devices (MedTech), and autonomous transport systems create cyber-physical risk surfaces where cybersecurity failures produce physical — potentially fatal — consequences
-
Risk management frameworks will integrate safety engineering methods (HAZOP, FMEA, fault-tree analysis, safety integrity level (SIL) assessment) with information security risk methods (STRIDE, FAIR) into unified cyber-physical risk assessment processes
-
IEC 62443 (Industrial Automation and Control System Security) and ISO/SAE 21434 (Automotive Cybersecurity) provide sector-specific frameworks that will be increasingly integrated into enterprise risk registers alongside IT-focused ISO 27001
Mandatory board cyber literacy and director accountability
-
Following the UK Cyber Governance Code of Practice (2024) and SEC cybersecurity disclosure rules (US, 2023), boards are required to demonstrate cyber risk governance competence as a fiduciary responsibility
-
Director-level cyber risk qualifications and literacy programmes will be developed by professional bodies (ISACA, (ISC)², Chartered Institute of Information Security in the UK)
-
Demand for board-level cyber risk advisory services and executive education will grow at business schools including London Business School, Saïd Business School (Oxford), and Judge Business School (Cambridge)
-
Personal liability for directors in cases of governance failures enabling significant cyber incidents — analogous to health and safety personal liability — is emerging as a regulatory direction
Supply chain AI risk and AI-BOM
-
As AI models become embedded in enterprise software (AI-powered SaaS applications, embedded ML inference in operational systems), the risk surface expands to include model supply chain attacks
-
Attack vectors include: poisoned training data in open-source datasets; malicious fine-tuned models distributed via Hugging Face-equivalent model hubs; vulnerable AI APIs exposing prompt injection pathways; model extraction attacks targeting proprietary models accessed via API
-
Cybersecurity risk management will incorporate AI Bill of Materials (AI-BOM) practices analogous to software BOM (SBOM) requirements — documenting all AI models, their training data provenance, and any fine-tuning applied
-
This convergence of software supply chain security and AI system AI Risk Management will produce unified risk assessment methodologies for AI-software hybrid systems in the 2026-2030 timeframe
Autonomous and Agentic AI Security Risk
-
Agentic AI systems — AI agents capable of taking actions in digital environments (browsing, executing code, interacting with APIs) — introduce novel attack surfaces: prompt injection attacks designed to hijack agent behaviour, tool-use exploitation, and cascading failures in multi-agent pipelines
-
Cybersecurity risk management frameworks will need to be extended to assess and govern agentic AI deployments, including sandboxing requirements, human-in-the-loop approval gates for high-risk actions, and agent audit logs as evidence artefacts
-
The convergence of cybersecurity Threat Modelling with AI safety red-teaming methodologies will accelerate as agentic deployments scale in enterprise environments
Research & Literature
Key academic and industry references spanning theoretical foundations, standards, threat landscape, and emerging areas:
-
NIST. (2024). The NIST Cybersecurity Framework (CSF) 2.0 (NIST CSWP 29). National Institute of Standards and Technology. https://nvlpubs.nist.gov/nistpubs/CSWP/NIST.CSWP.29.pdf
-
ISO/IEC. (2022). ISO/IEC 27005:2022 — Information security, cybersecurity and privacy protection — Guidance on managing information security risks. International Organisation for Standardisation.
-
Open Group. (2023). The FAIR Model — Factor Analysis of Information Risk. FAIR Institute. https://www.fairinstitute.org/
-
NCSC. (2025). NCSC Annual Review 2025. National Cyber Security Centre, GCHQ. https://www.ncsc.gov.uk/collection/ncsc-annual-review-2025
-
Anderson, R. (2001). Why Information Security is Hard — An Economic Perspective. Proceedings of ACSAC 2001. IEEE.
-
Hubbard, D. W., & Seiersen, R. (2016). How to Measure Anything in Cybersecurity Risk. Wiley.
-
NIST. (2023). AI Risk Management Framework (AI RMF 1.0) (NIST AI 100-1). National Institute of Standards and Technology.
-
NIST. (2020). Zero Trust Architecture (NIST SP 800-207). National Institute of Standards and Technology.
-
Shostack, A. (2014). Threat Modeling: Designing for Security. Wiley.
-
ENISA. (2024). NIS2 Technical Implementation Guidance. European Union Agency for Cybersecurity. https://www.enisa.europa.eu/publications/nis2-technical-implementation-guidance
-
NCSC. (2024). Cyber Assessment Framework (CAF) v4.0. National Cyber Security Centre. https://www.ncsc.gov.uk/
-
UK Government. (2025). Cyber Security and Resilience Bill — Policy Paper. HM Government.
-
NIST. (2012). Guide for Conducting Risk Assessments (NIST SP 800-30 Rev. 1). National Institute of Standards and Technology.
-
Papernot, N., McDaniel, P., Goodfellow, I., Jha, S., Berkay Celik, Z., & Swami, A. (2016). Practical Black-Box Attacks against Machine Learning. Proceedings of ASIACCS 2017. ACM.
-
Biggio, B., & Roli, F. (2018). Wild patterns: Ten years after the rise of adversarial machine learning. Pattern Recognition, 84, 317–331.
-
Sadeghi, A.-R., Wachsmann, C., & Waidner, M. (2015). Security and privacy challenges in industrial internet of things. Proceedings of DAC 2015. ACM/IEEE.
-
Ruan, K. (2019). Cybernomics: A Macroeconomic Analysis of Cybersecurity. Springer.
-
Balboni, P., & Macenaite, M. (2013). Privacy by design and anonymisation techniques in action: case of mobile personal data. Computer Law & Security Review, 29(4), 349–360.
-
HM Government Cabinet Office. (2024). Cyber Governance Code of Practice. Crown Copyright.
-
European Commission. (2022). Directive (EU) 2022/2555 of the European Parliament and of the Council of 14 December 2022 (NIS2 Directive). Official Journal of the European Union.
-
ISO/IEC. (2022). ISO/IEC 27001:2022 — Information security management systems — Requirements. International Organisation for Standardisation.
-
MITRE. (2024). MITRE ATT&CK Framework v15. The MITRE Corporation. https://attack.mitre.org/
-
Zalewski, M., Boneh, D., & Rescorla, E. (2024). ISADM: An Integrated STRIDE, ATT&CK, and D3FEND Model for Threat Modelling Against Real-World Adversaries. arXiv:2512.18751.
-
CIS. (2023). CIS Controls Version 8.1. Center for Internet Security. https://www.cisecurity.org/controls/
-
NIST. (2024). Cybersecurity Framework 2.0: Enterprise Risk Management Integration (NIST SP 1303 Initial Public Draft). NIST.
-
Darktrace. (2024). The Implications of NIS2 on Cybersecurity and AI. Darktrace Blog. https://www.darktrace.com/blog/the-implications-of-nis2-on-cyber-security-and-ai
-
NCSC. (2025). AI to 2027: UK Critical Systems Threat Assessment. National Cyber Security Centre. https://www.ncsc.gov.uk/news/ai-to-2027-threat-assessment
-
Nature / Scientific Reports. (2025). ZenGuard: A Machine Learning Based Zero Trust Framework for Context-Aware Threat Mitigation Using SIEM, SOAR and UEBA. Scientific Reports. https://www.nature.com/articles/s41598-025-20998-4
Additional standards and technical references:
-
-
NIST. (2022). Measuring and Improving Cyber Resilience (NIST IR 8286C). National Institute of Standards and Technology.
-
ISO/IEC. (2023). ISO/IEC 42001:2023 — Artificial intelligence management system. International Organisation for Standardisation.
-
CISA. (2023). Zero Trust Maturity Model Version 2.0. Cybersecurity and Infrastructure Security Agency.
-
Schneier, B. (2003). Beyond Fear: Thinking Sensibly About Security in an Uncertain World. Copernicus Books / Springer.
-
Moore, T., & Anderson, R. (2011). Internet security. In M. Cave, S. Majumdar, & I. Vogelsang (Eds.), Handbook of Telecommunications Economics, Vol. 2. North Holland / Elsevier.
-
Beautement, A., Sasse, M. A., & Wonham, M. (2008). The compliance budget: Managing security behaviour in organisations. Proceedings of the 2008 Workshop on New Security Paradigms. ACM.
Formal Analysis
The governance structure of cybersecurity risk management can be formalised as a hierarchical decision system operating across three layers. At the strategic layer, the board defines risk appetite — a bounded tolerance expressed as maximum acceptable annualised financial loss (e.g. £10M across all cyber risk categories) and maximum tolerable downtime for critical services (e.g. 4 hours for tier-1 payment processing). These strategic tolerances cascade into operational risk thresholds that govern which risks require treatment versus acceptance and at what cost ceiling controls are authorised. At the tactical layer, the security function executes risk assessment cycles producing probability distributions over loss event scenarios — ideally Monte Carlo simulations over FAIR decompositions of Threat Event Frequency × Vulnerability × Loss Magnitude. At the operational layer, Security Operations Centre analysts execute detection-response playbooks within SIEM and SOAR platforms, generating events and metrics that feed back into the risk assessment cycle.
The FAIR ontology provides the most rigorous formalisation for cyber risk quantification. It decomposes Loss Event Frequency (LEF) into Threat Event Frequency (TEF) and Vulnerability (V), where V = Threat Capability (TC) / Control Strength (CS). Loss Magnitude is decomposed into Primary Loss (direct operational loss) and Secondary Loss (reputational, regulatory, legal, and competitive losses following a material incident). Monte Carlo simulation across these parameters produces Probable Loss distributions rather than single-point ALE estimates, capturing the heavy tail of catastrophic scenarios that arithmetic means obscure. The Hubbard-Seiersen critique of standard qualitative risk matrices demonstrates that ordinal 5×5 red/amber/green representations consistently misrepresent risk by ignoring probability calibration and encouraging false precision — a systematic cognitive bias that FAIR-based quantitative methods address through empirically calibrated probability intervals.
Control assurance frameworks can be modelled as directed acyclic graphs (DAGs) mapping attack paths to control nodes, where each control has an estimated detection probability and mitigation efficacy. Bayesian network models have been applied to formalise the probabilistic relationships between threat events, control failures, and loss outcomes, enabling dynamic risk updating as new intelligence or audit findings are incorporated. The NIST Special Publication 800-30 risk model provides a formal taxonomy mapping threat sources, threat events, vulnerabilities, and predisposing conditions into a likelihood-and-impact assessment schema compatible with both qualitative and semi-quantitative approaches.
The intersection of Cybersecurity Risk Management with AI Risk Management introduces category expansions not captured by classical frameworks. Adversarial machine learning risks (evasion, poisoning, extraction, inference attacks) require probabilistic threat models operating over the ML training and inference pipeline, not just the network perimeter and application stack. The EU AI Act risk classification (unacceptable risk, high risk, limited risk, minimal risk) provides a regulatory risk taxonomy for AI systems that intersects with cybersecurity risk at the classification and conformity assessment stage — systems classified as high-risk under the Act must demonstrate not only functional compliance but also cybersecurity robustness against adversarial attacks.
Risk Framework Comparison
| Framework | Method | Primary Output | Scope | Quantification |
|---|---|---|---|---|
| NIST CSF 2.0 | Outcomes-based, six functions | Maturity profile, gap analysis | All organisations | Qualitative / tiered |
| ISO 27005:2022 | Risk-based, PDCA cycle | Risk treatment plan | ISMS context | Qualitative / semi-quantitative |
| FAIR | Factor-based, probabilistic | ALE distribution (£/$) | Enterprise | Quantitative (Monte Carlo) |
| NCSC CAF 4.0 | Indicator-based, 18 outcomes | Assessed outcome level | UK CNI operators | Qualitative (outcome levels) |
| OCTAVE Allegro | Asset-centric, workshop-based | Risk profile per asset | Mid-size orgs | Qualitative |
| PASTA | Attacker-centric, seven stages | Threat scenarios, risk rating | Application security | Semi-quantitative |
| STRIDE | Threat category enumeration | DFD-annotated threat list | Application design | Qualitative |
| NIST RMF | Control-centric, six steps | Authorisation to Operate (ATO) | US federal systems | Semi-quantitative |
Each framework addresses distinct use cases:
-
NIST CSF 2.0: board-level programme governance, cross-sector communication language, maturity benchmarking
-
ISO 27001/27005: ISMS audit readiness, certification, regulatory compliance evidence production
-
FAIR: ROI justification for security investment; insurance quantification; board-level financial risk language
-
NCSC CAF 4.0: regulatory inspection readiness for UK Resilience-critical sectors under NIS regulations
-
STRIDE and PASTA: developer-level Threat Modelling during system design and DevSecOps pipelines
-
Mature programmes layer frameworks: NIST CSF for strategic governance, ISO 27001/27005 for compliance assurance, FAIR for investment prioritisation, STRIDE/PASTA for DevSecOps Threat Modelling, NCSC CAF for regulatory reporting
Key Terminology
-
Risk appetite — The level of cyber risk an organisation is willing to accept in pursuit of its strategic objectives, defined and approved at board level.
-
Residual risk — The risk remaining after controls have been applied; formally accepted by risk owners.
-
Annualised Loss Expectancy (ALE) — Probabilistic estimate of financial loss from a risk event over a twelve-month period; core output of FAIR analysis.
-
Threat actor — An individual or group with the intent and capability to cause a cybersecurity event; classified by motivation (financial, espionage, hacktivism) and sophistication.
-
Attack surface — The totality of exploitable entry points across an organisation’s digital estate: external-facing services, APIs, email, removable media, and supply chain interfaces.
-
Control effectiveness — A measure of how well a security control reduces the likelihood or impact of a threat event; tracked through security metrics and testing.
-
MTTR (Mean Time to Respond/Recover) — Key operational metric measuring average elapsed time from threat detection to containment and restoration.
-
Zero Day — A vulnerability with no available patch at the time of exploitation, representing the highest-urgency risk category requiring compensating control responses.
-
Kill chain — A sequential model of attacker progression from initial access through to impact (Lockheed Martin Cyber Kill Chain; MITRE ATT&CK provides a more granular TTP taxonomy).
-
Risk treatment — One of four decisions for each identified risk: accept (document and monitor), mitigate (apply controls), transfer (insurance, contractual), or avoid (discontinue activity).
-
Threat Event Frequency (TEF) — In FAIR analysis, the probable frequency with which a threat agent will act against an asset within a given timeframe; a key input to loss event frequency estimation.
-
Vulnerability — In FAIR, the probability that a threat event results in loss, defined as the ratio of threat capability to control strength; expressed as a probability between 0 and 1.
-
SOC (Security Operations Centre) — The team and platform infrastructure responsible for continuous monitoring, detection, triage, and initial response to cybersecurity events; feeds the risk management cycle with real-time operational intelligence.
-
CVE (Common Vulnerabilities and Exposures) — A standardised identifier system for publicly disclosed software vulnerabilities; CVSS scores enable risk-prioritised vulnerability treatment.
-
PDCA (Plan-Do-Check-Act) — The ISO management system improvement cycle underpinning ISO 27001 and ISO 27005; risk management operates within this iterative governance structure.