A spreadsheet holds promises. The matrix holds observations.
Start where your team already is.
Import your matrix
Upload the Excel register your team already maintains. Re-importing updates it in place.
Start from the library
46 controls across 14 domains — agent permissions, review discipline, supply chain, skills, MCP, secrets, logging and more — each mapped to nine standards.
Clone and cut
Copy a framework per business unit and remove what doesn't apply.
Who answers, and what the answer is.
The band says who answers a control. Evidenced: the platform reads it from the repositories, every sync. Attested: a named person signs it, with a note and a due date. Automating next: attested today, evaluator on the roadmap. Via integration: lives in your IdP, MDM, DLP or vault.
The status says what the answer is today: evidenced, in progress, flagged, attested, not started or lapsed. A band of seventeen Evidenced can hold reds — that is the honesty, not a flaw.
One row, end to end — honestly.
SCM-02 as it sits in your spreadsheet, as the estate evidences it today, and as it lands in the sealed report.
Your row, exactly as it sits in the spreadsheet your team maintains.
12 of 14 repositories have AI-authored merges without an approving review; one approval came 2 minutes after opening with no comments on 26,043 lines.
An observed fact across the live estate, not a claim.
AI-Code Risk BriefingSealed into the report — verifiable on any date.
Evidence outranks attestation.
Four rules the matrix enforces so the status column stays trustworthy on an ordinary Tuesday.
A detected violation outranks anything a human typed — a flagged control has no Attest button.
A hand-typed "evidenced" is rejected by the server.
An attestation carries a due date and lapses on its own when the cadence runs out.
Bound once, true everywhere: the same evaluator fires in every framework that holds the control.
Set the date and the matrix shows itself as it stood.
A week ago, the last seal, the day you imported.
Six controls for regulated model owners.
Three the platform evidences from the repositories. Three your experts attest with cadence.
Read from the repositories
- Human review on AI-authored model changes
- No bypass mode in model repositories
- No hallucinated dependencies
Signed by your experts
- Independent validation within 12 months
- Bias and fairness review
- A current model card
Validation and bias review are the experts’ work; the platform records their outcome, who recorded it, when, and with what note. Nothing here is a legal determination.
Record it once — show it everywhere it counts.
Each control carries a crosswalk mapping so one recorded decision shows up across the standards your auditor reads. Two frameworks are evaluated built-in; the rest are crosswalks — “maps to,” never “certifies.”
- Evaluated built-in
EU AI Act
- Evaluated built-in
NIST AI RMF
- Maps (crosswalk)
ISO/IEC 42001
- Maps (crosswalk)
ISO/IEC 27001:2022 Annex A
- Maps (crosswalk)
NIST SP 800-53 r5
- Maps (crosswalk)
NIST SP 800-207
- Maps (crosswalk)
NIST SSDF 800-218
- Maps (crosswalk)
OWASP LLM Top 10 (2025)
- Maps (crosswalk)
OWASP Agentic AI
- Maps (crosswalk)
CIS Controls v8.1
The questions teams ask.
What is a custom control matrix?
It's the set of controls your organization is actually measured against — often a spreadsheet your security, risk, or audit team already maintains. Provenance lets you import that matrix as-is and treats each of your controls as a first-class governance object it can evidence against your estate.
How do I import my controls?
Upload your control register as an Excel workbook. Provenance parses each control — its id, name, description, and any framework mappings you've already recorded — and stores it as your tenant's own framework. Re-importing updates in place, so your matrix stays the source of truth as it evolves.
Does Provenance use an LLM to decide whether a control passes?
No. Each control is bound to a deterministic evaluator that reads observed facts from your estate — authorship, review records, dependency manifests, agent-config files — and returns a status (evidenced, in progress or flagged). This is 'evidence then report,' the opposite of a 'classify then derive' approach that asks a model to judge compliance. Deterministic bindings mean the same estate produces the same status every time.
Can I just mark a control as 'evidenced' myself?
Not silently — that's the honesty gate. A hand-typed 'evidenced' status that isn't backed by observed evidence is rejected by the server. Where a control genuinely needs human sign-off, that attestation is recorded as an explicit, dated human decision with a note — evidence of the sign-off, not a box someone quietly ticked.
Do you block a merge when a control is red?
No — by design. Your branch protection and tooling stay the gate. Provenance records that the control failed, names the repository and the reason, and keeps the decision on the record. A failed control can't be signed off by hand: evidence outranks attestation.
Which frameworks does it map to — and which does it evaluate?
Provenance evaluates two frameworks built in — the EU AI Act and NIST AI RMF — meaning it derives their status from your estate directly. For the other standards (ISO/IEC 42001, ISO/IEC 27001:2022 Annex A, NIST SP 800-53 r5, NIST SP 800-207, NIST SSDF 800-218, OWASP LLM Top 10 (2025), OWASP Agentic AI, CIS Controls v8.1), each control carries a crosswalk mapping so one recorded decision shows where it counts across the standards your auditor reads. The distinction is deliberate and honest: 'evaluated' for the two packs, 'maps to' for the crosswalk — never 'certifies.'
Who maintains the controls and mappings?
We maintain the library and its mappings and ship updates; every framework we ship is included. Your imported controls stay yours; mappings on them are labelled as crosswalks.
Can it push to our GRC platform?
Roadmap. Today: the sealed report, audit exports, and a read-only API and MCP server your tooling can pull from.
Related from Provenance.
See your evidence this afternoon.
Connect your first repo in minutes — read-only, no credit card, no sales call. Your Provenance Score, your blind spots, and your first board-ready briefing, from your own estate.