Skip to content

GRA · AI and Financial Model Risk

Spatial financeWhere capital meets hazard, exposure and transition

AI evaluation and assurance engineering for AI and financial model risk

AI assurance is the set of practices that give justified confidence in an AI or model system: validation, testing, red-teaming, monitoring, documentation and independent review. On this platform it connects established model risk management with the new evidence AI systems require.

01Register

AI evaluation and assurance engineering for AI and financial model risk on the record.

Method recordSTEM method
  1. MethodAI evaluation and assurance engineering
  2. Applied inAI and Financial Model Risk
  3. Canonical pageSTEM Commons
02Application

What AI evaluation and assurance engineering does here.

AI evaluation and assurance engineering develops methods to test, monitor and provide justified confidence in AI systems. It addresses performance, robustness, safety and societal impact across the system life cycle. In artificial intelligence and financial stability, AI assurance determines whether automated systems can be trusted in high-consequence settings. It helps manage risks when AI is embedded across finance, health and infrastructure. The canonical description is on the STEM Commons.

Validation of machine learning models

Conceptual soundness, data quality, outcome analysis and stability testing are adapted to models whose internal logic is hard to read.

Red-teaming generative AI

Adversarial tests probe language model applications for prompt injection, data leakage and harmful output before and after deployment.

Fairness assessment

Outcome rates and error rates are compared across groups, with the chosen fairness criterion and its legal basis documented for review.

03Exposure, loss and capital

What it means for exposure, loss and capital.

The exposure, loss, scenario and capital views a risk officer, supervisor or ministry of finance would ask for, with the frameworks they report against. Structures follow supervisory and actuarial practice. Values are illustrative: never prices, ratings or advice.

Transmission channels

How a shock in AI evaluation and assurance engineering for AI and financial model risk reaches credit, market, underwriting, liquidity and operational risk, and feeds back.

Channel structure after the Basel Committee’s work on climate-related risk drivers and transmission channels; links shown are typical paths, not estimated exposures.
NGFS climate scenarios · Network for Greening the Financial SystemIFRS S2 Climate-related Disclosures · ISSBTCFD recommendations · Financial Stability Board TCFDPrinciples for the effective management of climate-related financial risks · Basel Committee on Banking Supervision
04Data

What the method consumes.

Datasets and records used by AI evaluation and assurance engineering on this platform, with the role each plays and the label its values carry. Sources are listed in the source register.

DataJukumuLabel
Validation reportsAssurance evidenceDECLARED
Red-team resultsAdversarial weaknessesIMEONEKANA
Outcome dataReal-world performanceIMEONEKANA
05Mchakato

How the process runs.

Process explorer · Process

AI evaluation and assurance engineering for AI and financial model risk: AI risk management (NIST)

9 steps5 stages1 gate

Mchakato

AI evaluation and assurance engineering for AI and financial model risk: AI risk management (NIST)

The AI RMF Core has four functions, GOVERN, MAP, MEASURE and MANAGE, with GOVERN cross-cutting; the order drawn is one common reading, not a checklist.

  1. 01 Govern

    1. 01GOVERN: policies, roles and accountabilityStep · MRM committeeGOVERN is a cross-cutting function. It is infused throughout AI risk management and enables the other functions.
  2. 02 Map

    1. 02MAP: context and intended useDatasetThe MAP function establishes the context to frame risks related to an AI system, including intended purposes and impacts on people.
  3. 03 Measure

    1. 03MEASURE: evaluate trustworthy characteristicsModelAI systems are evaluated for trustworthy characteristics. They should be tested before deployment and regularly in operation.
    2. 04MEASURE: track identified risks over timeModelMechanisms for tracking identified AI risks over time are in place, including unanticipated and emergent risks.
  4. 04 Manage

    1. 05MANAGE: treat risksStepRisk treatment plans cover response to, recovery from and communication about incidents. Resources go to mapped and measured risks.
    2. 06Proceed or not (MANAGE 1.1)Gate · MRM committeeA determination is made whether the system meets its purposes and objectives, and whether to proceed. The framework sets no thresholds.
    3. 07Deployment decisionDecision · MRM committeeThe organisation that owns the system decides whether and under what conditions to deploy.
    4. 08Post-deployment monitoring and incidentsModelPost-deployment monitoring plans are implemented. Incidents and errors are shared with relevant AI actors, including affected communities.
  5. 05 Record

    1. 09Inventory of AI systemsDatasetGOVERN 1.6 asks for mechanisms to inventory AI systems. A model card is common practice and is not named in the framework.

Neutral outline of a published external standard or method, from its issuing body. Not a record of operation. Nexus does not perform, certify or approve any step shown. A gate or decision belongs to the party the source names. The actions are not necessarily an ordered set of steps. The EU AI Act is not drawn in this flow.

06Validation

How results are checked.

Evaluation methods are checked for reliability and relevance to deployment conditions. Independent replication and third-party audits test claims.

CheckHow it is done
UhuruAssurance is performed by people independent of development
Scope statedWhat assurance covered and excluded is recorded
Repeat after changeMaterial model or version changes trigger renewed assurance

Benchmarks may not reflect real-world use or novel capabilities. General-purpose systems have open-ended behaviour that resists complete testing.

08Usimamizi

Who maintains the method.

Artificial Intelligence and Autonomous Systems stewards AI evaluation and assurance engineering for the Consortium and reviews how it is applied across platforms.

10Maswali

Questions and answers.

What are the limits of AI evaluation and assurance engineering in this field?
Benchmarks may not reflect real-world use or novel capabilities. General-purpose systems have open-ended behaviour that resists complete testing.
How are results checked?
Evaluation methods are checked for reliability and relevance to deployment conditions. Independent replication and third-party audits test claims.
Are the values on this page real?
The data names, roles and checks are real descriptions of practice. The canvas shows a design of the method’s use, not a run; no result is reported here.
Where else is this method applied?
The canonical method page lists every platform that applies it.
RipotiChangia

Changia ushahidi kutoka ukurasa huu.

Reports ni chapisho la kila robo mwaka la Muungano. Unachojua kuhusu somo hili kinaweza kuwa ushahidi, kisa au sahihisho katika toleo lijalo, kikitajwa kwa jina lako na kuchapishwa chini ya CC BY 4.0 pale ambapo ni kazi yako mwenyewe.

Global Risks AllianceAI and Financial Model RiskMethods and TechnicalExponential Technology
Akili Bandia na Hatari za Kielelezo cha Fedha

Bring an exposure or capital question to the Alliance.

Information and enquiries are open today. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.