Inovai Platformrunning Testing, monitoring and evidence in one placeIt attacks your AI after every change and documents every finding. How the platform tests

Inovai / Who it’s for

The auditor will ask about your AI.

An evidence pack: what you run, how you tested it and what you fixed.

Inovai / monitoring / chatbot-supportruns after every change

Blocked attacks by run

prompt fix, 3 → 0 findingsnew model from the vendor, P1 regressionretest, 0 findings

Evidence for run 9

Inputattack CZ-114
Modelv2.3, prompt #41
Resultblocked 40/40
RegulationDecree 409, AI Act Art. 50
Confirmed bytester, 12:40
Problem

AI is missing from the asset register and there are no records of tests.

What we’ll do

Inventory, tests with records and mapping to regulations.

Result

A pack for the auditor and a quarterly report.

What usually happens without preparation

Three questions from an ISO auditor, a NÚKIB (the Czech cyber security authority) inspection or ČNB supervision that have no answer without preparation.

AI is missing from the asset registerNobody recorded the chatbot and Copilot as technical assets. The auditor asks for the risk assessment and there is nothing to point to.
There was a test, but no evidenceSomeone tried the chatbot, but nothing was written down: when, who, what was found. For an inspection, it is as if no test took place.
Vendor without an assessmentDecrees No. 409 and 410 require you to assess vendors and their products. For the chatbot vendor, the folder holds only an invoice.

How we proceed

From the register to the quarterly report.

Website chatbottest firstCopilotauditInvoice assistantok
Step 1Inventory and registerAI systems and vendors in the asset register, with owner, data and purpose.
Finding confirmed by a humanReproduction attached
Step 2Test with recordsDate, responsible people, model version, every finding with reproduction steps. A tester confirms serious findings.Verified by a human
Report, run 9P1Prompt leakP2AI labellingokInjection in PDF
Step 3Mapping in the reportFindings mapped to Decrees No. 409 and 410, DORA, the AI Act and ISO/IEC 42001, in a report for the auditor.
new model: P1 regression, 0 after the fix
Step 4Monitoring and quarterly reportA new run after every change. A quarterly summary for management and the auditor.

A pack for the auditor: register, test logs with reproduction steps, records of the retest and of briefing management.

FAQ

Can you promise the inspection will go well?

No. Compliance is decided by the auditor or the supervisory authority. We provide evidence that answers their questions and help remove the grounds for objections that can be removed.

Is the material also suitable for the ČNB under DORA?

Yes. DORA requires ICT resilience testing and third-party risk management. A report with reproduction steps and a vendor register are the supporting material; the assessment is up to the supervisor.

The audit is close. Where to start?

With a register and a test of the systems the auditor cares about most: those that talk to clients or have access to sensitive data. We add the rest according to the audit plan.