Methodology

A useful number
comes with context.

Read the modeled estimate alongside its source evidence, scope, assumptions and limitations.

The measures

Two views of modeled exposure.

01

SLN

Systemic Liability Number describes modeled systemic exposure under the stated scope and valuation assumptions.

02

ELN

Exploitable Liability Number describes modeled exploitable exposure under the analysis conditions.

Business-value inputs

Your context belongs in the model.

Where an IVaR analysis requires business-value inputs, the customer supplies or approves them. AIRE does not independently assert the customer’s revenue, loss or asset value. The readout should identify the input owner, source, assessment date and assumptions used. Proprietary weighting formulas and implementation details remain within the AIRE engine.

Reading the result

Keep observation, assumption and output distinct.

01

Observed evidence

Identity and access information available from the agreed sources.

02

Approved assumptions

Business-service mapping, valuation inputs and assessment conditions.

03

Modeled output

An estimate interpreted within that scope, rather than a prediction of realized loss.

Comparing a change

Compare like with like.

AIRE / CHANGE REVIEW Sample environment
Illustrative · synthetic data

A smaller permission.
A measurable difference.

build-agent
Service identity
→Export role
Access path
→Billing service
Business context
BASELINE $1.2M
CURRENT MODEL $1.2M
No change selected Model held constant
Inspect the example

The example identity has export access to a billing service. Select the proposed change to compare a narrower permission under the same illustrative valuation assumptions.

Scope: one synthetic identity path. Proposed scenario removes export access while retaining the required read access. This demonstration uses fixed illustrative values, not a live risk calculation or production connector.

Modeled exposure is not expected loss, cash savings, or an insurance valuation. Understand the measures ↗

A delta needs a consistent baseline.

Record the scenario, input values, scope and model version. Explain whether a difference comes from an access change, refreshed evidence, a valuation update or another model change.

After implementation, verify the access change and reassess. A proposed scenario is distinct from a confirmed operational result.

SLN, ELN and example deltas are not expected loss, cash savings, insurance value or guaranteed financial outcomes.

Your next move

Inspect the example with us.

We’ll walk through your use case, confirm the supported scope, and agree what a useful result looks like.