Probable maximum loss (PML) calculations in cybersecurity are usually done by in-house cybersecurity analysts who understand the firm’s systems, data, and risk profile. They blend technical insight with business context, while vendors offer tools. HR or government auditors don’t typically perform these specific assessments.

Multiple Choice

Who typically performs probable maximum loss calculations?

Probable maximum loss (PML) calculations are conducted to estimate the potential loss in value from a catastrophic event, which is crucial for risk management within an organization. Generally, cybersecurity analysts within a company possess the appropriate expertise and insight into the organization's systems, data security, and overall risk profile. They can analyze various factors, including the vulnerabilities present within their infrastructure, potential threat scenarios, and the impact that different cyber incidents could have on the business. Cybersecurity analysts are trained to evaluate the technical aspects of the system as well as the business context, allowing them to provide a more nuanced and accurate assessment of probable maximum losses. Their role enables them to tailor the PML calculations specifically to the company's operations, assets, and risk environment. While external software vendors may provide tools or models to assist in these calculations, they typically lack the deep understanding of the company's unique circumstances that in-house analysts have. Human resources representatives are generally not involved in risk assessments, as their focus is primarily on employee management and organizational structure. Similarly, government cybersecurity auditors are responsible for ensuring compliance with regulations and standards, rather than conducting specific PML calculations for individual companies. Their primary function is to audit and assess compliance rather than to focus solely on a company’s potential financial losses from

Probable maximum loss in a cyber world: who actually does the math?

If you’ve ever stood at the edge of a cybersecurity risk assessment, you’ve probably heard the term probable maximum loss, or PML. It sounds like something out of a risk officer’s playbook, a big number that shows how bad things could get if a cyber catastrophe hits. But who rolls up their sleeves to figure out that number? The short answer is: typically the cybersecurity analysts inside an organization. They’re the ones who blend technical know-how with business sense to translate a messy digital landscape into a financial lens you can actually use for decisions.

Let me explain why this work fits so naturally inside a company, and what that really means in practice. It’s not just about pinballing through a cascade of potential incidents and hoping for the best. PML is a structured way to estimate the worst reasonable loss from cyber events, given a company’s assets, data, dependencies, and resilience. That requires both systems insight and business context—two things in-house analysts spend their days cultivating.

What makes internal analysts the right fit?

  • Deep familiarity with your ecosystem: The moment you start mapping threats to assets, you’re tapping into something very grounded—where sensitive data lives, how critical systems tie together, and what could cause a chain reaction. External voices can offer models or tools, but they don’t live your topology. Analysts can tailor the math to reflect real-world interdependencies, third-party risks, and unique operational quirks.

  • The business lens, not just the tech lens: It’s easy to get lost in threat lists and CVSS scores, but PML needs to connect those technical details to financial impact. What would it mean if a customer database went dark for a week? How would regulatory fines, reputational costs, or recovery expenditures play out? Those are business questions as much as they’re technical ones, and in-house teams are best positioned to answer them.

  • Context on controls and resilience: Analysts know what controls exist, how effective they are, and where gaps lie. They can quantify how a given control—like multifactor authentication, segmentation, or incident response time—mitigates a potential loss. This isn’t abstract; it’s a practical map of risk reduction.

What does a typical PML workflow look like?

  1. Scope and asset inventory
  • The starting point is a clear map of what you’re protecting: data assets, systems, networks, and supply chain dependencies. This isn’t a shiny diagram; it’s a living inventory that includes critical processes, slippage points, and recovery timelines.
  1. Threat scenario development
  • Rather than chasing every possible threat, analysts outline plausible, high-impact scenarios. Think ransomware that encrypts core databases, a supply chain compromise, or a cloud misconfiguration that exfiltrates sensitive data. The goal is to stay focused on what would cause meaningful losses.
  1. Impact modeling
  • Here’s where business reality kicks in. Analysts estimate direct costs (ransom, downtime, forensic work) and indirect costs (customer churn, regulatory penalties, brand damage). They also consider recovery options, such as backups, cyber insurance, and incident response. It’s a careful balance of numbers and narratives—you need both to tell a credible risk story.
  1. Quantification and aggregation
  • PML isn’t one-off guesswork. It’s a structured calculation that accounts for probability, magnitude, and correlation across assets and events. For example, a ransomware scenario might have a certain likelihood, but if multiple systems fail in concert, the combined loss could be far larger than the sum of parts. Analysts model those dependencies to arrive at a probable maximum loss figure.
  1. Validation and governance
  • The figures don’t stand alone. They’re reviewed with risk governance bodies, legal, finance, and senior leadership. This helps ensure the assumptions are reasonable, the data is sound, and the conclusions align with the organization’s risk appetite and strategic priorities.
  1. Communication and decision support
  • The final product is a narrative plus numbers—a risk brief that explains where the big risks lie, why they matter, and what can be done to reduce exposure. It’s not a single number you worship; it’s a lens to guide investments in security controls, incident response capabilities, and resilience planning.

