Regulation packs¶
Before you rely on a regulation pack, you want to know exactly what it does for you and what it leaves to you. This page lists the built-in packs, what each kind sets, and for the regulations Vidai maps control by control, every control with what Vidai covers. Nothing is hidden: a control Vidai doesn't cover is listed as Your organisation's process, never left out. Vidai never says you're compliant; it shows evidence.
Find them in Policies › Regulations › Pack library. How following a regulation works, and the retention each one sets, is in Regulations, mapped.
Kinds of pack¶
| Kind | What it sets |
|---|---|
| Regulation | How long records are kept at least (prompt and reply text, call records, tamper-evident records), whether a ceiling is allowed (a law that limits how long personal data is kept), an archive, the client-communication period, and the content packs and recipes that serve it |
| Evidence for … | A framework your organisation is audited against. An evidence pack asked for one maps Vidai's records to each of its controls Enterprise. Evidence for your audit, never a statement that a control is met |
| Label only | Names policies so you can find them; sets nothing |
What Enterprise includes depends on the features your licence includes.
The built-in packs¶
The Pack library groups them by where they apply:
| Group | Packs |
|---|---|
| EU | GDPR, EU AI Act, DORA |
| UK | UK GDPR, UK FCA SYSC 9 and MiFID II |
| US | CCPA/CPRA (California), HIPAA, SOX, SEC 17a-4 and FINRA 4511, NIST AI RMF and Generative AI Profile |
| India | India DPDP Act 2023 |
| International | PCI DSS v4.0.1, ISO/IEC 42001, ISO/IEC 27001, SOC 2 |
| GCC | UAE PDPL; UAE health data law (Federal Law No. 2 of 2019); DIFC Data Protection Law; DIFC Regulation 10 (AI systems); ADGM Data Protection Regulations 2021; Qatar PDPPL; QFC Data Protection Regulations 2021; Qatar Central Bank AI Guideline; Saudi PDPL; Bahrain PDPL; Oman PDPL; Kuwait CITRA Data Privacy Protection Regulation; Saudi NCA Essential Cybersecurity Controls; SAMA Cyber Security Framework; UAE Central Bank (CBUAE) rules |
| Your own | Internal, Other |
Every pack except DORA, NIST AI RMF, Internal and Other carries a retention preset, so following it sets the retention it asks for. By what they do:
| Kind | Packs |
|---|---|
| Mapped control by control (below) | GDPR, the EU AI Act, ISO/IEC 42001, HIPAA, PCI DSS |
| Retention and evidence, no control mapping yet (No guidance yet) | UK GDPR, CCPA, India's DPDP Act, ISO/IEC 27001, SOC 2, SOX, FCA and MiFID II, SEC 17a-4 |
| Evidence for a framework | SOC 2, ISO/IEC 27001, ISO/IEC 42001, SOX, NIST AI RMF |
| Retention and personal-data guardrails for the GCC | Every pack in the GCC group above |
| Label only | DORA, Internal, Other |
A pack whose values still need confirming against a law's implementing rules lists them on its page under what needs a legal check. A release can bring a new version of a built-in pack; your copy of it never changes by itself.
What a pack's page shows¶
| Section | What it holds |
|---|---|
| What it sets | Retention minimums, whether a ceiling is allowed, an archive, the client-communication period, its note, and its content packs and recipes by name. "None" where it sets nothing |
| Our records for each control | For a framework: which of Vidai's records serve each control |
| Your organisation's own process | What it asks that the Control room doesn't do for you |
| Sources | The official text, or guidance about it |
| History | Each version, newest first: its date, what changed and why |
Marks on a pack¶
| Mark | Meaning |
|---|---|
| AI-specific | A law written for AI systems |
| Sector | A rule for one sector, such as banking |
| Changes pending | The law has implementing rules or amendments still to come |
| Version n | The pack's version; it rises when a release changes it |
| Draft, Active | Your own packs: only active ones are offered on Retention, in named policies and in recipes |
| Your copy, Your own, Imported | Where one of your packs came from |
| Beta | Which controls a setting covers is our reading, not legal advice, and is still being checked; the official text decides |
| Mapping checked | The mapping has been checked against the official text |
| No guidance yet | Its controls aren't mapped; its retention applies |
Control by control¶
For each mapped regulation, every control, what Vidai covers, and what stays yours. On Policies › Regulations, each control also shows its state now (Enforced, Observed only, Partly, Not checked, Nothing in place), from what's in force; see Statuses.
- Evidence: Vidai produces evidence for it.
- Part of it: Vidai produces evidence for some of it; the rest is yours.
- Your organisation's process: the product doesn't cover it.
GDPR (Regulation (EU) 2016/679)¶
Articles where the gateway's controls and records help when prompts may carry personal data. Lawful basis, notices, people's rights and contracts are your organisation's process, and are listed so you can see what isn't covered. Marked Beta. The official text.
| Control | Title | What Vidai covers | How it helps, and what stays yours |
|---|---|---|---|
| Art. 5(1)(c) | Data minimisation | Part of it | Personal data found in prompts can be blocked, masked or pseudonymised before it reaches a model. Deciding what's necessary is yours. |
| Art. 5(1)(f) | Integrity and confidentiality | Part of it | Only named keys reach models, each limited to the models its access allows, and region rules keep calls where you choose. |
| Art. 5(2) | Accountability | Part of it | The audit log and Request logs are records you can show. Demonstrating the rest is your process. |
| Art. 6 | Lawfulness of processing | Your organisation's process | Your organisation's process, not the product. |
| Art. 25 | Data protection by design and by default | Part of it | Guardrails act on personal data before a call leaves, and approved destinations limit which models any call may reach. |
| Art. 28 | Processor | Part of it | Approved destinations keep calls to the models (and so the providers) you've approved. The contracts themselves are yours. |
| Art. 30 | Records of processing activities | Part of it | Every call is recorded with who made it, which model and where it ran. The register itself is yours. |
| Art. 32 | Security of processing | Part of it | Named keys, model access, Stop AI traffic, guardrails and a tamper-evident audit log are technical measures. The organisational ones are yours. |
| Art. 33 | Notification of a personal data breach to the supervisory authority | Your organisation's process | Your organisation's process. Request logs and audit log can help you find out what happened. |
| Art. 35 | Data protection impact assessment | Part of it | Risk levels on agents and applications record your assessment and when it's due for review. The assessment is yours. |
| Art. 44 | General principle for transfers | Part of it | Region rules and compliance routes keep calls on models placed where you choose; approved destinations limit where any call may go. |
| Art. 45 | Transfers on the basis of an adequacy decision | Part of it | A region rule can keep calls to areas you consider adequate. Which countries are adequate is the Commission's list. |
| Art. 46 | Transfers subject to appropriate safeguards | Part of it | Approved destinations name the models calls may reach, and why. The clauses themselves are yours. |
| Art. 47 | Binding corporate rules | Your organisation's process | Your organisation's process, not the product. |
| Art. 48 | Transfers or disclosures not authorised by Union law | Your organisation's process | Your organisation's process, not the product. |
| Art. 49 | Derogations for specific situations | Your organisation's process | Your organisation's process, not the product. |
EU AI Act (Regulation (EU) 2024/1689)¶
Articles where the gateway's records and controls help a deployer of AI systems. Most high-risk duties fall on providers; obligations that are your organisation's process are listed as not covered. Marked Beta. The official text.
| Control | Title | What Vidai covers | How it helps, and what stays yours |
|---|---|---|---|
| Art. 4 | AI literacy | Your organisation's process | Your organisation's process, not the product. |
| Art. 5 | Prohibited AI practices | Part of it | A prohibited use isn't a risk level: it's kept out with model access. Deciding what's prohibited is yours. |
| Art. 9 | Risk management system | Part of it | Risk levels record your assessment of each agent and application; the system is your process. |
| Art. 10 | Data and data governance | Your organisation's process | Your organisation's (or the model provider's) process, not the product. |
| Art. 12 | Record-keeping | Evidence | Every call is logged automatically: who, when, which model, what was refused and why. |
| Art. 14 | Human oversight | Part of it | Stop, restrict and review controls: Stop AI traffic, model access, suspending keys and agents. Oversight itself is your process. |
| Art. 19 | Automatically generated logs | Part of it | Request logs are the record; how long they're kept is your setting. |
| Art. 26(5) | Monitoring the operation of high-risk systems | Part of it | Request logs and findings show how each agent behaves; informing the provider is yours. |
| Art. 26(6) | Deployers keep the logs | Evidence | Request logs and audit log are kept by your installation; check the retention setting. |
| Art. 27 | Fundamental rights impact assessment | Your organisation's process | Your organisation's process. A risk level can record the assessment's reference. |
| Art. 50 | Transparency obligations for providers and deployers of certain AI systems | Your organisation's process | Your organisation's process: labelling content and campaigns is yours. |
ISO/IEC 42001:2023 (AI management system)¶
Annex A controls. The gateway produces operational evidence for a few of them; most are your AI management system's own processes, shown here so you can see what isn't covered. Evidence per control, never a statement of conformity. Marked Mapping checked. The official text.
| Control | Title | What Vidai covers | How it helps, and what stays yours |
|---|---|---|---|
| A.2.2 | AI policy | Your organisation's process | Your organisation's process, not the product. |
| A.2.3 | Alignment with other organizational policies | Your organisation's process | Your organisation's process, not the product. |
| A.2.4 | Review of the AI policy | Your organisation's process | Your organisation's process, not the product. |
| A.3.2 | AI roles and responsibilities | Your organisation's process | Your organisation's process, not the product. |
| A.3.3 | Reporting of concerns | Your organisation's process | Your organisation's process, not the product. |
| A.4.2 | Resource documentation | Your organisation's process | Your organisation's process, not the product. |
| A.4.3 | Data resources | Part of it | Region rules and compliance routes show where data in calls may be processed. |
| A.4.4 | Tooling resources | Your organisation's process | Your organisation's process, not the product. |
| A.4.5 | System and computing resources | Part of it | Approved destinations list the models any call may reach. |
| A.4.6 | Human resources | Your organisation's process | Your organisation's process, not the product. |
| A.5.2 | AI system impact assessment process | Your organisation's process | Your organisation's process, not the product. |
| A.5.3 | Documentation of AI system impact assessments | Your organisation's process | Your organisation's process, not the product. |
| A.5.4 | Assessing AI system impact on individuals or groups | Your organisation's process | Your organisation's process, not the product. |
| A.5.5 | Assessing societal impacts of AI systems | Your organisation's process | Your organisation's process, not the product. |
| A.6.1.2 | Objectives for responsible development of AI system | Your organisation's process | Your organisation's process, not the product. |
| A.6.1.3 | Processes for responsible AI system design and development | Your organisation's process | Your organisation's process, not the product. |
| A.6.2.2 | AI system requirements and specification | Your organisation's process | Your organisation's process, not the product. |
| A.6.2.3 | Documentation of AI system design and development | Your organisation's process | Your organisation's process, not the product. |
| A.6.2.4 | AI system verification and validation | Your organisation's process | Your organisation's process, not the product. |
| A.6.2.5 | AI system deployment | Part of it | Region rules and compliance routes record where calls are deployed. |
| A.6.2.6 | AI system operation and monitoring | Evidence | Every call is recorded: who, when, which model, what was refused and why. |
| A.6.2.7 | AI system technical documentation | Your organisation's process | Your organisation's process, not the product. |
| A.6.2.8 | AI system recording of event logs | Evidence | Request logs and the tamper-evident audit log. |
| A.7.2 | Data for development and enhancement of AI systems | Your organisation's process | Your organisation's process, not the product. |
| A.7.3 | Acquisition of data | Your organisation's process | Your organisation's process, not the product. |
| A.7.4 | Quality of data for AI systems | Your organisation's process | Your organisation's process, not the product. |
| A.7.5 | Data provenance | Part of it | Region rules and compliance routes show where data went. |
| A.7.6 | Data preparation | Your organisation's process | Your organisation's process, not the product. |
| A.8.2 | System documentation and information for users | Your organisation's process | Your organisation's process, not the product. |
| A.8.3 | External reporting | Your organisation's process | Your organisation's process, not the product. |
| A.8.4 | Communication of incidents | Evidence | Request logs and audit log are the record of what happened. |
| A.8.5 | Information for interested parties | Your organisation's process | Your organisation's process, not the product. |
| A.9.2 | Processes for responsible use of AI systems | Your organisation's process | Your organisation's process, not the product. |
| A.9.3 | Objectives for responsible use of AI system | Your organisation's process | Your organisation's process, not the product. |
| A.9.4 | Intended use of the AI system | Evidence | Model access limits each key to the models it's meant to use. |
| A.10.2 | Allocating responsibilities | Your organisation's process | Your organisation's process, not the product. |
| A.10.3 | Suppliers | Part of it | Approved destinations name the models (and so the suppliers) you've approved. |
| A.10.4 | Customers | Your organisation's process | Your organisation's process, not the product. |
HIPAA Security Rule (45 CFR §164.312)¶
Technical safeguards the gateway helps with for calls that may carry health data. Administrative and physical safeguards are your organisation's. Marked Beta. The official text.
| Control | Title | What Vidai covers | How it helps, and what stays yours |
|---|---|---|---|
| §164.312(a) | Access control | Evidence | Named keys, each limited to the models its access allows. |
| §164.312(b) | Audit controls | Evidence | Request logs and the tamper-evident audit log. |
| §164.312(c) | Integrity | Part of it | Health identifiers found in prompts are acted on before a call leaves. |
| §164.312(d) | Person or entity authentication | Your organisation's process | Your identity provider's job. |
| §164.312(e) | Transmission security | Part of it | Region rules keep calls where you choose; the HIPAA pack acts on health identifiers. |
PCI DSS v4.0¶
Requirements the gateway helps with where card data might reach an AI model. Your cardholder data environment is outside its scope. Marked Beta. The official text.
| Control | Title | What Vidai covers | How it helps, and what stays yours |
|---|---|---|---|
| Req. 3.3 | Sensitive authentication data is not retained after authorisation | Part of it | Card data in prompts is found and blocked or masked before a call leaves. |
| Req. 3.4 | Access to displays of full PAN is restricted | Part of it | Card numbers in prompts are masked or blocked. |
| Req. 7 | Restrict access by business need to know | Evidence | Model access limits each key to what its holder needs. |
| Req. 8 | Identify users and authenticate access | Part of it | Every call is made with a named key; sign-in is your identity provider's. |
| Req. 10 | Log and monitor all access | Evidence | Request logs and the tamper-evident audit log. |
| Req. 12 | Information security policy | Your organisation's process | Your organisation's process, not the product. |
Related¶
- Regulations, mapped: what following a regulation does, and the retention each sets
- Follow a regulation and take its recommended policies
- Copy, change or import a regulation pack
- Evidence and the auditor report