Table of Contents

Reach SOC 2 Compliance in 6 Weeks or Less.

  /

  / AIUC-1 AI Agent Certification: The Complete Guide

AIUC-1 AI Agent Certification: The Complete Guide

Most security certifications were built for software that follows rules. AI agents do not. They consume data, draw conclusions, call tools, and take action, increasingly without a human in the loop.

That gap is what AIUC-1 was created to close: it is the first auditable security standard built specifically for AI agents, and a few enterprise buyers have started asking vendors for it by name.

This guide covers what AIUC-1 actually tests, the six risk domains it audits, how the certification process works, what it costs, how long it lasts, and how it aligns with SOC 2, ISO 42001, ISO 27001, and the NIST AI Risk Management Framework. It also covers the structural questions worth asking before you treat an AIUC-1 report as proof of anything.

AIUC-1 AI Agent Certification The Complete Guide

What Is AIUC-1 Certification?

AIUC-1 is a certifiable standard for AI agents created by the Artificial Intelligence Underwriting Company (AIUC), a San Francisco-based, venture-backed startup founded by people with experience at organizations including Anthropic. The standard was developed with input from Orrick, Stanford, the Cloud Security Alliance, MIT, and MITRE, and launched in mid-2025.

The framework comprises 51 requirements and 130 controls, organized across six risk pillars. It evaluates whether an organization has implemented and tested the technical guardrails, operational practices, and legal policies needed to reduce the risk of unsafe, unreliable, or unauthorized AI behavior. Certification applies to a specific AI system or product, not to the organization as a whole. An AIUC-1 certificate, audit report, and badge tell enterprise buyers that an agent has been independently tested against agent-specific risks.

People describe AIUC-1 as the “SOC 2 for AI agents,” and the analogy holds in spirit. The difference is what it looks at. SOC 2 examines a service organization’s general controls. AIUC-1 examines how an agent behaves under pressure: when someone tries to jailbreak it, when it is asked to do something outside its scope, when it has access to data it should not expose.

Worth Knowing: About AIUC-1

AIUC-1 does not define what counts as an "AI agent." The vendor decides which system to certify and what falls in scope. That makes scope the single most important thing to check on any certificate, because a narrowly scoped audit may not cover the agent you actually use.

Why AIUC-1 Certification Matters for Enterprise AI Adoption

The business case rests on a simple problem: enterprises cannot reliably assess the security of their AI vendors, and the failures are expensive. According to EY research on responsible AI, 64% of companies with over $1 billion in revenue have already lost more than $1 million to AI-related failures. 

That gap shows up directly in sales cycles. When security, legal, and procurement teams evaluate an AI vendor, they ask about hallucinations, prompt injection defenses, and what happens when an agent makes an unauthorized call. SOC 2 and ISO 27001 do not answer those questions. AIUC-1 gives buyers a structured, third-party-tested answer, which is why holding the certificate can move a stalled procurement review forward.

The certification also produces real engineering outcomes, not just a badge. AIUC has reported cases where a customer service agent’s hallucination rate dropped from 11% to under 2% after strengthening its groundedness filter, and another where inappropriate-tone outputs fell from 9% to under 2% through better defensive prompting and output moderation. One company found and patched a PII exposure vulnerability during the certification process itself.

The Six Core Risk Domains Covered by AIUC-1

The Six Core Risk Domains Covered by AIUC-1

AIUC-1’s 51 requirements are grouped into six domains. Each targets a category of risk that traditional security frameworks were not designed to handle.

Data and Privacy

Covers how customer data is used, retained, and protected. Requirements address input and output data policies, limits on what data the agent can access, protection of IP and trade secrets, prevention of cross-customer data exposure, and prevention of PII leakage. This is where the standard forces clarity on whether customer data trains the model and how long it is kept.

Security

The adversarial-resistance domain. It covers third-party testing of adversarial robustness, detection and real-time filtering of malicious inputs, prevention of prompt injection and unauthorized agent actions, enforcement of user access privileges, and protection of the deployment environment. This is the heart of what separates an agent audit from a general security audit.

Safety

Focuses on preventing harmful and out-of-scope outputs. Requirements include defining an AI risk taxonomy, conducting pre-deployment testing, preventing harmful and customer-defined high-risk outputs, and flagging high-risk outputs for human review. Safety is partly judgment-based, which means documentation alone can sometimes satisfy a requirement, so the testing behind it deserves scrutiny.

Reliability

