Skip to content

Model Risk Governance System of Records and actions

   days left

Can you prove that your models and AI are governed?

MINERVA Studio: We make you OSFI E‑23 compliant.

Our partners and risk management experts will close the book.

Contact us
FilmMINERVA — E-23 readiness, walked (4 min)
app.minerva.studio › Map

01 · System of recordsEvery model, person, policy, vendor and decision on one record, each row chained to the one before.

02 · InventoryEvery model in E‑23's own fields: owner, developer, reviewer, approver, rating and next review.

03 · AssessmentEach model is rated on E‑23's factors. The rating, a person's judgment, sets how hard it is checked.

04 · ValidationThe plan follows the rating. Your notebook runs the suites, each result lands on the record, and a failure opens a finding.

05 · System of actionsDoors that refuse: the same hands, owed evidence or an open high finding keep a model out. The software proposes; a person decides.

06 · Evidence packetOne folder of every record, receipt and checkpoint. Your examiner checks it offline, with Node.js alone.

07 · Audit portal / trailEvery row says who and when, witnessed by outside time-stamp authorities. Examiners read it with time-boxed, read-only access.

08 · Enterprise supportHosted in Canada, a dedicated instance or your own servers; single sign-on through your provider, and an open API to the same record.

09 · Rule packsRule packs are data: OSFI E‑23, SR 26‑2, PRA SS1/23, NIST AI RMF, the EU AI Act and more. A pack's fields, doors and gates apply to the record.

