TL;DR: Breach susceptibility can be estimated across portfolios using posture data, footprint size, and insurance claims history from more than 10,000 cyber insurance policies, according to SecurityScorecard. The bigger shift is that underwriting and third-party risk teams now need to treat exposure scoring as a governance input, not a substitute for control evidence, with validation from Marsh McLennan CRIC.
At a glance
What this is: SecurityScorecard argues that breach susceptibility scoring can quantify likely breach exposure across a portfolio by combining posture data, footprint size, and insurance history.
Why it matters: Risk teams should treat susceptibility scores as a directional input for underwriting and third-party review, while still requiring direct evidence of control performance.
Context
Breach susceptibility scoring tries to solve a familiar governance problem: security teams and insurers often need to compare risk across many organisations, but control evidence alone does not always explain why one insured is more likely to breach than another. In this article, SecurityScorecard positions BSI as a way to estimate inherent exposure from posture and footprint data, which is particularly relevant where third-party risk, underwriting, and portfolio management overlap.
For IAM and broader identity governance programmes, the important lesson is not that a score can replace validation, but that risk programs increasingly want a quantified view of exposure. That affects how teams evidence access control maturity, third-party assurance, and remediation priority, especially when machine identities, external access, and digital footprint growth widen the attack surface.
Key questions
Q: How should security teams use breach susceptibility scores in practice?
A: Use them as prioritisation signals, not as proof of control failure or control success. The best practice is to pair the score with evidence from access reviews, third-party attestations, and credential lifecycle checks so risk teams can separate directional exposure from remediable gaps. That prevents a high-level metric from replacing operational judgement.
Q: Why can two organisations with similar security posture still have different breach risk?
A: Because breach likelihood depends on more than current control grades. Digital footprint, third-party connections, exposed services, and historical loss patterns all shape how likely a breach is to occur and how far it can spread. Similar posture can therefore mask very different exposure profiles, especially when identity paths and external reach vary widely.
Q: What should teams do when a cyber risk score is based on probabilistic modelling?
A: Treat the score as a directional indicator and test it against real control evidence. Probabilistic models are useful for ranking and portfolio analysis, but they cannot prove a weakness or replace remediation verification. The practical test is whether the score aligns with known exposure, access scope, and third-party risk conditions.
Q: How do identity and third-party access affect breach susceptibility?
A: They expand the number of reachable paths into the environment. Broad vendor access, unmanaged service accounts, and exposed machine identities increase the likelihood that a threat actor can move from initial access to meaningful impact. That is why identity governance should be part of any susceptibility review, especially in supply chain-heavy environments.
Technical breakdown
How breach susceptibility scoring differs from posture scoring
Breach susceptibility scoring is intended to estimate the likelihood of a breach, not just describe current control health. Posture scoring usually focuses on configuration and remediation signals, while susceptibility models blend those signals with historical patterns and exposure characteristics such as footprint size. That means two organisations with similar control grades can still have different predicted risk if their external exposure, operating profile, or historical breach patterns differ. The technical point is that these models are probabilistic, not deterministic. They can improve prioritisation, but they do not prove security or identify a specific weakness on their own.
Practical implication: Use susceptibility scores to rank attention, then validate with direct control evidence before changing underwriting or governance decisions.
Why insurance data changes the model signal
Insurance claims data gives the model an outcomes-based training set, which is different from purely control-oriented risk scoring. Instead of asking only whether controls exist, the model learns which combinations of posture and exposure have historically aligned with loss events. That matters because cyber risk is often cumulative: weak segmentation, broad exposure, unmanaged third parties, and stale access controls can combine into a higher breach likelihood even when no single issue looks decisive. The model therefore reflects historical loss patterns as well as present-day security posture, which can make it useful for portfolio-level comparison.
Practical implication: Treat claims-informed scores as a portfolio lens, not as evidence that a specific control failed or that a specific breach is inevitable.
Where susceptibility scoring intersects with identity governance
The article’s identity angle sits in how digital footprint and exposure are shaped by access paths, vendor trust, and account sprawl. Breach likelihood rises when external-facing systems, third-party connections, and unmanaged service accounts expand the number of ways a threat actor can reach valuable assets. In practice, that means identity governance, NHI oversight, and vendor access review all feed into the quality of the risk signal. A score that ignores identity lifecycle weaknesses can understate exposure, especially in environments where access is broad but lightly evidenced.
Practical implication: Tie susceptibility review to identity and access evidence, especially for third-party accounts and non-human identities with broad exposure.
NHI Mgmt Group analysis
Susceptibility scoring is a governance input, not a control substitute. The article is useful because it acknowledges a real underwriting problem: security posture alone does not explain loss likelihood. But once a score starts shaping risk acceptance, pricing, or third-party prioritisation, teams must still demand control evidence for the underlying access paths, exposure, and identity lifecycle conditions that create the score in the first place.
Digital footprint is becoming an identity problem as much as a perimeter problem. The model’s emphasis on footprint size matters because exposed assets are rarely just technical surfaces. They are also the products of service accounts, vendor integrations, external authentication paths, and unmanaged machine identities that widen the reachable attack surface. Practitioners should read this as an argument for stronger identity governance in risk modelling, not as a call to trust the score blindly.
Breached-or-not logic is too coarse for modern cyber underwriting. A portfolio can look well controlled and still carry uneven inherent exposure because attack paths are distributed across vendors, cloud assets, and unmanaged credentials. That is why susceptibility scoring has value: it helps surface relative risk at scale. The practitioner conclusion is to use it to sharpen prioritisation, then validate with control testing and access governance before making binding decisions.
Model confidence depends on the quality of the underlying breach and exposure data. SecurityScorecard’s validation with insurance claims data strengthens the case for statistical correlation, but it does not remove model risk. Data drift, sector bias, and incomplete visibility can all distort outputs. For practitioners, the right response is to treat the score as a decision aid inside a broader governance process that includes identity evidence, remediation history, and third-party assurance.
Exposure scoring will keep moving closer to operational security decisions. As insurers and risk teams seek faster ways to compare portfolios, scoring models will increasingly influence who gets reviewed, priced, or escalated. That makes identity governance, especially around vendor access and NHI oversight, more central to cyber risk management than many underwriting teams have assumed.
From our research library:
- Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.
- Read next: Threat Modelling AI Agents
What this signals
Susceptibility scoring will only be useful where programmes can still trace the access paths behind the score. If an underwriting or third-party review process cannot map service accounts, vendor access, and exposed systems back to owned controls, the score becomes a broad indicator rather than a decision-grade signal. That pushes identity governance closer to the centre of cyber risk management than many teams expect.
Digital footprint is becoming a proxy for governance complexity. As the number of reachable systems, accounts, and integrations grows, so does the difficulty of proving which exposures are acceptable, which are temporary, and which are unmanaged. Teams that link third-party risk review to access lifecycle evidence will get more value from susceptibility scoring than teams that use it as a standalone rating.
Service account visibility remains a weak point in many environments. Only 5.7% of organisations have full visibility into their service accounts according to the Ultimate Guide to NHIs, which matters because hidden machine identities can distort the exposure picture that susceptibility models try to capture.
For practitioners
- Review susceptibility scores alongside control evidence Use the score to prioritise review, but require direct proof of access controls, remediation history, and external exposure before changing underwriting or risk treatment.
- Validate vendor and third-party access paths Check whether third-party accounts, integrations, and externally reachable systems are inflating the organisation’s breach susceptibility through unmanaged trust paths.
- Incorporate NHI exposure into portfolio review Assess service accounts, API credentials, and other non-human identities as part of the digital footprint that feeds susceptibility scoring and breach likelihood.
- Separate inherent risk from remediable posture Use susceptibility outputs to distinguish exposure that can be reduced quickly from structural risk that needs contract, architecture, or governance changes.
Key takeaways
- Breach susceptibility scoring is best understood as a portfolio risk signal that complements, rather than replaces, control evidence.
- Insurance claims history and digital footprint data can improve comparative risk assessment, but they also make model quality dependent on the visibility of underlying access paths.
- Identity governance, especially for third-party access and non-human identities, becomes more important when susceptibility scores influence underwriting and risk prioritisation.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK addresses the attack and risk surface, while NIST CSF 2.0 and CSA Cloud Controls Matrix set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | GV.RM-01 — Risk management strategy | The article is about using susceptibility scores inside cyber risk decisions and underwriting. |
| ID.RA-01 — Asset vulnerabilities are identified and documented | Breach susceptibility depends on posture and footprint exposure data feeding the model. | |
| ID.AM-01 — Physical devices and systems are inventoried | Digital footprint size is a core input to the model and requires accurate asset inventory. | |
| Recommendation — Use GV.RM-01 to embed susceptibility scoring into a documented risk management strategy. Use ID.RA-01 to document vulnerabilities and exposure signals that affect susceptibility scoring. Use ID.AM-01 to maintain a complete inventory of externally reachable systems and assets. | ||
| CSA Cloud Controls Matrix | IAM — Identity and Access Management | Identity and third-party access influence the exposure picture used in breach susceptibility scoring. |
| SEF — Security Incident Management, E-Discovery, and Forensics | The model is trained and validated against breach and claims history. | |
| Recommendation — Apply IAM controls to reduce exposed access paths that distort susceptibility results. Use SEF to preserve and analyse breach evidence that improves risk modelling accuracy. | ||
| MITRE ATT&CK | TA0006;TA0008 — Credential Access; Lateral Movement | The article’s risk model is shaped by exposure conditions that can enable credential abuse and spread. |
| Recommendation — Map exposure-heavy findings to TA0006 and TA0008 to prioritise controls that limit breach spread. | ||
Key terms
- Breach Susceptibility Indicator: A breach susceptibility indicator is a predictive metric that estimates how likely an organisation is to suffer a breach. It usually blends posture, footprint, and historical loss data so risk teams can rank exposure. It is useful for prioritisation, but it is not the same as proving a control is effective or absent.
- Online Footprint: An online footprint is the digital evidence that links a customer or device to a transaction, such as an IP address or device ID. Visa CE 3.0 uses this signal as part of the proof set for historical orders. It helps establish continuity between past and disputed purchases.
- Inherent risk: The level of risk that exists before any control is applied. In identity and audit contexts, it reflects the natural complexity of the process, the volume of transactions, and the likelihood of error or judgement failure. It is the starting point for assessing how much uncertainty the environment creates on its own.
- Third Party Risk: Third party risk is the chance that an outside organization, supplier, contractor, or service provider will create harm for your business. It includes security, privacy, operational, legal, and compliance exposure caused by access to data, systems, or processes. In identity terms, it often arises from shared credentials, integrations, and delegated trust.
Deepen your knowledge
NHI Foundation Level course, the industry's only accredited NHI security programme, covers NHI governance, machine identity security, and secrets management. It helps security and identity practitioners connect exposure signals to the controls that reduce real risk.
Published by the NHIMG editorial team on July 11, 2026.
Updated on October 11, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org