Compliance
Turn AI governance into evidence you can hand over
MERIDVAR helps organisations operationalise governance controls and generate evidence relevant to the frameworks they answer to. Compliance itself remains your determination. MERIDVAR gives you the record to support it.
- Mapped: EU AI Act, NIST AI RMF and ISO/IEC 42001
- Control status computed from the running appliance
- MERIDVAR issues no certification
ISO/IEC 42001, Clause 8: operational controls Partial
Three of four observations are satisfied.
A control that the product cannot observe is reported as uncomputed, with the reason.
Computed status
A control status that reads the running system
The status of each mapped control is derived from named observations of the live appliance. Each observation shows what was measured and whether it satisfied the control. Switch off a control, and the status changes.
- AI systemsThe inventory, with each system’s governance state
- ControlsThe policy enforced at the gateway
- EvidenceObservations computed from the appliance, and the evidence log
- FrameworkA mapped control and its computed status
- AuditA package for each AI system and each vendor
By territory
What is mapped, and what is supporting evidence
There are two categories. Mapped means that the product ships a control mapping for the framework. Evidence means that records in MERIDVAR are relevant to the framework, with no mapping in the product.
| Framework | Status | What MERIDVAR contributes |
|---|---|---|
| Europe | ||
| EU AI Act | Mapped | A control mapping with computed status. The risk rules read the organisation’s own EU AI Act classification of each system. |
| GDPR | Evidence | Prompt DLP on personal identifiers, a data residency policy and a privacy review that records the organisation’s DPIA position. |
| DORA | Evidence | Vendor due diligence, vendor approval and the register of AI systems that depend on each provider. |
| NIS2 | Evidence | Access roles, the audit trail and security review records. |
| United Kingdom | ||
| UK GDPR and the Data Protection Act 2018 | Evidence | The same privacy review, DLP and residency evidence as for the GDPR. |
| Regulator-led AI principles | Evidence | Inventory, ownership, risk classification and approval history for each AI system. |
| United States | ||
| NIST AI RMF | Mapped | Govern, Map, Measure and Manage, each with observations computed from the running appliance. |
| State AI and privacy laws | Evidence | Records of systems whose outputs support decisions about individuals, and of human review. |
| International standards | ||
| ISO/IEC 42001 | Mapped | Clauses 5 to 9 and the supplier controls of Annex A, with computed status. |
| ISO/IEC 27001 and SOC 2 | Evidence | Access control and logging evidence for your own programme. |
| Latin America | ||
| LGPD (Brazil) | Evidence | Prompt DLP on personal identifiers, a residency policy and privacy review records. |
| Asia Pacific and the Middle East | ||
| National AI governance frameworks and data protection laws | Evidence | The governance record, the residency policy and the evidence log apply regardless of framework. No regional framework is mapped in the product today. |
Framework summaries are drawn from public sources and are not legal advice. Your own counsel should confirm what applies to you.
EU AI Act timeline
Scoped to the obligations that are actually on the calendar
The Digital Omnibus on AI moved the high-risk deadlines. The transparency and general-purpose model obligations did not move. MERIDVAR’s mapping reflects the amended timeline.
- 2 February 2025Prohibited practicesApplies
- 2 August 2025General-purpose AI model obligationsApplies
- 2 August 2026Transparency obligations under Article 50Applies
- 2 December 2027High-risk systems listed in Annex IIIAhead
- 2 August 2028High-risk systems embedded in products under Annex IAhead
Support reply assistant
One downloadable package for each AI system and each vendor.
The package states what it does not prove.
The audit package
Evidence that is explicit about its own scope
What each package holds
- The subject’s governance state
- Its classifications, reviews and approvals
- Its assessments, with the exact questionnaire versions answered
- Every evidence record about it, as stored, with its hash, the previous hash and its signature
- The public signing keys
What it states about its scope
- Each record can be checked against its hash and signature
- Signatures are made with a key held on your appliance
- Statements are recorded as stated, with who made them and when
The product views on this page are illustrative, with invented example data.
Guides on this topic
See MERIDVAR refuse a request on your own network
A working session with the founder, on a host you control.
What happens next
- You send the formYour request goes straight to the founder.
- We reply by emailWe agree a time and what you want to see.
- We run a working sessionWe install the appliance with you, route a test request through it and read the evidence it leaves.