Skip to content

Portfolio Overview ​

In Modulos, risk quantification is a primary part of AI governance. It changes the question "what could go wrong" into a monetary value. You can use this value to set priorities and budgets, to delegate decisions, and to do audits.

What this is ​

Risk quantification does not remove risk. Quantification makes risk clear. Leaders can then select which risks to accept, which risks to decrease, and which activities to stop.

When risk has only a qualitative rating, governance can become a veto without a basis. When risk is a monetary value, the decision uses facts: the expected loss, the risk appetite, and the cost of mitigation.

Quantification also makes decisions quicker:

  • decisions at each gate of the AI System life cycle become clear and repeatable
  • teams can make decisions in the limits that the organization sets
  • "too risky" becomes a statement that you can examine and make better

Where in Modulos ​

Use these tabs and pages to see and manage the risk exposure:

  • Organization → Risk Management → Risk Overview for the totals, the trend, and the risks with the highest values
  • Organization → Risk Management → Portfolio for a map of the risk values against the limits, and for the economic value of each AI System against its risk value
  • Organization → Risk Management → Risk Limits and AI System Risk Limits for the appetite and the limits
  • AI System → Risks to add risks, select threats, and quantify

For the roles and the rules for totals, see Risk Operating Model.

Permissions

  • Risk Managers change the risk configuration of the organization.
  • AI System Owners usually start the quantification runs.
  • On the Portfolio tab, users without full access to all AI Systems see only the AI Systems where they have a role.
Risk Overview tab with four KPI cards, the Risk Distribution by Category card, and the Top 3 Highest Risk Value AI Systems card.
The Risk Overview tab shows the totals of the organization and the AI Systems with the highest risk values.
  1. 1
    Total Organization Risk Exposure
    The sum of the risk values of all AI Systems, with the limit of the organization.
  2. 2
    Risk Distribution by Category
    The value of the first five categories, each against its limit.
  3. 3
    Top 3 Highest Risk Value AI Systems
    The AI Systems with the highest values. Select one to open its Risks page.

The Risk Overview tab ​

The Risk Overview tab in Organization → Risk Management is the dashboard of the organization. It shows these items:

ElementWhat it shows
Total Organization Risk Exposure (KPI)The sum of the risk values of all AI Systems. The Limit below the value is the total risk appetite.
Total Economic Value (KPI)The sum of the annual economic values of the AI Systems.
Risks Identified (KPI)The number of risks in the organization taxonomy. This number includes the archived risks.
Risk / Total Appetite (KPI)The total risk appetite of the organization, as money.
Risk Distribution by CategoryThe value of the first five categories, each against the limit of the category.
Top 3 Highest Risk Value AI SystemsThe three AI Systems with the highest values, each against its limit. Select one to open its Risks page.
Risk Value Over TimeThe total risk value across time, and a line for the total risk appetite. The Stacked and Breakdown views show each AI System.
Top 3 Highest Risk per Category (across AI Systems)The three risks with the highest values in each category, each with the name of its AI System.

The Risk Overview tab counts only AI Systems with the registration status Pending or Approved, and not the organization AI System. The values follow the rules in How risk becomes a portfolio signal. To change the appetite or a category limit, use the Risk Limits tab.

Organization history

The organization has no Quantification History table. The history of the runs is on the Threat Quantification Detail page of each threat. See Run history and trends.

How it works ​

In Modulos, the value of a risk comes from its threats:

text
Expected loss = Σ (rate × damage)
  • Rate: how frequently the threat becomes an incident.
  • Damage: the monetary loss for each incident.

This division into rate and damage shows where the risk comes from. It also shows which part a mitigation must decrease.

Platform objects and rollups ​

  • Organization taxonomy: shared categories, risks, and threat vectors.
  • AI System risks: taxonomy risks that an AI System uses.
  • Risk threats: threat vectors in one AI System.
  • Quantification runs: the method, the inputs, the outputs, the status, and one monetary value for each risk threat.
  • Rollups and limits: risk threat → risk → AI System → category → organization.

The Portfolio tab ​

The Portfolio tab has two views. Select Treemap or Value and Risk at the top of the tab.

  • Treemap shows the risk values as a map of tiles and compares them with the risk limits. See Treemap.
  • Value and Risk compares the annual economic value of each AI System with its risk value, and gives each AI System an assessment. See Value and Risk.

Each user of the organization can open the Portfolio tab when risk management is on for the organization. The two views include only AI Systems with the registration status Pending or Approved, and not the organization AI System. Users without full access to all AI Systems see only the AI Systems where they have a role.

Risk appetite and limits ​

Limits connect quantification to the risk appetite of the organization:

  • The organization sets a total monetary risk appetite.
  • Each category gets a percentage of the appetite.
  • Each AI System with the status Pending or Approved, other than the organization AI System, gets a risk limit from the appetite.
  • In each AI System, each risk gets a limit from the budget of its category.

For the rules and the warnings, see Risk limits.

Portfolio reality

The sum of the expected losses is a good start. But shared vendors, shared foundation models, and shared infrastructure can connect risks. For exposures that collect in one area, use scenario analysis and examine the dependencies.

How to use it ​