Targets the failure modes that erode trust in production: hallucinations and tool misuse. Controls cover hallucination prevention and restrictions on which tools an agent can call and when. For a customer-facing agent, this is the domain that keeps it from inventing a refund policy or triggering the wrong workflow.

Accountability

Covers what happens when things go wrong. Requirements include AI failure response plans, vendor due diligence, and clear AI disclosure so users know when they are interacting with an agent. With human workers, accountability is built into org charts and chains of command. Agents need an equivalent, and this domain supplies it.

Society

The broadest domain, focused on preventing misuse with wider consequences: AI-enabled cyber attacks and CBRN (chemical, biological, radiological, nuclear) misuse. Most enterprise agents will touch only a few of these controls, but they matter for higher-capability systems.

Insider Note: Of the 130 total controls, roughly 65 are mandatory, and 65 are optional. A straightforward agent typically needs to meet around 40 controls. A complex, multi-modal agent gets closer to 65. The scoping exercise determines which apply, so two AIUC-1 certificates can represent very different amounts of work.

Ready to Earn Your AIUC-1 Certification?

Accelerate Your AI Certification Journey

Who Needs AIUC-1 Certification?

AIUC-1 is built for any company developing or deploying agentic AI that sells into enterprises. The strongest fit is an organization whose product uses AI agents in customer-facing operations, handles confidential data through autonomous workflows, or makes decisions that affect critical business processes.

Certified systems so far include customer service agents, candidate scoring and interviewer agents, internal automation agents, summarization agents, and image generation agents. Certified organizations range from seed-stage startups to publicly traded enterprises, so company size is not the gating factor. Buyer demand is. The clearest reason to pursue AIUC-1 is that your enterprise buyers are asking for it, though early adoption also lets a vendor shape the security conversation before competitors do.

How the AIUC-1 Certification Process Works

The certification runs in distinct phases, with an accredited auditor guiding the organization through evidence collection and gap remediation.

Pre-Audit Readiness Assessment

Scoping and kickoff usually take one to two weeks. The organization works with the auditor to complete a scoping questionnaire, define which system and which controls are in scope, appoint internal leaders, and identify where current practices fall short of AIUC-1’s requirements. An internal-facing agent with limited data access will scope into far fewer controls than an external customer service agent handling sensitive data.

Evidence Collection and Documentation

The bulk of the work, typically three to five weeks. Teams gather documentation across operational practices, legal policies, and technical implementations, then remediate gaps surfaced during scoping. This phase includes hands-on testing of the system for hallucinations, prompt injection resistance, and the other risks the standard covers.

Independent Third-Party Audit

An accredited auditor reviews the evidence, conducts or reviews technical testing, and assembles the report. The audit combines upfront technical testing with a review of operational controls.

Certification Issuance

The Artificial Intelligence Underwriting Company issues the certificate. Finalizing the audit, building the report, and obtaining sign-off generally takes one to three weeks. The deliverables are the certificate, a detailed audit report with third-party attestation and evaluation results, and a badge for use in a trust center or sales collateral.

Ongoing Monitoring and Renewal

Certification is not a one-time event. Technical tests are re-run at least quarterly, and the full set of technical, operational, and legal controls is re-audited annually. This continuous cadence is meant to keep safeguards current as both AI capabilities and attack techniques evolve.

Requirements for AIUC-1 Certification

There is no single checklist that applies to every applicant, because scope drives requirements. Every certification covers the mandatory controls relevant to the system, plus whichever optional controls the agent’s data access, autonomy, and modality bring into scope.

In practice, organizations need documented input and output data policies, demonstrated defenses against prompt injection and unauthorized actions, evidence of pre-deployment and adversarial testing, a defined risk taxonomy, failure response plans, and clear disclosure practices. Where there is no single industry best practice, such as data retention, the standard emphasizes clear disclosure and enforcement over mandating one specific approach.

 

How Long Does AIUC-1 Certification Take?

AIUC lists a typical timeline of four to eight weeks, depending on the maturity of the organization’s existing safeguards and governance. Its FAQ gives a slightly wider range of five to ten weeks. Organizations that already have AI governance in place, for example an ISO 42001 management system, tend to land at the faster end because much of the operational and legal groundwork already exists.

 

How Much Does AIUC-1 Certification Cost?

AIUC does not publish standard pricing, and any firm quote depends on scope, the number of controls in play, the agent’s complexity, and the auditor engaged. Cost is driven by the same factors as the timeline: a simple internal agent scoping into roughly 40 controls is a smaller engagement than a complex multi-modal agent scoping into 65, with the adversarial testing that entails.

