Table of Contents

Reach SOC 2 Compliance in 6 Weeks or Less.

  / ISO 27001 Internal Audit Explained: Key Steps and Best Practices

ISO 27001 Internal Audit Explained: Key Steps and Best Practices

Achieving ISO 27001 certification signifies excellence in information security management, demonstrating your organization’s dedication to protecting sensitive data. However, this process involves careful steps, with one of the most important being the internal audit. This crucial phase verifies that your Information Security Management System (ISMS) meets ISO 27001 standards and is strong enough to reduce risks.

Watch the Loom Video for a detailed explanation of our internal audit services, check out our Loom video, where our Principal Consultant Ali Hayat breaks down the process step-by-step and shares tips for seamless ISO 27001 compliance. Click here to watch the Loom video.

ISO 27001 Internal Audit

What is an ISO 27001 Internal Audit?

 

An ISO 27001 internal audit is a structured review of your ISMS to check its compliance with the standard’s requirements. Unlike external audits done by certification bodies, internal audits are performed by the organization itself or by a third-party auditor to find gaps, evaluate risks, and ensure readiness for certification.

The main goal of an internal audit is to ensure that your ISMS meets ISO 27001 requirements and effectively reduces risks. It also offers a chance to find areas for improvement and strengthen your organization’s security efforts. By conducting a thorough gap analysis during this stage, you help set your organization up for success in the certification process.

ISO 27001 Internal Audit Requirements: Understanding Clause 9.2

 

Clause 9.2 of ISO 27001:2022 establishes the specific requirements for internal audits, forming the backbone of audit governance. This section mandates that organizations establish and implement audit programs to evaluate the effectiveness of their ISMS at planned intervals.

The standard specifies several critical requirements within Clause 9.2:

Clause 9.2.1 – Audit Program Requirements: Organizations must define audit objectives, scope, frequency, and methodologies. Your audit program should establish criteria against which the ISMS will be evaluated, ensuring that all relevant information security controls are systematically reviewed over a defined period.

Clause 9.2.2 – Auditor Competence and Objectivity: This is perhaps the most critical requirement. Auditors must be objective, impartial, and free from conflict of interest. The standard explicitly prohibits auditors from evaluating areas for which they hold direct responsibility, as this compromises independence and undermines audit credibility.

To meet Clause 9.2.2, auditors should possess documented competence in ISO 27001 standards and audit methodologies. Many organizations require auditors to hold certifications such as Certified Information Systems Auditor (CISA) or ISO 27001 Lead Auditor. Reference to ISO 19011 – Guidelines for auditing management systems – provides additional guidance on selecting, evaluating, and managing auditors.

Who Can Perform an ISO 27001 Internal Audit?

Internal audits can be carried out by your organization’s own internal audit team or outsourced to a third-party auditor or an ISO 27001 consulting firm. Unlike external certification audits, you can choose the most suitable approach for your organization. However, it’s crucial to follow Clause 9.2(e) of the ISO 27001 standard, which stresses the importance of selecting an internal auditor who is objective and impartial. This means avoiding any potential conflicts of interest—specifically, the auditor should not have been involved in developing the ISMS or in operating or monitoring any of the controls under review. The reason for this requirement is simple: reviewing your own work can undermine objectivity and hinder a thorough evaluation.

Essential Auditor Qualifications

When selecting an auditor, ensure they meet the following criteria:

In-Depth ISO 27001 Knowledge: Auditors must understand the standard’s requirements, Annex A controls, and how they apply to your organization’s context.

Audit Methodology Expertise: Knowledge of audit planning, sampling techniques, evidence collection, and report writing.

Relevant Certifications: ISO 27001 Lead Auditor (IRCA or equivalent), CISA, or similar credentials demonstrate formal competence.

Industry Experience: Understanding of your sector’s specific security challenges and regulatory landscape adds significant value.