WHERE IT COMES FROMA spreadsheet importinventory.xlsxA registry pullMLflow · Archer · OpenPagesA person's editevery change attributedTHE RECORDEACH ROW CHAINEDMODELIFRS 9 ECL overlaydrawn by Yusuf Bellob81e04c2⑆69ad53e5PERSONLena Fischerline 2 · model reviewer5d3a91f0⑆b81e04c2POLICYModel risk policyversion 3c4dbc2c0⑆5d3a91f0VENDORFeaturespace Ltdassessed this year7e9aa8c5⑆c4dbc2c0DECISIONApproved for useRajiv Menon · senior management4a0f5797⑆7e9aa8c5ANYONE CAN RECOMPUTEsha256(the row, canonical)= 4a0f5797…and each row names the one beforeIMPORTinventory.xlsx13 rows · 10 E‑23 columnsINVENTORYMINERVA BANK · DEMOMODELDEVELOPERREVIEWERMarket risk VaRMNB-VAR-009Priya SharmaLena FischerIFRS 9 ECL overlayMNB-ECL-005Yusuf BelloYusuf BelloCustomer assistantMNB-GEN-013 · AIMicrosoftMiguel SantosAML monitoringMNB-AML-011NICE ActimizeMiguel SantosCard fraudMNB-FRD-012FeaturespaceLena FischerSAME HANDS5 OF 13 MODELS · E‑23 FIELDSE‑23 FIELDSOwnerDeveloperReviewerApproverRatingNext reviewRATED BYHZHelen Zhaohead of model risk · line 2RATINGIFRS 9 ECL OVERLAYPotential financial impactHIGHComplexity, and level of autonomyMEDIUMBusiness use or purposeHIGHReliability of the data it takes inMEDIUMImpact on customersLOWRegulatory riskHIGHBAND · A JUDGMENT OVER THE FACTORSHighre-rate by 14 Oct 202710 FACTORS · E‑23 PRINCIPLE 2.2WHAT HIGH ASKSVALIDATIONevery 12 monthsMONITORINGevery 31 daysRE-RATINGevery 12 monthsAPPROVALsenior managementTEST SUITESnineYOUR NOTEBOOKMINERVA-MRMrun = mn.run(model["id"], suite="stability")run.add(suites.stability(X_train, X_recent))run.record(open_findings=True)VALIDATION PLANHIGH · NINE SUITESPerformancePASSStabilityMIXED · FINDINGData qualityPASSCalibrationPASSBacktestingPASSSensitivityOWEDBenchmarkOWEDSegmentsOWEDFairnessOWEDLFLena Fischer signs off, as the reviewerthe developer is refused by nameRUN IN YOUR NOTEBOOK · RECORDED HEREFINDING · OPENED BY THE RUNStability: 4 of 16 failedHIGH · OPENblocks approval until it is closeda later pass is stamped as a retestTHE SOFTWARE PROPOSESBABuilt-in analystmay propose; may not decide or signREVIEW & APPROVALIFRS 9 ECL OVERLAYApprove for useMNB-ECL-005 · HIGH · SENIOR MANAGEMENT DECIDESOwner and approver namedValidation evidence on fileLimitations and uses recordedSame hands: Yusuf Bellobuilt it and reviewed itIndependent reviewLena FischerREFUSED · PICK ANOTHER REVIEWEROPEN · SENIOR MANAGEMENT DECIDESBABuilt-in analyst proposed itAPPROVEAPPROVEAPPROVEDR. MENON · 14 OCT 2026THE SOFTWARE PROPOSES · A PERSON DECIDESA PERSON DECIDESRMRajiv Menonsenior management · not the proposerTHE EVIDENCE DESKEXPORT THE PACKETthe export is itself a rowTHE PACKETEVIDENCE-PACKET.ZIPREADME.mdledger/ledger.jsonregisters/dossiers/receipts/ · 4checkpoints/verify.mjs$ node verify.mjsok: 3060 events, head 4a0f5797…ok: 127 files match SHA256SUMSok: 4 anchor receipts name a ledger rowEVERY RECORD, RECEIPT AND CHECKPOINTTHE EXAMINER'S MACHINENode.js and a shellnone of our softwarechecked offline, without usEXAMINER ACCESSEXOSFI examinerreads every row; proposes nothingREAD-ONLY · UNTIL 31 MAR 2027THE TRAILNEWEST FIRST3,060RMRajiv Menonapproved for use4a0f5797⑆7e9aa8c53,059BABuilt-in analystproposed: approve for use7e9aa8c5⑆c4dbc2c03,058HZHelen Zhaonamed Lena Fischer reviewerc4dbc2c0⑆69ad53e5WITNESSEDWITNESSEDWITNESSEDfreetsa.org · 2026-10-14 18:00:58ZITS OWN CLOCKCheckpoint: the day's head, signedED25519WHO · WHAT · WHEN · WITNESSEDTIME-STAMP AUTHORITIESfreetsa.orgtimestamp.sectigo.comWHERE IT RUNSHosted · AWS Canada (Central)Montréal · the records stay in CanadaA dedicated instanceone institution, the same regionYour own serverson-prem, your registry exportsOPEN APIV1GET /api/v1/nodes/{id}/runs200 OK{ "suite": "stability", "status": "mixed", "counts": { "pass": 12, "fail": 4, … }, "by_name": "Lena Fischer", "hash": "de7671b4…"}THE SAME RECORD, BEHIND THE SAME GATESSIGN-INSingle sign-onOIDC · SAML · SCIMthrough your identity providera second admin approves sign-in changesWHAT A PACK CARRIESFIELDSwhat the record must holdDOORSwhen a model may moveGATESwhat an overlay addsRULE PACKSSEVENOSFI E‑23model risk management · CanadaAI riskNIST AI RMF · ISO/IEC 42001SR 26‑2model risk management · USPRA SS1/23model risk management · UKEU AI Actthe high-risk tierOSFI B‑10third-party riskInformation assetsthe asset registerA PACK IS DATA · THE ENGINE IS ONEAPPLIED TO THE RECORD13 modelsgaps printedthe gap report, by the pack's own words

AI, security and GRC