Treat published figures from third parties with caution and get a scoped quote from an accredited auditor. As a directional anchor, AIUC-1 sits in the same tier as other independent technical audits rather than a self-attestation, so budget alongside what you would expect for a SOC 2 Type II or ISO 42001 audit, plus the cost of any remediation the readiness phase surfaces.

Pro Tip: Run a Gap Assessment

Run a gap assessment before you commit to a full audit. The readiness phase is where most of the real cost hides, because remediation work, not the audit fee, is usually the larger line item. Knowing your gaps first lets you budget accurately and avoid a stalled audit halfway through evidence collection.

How Long Is an AIUC-1 Certificate Valid?

An AIUC-1 certificate is valid for twelve months. Maintaining it requires technical testing at least every three months. Miss the quarterly cadence and the certificate lapses, even inside the twelve-month window. New requirements introduced through quarterly updates are evaluated at the next annual re-audit, so the certificate you hold reflects the version of the standard in force when you were audited.

 

Who Can Issue an Official AIUC-1 Certificate?

The Artificial Intelligence Underwriting Company issues all certificates. Schellman was the first accredited auditor for the standard, and accredited auditors handle evidence collection and prepare the reports. The ongoing quarterly technical evaluations are run centrally by AIUC itself rather than by individual auditors, which the company says keeps testing consistent across all certified organizations.

This structure matters for how much weight a certificate carries, a point covered in the challenges section below.

AIUC-1 Certification vs. Other Frameworks

AIUC-1 is designed to complement existing frameworks, not replace them. It operationalizes the AI-specific frameworks and avoids duplicating the general-purpose ones.

Framework

What it covers

Certifiable?

AI-agent specific?

Relationship to AIUC-1

AIUC-1

Technical, operational, and legal controls for AI agent risk

Yes

Yes

The standard itself

SOC 2

General service organization security controls

Attestation

No

Coexists; still required for enterprise sales

ISO 42001

AI management system (governance and process)

Yes

Partly

AIUC-1 validates that the governance produces working controls

ISO 27001

Information security management system

Yes

No

Foundational security; AIUC-1 sits on top

NIST AI RMF

Voluntary AI risk-management guidance

No

Partly

AIUC-1 translates its functions into testable controls

AIUC-1 vs. SOC 2

SOC 2 covers a vendor’s general cybersecurity posture. It does not address hallucinations, prompt injection, or unauthorized tool calls. The two are complementary: SOC 2 remains table stakes for selling into enterprise, while AIUC-1 answers the AI-specific questions SOC 2 leaves open.

AIUC-1 vs. ISO 42001

ISO 42001 certifies that an organization has a responsible AI management system, the policies and processes for developing and operating AI. AIUC-1 incorporates a number of controls directly from ISO 42001 and then extends them, translating management-system requirements into auditable technical controls and adding protections against risks like hallucinations and jailbreaks. Many organizations pursue both: ISO 42001 builds the governance, AIUC-1 proves the safeguards behind it hold up under testing.

AIUC-1 vs. ISO 27001

ISO 27001 governs information security management broadly. It is foundational and agnostic to AI. AIUC-1 assumes that kind of security baseline exists and focuses on the agent-specific layer above it, so the two rarely overlap.

AIUC-1 vs. NIST AI RMF

The NIST AI Risk Management Framework provides high-level, voluntary guidance with no certification path. It tells organizations what to think about, not how to prove they have done it. AIUC-1 takes NIST’s functions and turns them into specific, testable controls, which is the piece NIST deliberately leaves open.

AIUC-1 also maps to threat models the security community already uses, including MITRE ATLAS, the OWASP Top 10 for Agentic Applications, and the OWASP LLM Top 10, and it maps more than 30 articles of the EU AI Act to auditable requirements.

Ready to Earn Your AIUC-1 Certification?

Accelerate Your AI Certification Journey

How to Prepare for AIUC-1 Certification

Start with scope. Decide which agent or product you are certifying and document its data flows, the tools it can call, the models and versions it runs on, and its level of autonomy. That definition determines which controls apply and shapes everything downstream.

Next, run a readiness assessment against the six domains and fix the gaps before the formal audit begins. If you already hold ISO 42001 or have a NIST AI RMF program, map what you have onto AIUC-1’s controls; much of the operational and legal evidence will carry over. Build out the technical testing capability you will need: adversarial testing for prompt injection, groundedness evaluation for hallucinations, and output moderation. Going into the audit with that infrastructure already running is what separates a four-week certification from a ten-week one.

 