If internal expertise is limited, hiring an experienced third-party auditor or consulting firm can provide a fresh, unbiased perspective and valuable insights tailored to your organization’s unique environment.

Internal Audit vs External Certification Audit: Key Differences

Understanding the distinction between internal and external audits is crucial for effective compliance strategy. While both serve important roles, they differ significantly in purpose, scope, and outcome.

Aspect

Internal Audit

External Certification Audit

Conducted By

Organization (internal or contracted third party)

Accredited certification body

Primary Purpose

Identify gaps and prepare for certification

Verify compliance and issue certificate

Focus

Detailed improvement; addresses specific findings

Overall conformance; verifies readiness

Flexibility

High – customize scope and approach

Low – standardized audit procedures

 

Internal audits serve as your organization’s opportunity to address vulnerabilities proactively before the certification audit. They foster a culture of continuous improvement and ensure that any gaps are remediated well in advance. This strategic advantage makes internal audits invaluable in the certification journey.

How to Conduct an ISO 27001 Internal Audit: Key Phases

Conducting an ISO 27001 internal audit involves a series of well-defined steps to ensure that your Information Security Management System (ISMS) is thoroughly evaluated. Below is a detailed breakdown of the process:

Phase 1: Determine the Scope of the Audit

The first step is to clearly outline the audit’s scope, specifying the systems, functions, people, and processes that will be assessed. This scope ensures the audit comprehensively covers all necessary areas to meet compliance objectives. Defining the boundaries early on helps the auditor focus on the most relevant elements of the ISMS, particularly considering your organization’s specific ISMS scope boundaries and the applicability of controls.

Phase 2: Documentation Review

Before proceeding with on-site evaluations, the internal auditor will review all key ISMS documents to verify that they align with ISO 27001 requirements. An effective ISMS requires a well-defined scope, a comprehensive Statement of Applicability (SoA), a robust Information Security Policy, a thorough risk assessment and treatment plan, and clear definitions of responsibilities. Additionally, identifying individuals responsible for implementing and operating controls, and documenting evidence of control implementation, provides valuable context for the field review.

Phase 3: Management Review and Approval

The audit plan must be reviewed and approved by senior management. Regular meetings should be scheduled to set expectations, discuss timelines, and maintain open communication. Management also plays a critical role in reviewing the internal audit findings, collaborating with the auditor to assess the organization’s readiness for an external certification audit, and ensuring that all significant issues are addressed beforehand.

Phase 4: Pre-Audit Preparation

Preparation is critical for a successful audit. This phase includes developing detailed audit checklists, identifying key personnel for interviews, scheduling on-site activities, and gathering necessary documentation. A well-prepared audit checklist aligned with ISO 27001 requirements and your organization’s context ensures comprehensive coverage and consistency.

Phase 5: Conducting the Field Review

The field review is the core of the internal audit process. During this phase, the auditor evaluates the ISMS through multiple evaluation methods, gathering evidence to support findings and determine the effectiveness of controls.

Audit Tests: Assessing controls to ensure they are effectively implemented and functioning as intended. This involves testing a sample of control activities to verify control effectiveness.

Audit Evidence Collection: Reviewing documented information and audit trails to confirm compliance and identify gaps. Evidence should support all audit conclusions.

Staff Interviews: Engaging with employees to gauge their understanding of and adherence to ISMS policies. These interviews provide crucial insight into whether controls function as designed in practice.

Observations and Documentation: Recording findings, highlighting areas of non-conformity, and identifying strengths. Clear documentation enables transparent reporting and actionable recommendations.

This comprehensive review enables the auditor to pinpoint what’s working well and what needs improvement, providing a clear roadmap for corrective actions.

ISO 27001 Internal Audit Checklist: Essential Items

A well-designed audit checklist is fundamental to conducting a thorough and consistent internal audit. The checklist should cover all ISO 27001 requirements and be tailored to your organization’s context. Below are the essential categories and items to include:

