All’s FAIR in love and risk reporting

Fair Institute and Phoenix Security to quantify risk in appsec and cloudsec
Fair Institute and Phoenix Security to quantify risk in appsec and cloudsec
Fair Institute and Phoenix Security to quantify risk in appsec and cloudsec

“It takes 20 years to build a reputation and a few minutes of a cyber-incident to ruin it.”
 Stephane Nappo

Last year was a year of statistics. We all got very used to reading and watching the news and being bombarded with facts and figures and graphs and numbers from the get-go. So, here’s another one: 18,362. That’s the number of CVEs the NVD database published in 2020. That’s higher than in previous years and looks certain to keep rising.  One consequence is that most are struggling to control the large volume of software vulnerabilities across their entire IT systems, and resources are simply not available to fix these issues efficiently and effectively.

Despite the scale of the problem being well recognised, few organisations have developed consistent, measurable, and insightful risk reporting that identifies the vulnerability risk profile across the complete attack surface of their business.  Unless such reporting is implemented, it is impossible for the Board and senior leadership of an organisation to:

  • Establish whether they are operating within risk appetite.
  • Assess the effectiveness of their vulnerability management strategies.
  • Understand the investment in vulnerability remediation and assess whether the return on investment is proportionate.
  • Demonstrate to key stakeholders that the internal control and reporting framework is appropriate relative to the residual information security risks that exist.

At AppSec Phoenix we have used the Factor Analysis of Information Risk (FAIR) framework to develop meaningful and quantifiable reporting on vulnerability risk. We have started using the FAIR approach defining the loss magnitude ontology:

<Risk> = <Threat Event Frequency> x <Vulnerability> x <Loss Magnitude>

Threat Event Frequency, as the name would suggest, is a function of Contact Frequency and Probability of Action.  Until recently the existence of an exploit in the wild was the most relevant proxy for assessing the probability that an exposed vulnerability can be used to compromise a firm’s network.  However, as more data is produced, predictive machine learning is starting to be used to identify which vulnerabilities are most likely to be exploited in the future.

The CVSS score is the industry standard for measuring the severity of a Vulnerability.  We have introduced a new parameter in our risk engine, Vulnerability Density, which identifies clusters of vulnerabilities at the component level, which exceeds the risk threshold of the organisation. Loss Magnitude is evaluated by measuring both Primary Risk (the loss that materialises directly from the event) as well as the Secondary Risk (the potential for secondary stakeholder reaction to the primary event, so things like regulatory sanction, for example).

The risk assessment starts with each vulnerability and is then aggregated at all levels and consolidated to report on the entire organisation. The benefits of this systematic and objective risk reporting go beyond protecting an organisation against loss. Our model also improves the working relationship between the Information Risk and Software Development teams and consequently:

  • There is a reference point which facilitates a constructive and objective discussion between the business and technology teams.
  • Measurable KPIs can be agreed.
  • Management can measure ‘cost to fix’ against the risk mitigation achieved and calculate the return on investment.
  • There is increased visibility on the true costs of maintaining a cyber secure application architecture.

Governance forums also need to be presented with aggregated reporting across the organisation as well as heat maps showing the risk profile down to sub-component level to highlight any ‘hot-spots. This holistic, data-driven approach application security risk management is now a prerequisite for all organisations to enable them to honour their obligations to stakeholders, improve operational performance and, ultimately, boost their bottom line.

For more information, please contact us at AppSec Phoenix!

Francesco is an internationally renowned public speaker, with multiple interviews in high-profile publications (eg. Forbes), and an author of numerous books and articles, who utilises his platform to evangelize the importance of Cloud security and cutting-edge technologies on a global scale.

Discuss this blog with our community on Slack

Join our AppSec Phoenix community on Slack to discuss this blog and other news with our professional security team

From our Blog

