cd /news/ai-policy/en-18286-is-out-what-would-an-audito… · home › topics › ai-policy › article
[ARTICLE · art-159660] src=dev.to ↗ pub= topic=ai-policy verified=true sentiment=· neutral

EN 18286 is out. What would an auditor ask about your AI agents?

A VP of R&D at authorization vendor Permit published an analysis of EN 18286:2026, the first harmonised standard under the EU AI Act, approved by CEN on 12 July 2026 and referenced in the Official Journal around 14 October. The standard converts Article 17 quality management system requirements for high-risk AI system providers into auditor-checkable processes and grants a presumption of conformity, though it never mentions AI agents, authorization or MCP. The analysis argues agent teams should still read it because its risk management, human oversight, data quality and cybersecurity processes map onto questions enterprise security reviews already ask, particularly when agents authenticate as users and inherit all their permissions.

read2 min views3 publishedOct 28, 2026

I work at Permit. Our VP of R&D wrote up what EN 18286:2026 means for teams shipping AI agents. We sell authorization, so read this with that bias in mind.

EN 18286:2026 is the first harmonised standard under the EU AI Act. It turns the Article 17 quality management system requirements for providers of high-risk AI systems into processes an auditor can check. CEN approved it on 12 July 2026, and its reference was published in the Official Journal around October 14. Following it gives you a presumption of conformity for the Article 17 requirements it covers. It's meant to sit on top of a QMS you may already have, like ISO/IEC 42001 or ISO 9001.

It doesn't mention AI agents, authorization or MCP anywhere. It also only applies to high-risk systems, and most agents won't be classified that way. I still think agent teams should read about it, because the processes it asks for (risk management, human oversight, data quality, cybersecurity) are the same things enterprise security reviews already ask about agents.

Once an agent can call tools, change data or send messages, those processes turn into pretty concrete questions:

A lot of agents authenticate as the user and run with everything that user can do. If an auditor asks which actions the agent was authorized to take, the honest answer is all of them. Why was a given action allowed? Because the user could have done it. What oversight happened first? None was required.

The post also covers where Permit fits. It says plainly that the standard doesn't prescribe any vendor, and that EN 18286 covers Article 17 only, so it won't make you AI Act compliant on its own.

Is anyone here getting asked about EN 18286 yet, either by a notified body or by enterprise customers?

── more in #ai-policy 4 stories · sorted by recency
── more on @permit 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/en-18286-is-out-what…] indexed:0 read:2min 2026-10-28 · —