Trusted AIAccuracyAccountabilityControlGatewayPrompt defenceAccess controlGuardrailsValidationModel testingIndependent reviewMonitoringAuditControl monitoringAccess reviewsAttestationVendorsHiddenLayerNoma SecurityStraikerVendorsValidMindYieldsSASVendorsVantaDrataSecureframeAIImplementationOpenAIAnthropicGoogle DeepMindFrontier modelsCopilotsAgentsSecurityProtectionPalo Alto NetworksFortinetCiscoThreat detectionZero trustIdentityGRCInventoryMINERVAMINERVA providesCompliance servicesGRC platformTo make you E‑23 compliantMINERVA SOFTWARE INCAI assurance09 Oct 2026
Model inventoryEvidence packetsAudit readinessforNIST AI RMFOSFI E‑23SR 26‑2
AI Implementation
OpenAI
Anthropic
Google DeepMind
Security Protection
Palo Alto Networks
Fortinet
Cisco
GRC Inventory
MINERVA
AISecurityGatewayValidationAuditTrusted AIGRCMINERVA
  1. AI Implementation

    • OpenAI
    • Anthropic
    • Google DeepMind

    Frontier modelsCopilotsAgents

  2. Security Protection

    • Palo Alto Networks
    • Fortinet
    • Cisco

    Threat detectionZero trustIdentity

  3. Gateway

    Prompt defenceAccess controlGuardrails

    Vendors

    • HiddenLayer
    • Noma Security
    • Straiker
  4. Validation

    Model testingIndependent reviewMonitoring

    Vendors

    • ValidMind
    • Yields
    • SAS
  5. Audit

    Control monitoringAccess reviewsAttestation

    Vendors

    • Vanta
    • Drata
    • Secureframe
  6. Trusted AI

    AccuracyAccountabilityControl

  7. GRC Inventory

    MINERVA

    Model inventoryEvidence packetsAudit readiness

    forNIST AI RMFOSFI E‑23SR 26‑2

    MINERVA provides

    Compliance servicesGRC platform

    To make you E‑23 compliant

Two plans.

One goal: Govern, Map, Measure and Manage.

What we deliver.

01 / 06
app.minerva.studio › Home
Home on the demo bank: the seven steps of the programme as cards with their live counts; the queue of what waits on the owner, a breach, a blocked door, the same hands, an owed line of defence, a supplier; and the record's figures for the day with the doors to the evidence and the trail.

The seven steps

E‑23's seven steps are the navigation. Every count comes from the record, and the queue says what waits on you.

app.minerva.studio › Inventory
The inventory: thirteen models in rows with their rating, where each stands, the model owner, reviewer and approver, the next review date and the monitoring status, with the saved views, the column picker and the gap report above the table.

The inventory in E‑23's own fields

Every model with its owner, rating, reviewer, approver and review date, and the register as it stood on any date.

app.minerva.studio › Review & approval
A shut decision card on the review page: the approve door for the IFRS 9 ECL macro overlay with each reason it is shut, the approver and the approved uses not yet recorded, validation evidence owed, the same person named as developer and reviewer, the fix beside each reason, and Reject with a reason as the only button.

Doors that refuse

A model is not approved while the same hands built and reviewed it, evidence is owed or a high finding stands open. The card says what would open the door.

app.minerva.studio › Review & approval
The review page with the sweep's proposal at its head: the built-in analyst asks to send the Card behavioural score back for review, the watched figure and the line it crossed printed in the note, and the owner's one door, Reject with a reason.

A sweep that cannot decide

Monitoring proposes sending a breached model back for review. A person decides, and the decision is a row on the record.

app.minerva.studio › Evidence › The trail
The trail: the record's rows newest first, each with its sequence number, its time, the hand, what changed and the seam of its hash joined to the one before; a witness column prints the time-stamp authority's own clock for every row a receipt covers; the head strip counts the rows, the receipts on file, the chain's verdict and the checkpoints.

The witnessed trail

Every row is chained to the one before it and time-stamped by an outside authority, printed in that authority's own clock.

app.minerva.studio › Evidence › The examiner
The evidence packet preview: the files it holds down the left, the README, the ledger, the receipts, the registers, the dossiers, the binders and verify.mjs; the README open in the middle saying what the packet is and what is inside; Download at the foot.

A packet your examiner verifies offline

Every record, receipt and checkpoint in one file, checked on their own machine with one command, without us.

Contact us for exclusive deals.

FormContact
Which way

A person replies within one working day