Skip to content

Playbook · for Leadership, Security

EU AI Act and ISO 42001: a starter for small teams

Find out which AI Act role you have, which dates apply, and how to build the evidence once with ISO 42001 and ISO 27001.

By Mr.DLast reviewed 3 min read

Start with your role

The EU AI Act (Regulation (EU) 2024/1689) gives different duties to different roles. Most small companies are deployers: they use AI systems built by others. You are a provider if you develop an AI system, or have one developed, and put it on the EU market under your name, which includes AI features inside your SaaS product. Importers and distributors have their own, lighter duties. Many companies are both deployer and provider.

Then find your risk level

LevelExamplesWhat it means
Prohibitedsocial scoring, manipulative techniques, some biometric usesBanned since 2 February 2025
High-riskAI in hiring, credit scoring, education, critical infrastructure, or safety components of regulated productsRisk management, data governance, logging, human oversight, accuracy, cybersecurity, documentation, conformity assessment
Transparencychatbots, AI-generated or manipulated contentTell people they deal with AI; mark synthetic content
Minimalspam filters, most internal productivity usesNo new duties beyond AI literacy

Providers of general-purpose AI models have had their own obligations since 2 August 2025.

The dates after the Digital Omnibus

The Digital Omnibus on AI (Regulation (EU) 2026/1744, in force since 27 July 2026) moved the high-risk dates:

  • 2 December 2026: marking of AI-generated content applies to systems placed on the market before 2 August 2026 (other transparency duties already apply).
  • 2 December 2027: obligations for stand-alone high-risk systems listed in Annex III.
  • 2 August 2028: obligations for high-risk AI built into products covered by EU product law (Annex I).

The delay changes when the duties apply, not what they are. Building the evidence takes longer than the remaining time suggests.

Five steps for this quarter

  1. Inventory every AI system you build or use, with an owner, purpose, data used and vendor.
  2. Classify each by role and risk level, and record why. Most will be minimal risk; write that down too.
  3. AI literacy: take measures so staff and others who operate AI for you understand its limits; since the Omnibus this is a duty of effort, so keep training records as proof of the effort.
  4. Transparency: label chatbots and mark AI-generated content where the Act requires it.
  5. Gap-check high-risk candidates early, because their documentation, logging and human oversight take months.

Where ISO 42001 fits

ISO/IEC 42001:2023 is the certifiable management system for AI. It gives you the structure the Act assumes you have: an AI policy, roles, risk and impact assessments, lifecycle controls, supplier oversight, monitoring and improvement. If you already run an ISO 27001 ISMS, you reuse its clauses for context, leadership, documents, internal audit and management review, and add the AI-specific parts. ISO 42001 certification does not by itself prove AI Act conformity, but it produces much of the evidence.

And the NIST AI RMF

The NIST AI Risk Management Framework (Govern, Map, Measure, Manage) and its Generative AI Profile are free, practical and widely referenced by US customers. Use them as the working method for the risk assessments that ISO 42001 and the AI Act ask for.

How WardBee helps

WardBee already automates the technical evidence the Act and ISO 42001 share with ISO 27001: access control, logging, encryption and secure development across AWS, GitHub and GitLab, plus policies and manual controls for the rest. ISO 42001, EU AI Act and NIST AI RMF are guidance in WardBee today; automated control mapping for them is coming. This page is not legal advice; check the regulation text for your case.

Related standards: EU AI Act · ISO/IEC 42001 · NIST AI RMF

More playbooks

Check this playbook against your own AWS account.

WardBee connects read-only to AWS and, if you choose, to GitHub or GitLab, and shows which of these controls pass, fail or still need a person, as ISO 27001 and SOC 2 evidence.

What's new · v1.0.0

ScanComb and WardBee 1.0: compliance checks, TISAX and SOC 2 readiness, and a new public site

This is the first release of ScanComb and WardBee. WardBee brings automated compliance checks, framework workspaces, reports and task tracking for engineering, security and compliance teams. scancomb.com adds free checks and a TISAX readiness check, plus guides and news.

Highlights

  • TISAX readiness check Answer a public questionnaire and get a free readiness score by email. A paid report adds findings, an action plan for each chapter, a roadmap and a PDF. You can import the gaps into a WardBee workspace as tasks.
  • Dedicated TISAX section in WardBee Manage TISAX in one place. Set the scope, keep a self-assessment register, follow an action plan with tasks, track audits and labels, and manage suppliers and exports.
  • SOC 2 readiness Work through a readiness questionnaire, criterion guidance, a policy pack and reviews. Criteria are explained in plain words and questions can be answered in the side drawer. You can download a SOC 2 readiness report as a PDF.
  • Sovereignty Profile free check Run the free Sovereignty Profile check and get a report. The scores are explained in plain words.
  • Projects with a shared scan pool Run several projects or clients in separate workspaces that share one pool of scans. A For consultants page explains the setup.

Improvements

  • Resource inventory See an inventory of your resources with filters, saved views and notifications.
  • EU Cyber Resilience Act support Prepare for the EU Cyber Resilience Act with product classification and a continuous technical file.
  • NIS2 Supplier Check Assess suppliers against NIS2 with the NIS2 Supplier Check.
  • Free AI security check and AI Shield playbooks Take a free AI security check and read practical playbooks on AI agent permissions, prompt injection, shadow AI and more.
  • Manual control verification Verify controls that cannot be checked automatically, using a clearer drawer for manual controls.
  • Clearer controls and findings Findings and resource names are easier to read, you can filter to checks-only scans, and you can compare one scan with the previous one.
  • Faster control and dashboard pages Controls, the dashboard and risks load faster. App pages show a loading state right away.
  • Better start for new workspaces New workspaces start with ISO 27001 and SOC 2, with an explanation of what scans do. If no frameworks are chosen, a Choose frameworks step guides you.
  • Support tickets, announcements and notification bell Open support tickets inside WardBee and get email updates. Announcements appear in a header bell.
  • New site design, menu and guides scancomb.com has a new look and a grouped menu with News, Free checks and Guides. WardBee uses the same visual style, and the in-app docs are task-focused guides.
  • What's New and Framework Watch A What's New dialog shows release notes on scancomb.com. A weekly Framework Watch news issue is also published.
  • Team invitations and two-factor sign-in Invite teammates by email with consistent role names. Two-factor setup includes a QR code.

Fixes

  • Security improvements to sign-up and sign-in Sign-up and sign-in are now better protected.
  • More accurate AWS multi-factor authentication checks All MFA device types are now recognized, and users who only use programmatic access are no longer flagged.
  • Confirmed failures are shown correctly A confirmed failure now outranks an error in a control's status.
  • One critical-control email per scan You now get a single critical-control email per control for each scan.
  • Smoother onboarding and failed checks Workspaces without frameworks are sent to setup. Checks that fail are refunded, and queued checks show as Queued.
  • Correct access errors Signed-out or unauthorized requests now get a proper access error instead of a server error.