Organizational Context (Clauses 4.1-4.3): Verify that the organization understands its internal and external context, interested parties, and scope of the ISMS.

Leadership and Governance (Clauses 5-6): Confirm management commitment, information security policy, allocation of roles and responsibilities, and evidence of management review.

Planning (Clause 6): Assess risk assessment methodology, risk treatment plans, and management of information security objectives.

Support and Operation (Clauses 7-8): Check resource availability, competence assessments, awareness and training programs, and operational control implementation.

Performance Evaluation (Clause 9): Review monitoring and measurement of controls, incident management procedures, and evidence that internal audit has been appropriately planned and conducted.

Improvement (Clause 10): Evaluate management of non-conformities, corrective action effectiveness, and documented information control.

Incorporating Annex A controls into your checklist ensures that all 114 control objectives are evaluated within the scope of your ISMS. Many organizations create control-specific evaluation criteria linked to this comprehensive checklist.

Addressing Non-Conformities

 

Non-conformities can range from minor documentation gaps to critical security flaws. Identifying and addressing these issues promptly is essential to maintain the integrity of your ISMS. By developing comprehensive corrective action plans and monitoring their implementation, organizations can ensure continuous improvement and long-term compliance with ISO 27001 standards.

 

Common ISO 27001 Internal Audit Findings

Understanding typical non-conformities helps organizations proactively address vulnerabilities. Here are the most frequently encountered findings:

Documentation Gaps: Missing, incomplete, or outdated policies, procedures, or records. For example, risk assessment documentation that doesn’t clearly link to implemented controls.

Access Control Deficiencies: Inadequate user access reviews, orphaned accounts, lack of segregation of duties, or insufficient multi-factor authentication implementation.

Incident Management Issues: Incomplete incident logs, lack of timely incident classification, or insufficient root cause analysis documentation.

Training and Awareness Gaps: Insufficient security awareness training records, lack of role-specific training, or no evidence of competency assessment.

Change Management Failures: Changes implemented without proper authorization, risk assessment, or documented approvals.

Backup and Recovery Defects: Untested backup procedures, unclear recovery objectives, or lack of documented restoration testing records.

The Corrective Action Process

Addressing non-conformities requires a structured, documented approach. The standard corrective action process includes:

Classification: Categorize each finding as Major (major risk or complete absence of a control) or Minor (temporary deviation or incomplete implementation that doesn’t significantly impact security).

Root Cause Analysis: Investigate why the non-conformity occurred—whether due to lack of awareness, insufficient resources, or inadequate procedures.

Corrective Action Plan: Develop specific, measurable actions with defined timelines and responsible parties. Plans should address root causes, not just symptoms.

Implementation Monitoring: Track progress toward completion and verify that actions are implemented as planned.

Effectiveness Verification: Re-audit completed actions to confirm they have resolved the non-conformity and prevented recurrence.

Major non-conformities must be resolved before certification, while minor findings require documented action plans with appropriate timelines. Organizations should also review common mistakes during ISO 27001 implementation to avoid repeating the same errors across multiple audits.

Timeline of Internal Audits

A successful ISO 27001 internal audit requires careful planning and execution. Here’s a detailed breakdown of the key phases and estimated time required for each, though actual duration depends on organization size, ISMS complexity, and control maturity.

Planning (0.5 days): Define the audit scope, objectives, and methodology. Develop an audit plan, including the schedule and resource allocation. This phase establishes the foundation for all subsequent work.

Preparation (0.5 days): Review relevant documentation, develop audit checklists, and identify key personnel to be interviewed. Preparation ensures efficiency during field activities.

Audit Execution (1-2 weeks): Conduct interviews, document reviews, and observations. Verify the implementation of controls and procedures. Identify non-conformities and opportunities for improvement. This phase is the most time-intensive and involves active on-site engagement.

Reporting (1 day): Prepare a detailed audit report, including findings, recommendations, and corrective action requirements. Review the report with management to ensure accuracy and completeness.