Why not leave PML to vendors or auditors?

You’ll sometimes see PML models offered as part of security software suites, or you might hear about external auditors weighing in on risk. Those inputs are valuable, but they don’t replace the value of internal expertise. External tools can provide structured frameworks, standardized metrics, and scalable calculations, which is great. Yet the nuance of your organization—the specific data sets, the way systems interconnect, the regulatory obligations you face, and the business implications of downtime—stays best understood by people who live and breathe the environment every day.

External tools often serve as powerful accelerators rather than complete substitutes. They can help you run scenarios more efficiently, automate data collection, or apply a common framework to your risk assessments. But without the in-house perspective, you risk misinterpreting results or overestimating the efficiency of a control that, in your real world, behaves differently.

Common pitfalls and how to avoid them

  • Overreliance on a single threat seed: It’s tempting to fixate on the latest fright story. PML benefits from a spectrum of plausible scenarios, including some less flashy but highly likely risks. Diversity in scenarios prevents a skewed risk view.

  • Underestimating third-party risk: Vendors, partners, and cloud providers extend your attack surface. If you don’t quantify how those external nodes influence losses, you’ll miss a big piece of the puzzle.

  • Ignoring recovery costs: People often focus on ransom or downtime, but recovery work—forensics, system rebuilds, legal counsel, notification expenses—can add up fast. A comprehensive PML includes those recovery arcs.

  • Treating PML as a one-off exercise: Risk is dynamic. Revisit and refresh your PML assumptions as tech stacks evolve, threat actors shift tactics, or business priorities change. A stale PML becomes a liability, not a compass.

  • Too much complexity, too little clarity: It’s tempting to chase precision with endless data layers. The risk is paralysis. Aim for a clear, defendable model that communicates the key drivers of loss.

A few practical tips to keep the momentum

  • Start with the critical paths: Prioritize assets that would disrupt the business most if they failed. That keeps the effort focused where it matters.

  • Build a living data lake: Centralize asset information, risk inputs, and cost data. When the numbers pile up, you’ll thank yourself for the organization.

  • Use a credible framework, and adapt it: The FAIR framework (Factor Analysis of Information Risk) is popular in the industry for structuring cyber risk. You don’t have to copy it exactly, but borrow its disciplined way of thinking—probabilities, losses, and controls—and adapt it to your context.

  • Pair tech with business insight: Involve finance for cost accounting and legal for regulatory framing. The best PML assessments come from cross-functional collaboration.

  • Keep the story human: Numbers tell a story, but people connect with narratives. A scenario’s impact on customers, employees, and partners can be as persuasive as the math itself.

Real-world flavor: what PML looks like in practice

Imagine a mid-sized financial services firm with a hybrid tech stack—on-prem data centers, cloud workloads, and a sprawling partner network. The in-house cybersecurity team starts with a high-impact scenario: a ransomware incident that locks down core payment processing systems and blocks customer data. They estimate direct costs (ransom negotiations, data restoration, forensics), downtime losses (fraud checks halt, customers can’t complete transactions), and recovery expenses (security upgrades, third-party pen tests, regulatory notifications).

But they don’t stop there. They overlay the probability of this scenario based on recent threat intel and the current control environment—strong backups, segmented networks, and a robust incident response playbook. They also factor in third-party risk: what if a critical payment processor is breached? What would the cascading losses look like across the ecosystem?

The result is a defensible PML figure that guides budget decisions. Maybe it highlights a higher risk tied to the third-party gateway, prompting investment in stronger vendor risk management and redundant downstream partners. Maybe it spotlights a need for faster tabletop exercises to improve detection and containment. Either way, the PML becomes a practical compass, not a mystical number.

Why this matters for the broader cyber security narrative

PML is more than a financial curiosity. It’s a way to translate complex cyber risk into a language that leadership and stakeholders can act on. It helps teams set priorities, justify investments, and measure progress over time. If you think about risk in terms of potential losses and the likelihood of those losses, you gain a framework for resilience that’s both disciplined and adaptable.

On a personal level, the work can feel empowering. It’s about turning a sprawling cyber risk landscape into something tangible and actionable. That’s the bridge between technical prowess and strategic impact—the bridge you want your organization to walk across with confidence.

A final reflection: the human side of numbers

PML sits at an interesting crossroads. It demands precision and humility in equal measure. Precision, because you’re quantifying something that matters deeply to the business; humility, because you’ll never predict every permutation of the future. PML is a living conversation between what the data says, what the systems allow, and what the leadership cares about. It’s less about chasing a perfect figure and more about building a shared understanding of risk, and the steps we’ll take to stay one move ahead.

If you’re curious about how to start shaping a practical PML process in your organization, begin with the basics: map your critical assets, frame a handful of high-impact scenarios, and invite the finance folks to the table early. You’ll likely discover that the most valuable insight isn’t a single number but a clearer sense of where to focus time, money, and energy to keep the business moving forward—safely.