Regulations · Payment Card Industry Data Security Standard, version 4.0

PCI DSS v4.0, on every AI call.

Card numbers found with check digits and kept out of every model, unused keys suspended, and access reviewed.

In brief

Vidai applies PCI DSS v4.0 to every AI call your organisation makes, inside your own network. Card numbers found with check digits and kept out of models; unused keys suspended automatically; access reviews. Vidai gives you the evidence; your auditor makes the call on compliance.

What Vidai enforces or records

Following PCI DSS v4.0.

Mapped control by control. The mapping is in beta: our reading of the text, which decides.
  • Card numbers found with check digits and kept out of models
  • Unused keys suspended automatically
  • Access reviews
  • Provider attestations on record

Retention it sets

Call records and tamper-evident records kept for at least a year. PCI DSS also expects an archive that can't be altered.

Starting values your compliance team confirms. A period is never shortened behind your back.

Coverage

Each control, shown as it really is.

Following a regulation sets its retention and proposes its policies, in observe mode first. On Enterprise, each control shows its coverage, gaps first, with the calls that prove it.
EnforcedEvery key in scope has it in force.
Observed onlyIt's watched and logged, but some keys only observe.
PartlySome keys have it and some don't, with how many.
Nothing in placeNothing in scope provides it yet.
Your organisation's processVidai doesn't cover it. Listed so you see what isn't covered: always last, never hidden.

Which controls a setting covers is our reading, not legal advice; the official text decides, and your auditor makes the call on compliance. Coverage counts AI calls sent through Vidai, not your other systems.

Vidai Control room · Regulations
One GDPR control, partly covered: the evidence it looks for, 30 days of findings and the policies behind it.
One GDPR control, partly covered: the evidence it looks for, 30 days of findings and the policies behind it.

Questions

Straight answers.

Does Vidai make us compliant with PCI DSS v4.0?
No tool can, and Vidai never claims it. Vidai applies PCI DSS v4.0 to every AI call and produces the evidence; your auditor or supervisor makes the call. A 20-minute demo shows it on infrastructure like yours, and Community edition is free to try.
What does Vidai enforce or record for PCI DSS v4.0?
Card numbers found with check digits and kept out of models. Unused keys suspended automatically. Access reviews. Provider attestations on record.
How long are records kept under PCI DSS v4.0?
Call records and tamper-evident records kept for at least a year. PCI DSS also expects an archive that can't be altered. These are starting values your compliance team confirms, and a period is never shortened behind your back.
Are PCI DSS v4.0's controls mapped in Vidai?
Mapped control by control. The mapping is in beta: our reading of the text, which decides.

How we start together

Start with one team, on your own AI traffic.

After a 20-minute demo, we agree a two-week pilot with you: one app or team, your traffic, your infrastructure.
  1. 01

    Pick one app or team

    Point it at the Control room. One configuration change; nothing else changes.

  2. 02

    Watch for two weeks

    Every call priced, checked and recorded. Rules start in observe mode.

  3. 03

    See the evidence

    What it cost, what it caught and what it would have stopped, from your own traffic.

Page updated