Benefits of Becoming AIUC-1 Certified

The headline benefit is faster enterprise deals. A certificate, report, and evaluation results give procurement, legal, and security teams a structured way to clear AI-specific risk, which removes a common point of friction late in the sales cycle. One certified executive summed it up by saying the certificate lets them sign contracts faster because it is a clear signal of trust.

Beyond sales, the process improves the product. The measurable drops in hallucination and inappropriate-output rates that companies report during certification are real engineering wins, not marketing. AIUC-1 also carries an insurance dimension that sets it apart: certification is backed by Lloyd’s of London insurance, and AIUC underwrites the risk associated with the certified agent. That changes the incentive structure, because the body certifying the agent also takes on financial exposure if it fails.

 

Common Challenges in Achieving AIUC-1 Certification

The first challenge is technical readiness. Building reliable defenses against prompt injection and hallucination is hard engineering work, and the readiness phase often surfaces gaps that take real effort to close.

Scope ambiguity is the second: because AIUC-1 does not define “AI agent,” getting the scope right requires careful judgment, and a scope drawn too narrowly undermines the certificate’s value.

The third challenge is structural, and buyers as much as vendors should understand it. AIUC authors the standard, runs the technical evaluations, issues the certificates, and sells the AI agent insurance that the certification enables. Security researcher Zack Korman has argued that this vertical integration creates potential conflicts of interest at several steps, with the closest precedent being the issuer-pays model in credit ratings, an arrangement that contributed to inflated ratings before the 2008 financial crisis. AIUC’s counterargument is that its insurance business creates a counter-incentive, since losses on a certified agent hit AIUC directly. There is also no external accreditation body: AIUC accredits its own auditors, so calling AIUC-1 a “standard” rests on AIUC’s own authority rather than a third party like ANSI or UKAS. None of this makes the certificate worthless. It makes it evidence to interrogate rather than a guarantee to accept at face value.

Important: No certification eliminates risk from a probabilistic, fast-changing system. Just as a SOC 2 report or a penetration test does not prove a system is secure against every threat, an AIUC-1 certificate cannot guarantee an agent is safe. Treat it as tested evidence of specific controls, scoped to a specific system, at a specific point in time.

 

The Bottom Line

AIUC-1 is the first serious attempt to give AI agents the kind of independent, testable security assurance that SOC 2 gave SaaS. It audits six domains that existing frameworks miss, runs on a quarterly testing cadence built for how fast AI moves, and comes backed by insurance that puts the issuer’s own money behind the result. It is also young, self-accredited, and commercially structured in ways worth scrutinizing.

For vendors selling agentic AI into enterprises, the practical question is no longer whether AI-specific certification is coming, but whether you would rather lead the conversation or explain to a procurement team why you cannot answer it. If buyers are already asking, the answer is straightforward.

Frequently Asked Questions About AIUC-1 Certification

Is AIUC-1 certification mandatory?

No. AIUC-1 is voluntary. It is not required by law anywhere. Demand is driven by enterprise buyers who want independent assurance on AI-specific risks, not by regulation.

Yes. Certified organizations range from seed-stage startups to publicly traded enterprises. Company size does not gate eligibility; the scope and maturity of the agent’s safeguards do.

No. Like a SOC 2 report or a penetration test, AIUC-1 provides evidence that specific controls were tested, scoped to a specific system at a point in time. It cannot eliminate all risk from a probabilistic, fast-evolving system.

A certificate is valid for twelve months but depends on quarterly technical testing to stay current. Failing to maintain the quarterly cadence causes the certification to lapse before the twelve-month period ends.

No. AIUC-1 complements SOC 2, ISO 27001, and ISO 42001 rather than replacing them. It covers agent-specific risks those frameworks were not designed to address, and SOC 2 in particular remains expected for enterprise sales.

No. Customer service agents are a common use case because brand and customer data are on the line, but certified systems also include candidate scoring agents, internal automation agents, summarization agents, and image generation agents.

Through the audit and the insurance model rather than through regulation. Accredited auditors prepare reports, AIUC issues certificates and runs quarterly technical testing, and the insurance backing ties certification to real financial exposure if a certified agent fails.

Axipro Author

Picture of Pedro Dias

Pedro Dias

Pedro has been writing online for over 10 years. With experience in all things programming, cyber security, and compliance, he is our editor-in-chief at Axipro.

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