Closure (1 day): Finalize the audit report and distribute it to relevant stakeholders. Monitor the implementation of corrective actions. Schedule follow-up audits to verify the effectiveness of corrective actions and ensure sustainable improvement.

The audit execution timeline varies significantly based on organization size. A small organization with a well-defined scope might complete field activities in 3-5 days, while a larger enterprise with multiple business units could require 2-3 weeks. The complexity of your ISMS and the maturity of your existing controls also play significant roles in determining realistic timelines.

ISO 27001 Internal Audit Timeline

Benefits of a Well-Executed Internal Audit

Conducting a comprehensive internal audit provides key benefits for organizations aiming for ISO 27001 certification:

Certification Readiness: Identifying and fixing gaps before the certification audit greatly boosts the chances of passing on the first attempt and minimizes the need for re-audits.

Enhanced Security: Internal audits reinforce your ISMS by verifying control effectiveness, reducing weaknesses, and increasing your organization’s resilience to security risks.

Operational Efficiency: The process reveals inefficiencies and overlaps, helping you streamline workflows and better allocate resources for security efforts.

Stakeholder Trust: Showcasing strong, documented security practices through internal audits builds confidence with clients, partners, regulators, and other stakeholders. This often provides a competitive edge and supports business growth.

Culture of Improvement: Regular audits foster a mindset of continuous enhancement, motivating ongoing review and improvement of security measures beyond mere compliance.

Understanding Your Path to Certification with Axipro

 

Axipro’s internal audit services are designed to simplify the ISO 27001 compliance process. Our team of experienced auditors conducts thorough assessments, identifying gaps and providing actionable insights to strengthen your ISMS.

We tailor our approach to your organization’s unique needs, offering guidance from planning to corrective actions. With Axipro, you can streamline your internal audit process, reduce complexity, and achieve ISO 27001 certification confidently.

Conclusion

 

An ISO 27001 internal audit is a cornerstone of effective information security management. It ensures compliance, enhances security practices, and prepares your organization for certification success. By following a structured approach and leveraging expert support, you can make the audit process smooth and impactful.

Frequently Asked Questions

What is the purpose of an ISO 27001 internal audit?

The primary purpose is to verify that your ISMS aligns with ISO 27001 standards, identify gaps and non-conformities before external certification, ensure controls are effectively operating, and prepare the organization for successful certification audit.

Internal audits can be conducted by your organization’s internal audit team or outsourced to qualified third-party auditors or consulting firms. However, auditors must be objective, impartial, and free from conflicts of interest as required by Clause 9.2.

After completion, the audit report is distributed to management. Non-conformities are categorized and corrective action plans are developed. Organizations then implement and monitor these corrections. Follow-up audits verify the effectiveness of corrective actions. Once major non-conformities are resolved, the organization proceeds to schedule the external certification audit.

ISO 27001 requires audits at planned intervals, typically at least annually for certified organizations. Pre-certification organizations should conduct audits multiple times (3-6 months before certification). Focused audits can be conducted quarterly or as-needed after significant changes.

Simplify your ISO 27001 compliance journey with Axipro’s expert internal audit services.

Axipro Author

Picture of Abeera Zainab

Abeera Zainab

Blog Highlights

Explore More Articles

