Sid Ali Boutellis, a freelance legal technology professional with over ten years’ experience and recently acquired legal credentials, was joined by Alexander Deicke, Legal Interim Manager at K11 Consulting GmbH, which provides flexible regulatory resources. Together they examined how two voluntary AI governance frameworks, the US NIST AI Risk Management Framework and ISO/IEC 42001, relate to the EU AI Act. Sid mapped the frameworks to the Act, while Alexander drew on his work helping organisations implement and maintain certifications.
Overview
The central question was whether adopting these frameworks is worth the effort, and what motivates organisations to do so. Sid explained that the NIST framework runs through govern, map, measure and manage, each a prerequisite for the next, while ISO 42001 follows plan, do, check and act. Neither is regulation, but he argued that aligning with them helps build a compliance strategy that works across borders, whether for a US business with EU operations or a European one planning to expand.
Sid linked the frameworks to specific provisions of the Act: Article 9 (documented lifecycle risk management), Article 11 (technical documentation, matching the NIST measure and ISO check stages), Article 15 (accuracy, robustness and cybersecurity, including incident response) and Article 72 (post-market monitoring). In his view, the incentives are client demands, outside counsel guidelines, competitive advantage (he cited a legal technology vendor that sought ISO 42001 certification to reassure EU clients) and, as a prediction, insurers eventually requiring a governance standard. Alexander noted that his clients are pushing towards ISO 27001 and hesitating over 42001, partly because AI elements may later be added to 27001. Sid countered that 27001 groundwork complements 42001 and that the underlying process matters more than any single standard.
Alexander argued that small and midsize organisations benefit most by choosing one framework, embedding it as a core process, and combining it with needs such as data protection. He observed that large organisations often manage ten to twenty certifications and treat them as box-ticking. Realistic limits emerged: Alexander estimated three to six months to certification and, for ISO 27001, costs from about €30,000 to €120,000–150,000, with €10,000–15,000 a year to maintain. Sid added that SOC 2 Type 2 can cost $15,000 to $50,000, and that regulators currently have very little capacity to enforce.
Key Takeaways
- Treat the frameworks as a bridge to the Act. Mapping NIST and ISO 42001 to Articles 9, 11, 15, and 72 lets you build one compliance approach instead of separate ones.
- Choose one framework and make it a working process. Alexander warned that annual certification without real use leaves documents unused; embed governance in core operations.
- Start with a data and digital inventory. Sid suggested this takes weeks to a month and makes later timelines and costs easier to estimate.
- Expect commercial pressure before regulatory pressure. Client demands, procurement requirements, and possibly insurance may drive adoption, so check what your clients and vendors already ask for.
- Build on existing certifications. ISO 27001 or SOC 2 work can reduce cost and effort, but budget realistically for consulting, maintenance, and the data protection and security functions that come with certification.
- Use certification evidence in vendor due diligence. Asking suppliers to follow a recognised framework gives you documentation to inform procurement decisions.