ISO 42001 for AI-Native Startups: Where to Start Your AI Management System
Build an AI management system around your real use cases: an agent register, risk and impact assessments, shared responsibilities, governance policy and Statement of Applicability.
Picture a small startup that gives its customers AI agents to work alongside their employees. It was founded on an AI opportunity, so AI isn't only what it delivers to users. It's how the company runs its operations, support and almost everything else.
For a company like this, ISO 42001 covers a lot of ground. This guide sets out where to start building the AI management system, the core pieces to put in place and the order to build them, and what else the standard expects.
What is ISO 42001, and why does it matter for an AI-native startup?
ISO/IEC 42001 is the international standard for an AI management system: the policies, roles, processes and controls an organisation uses to govern how it develops, provides and uses AI. It's certifiable, and it shares the same management system structure as ISO 27001, so the two can run as one integrated system.
For an AI-native startup, the standard reaches further than it would for most companies. An employee agent platform plays several roles at once:
AI provider to its customers, who deploy its agents in their businesses.
AI user internally, across operations, support and development.
AI customer of the model providers its product depends on.
Each role brings different responsibilities, so it pays to be clear on them from the start.
Where should you start?
For a company already using AI, start with its real use cases, then assess them and build the policy around what you find. Many people will tell you to start top-down with the AI policy, because it defines why you use AI. For a company already using AI in practice, it works better the other way round:
A register of AI use cases, agents and models, so you know exactly what you're governing. It also becomes the home for the next two steps.
A risk and impact assessment of each entry, done together.
Responsibilities between the platform, its customers and its model providers, mapped for each entry.
An AI governance policy that rolls all of this up into how the company governs AI.
A Statement of Applicability, last, setting out which controls apply and how.
An AI-native company has already worked through the policy questions intuitively; they just aren't written down. Doing the register and risk assessment first gives you the context for what really matters in the policy. This is a practical building sequence, not a requirement to follow the standard's clauses in this order.
What goes in an AI use case and agent register?
With AI used so broadly, cataloguing every use case is the natural starting point, and it supports everything that follows. The register should identify each use case individually, and ideally each specific agent and what it has access to.
Field
What it captures
Use case or agent
A unique name and ID for each AI application
Owner
The person ultimately responsible for its governance and oversight
Purpose
What it's for, and the outcome it's meant to deliver
Scope and boundaries
What it may and may not do, and the systems it can reach
Authorised users
Who may use it
Authorised changers
Who may change its configuration, prompts, tools or model
Data in and out
What data it takes in, what it produces, and where that data goes
Model and provider
The underlying model and the third party behind it
The register is also the natural home for each entry's risk assessment, impact assessment and responsibilities, covered below.
How far you go is a judgement call. Much casual, general-purpose AI use is hard to define one case at a time, and can be grouped. But every material application deserves its own entry.
For an employee agent platform, the first entries might look like this:
Use case
Owner
Purpose and boundaries
Customer-deployed agents
Head of Product
Agents customers deploy in their own businesses, limited to the tools and data each customer approves
Support agent
Head of Support
Answers customer questions from documentation; can't change customer accounts
Coding agents
CTO
Writes code for human review; can't merge or deploy without approval
General AI assistants
Operations lead
Staff use for drafting and research; no customer data
How do you assess the risks and impacts of each AI use case?
Work through the register one entry at a time. For each use case, ask where it could go wrong, where that could cause harm, who would be affected, and what matters to them.
For customers, that includes your terms of service, the risks to their business, their insurance and their personal data. Then come the risks specific to what the agent is meant to do. For an employee agent platform:
Risk
What it looks like
Ways to mitigate it
Misconfiguration
An agent deployed with the wrong scope, permissions or instructions
Guided onboarding; configuration guardrails built into the product
Unavailability
The agent goes down when a customer depends on it
Clear service commitments; monitoring; contingency guidance for customers
Erroneous changes
The agent changes data or takes actions incorrectly
Guardrails that hold the system's boundaries; logging; clear customer responsibilities
Missing context
The agent lacks the context to make the right call
Products that require context before an agent goes live; onboarding and training
Unexpected judgement
The agent processes or decides something in a way the customer didn't expect
Clear terms of service; data flow diagrams; agreed responsibilities with each customer
How is an impact assessment different from a risk assessment?
Risk assessments consider what could go wrong from using AI. Impact assessments consider the effects on individuals and society. ISO 42001 asks for both, and they look at different things:
Risk assessment
Impact assessment
Focus
What could go wrong, and its implications, from using AI
The effects of an AI system on individuals and society
Typical concerns
Financial losses, compliance failures, reputational damage, AI straying from its intended purpose
Ethical, legal, social and privacy effects on the people the AI touches
For an agent platform
An agent's error costs a customer money, and costs you the account
An agent's decision treats a customer's employee unfairly, or exposes their personal data
Run the two together, and house both in the register. Each flows logically from the purpose, scope and objectives the register defines for every use case, model and agent. That context is what tells you what the risks and impacts actually are.
Keeping everything in one place also supports governance and oversight, and gives everyone involved a shared understanding of each AI use.
How should responsibilities be split between the platform, its customers and model providers?
Map responsibilities in the register for each use case, model and agent, then put them where each party can understand and act on them. The split differs from entry to entry. An internal use case puts no responsibilities on customers. Every entry carries some responsibility for the model provider, but the use case shifts how far it extends and how much you depend on it.
Each party's responsibilities then need to land somewhere they'll be understood and acted on:
Party
Where their responsibilities land
Customers
Your terms of service, covering the use cases customers rely on, whether that's one or many
The platform
Your acceptable use policy, security policies and AI governance policy, so the right people across the company understand and perform their roles
Model providers
Third-party governance: due diligence, a risk assessment of each provider, and mitigations such as model settings, access restrictions and limits on how far certain models are used
This also helps you answer enterprise security reviews, where buyers need to understand what you control and what remains their responsibility.
What should the AI governance policy cover?
With the register and risk assessment done, the policy almost writes itself. Roll the use cases up and you can see what AI means for the company, and the governance needed to keep it under control. At a high level, the policy should set out:
Why the company uses AI, drawn from the register as a whole.
Ownership. Who owns each model and agent, and how that ownership is maintained.
Oversight. How the company keeps appropriate oversight of every material use case.
Risk assessment cadence. How often assessments are refreshed to stay current.
Customer support. Clear terms of service, onboarding, training, monitoring and guardrails for customers deploying agents.
Product direction. Guardrails built into the product, such as not letting customers deploy an agent without the context its purpose needs.
Responsibilities. Who is ultimately accountable, and who helps manage the system.
Audit. The internal and external audit requirements for the management system.
The product direction point deserves emphasis. You wouldn't deploy an employee without training and confidence that they understand their role, and you shouldn't deploy an agent that way either. An agent platform can help its customers get this right.
How do you build the Statement of Applicability?
Build it last in this practical sequence. Once the register, assessments, responsibilities and policy are in place, they give you the context for which controls apply, and how.
The Statement of Applicability works through the predefined controls in ISO 42001's Annex A. For each one, it records whether it applies, with a justification for any exclusion, how it's implemented, where the evidence lives and who is responsible. Together, that becomes the map of controls supporting the whole AI management system.
Control
Applies?
How it's implemented
Evidence
Owner
A.6.2.8 Recording of event logs
Yes
Every agent action is logged with its inputs, outputs and approvals
Logging platform and retention settings
CTO
For an AI-native agent platform, expect many Annex A controls to apply; what varies is how each one looks in practice. Applicability and any exclusions depend on your scope, risk assessment and AI roles. Areas to examine include:
Data for development (A.7). A company that doesn't train or fine-tune models may scope down the controls on training data. Data quality and provenance still matter if agents act on customer data or retrieved context.
The development life cycle (A.6). A company that only uses third-party AI tools, without building or configuring its own AI systems, may exclude some development controls.
Customer relationships (A.10). An AI management system that covers internal use only may exclude controls relating to customers.
An AI-native agent platform builds agents and serves customers, so expect broad control coverage. Auditors look closely at each exclusion, so justify every one against the register.
What else does an ISO 42001 AI management system need?
The pieces above form the core. The rest of the standard builds on them:
Component
Where in ISO 42001
What it means for an agent platform
Context, interested parties and scope
Clause 4
Define what the system covers, who has a stake (customers, their employees, model providers, regulators) and your AI roles
AI objectives
Clause 6.2
Set measurable goals for responsible AI, such as agent accuracy or incident rates
Competence and awareness
Clause 7
Make sure staff understand AI risks and their responsibilities
AI system life cycle
Annex A.6
Requirements, verification and validation, deployment, monitoring and event logs for each agent
Data for AI systems
Annex A.7
Quality, provenance and preparation of the data agents learn from or act on
Information for interested parties
Annex A.8
Documentation for users, and how you tell customers about incidents
Responsible use
Annex A.9
Rules for how the company itself uses AI, matched to each intended use
Internal audit, management review and corrective action
Clauses 9 and 10
Regular checks that the system works, leadership review, and fixing what doesn't
Certification follows the same pattern as ISO 27001: a two-stage audit by an accredited certification body, then annual surveillance audits over a three-year cycle. Because the management system structures match, ISO 27001 and ISO 42001 can share governance processes. A company with SOC 2 can also reuse relevant evidence where the scope and requirements align.
Former PwC manager, founder of AssuranceLab and former Sensiba partner and Chief Innovation Officer. Now founder of Throughline, focused on compliance and assurance for AI-native companies.
Beyond credentials, frameworks and pricing, ask who will do the work, how offshore teams operate, when auditors are available, whether controls fit your business and what happens when plans change.
Paul Wenham explains the proposed 2027 SOC 2 criteria, AI points of focus, governance and change management updates, transition effort and Throughline's approach to fees.
How certification bodies set ISO 42001 audit days under ISO/IEC 42006, how AI roles and in-scope headcount drive the price, and when scoping to engineering and product makes sense.
SOC 2 for startups, from planning to reporting: typical USD audit fees, timelines, internal team hours, AI-assisted readiness and keeping a first report on track.
SOC 2 for mid-sized companies: typical USD costs, timelines and team hours, plus existing controls, multiple products, regulatory drivers and auditor changes.
SOC 2 for enterprises: typical USD costs, timelines and team hours, plus ISO 27001 reuse, multi-entity scope, vendors, procurement and customer deadlines.
Typical SOC 2 costs and timelines for startups, mid-sized companies and enterprises, by report type. Compare planning, readiness, observation, fieldwork and reporting, plus related costs in USD.
Three worked SOC 2 examples: AI-written code, agent-led access reviews and agents changing customer data. Follow each risk through its control, audit test and evidence.
How to cover production AI agents in SOC 2: governance, access, change management and monitoring, with indicative criteria mappings, customer responsibilities and practical audit expectations.
Australian companies need a SOC 2 report issued under the AICPA standards by a US-licensed CPA firm, delivered by a strong local team in Australian time zones. Here's how the provider options compare, and what to check.
Experienced CTOs don't choose a SOC 2 audit firm on price or speed. They look for tech stack expertise, a tailored approach, flexible scheduling, responsiveness and year-round partnership, because those factors decide how much time the audit really costs.
What Security, Availability, Confidentiality, Processing Integrity and Privacy each cover, how often they're included, and how to decide which belong in your SOC 2 report.
Which SOC 2 report should come first? Six client cases, practical decision tables and an illustrative 18-month cost comparison explain when to start with Type 1 and when to go straight to Type 2.
How long a SOC 2 Type 2 observation period should be, how to work backwards from a customer deadline, when auditors test, why reports run late and how much buffer to build in.
A category-by-category SOC 2 budget in USD, covering audit fees, readiness, platforms, penetration testing, consultants, internal assessments and operational costs. Learn what is required, what is optional, and what a quote can leave out.
Five signals of real quality in assurance and security, with practical guidance on building a compliance program that supports customer TPRM, repeatable enterprise reviews and revenue growth.
The person leading your SOC 2 audit is the most underrated factor in choosing an audit firm. Companies compare price, timelines and platform integrations, then barely ask who will actually do the work.
SOC 2 is a risk report, not a certificate. Understand how enterprise customers use it, why having a report is only base camp, and how to turn your audit into a trust asset for growing revenue.
What readiness should cover, when to involve your auditor, which gaps matter most, and how readiness, Type 1 and Type 2 can work as one continuous engagement. A practical guide to preparing for a report your customers can rely on.
CPA firm registration, signing licenses and peer review are the starting point, not proof of quality. A practical guide to checking credentials and asking the questions that matter before choosing your SOC 2 auditor.
Neither is better for everyone. The right choice depends on your customers, how you run security and where you are headed. For AI-native and AI-centric companies, SOC 2's flexible criteria usually make it the stronger starting point.
Enterprise buyers use SOC 2 as an initial qualifier, then look deeper. A quality report is what carries you through that assessment and turns your compliance investment into real trust.
Audit quality isn't service quality, and it isn't only professional standards. The real test is whether a reader of your report thinks: this tells me what I need to know.
Enterprise security teams review you in the background and rarely give feedback. What they look at beyond SOC 2, what counts as a genuine pen test, and how a quality report does the heavy lifting.
Compliance from first principles, the 95% problem, the compliance metadata AI needs, rethinking screenshots, spreadsheets and policies, and why audits should meet clients where they are.