One in five organizations has already suffered a breach traced back to shadow AI. Meanwhile, 63% of breached organizations either have no AI governance policy at all or are still drafting one. Below is a complete, copy-ready shadow AI policy template with twelve sections, plus guidance on adapting it for your company size, your industry, and the regulatory frameworks you answer to. The template assumes one hard truth up front: your employees are already using unapproved AI tools. A policy that pretends adoption hasn’t started yet fails on day one, so this one starts from the assumption that it has. What Is a Shadow AI Policy? A shadow AI policy is a formal document that defines how your organization discovers, evaluates, approves, and governs AI tools that employees adopt outside official IT channels. The term borrows from shadow IT, the older problem of unsanctioned software and hardware, but the AI version carries sharper risks: data pasted into a public model may be retained, used for training, or exposed in ways the organization can’t reverse. The policy does three jobs: it separates approved use from unapproved use, gives employees a fast and visible way to request new tools so the sanctioned route beats the workaround, and spells out what happens when someone crosses the line, including how the organization detects it and responds. Shadow AI Policy vs. General AI Acceptable Use Policy Many organizations already have an AI acceptable use policy (AUP) and assume it covers shadow AI. It usually doesn’t. An AUP tells employees how to behave inside approved tools. A shadow AI policy governs the tools themselves: which ones exist in your environment, which ones are allowed, and what happens with the rest. You need both. The AUP handles conduct; the shadow AI policy handles inventory and control. If you only have room for one document, fold the AUP’s data-handling rules into Section 6 of the template below. Let Axipro help you build a business continuity plan that’s practical, compliant, and audit-ready. Strengthen Your Business Continuity Strategy​ Schedule A Consultation The Shadow AI Policy Template (Download Link and Copy-Ready Sections) We’ve created a compliance safe template for Shadow AI Policy, use the link below to create a copy and customize for your company: Download The Shadow AI Policy Template → Copy the sections below into your policy management system and replace the bracketed placeholders. The language is plain on purpose. Legalese gets skimmed. Section 1: Purpose and Scope This policy governs the acquisition, approval, and use of artificial intelligence tools, features, and services at [Company]. It applies to all employees, contractors, interns, and third parties with access to [Company] systems or data. It covers standalone AI applications, AI features embedded in existing software, browser extensions, AI agents, APIs, and personal AI accounts used for work purposes, on both corporate and personal devices. The purpose of this policy is to enable productive AI use while protecting [Company] data, customers, and legal obligations. This policy does not prohibit AI. It prohibits ungoverned AI. That last sentence matters. Employees read the purpose statement first, and it decides whether they see the policy as an enabler or a blocker. Section 2: Definitions and Terminology Shadow AI: any AI tool, feature, agent, or service used for work purposes without formal approval under this policy. Approved AI Tool: an AI tool listed in the Approved AI Tools Registry (Section 4) and used under a [Company]-managed account. Personal AI Account: an account on any AI service registered to a personal email address or paid for personally. AI Feature: AI functionality embedded within otherwise approved software (e.g., an AI assistant added to a project management tool), which requires separate evaluation. Sensitive Data: data classified as [Confidential] or [Restricted] under [Company]‘s data classification policy, including the prohibited data classes in Section 6. Define “AI feature” explicitly. Vendors now ship AI additions into already-approved SaaS products every month, and without this definition, those features inherit approval they never earned. Section 3: Roles and Responsibilities The CISO (or designated security lead) owns this policy, maintains the Approved AI Tools Registry, and runs the approval workflow. Department heads ensure their teams know the policy and surface tool requests rather than suppressing them. Legal and Compliance review tools that touch regulated data or fall under the EU AI Act, GDPR, HIPAA, or client contractual restrictions. IT operates detection and monitoring controls (Section 9). Every employee is responsible for using only approved tools for work, reporting unapproved AI use they discover, and requesting new tools through the workflow in Section 7 rather than adopting them directly. Insider Note: In organizations under roughly 200 people, the “CISO” in this section is often the same overworked IT lead who manages laptops. Name a real person, not a title that doesn’t exist yet. A policy that assigns duties to a phantom role is unenforceable, and auditors notice. Section 4: Approved AI Tools Registry [Company] maintains a registry of approved AI tools at [location/URL]. For each tool, the registry records: tool name and vendor, approved use cases, prohibited use cases, permitted data classes, account type (enterprise/team/individual), data retention and training settings, risk tier (Section 5), approval date, and next review date. Only tools listed in the registry may be used for work. Tools not listed are unapproved by default. The registry is reviewed [quarterly]. Keep the registry somewhere employees actually look, such as your intranet homepage or IT help center, not buried in a GRC platform they can’t access. An invisible registry recreates the problem the policy exists to fix. Section 5: Risk Tier Classification (Low, Medium, High) Each tool in the registry is assigned a risk tier. Low: the tool processes only public or internal non-sensitive data, runs under an enterprise agreement with training opt-out, and produces output that a human reviews before use. Approval by IT Security alone. Medium: the tool processes internal business data or connects to [Company] systems via API or integration. Approval by IT Security plus the data owner. High: the

