Loss event frequency
How often a loss event is expected to occur, combining how often a threat acts against an asset and how likely that action is to succeed.
Vulnerabilities show where your organization is exposed. Cyber Risk Quantification helps you understand the impact of that exposure on the business and creates a common language between security, risk, finance and executive leadership.
Eagle connects technical context, risk scenarios, business impact and treatment decisions to turn security data into risk intelligence.
Number of vulnerabilities, severity, CVSS, vulnerability age, SLA and technical criticality remain important. On their own, they are not enough to determine business impact.
The goal is not to fix everything first. It is to reduce the right risk first.
Cyber Risk Quantification is the discipline of representing cyber risk scenarios using quantitative metrics and, when appropriate, financial estimates.
Instead of stopping at high, medium or low, quantitative risk analysis asks how often an event is likely to happen and how much it may cost — and records how confident the estimate is. The analysis may consider:
CRQ does not eliminate uncertainty. It makes uncertainty explicit, measurable and useful for decisions.
FAIR — Factor Analysis of Information Risk — provides a structure for breaking risk down into loss event frequency and loss magnitude. It is maintained as an open standard, Open FAIR, by The Open Group.
How often a loss event is expected to occur, combining how often a threat acts against an asset and how likely that action is to succeed.
How much each event may cost, including primary losses and secondary losses that come from the reaction of customers, regulators and the market.
Eagle is not presented as FAIR-certified, nor as formally compliant with the standard. Its risk model organizes scenarios, assets, threats, controls, likelihood and impact — context that is conceptually compatible with quantitative approaches inspired by models such as FAIR.
An estimate of the financial loss expected over a given period.
An estimate of the loss associated with a given confidence level and time horizon.
The probability that a given loss will be exceeded.
A consolidated representation of the financial exposure associated with risk scenarios.
Applying these indicators depends on the methodology, the quality of the data, the assumptions used and the maturity of the risk process.
Eagle seeks to connect technical signals and business context so that vulnerabilities are not analyzed in isolation.
A modern approach to vulnerability management can consider:
Two vulnerabilities with the same CVSS do not necessarily represent the same risk — and a lower score can hide a higher priority.
Illustrative example
Priority should reflect risk context, not just technical severity. To read a CVSS score correctly, see the article CVSS 4.0: how to read a vulnerability score.
ROSI is an approach used to evaluate security investments economically, comparing the cost of protection with the expected reduction in losses.
ROSI = (Expected loss reduction − Investment cost) ÷ Investment cost
ROSI can support comparisons between alternatives such as:
The goal is to move from “how much does security cost?” to “how much risk are we reducing with this investment?”
The three layers describe a maturity path. Eagle’s risk architecture creates the foundation for incorporating quantitative risk models and the economic analysis of treatments; financial quantification and ROSI are presented here as an evolution of the model, not as current features.
This view builds a bridge between CISO, CRO, CFO, CEO and the Board.
Cyber Risk Quantification depends on context that already lives in different modules of the platform.
Scenarios, assessment, treatment, inherent and residual risk.
Explore the moduleContextualization of vulnerabilities and technical exposure.
Explore the moduleControls, frameworks, evidence and requirements.
Explore the moduleConsolidation of the enterprise risk view.
Explore the moduleContext on vendors, contracts and external dependencies.
Explore the moduleOperational impact, critical processes and resilience.
Explore the moduleThe capabilities shown may vary by environment and contracted scope.
| Role | Key question |
|---|---|
| CISO | Which risks should be prioritized? |
| Vulnerability Manager | Which vulnerabilities actually change our exposure? |
| CRO | Are we within the defined appetite and tolerance? |
| CFO | What is the financial exposure, and where should we invest? |
| CEO | Which processes and objectives are threatened? |
| Board | Is the organization reducing the most relevant risks? |
A technical score has no deterministic financial relationship. Converting CVSS, EPSS or vulnerability counts directly into monetary values creates a false sense of precision.
A defensible analysis requires:
Apparent precision is not the same as confidence in the decision.
Quantitative estimates should make it possible to record:
The value of quantification lies not only in the final number, but in the ability to explain how it was obtained.
It is the discipline of representing cyber risk scenarios with quantitative metrics and, when appropriate, financial estimates, such as likely event frequency and loss magnitude.
CRQ stands for Cyber Risk Quantification: expressing cyber risk in quantitative terms so that it can be compared, prioritized and discussed with finance and leadership.
Traditional vulnerability management tends to prioritize by technical severity. Risk-Based Vulnerability Management adds likelihood of exploitation, exposure, asset criticality, business context and existing controls to decide what to treat first.
CVSS measures the technical severity of a vulnerability. EPSS estimates the probability that it will be exploited. Risk combines these signals with the asset, the threat, the controls in place and the impact on the business.
FAIR, Factor Analysis of Information Risk, is a model maintained as an open standard by The Open Group that breaks risk down into loss event frequency and loss magnitude.
Annual Loss Expectancy is an estimate of the financial loss expected from a risk scenario over one year. Its reliability depends on the data and assumptions used.
Return on Security Investment compares the expected reduction in losses with the cost of a security investment: expected loss reduction minus investment cost, divided by investment cost.
Not necessarily. CRQ can complement qualitative and semi-quantitative methods, which remain useful for initial triage and for scenarios with little data.
Not directly. Vulnerabilities need to be related to scenarios, threats, assets, frequency and impact. Converting CVSS or vulnerability counts directly into money creates false precision.
Inherent risk is the risk before considering the effect of controls. Residual risk is what remains after controls and treatment are applied. It is never zero.
It expresses exposure in terms comparable to other enterprise risks, supports budget and insurance discussions and shows whether investments are reducing the most relevant risks.
Yes. Third-party scenarios, such as the outage of a critical supplier or a data breach at a partner, can be analyzed with the same frequency and impact logic.
Yes. Comparing the expected risk reduction of each alternative with its cost helps decide where an investment reduces the most risk.
See how Eagle connects exposure, risk, controls and business context to support risk management that is more quantitative, explainable and decision-oriented.