Questionnaire answers · Security · Article 15(1) · Article 15(5)
How to answer information security questions about AI in a supplier questionnaire
Written by Yobel TzegaiLast reviewed 14 October 2026Checked against Regulation (EU) 2024/1689 as amended by Regulation (EU) 2026/1744 (the Digital Omnibus on AI)
The short answer
Name the security programme the AI features sit inside, the measures that apply to them and how you test those measures, and show the evidence. The GDPR asks for measures appropriate to the risk (GDPR Article 32(1)), and a high-risk AI system must achieve an appropriate level of cybersecurity throughout its lifecycle (Article 15(1) of the AI Act). Complipath (complipath.io) keeps the record these answers rest on.
What they usually ask
- Q1“Does your information security policy cover the AI features?”
- Q2“Which certifications or audits cover the AI features?”
- Q3“Who is responsible for information security?”
- Q4“How do you assess AI-specific security risks?”
An example answer, part by part
An illustration for an invented product, not a real supplier's answer, to the question: Which certifications or audits cover the AI features?
- Direct answerYes, partly or no first
- Our ISO/IEC 27001 certificate covers the product, the AI features included.
- ControlWhat you actually do
- The AI features are in the certificate's scope statement and in the annual internal audit.
- ScopeWhich AI systems
- The whole product. The data science sandbox is outside the scope.
- EvidenceWhat you can show
- The certificate, its scope statement and the last surveillance audit report, dated June 2026.
- ExceptionsBe honest
- None.
Example. Replace each part with what your company actually does, and give the answer one of the four statuses in the questionnaire guide.
What counts as proof
- DOCThe security policy and the scope it names.
- DOCThe certificate or the audit report, with its scope.
- DOCFor a high-risk system, the cybersecurity measures in its technical documentation (point 2(h) of Annex IV).
Common mistakes
- ✗Answering for the company. Article 6 classifies systems, not companies.
- ✗"Yes" with no evidence. If you cannot attach it, the status is Partially implemented or Planned.
- ✗A policy title as the control. It says nothing about what happens to an output.
- ✗Mixing up the roles. Article 50(1) is a provider duty; Article 26 is the deployer's. Which one you are is set per system: see provider or deployer.
- ✗Not applicable with no reason. The reason is the classification.
- ✗Dropping the exception. The summary that leaves out "unless" is the one that is wrong.
What the law says
Article 15(1)a high-risk AI system is designed and developed to achieve an appropriate level of accuracy, robustness and cybersecurity and to perform consistently in those respects throughout its lifecycle.
Read Article 15 on EUR-Lex ↗ Article 15(5)- a high-risk system is resilient against attempts by unauthorised third parties to alter its use, outputs or performance by exploiting system vulnerabilities.
- The measures for AI-specific vulnerabilities include, where appropriate, measures to prevent, detect, respond to, resolve and control for data poisoning, model poisoning, adversarial examples or model evasion, confidentiality attacks and model flaws.
Read Article 15 on EUR-Lex ↗ GDPR Article 32(1): taking into account the state of the art, the costs, the nature, scope, context and purposes of processing and the risk, the controller and the processor implement appropriate technical and organisational measures, including as appropriate pseudonymisation and encryption, the ongoing confidentiality, integrity, availability and resilience of processing systems, the ability to restore availability and access after an incident, and a process for regularly testing the measures.
Point 2(h) of Annex IV: the technical documentation of a high-risk system describes the cybersecurity measures put in place.
- Article 15 is in Chapter III, Section 2, which applies from 2 December 2027 for systems that are high-risk under Article 6(2) and Annex III and from 2 August 2028 under Article 6(1) and Annex I (Article 113, third paragraph, point (c), as replaced by Regulation (EU) 2026/1744).
- The GDPR articles were read from its Official Journal text (OJ L 119, 4.5.2016) on 9 October 2026; the GDPR is not in the pinned corpus behind the rest of this site.
What Complipath does
- ✓Risk classification Answers go through rules in code, never a language model, so the same answers always give the same result. Rules decide. AI only drafts. A person confirms.
- ✓Evidence management Upload a file once. We read it and use it everywhere it helps: proof for requirements, text for the documentation, and a flag when it disagrees with an earlier answer.
- ✓Audit log Shows who did what in the workspace, and when, as a list you can read and export.
- ✓Two-factor sign-in A code from your phone after the email link. The owner can require it for everyone.
- ✓Customer questionnaires (audit room) Drop the customer's file and name the customer: Complipath answers what it already knows from your earlier audits, your data answers and your register, each answer with its source; only short questions are left for you, and Confirm all confirms the rest.
Rules decide. AI only drafts. A person confirms.
What it does not do yet
- ✗Risk management (Article 9) With limits The risk register records each risk your AI systems carry, with the level a person gives it — low, medium or high — the reason in words, an owner, an action and a status, never a score; the risk map places each risk by likelihood and impact before and after the action. For a provider of a high-risk system, Growth drafts risk management (Article 9) from the risk register, and a person completes and signs it. The testing in Article 9(6) to (8) is not in the app's list.
Questions
Does Complipath do our information security work?
Not the work itself. Complipath keeps the evidence and answers with a source. On Starter its security list holds every tool you add, AI or not, drafts a security policy for each AI system from the register for a named person to confirm, records training per person and keeps a checklist for when someone leaves.
Is an ISO/IEC 27001 certificate enough for the AI Act?
Not on its own. The certificate is evidence for your security programme. For a high-risk system the AI Act's cybersecurity requirement is Article 15, including the AI-specific attacks Article 15(5) names, and the technical documentation describes the measures under point 2(h) of Annex IV.
Answer your next questionnaire with proof.No account needed. Every answer cites the article it rests on.