Legacy threat modeling frameworks such as STRIDE were designed for software that behaves the same way over and over again. Agentic AI does no such thing. It can rewrite its own plan mid-task, call external tools, negotiate with other agents, and produce a different output from identical input. MAESTRO exists because none of the legacy threat modeling frameworks were built to handle that. MAESTRO stands for Multi-Agent Environment, Security, Threat, Risk, and Outcome. It is a seven-layer threat modeling framework created specifically for agentic AI systems, and it has become the closest thing the industry has to a standard method for reasoning about agent security. Understanding MAESTRO in the Context of Agentic AI What MAESTRO Stands For Each word in the acronym carries meaning. Multi-Agent Environment signals that the framework models entire ecosystems of interacting agents, not a single model behind an API. Security, Threat, Risk covers the core discipline: identifying attack surfaces, cataloging threats, and assessing likelihood and impact. Outcome is the part most frameworks skip. MAESTRO asks what an attack actually produces in the real world, because an autonomous agent with tool access turns a compromised prompt into a compromised action. The Origin of MAESTRO (Cloud Security Alliance) The Cloud Security Alliance published MAESTRO in February 2025. Its creator is Ken Huang, Co-Chair of the CSA AI Safety Working Groups and CEO of DistributedApps.ai. The CSA has since applied the framework publicly to real systems, including OpenAI’s Responses API and Google’s A2A protocol, which gives practitioners worked examples rather than just theory. The framework is openly published, and the CSA maintains an official companion tool, the MAESTRO Threat Analyzer, on GitHub. SOC 2, ISO 27001 and HIPAA done for you. Fixed fee, 100% audit pass rate. Audit-ready in 6 weeks. Not 6 months. Schedule Free Assessment Why Traditional Frameworks Fall Short for Agentic AI STRIDE, PASTA, LINDDUN, and OCTAVE all share a founding assumption: the system under analysis follows predictable logic with clearly defined boundaries. You draw the data flow diagram, mark the trust boundaries, and enumerate threats against components that behave deterministically. Agentic AI breaks every part of that assumption. Unique Security Challenges of Autonomous Agents Agents introduce three properties that legacy models cannot express. Non-determinism means the same input can produce different behavior, so you cannot enumerate execution paths in advance. Autonomy means the agent makes decisions and takes actions without a human approving each step, which collapses the usual assumption that a person sits between intent and execution. And in multi-agent systems there is often no stable trust boundary: agents delegate to other agents, consume tool outputs from external servers via protocols like the Model Context Protocol (MCP), and update their own memory and goals at runtime. The Gap Between Legacy Frameworks and Agent-Based Systems The practical consequence is coverage gaps. STRIDE has no category for goal manipulation, where an attacker gradually steers what an agent is trying to achieve. PASTA assumes attacker objectives and data flows are fixed, which fails for systems that learn and adapt during operation. LINDDUN addresses privacy but says nothing about agent collusion or memory poisoning. A threat model built purely on these frameworks will pass review and still miss the attacks that matter most in an agentic deployment. How MAESTRO Addresses Agentic-Specific Risks MAESTRO does not discard the older frameworks. It extends them with a layered reference architecture, an AI-specific threat catalog for each layer, and, critically, explicit analysis of how threats propagate between layers. That cross-layer lens is the framework’s real contribution, because most serious agentic incidents are chains: poisoned data influences a model, the model misleads an agent, and the agent takes an unauthorized action three layers away from where the attack started. The Seven Layers of the MAESTRO Framework MAESTRO decomposes any agentic system into seven layers, each with its own threat landscape. Layer 1: Foundation Models The core LLMs or other models the agents reason with. Threats here include adversarial examples, model extraction, backdoored weights, and jailbreaks that bypass safety training. If the model is a third-party API, supply chain risk lives at this layer too. Layer 2: Data Operations Everything the agent ingests, stores, and retrieves: training data, RAG pipelines, vector databases, and agent memory. Data poisoning and memory tampering are the signature threats at this layer, and they are especially dangerous because a poisoned memory persists across sessions and keeps shaping future decisions long after the initial attack. Layer 3: Agent Frameworks The orchestration software that turns a model into an agent: LangChain, CrewAI, AutoGen, custom planners, and tool-calling logic. Threats include prompt injection through tool outputs, insecure tool definitions, and manipulation of the planning loop itself. Layer 4: Deployment Infrastructure The servers, containers, and cloud services the agents run on. The CSA’s threat catalog here reads like traditional cloud security with an agentic twist: compromised container images carrying malicious agent code, Kubernetes orchestration attacks, denial of service against agent runtimes, and tampering with Infrastructure-as-Code templates that provision agent resources. Layer 5: Evaluation and Observability The systems that monitor, evaluate, and debug agent behavior. This layer is often forgotten, and attackers know it. The CSA specifically flags poisoning observability data: manipulating the telemetry fed to monitoring systems so that incidents stay hidden from security teams while malicious activity continues. Layer 6: Security and Compliance MAESTRO treats this as a vertical layer that cuts across all others: identity and access management, guardrails, policy enforcement, and compliance controls. Threats include permission escalation, guardrail bypass, and compromise of the security agents themselves in architectures where AI enforces policy on other AI. Layer 7: Agent Ecosystem The environment where agents interact with users, other agents, and marketplaces. This is where the genuinely novel threats live: agent impersonation, misleading agent capability cards, tool squatting, and collusion between agents to achieve outcomes no single agent was authorized to pursue. Insider Note: In real assessments, Layers 5 and 6 expose the maturity gap fastest. Most teams’ shipping agents can describe their model and their orchestration framework in detail, then

