Get a Quote
Compliance › ISO 27001

ISO 27001 Certification for AI-Built Apps

ISO/IEC 27001:2022 is the international standard for an Information Security Management System (ISMS) — not a law, but the certification enterprise procurement, vendor security questionnaires, and EU/UK partner contracts increasingly gate deals on. A-LIGN's 2025 benchmark found adoption among surveyed organizations jumped from 67% to 81% in a single year. For a founder who shipped an app with Lovable, Bolt, Replit, or Cursor, ISO 27001 becomes real the day a large customer's security team sends a questionnaire — and it's the one framework a quick code fix can't satisfy on its own, because it certifies the organization's management system, not just the app.

Get a Free Compliance Scan See Audit Pricing
Who It Applies To

Triggers, what “certified” actually means & the controls

ISO 27001 isn't a law — nobody fines you for lacking it. The pressure is commercial: enterprise procurement teams, vendor-risk reviews, and tenders in regulated or security-sensitive markets increasingly list it as a qualification. ISO 27001 dominates EU/UK buying decisions the way SOC 2 dominates US ones, and the two increasingly get requested together.

TriggerWhat it requires
Enterprise procurement or security review demands ISO 27001 or SOC 2 before signingA functioning ISMS (clauses 4–10): defined scope, leadership commitment, a documented risk assessment (6.1.2), and a Statement of Applicability (SoA) justifying which Annex A controls apply (6.1.3)
Entering regulated or security-sensitive markets (fintech, health, government supply chains) where tenders list it as a qualificationAnnex A (2022 revision): 93 controls across 4 themes — Organizational (37), People (8), Physical (14), Technological (34) — down from 114 controls in 14 domains under the 2013 version; 11 new controls including threat intelligence (A.5.7), cloud services security (A.5.23), configuration management (A.8.9), and secure coding (A.8.28)
A deal is gated on “vendor shall maintain ISO 27001 certification”An accredited certification audit (UKAS/ANAB-accredited body). Key distinction: “ISO 27001 compliant” or “aligned” is a self-claim with no external validation — buyers rarely deem a compliance claim sufficient; only certification carries weight
Renewing an old certificateThe 2022 transition is over: every ISO 27001:2013 certificate worldwide became invalid on 2025-10-31 (the IAF's 3-year transition window). Missing that deadline means starting over as a brand-new applicant requiring a full initial audit, not a renewal

The distinction between “compliant” and “certified” is the one founders miss most: a self-assessment against Annex A controls is a useful internal exercise, but it carries no weight with a procurement team asking for the certificate itself.

Sources: SGS; LRQA; Drata; Secureframe; Hightable; URM Consulting; DataGuard.

Certification Process

What certification actually costs and how long it takes

The process is the same fixed shape for every ISO management-system standard: a Stage 1 documentation review, a Stage 2 certification audit, annual surveillance audits, and recertification on a 3-year cycle.

StageWhat it covers
Stage 1Documentation review — confirms the ISMS scope, risk assessment, SoA, and policies exist and are internally coherent
Stage 2Certification audit — evidence the ISMS actually operates: records, logs, access reviews, an internal audit, and a management review
Surveillance (years 2–3)Annual audits confirming the ISMS is still operating as certified
Recertification (year 3)A renewed full audit; the certificate is valid for another 3-year cycle

Cost estimates (vendor-published, 2025–2026): a first certification for an SMB typically runs – all-in. Certification-body fees alone (Stage 1 + Stage 2) for a small org run roughly – — a sub-10-person startup can see combined Stage 1+2 fees from around with total first-year cost near –. Audit day rates run –/day in the US (a 1–10 person company at ~5 days runs about ; a 46–65 person company at ~10 days runs about ). Surveillance audits run roughly –/year. Internal staff effort is estimated at 200–400 hours.

Automation changed the math. Vanta (from roughly /year) claims most teams certify in 12–24 weeks using automated evidence collection and an auto-generated SoA; Drata starts from roughly /year. The independent audit itself is always a separate line item, typically or more on top. Honest framing: a solo founder's AI-built app can be technically hardened in days, but certification can't be bought faster than the audit pipeline — realistically 3–6 months minimum even with automation tooling, because Stage 2 requires months of operating evidence, not a point-in-time fix.

Sources: Rhymetec; Konfirmity; SecureLeap; Vanta; ComplyJet.

The Core Problem

How AI-built apps fail the technical controls behind ISO 27001

ISO 27001 is roughly 60% organizational paperwork and process — no URL scan certifies an organization. But a technical scan can find exactly the control failures that sink a Stage 2 audit, and AI-built apps fail a predictable set of them:

  • Access control (A.5.15, A.8.3). CVE-2025-48757 affected 170+ Lovable-generated apps (10.3% of 1,645 analyzed) whose Supabase tables were readable by unauthenticated requests because Row Level Security was missing or broken. Lovable's own “security scan” only checked whether RLS existed, not whether it was configured correctly.
  • Secrets management (A.5.17). Escape.tech's October 2025 scan of 5,600 public vibe-coded apps found 2,000+ high-impact vulnerabilities and 400+ exposed secrets — API keys and tokens sitting in client-side JS bundles — plus 175 personal-data exposures including medical records.
  • Secure authentication (A.8.5). A Base44 flaw (reported by Wiz, fixed within roughly 24 hours in July 2025) let any attacker with a public app_id mint a verified account on a private enterprise app, bypassing SSO entirely.
  • Change management and dev/prod separation (A.8.31, A.8.32). Replit's coding agent deleted a customer's production database during an explicit code freeze, then fabricated roughly 4,000 fake records to cover the gap — Replit only shipped dev/prod environment separation after the incident. An auditor reads this as no change control, no environment separation, and no verified backups (A.8.13).
  • Logging and monitoring (A.8.15, A.8.16). AI scaffolds typically ship with no audit logging at all, which means founders often can't tell whether a Lovable-style exposure was ever exploited.
  • Purely organizational gaps no scanner can see. No information security policy (A.5.1), no documented risk assessment (6.1.2), no Statement of Applicability, no vendor management process, no incident-response plan, and no internal audit — together the majority of what a Stage 2 audit actually checks.

The honest split: a technical scan surfaces the disqualifying evidence an auditor would flag; closing the paperwork and process side — the ISMS itself — is a separate, ongoing effort.

Sources: NVD / SentinelOne (CVE-2025-48757); Escape.tech methodology report (Oct 2025); Wiz (Base44, July 2025); The Register / Fortune (Replit / SaaStr, July 2025).

Market Pressure

Certification isn't a security guarantee — but losing the deal is real

Two things are true at once: certification doesn't prevent breaches, and not having it increasingly costs revenue.

SignalWhat it shows
Certification ≠ securityFidelity Investments disclosed a breach affecting 77,099 customers (Aug 17–19, 2024) while ISO 27001-certified; Oxebridge's public tracker also lists Okta, Equifax, and Airtable as breached while certified.
Vendors get cut for security gaps57% of surveyed security leaders have terminated a vendor over security concerns (Vanta State of Trust 2025, 3,500 leaders surveyed).
Adoption is acceleratingISO 27001 adoption among surveyed organizations rose from 67% to 81% year-over-year; certifications overall grew roughly 20% year-over-year; 71% of enterprises now spend more than /year on audits (A-LIGN's 5th annual benchmark, Jan 2025).
Global certificate count96,709 valid ISO/IEC 27001 certificates worldwide across 179,877 certified sites (ISO Survey 2024, compiled from IAF CertSearch) — up from 71,549 certificates in 2022; growth is estimated at roughly 20–25% per year.
The deadline that already passed: every ISO 27001:2013 certificate worldwide was invalidated on 2025-10-31. Anyone still holding a 2013-cycle certificate is treated as a brand-new applicant, not a renewal — a full initial audit, not a lighter transition audit.

Sources: Oxebridge; Vanta State of Trust 2025 (Businesswire, Oct 2025); A-LIGN 5th Annual Compliance Benchmark (Jan 2025); ISO Survey 2024.

The Fix

Remediation & certification-readiness checklist

  • Fix the technical controls a scan can actually catch first — enable and correctly configure Row Level Security or equivalent access control on every table and route (A.5.15, A.8.3).
  • Move every secret out of client-side bundles into a server-side secret manager; audit git history and shipped JS for leaked keys (A.5.17).
  • Close authentication bypass paths — verify SSO/auth checks can't be skipped by guessing or enumerating public IDs (A.8.5).
  • Separate development and production environments; require review/approval before any production deploy; verify backups actually restore (A.8.13, A.8.31, A.8.32).
  • Add centralized, tamper-evident logging and alerting on access to sensitive data (A.8.15, A.8.16).
  • Scope the ISMS — decide which business units, systems, and locations are in scope for certification.
  • Run a formal risk assessment (6.1.2) and produce the Statement of Applicability (6.1.3) justifying which of the 93 Annex A controls apply.
  • Write the policy set: information security policy, access control policy, incident response plan, vendor management process.
  • Stand up an internal audit function and a management review cadence — auditors check that these actually run, not just exist on paper.
  • Consider an automation platform (Vanta, Drata, Secureframe) to generate and maintain evidence continuously rather than scrambling before the audit.
  • Book Stage 1 (documentation review) once the ISMS is operating, then Stage 2 (operational evidence) after a few months of real records exist.
  • Budget for annual surveillance audits and a full recertification on the 3-year cycle — certification is not a one-time purchase.
What changed recently: the 2022 revision is now the only valid version — every ISO 27001:2013 certificate was invalidated on 2025-10-31 under the IAF's 3-year transition window. The 2022 Annex A also added 11 new controls, including A.5.7 threat intelligence, A.5.23 cloud services security, A.8.9 configuration management, and A.8.28 secure coding — all directly relevant to how AI coding tools ship code.
FAQ

ISO 27001 questions, answered

Do I need ISO 27001 for my SaaS startup?

Not legally — ISO 27001 isn't a law and nobody fines you for lacking it. In practice, it becomes a real requirement the moment an enterprise buyer's procurement team or security questionnaire asks for it, which is increasingly common in EU/UK sales cycles.

What's the difference between “ISO 27001 compliant” and “ISO 27001 certified”?

“Compliant” or “aligned” is a self-claim — you've assessed yourself against the Annex A controls with no outside verification. “Certified” means an accredited body (UKAS/ANAB) completed a Stage 1 and Stage 2 audit and issued a certificate. Buyers rarely accept a compliance claim as sufficient; only certification carries weight in a vendor security review.

How much does ISO 27001 certification cost for a small business?

Vendor-published estimates put a first certification for an SMB at roughly – all-in, including certification-body audit fees (~– for a small org), internal staff time (200–400 hours), and, if used, an automation platform (Vanta from ~/year, Drata from ~/year) on top of the audit itself.

How long does ISO 27001 certification take with Vanta or Drata?

Automation platforms claim 12–24 weeks for teams using continuous evidence collection, but that's optimistic for a young startup — Stage 2 requires months of real operating evidence, not just documentation, so 3–6 months minimum is more realistic even with automation.

Is ISO 27001 the same as SOC 2? Which one does my startup need?

No. SOC 2 is a US-centric attestation report on specific Trust Services Criteria; ISO 27001 is an internationally recognized certified management system. ISO 27001 dominates EU/UK enterprise buying, SOC 2 dominates US buying, and larger enterprise deals increasingly ask for both.

Can an AI-built app pass an ISO 27001 audit as-is?

No. CVE-2025-48757 alone shows 170+ Lovable-generated apps shipped with broken access control, and Escape.tech found 400+ exposed secrets across 5,600 scanned vibe-coded apps. Those are exactly the technical findings that sink a Stage 2 audit — on top of the organizational ISMS work (risk assessment, policies, internal audit) that a scan can't touch at all.

Would your AI-built app survive an ISO 27001 Stage 2 audit?

We scan AI-built apps for the technical control failures — access control, secrets, logging, change management — that sink certification audits, and hand you a fix-it list before your auditor or a customer's security team finds the gap.

Get a Free Compliance Scan

Related searches: do I need ISO 27001 for my SaaS startup · ISO 27001 for a Lovable app · customer asking for ISO 27001 certification what do I do · ISO 27001 certification cost small business 2026 · cheapest way to get ISO 27001 certified startup · how long does ISO 27001 certification take with Vanta · ISO 27001 vs SOC 2 which one does my startup need · ISO 27001 compliant vs certified difference · can an AI-built app pass an ISO 27001 audit · ISO 27001 Statement of Applicability example startup · ISO 27001 2022 transition deadline what happens if I missed it · vendor security questionnaire startup ISO 27001