The journey of securing an organization’s application landscape varies dramatically, depending on where a company stands in its maturity. Early-stage startups with small security teams face challenges not only with vulnerabilities but also with scaling their security processes in line with their growth. On the flip side, established enterprises struggle with managing complex environments, prioritizing remediation, and dealing with vast amounts of vulnerabilities while staying ahead of sophisticated threats. For startups, the focus is clear—establish visibility and ensure core security practices are in place. Application Security Posture Management (ASPM) tools provide a straightforward, automated approach to detecting vulnerabilities and enforcing policies. These solutions help reduce risk quickly without overburdening small security teams. Mature organizations, on the other hand, are tackling a different set of problems. With the sheer number of vulnerabilities and an increasingly complicated threat landscape, enterprises need to fine-tune their approach. The goal shifts toward intelligent remediation, leveraging real-time threat intelligence and advanced risk prioritization. ASPM tools at this stage do more than just detect vulnerabilities—they provide context, enable proactive decision-making, and streamline the entire remediation process. The emergence of AI-assisted code generation has further complicated security in both environments. These tools, while speeding up development, are often responsible for introducing new vulnerabilities into applications at a faster pace than traditional methods. The challenge is clear: AI-generated code can hide flaws that are difficult to catch in the rush of innovation. Both startups and enterprises need to adjust their security posture to account for these new risks. ASPM platforms, like Phoenix Security, provide automated scanning of code before it hits production, ensuring that flaws don’t make it past the first line of defense. Meanwhile, organizations are also grappling with the backlog crisis in the National Vulnerability Database (NVD). A staggering number of CVEs remain unprocessed, leaving many businesses with limited data on which to base their patching decisions. While these delays leave companies vulnerable, Phoenix Security steps in by cross-referencing CVE data with known exploits and live threat intelligence, helping organizations stay ahead despite the lag in official vulnerability reporting. Whether just starting their security program or managing a complex infrastructure, organizations need a toolset that adapts with them. Phoenix Security enables businesses of any size to prioritize vulnerabilities based on actual risk, not just theoretical impact, helping security teams navigate the evolving threat landscape with speed and accuracy.
Francesco Cipollone
The cybersecurity world is reeling as MITRE’s funding for the CVE and NVD systems expires, disrupting the backbone of global vulnerability management. As traditional sources like the National Vulnerability Database collapse under funding cuts and submission backlogs, security teams face delays, incomplete data, and loss of automation in remediation pipelines. This isn’t just a data problem—it’s a structural crisis for application security and vulnerability correlation. In this landscape of uncertainty, Phoenix Security’s ASPM platform steps up with a code-to-cloud correlation engine that doesn’t depend on outdated data workflows. By connecting code-level insights (including tools like Semgrep) to runtime and cloud environments, Phoenix enables faster, context-aware vulnerability remediation—even as NVD and CVE pipelines deteriorate. This article dives into the implications of the CVE shutdown and how Phoenix Security is helping security and development teams transition to a resilient, correlation-first approach to cybersecurity.
Francesco Cipollone
Learn how to predict ransomware risks and vulnerability exploitation using a threat-centric approach. Explore data-driven insights, verified exploit trends, and methods for assessing the likelihood of attacks with key references to CISA KEV, EPSS, and Phoenix Security’s 4D Risk Formula.
Francesco Cipollone
Remote Code Execution flaws continue to undermine Kubernetes ingress integrity. IngressNightmare (CVE-2025-1097, CVE-2025-1098, CVE-2025-24514, CVE-2025-1974) showcases severe threat vectors in NGINX-based proxies, leading to cluster-wide exposure. ASPM, robust remediation tactics, and strong application security solutions—like Phoenix Security—mitigate these vulnerabilities before ransomware groups exploit them.
Francesco Cipollone
Remote Code Execution flaws continue to undermine Kubernetes ingress integrity. IngressNightmare (CVE-2025-1097, CVE-2025-1098, CVE-2025-24514, CVE-2025-1974) showcases severe threat vectors in NGINX-based proxies, leading to cluster-wide exposure. ASPM, robust remediation tactics, and strong application security solutions—like Phoenix Security—mitigate these vulnerabilities before ransomware groups exploit them.
Francesco Cipollone
The recent Google acquisition of Wiz for $32 billion has sent shockwaves through the cybersecurity industry, particularly in the realm of Application Security Posture Management (ASPM). This monumental deal highlights the critical importance of cloud security and the growing demand for robust ASPM solutions. While the acquisition promises potential benefits for Google Cloud users, it also raises concerns about vendor lock-in and the future of cloud-agnostic security. Explore the implications of this acquisition and discover how neutral ASPM solutions like Phoenix Security can bridge the gap in multi-cloud environments, ensuring continuous, collaborative, and comprehensive security from code to cloud.” – Find Assets/Vulns by Scanner – Detailed findings Location information Risk-based Posture Management – Risk and Risk Magnitude for Assets – Filter assets and vulnerabilities by source scanner Integrations – BurpSuite XML Import – Assessment Import API Other Improvements – Improved multi-selection in filters – New CVSS Score column in Vulnerabilities
Alfonso Eusebio
x  Powerful Protection for WordPress, from Shield Security
This Site Is Protected By
ShieldPRO