EU AI Act Hiring Map

AXIPRO STUDY New Study: Europe is hiring AI builders faster than AI governance professionals Axipro analyzed 3,519 AI-related job postings across eight EU countries. For every professional hired to keep AI lawful, safe and accountable, nearly seven were hired to build more of it, and the gap is widest exactly where you’d least expect. Take EU AI ACT READINESS QUIZZ 16 AI Builders : 1 AI Governors Sweden — Europe’s widest AI governance gap 3,519 Job Postings Analyzed 8 EU Countries 2 Role Categories: Builders vs Governors July 2026 Date of Job Postings Analyzed The findings Finding 1: Sweden hires 16 AI builders for every 1 person to govern them Throughout our data-set we found the same pattern across all eight countries: the more a nation hires to build AI, the less it hires to govern it. France runs eleven builders to every governor. Even Ireland, the most balanced in Europe, looks responsible mainly because the US tech giants headquartered there import global-governance discipline under overlapping DORA and AI Act pressure.  3.5→16 builders hired per governor, Europe’s most balanced country to its least. Ireland 3.5 Germany 5.7 Spain 6.0 Italy 7.1 Netherlands 7.2 Belgium 7.9 France 11.4 Sweden 16:1 0 4 8 12 16 Builders hired per AI governor Source: Axipro, 2026 Sweden has one of the strongest engineering cultures in Europe. It also carries the widest governance gap we measured: sixteen AI builders hired for every person hired to govern them. France sits close behind at eleven to one. The most balanced country, Ireland at 3.5 to one, looks responsible for a reason that has little to do with virtue. The US tech giants headquartered in Dublin import global governance discipline, and they do it under the combined weight of the AI Act and DORA, the EU financial-sector resilience regime in force since January 2025. Engineering strength does nothing to close a governance gap, and it may widen it. A country that ships AI faster produces more systems that fall under the Act’s scope and, on this evidence, fewer people positioned to document, monitor, and defend them. Being good at building AI offers no protection against governing it badly. The countries most confident in their technical talent are running the largest deficit against the law. Explore AI governance hiring by country Click any country to see how many AI builders it hires for every governance professional, and where it ranks against the rest of Europe. Germany — 5.7 builders per governorDE France — 11.4 builders per governorFR Spain — 6.0 builders per governorES Italy — 7.1 builders per governorIT Netherlands — 7.2 builders per governorNL Belgium — 7.9 builders per governorBE Ireland — 3.5 builders per governorIE Sweden — 16 builders per governorSE 3.5 — balanced 16 — widest gap Source: Axipro, 2026 Sweden 16builders for every governance professional Rank 1 of 8 · 20 governance roles vs 319 builder roles posted Only 30% of the AI governance roles name the AI Act Share this Embed this map Copy & paste — links back to Axipro Copy embed code Branded, one paste, backlink included. × Share this country insight Share this AI governance gap X / Twitter LinkedIn Facebook WhatsApp Bluesky Email Copy link Choose a platform or copy the link. A view of the same country-level dataset behind the interactive map: governance roles, builder roles, builder-to-governance ratio, and the share of governance postings that name the EU AI Act. AI governance jobs Europe statistics by country: governance roles, builder roles, builder-to-governance ratio and AI Act mention percentage. Country Governance roles Builder roles Builder-to-governance ratio AI Act mention % Sweden 20 319 16.0:1 30.0% France 39 443 11.4:1 38.5% Belgium 38 299 7.9:1 39.5% Netherlands 61 439 7.2:1 31.1% Italy 40 284 7.1:1 45.0% Spain 64 384 6.0:1 28.1% Germany 88 501 5.7:1 27.3% Ireland 96 335 3.5:1 14.6% Source: Axipro analysis of AI builder, governance and compliance job postings across eight European countries. “AI Act mention %” is the share of governance postings that explicitly name the EU AI Act. Finding 2: The law nobody names. Most AI governance jobs still do not mention the EU AI Act Europe spent years drafting the AI Act. It cleared the European Parliament, survived the Digital Omnibus revisions, and now carries penalties that reach €35 million or 7% of global turnover for the most serious breaches, a ceiling that makes GDPR fines look modest. Yet fewer than three in ten of the governance roles created to handle it actually name the law in the job description. Among builder roles, the figure collapses to one in twenty-five. More than 7 in 10 Governance job descriptions do not mention the EU AI Act. This number rises to 9 in 10 for all AI job descriptions. Despite hiring for governance, risk, privacy, and compliance roles, most employers are not yet translating the EU AI Act into explicit job requirements. That disconnect should stop you. The people being hired to make Europe compliant are, for the most part, not being hired against the Act by name. They are titled around adjacent ideas: risk, ethics, model validation, data protection. Some of that work will map onto the Act’s requirements. Much of it will not, because a role written without the regulation in view rarely produces the conformity assessments, technical documentation, and human-oversight structures the Act specifically demands. Readiness is even thinner than the headcount suggests. Simply counting governance hires overstates how many people are actually working the law. What job descriptions actually name The EU AI Act is visible in governance roles — but still absent from most job ads. Across the laws and frameworks most relevant to AI governance hiring, the EU AI Act appears in fewer than three in ten governance postings, and only 4% of builder postings. Law or framework Governance roles naming it Builder roles naming it All roles naming it Governance mentions EU AI Act 28.5% 4.0% 7.6% 127 GDPR 26.9% 5.7% 9.6% 120 ISO 27001 11.4% 1.3% 2.8% 51