Table of Contents

Reach SOC 2 Compliance in 6 Weeks or Less.

  /

  / How Much Does Vanta Cost? Plans & Real Costs

How Much Does Vanta Cost? Plans & Real Costs

Vanta does not publish a single price on its website. Every quote is custom, generated after a sales call, and shaped by four variables: your headcount, the number of frameworks you need, the add-ons you select, and how long you commit. The median Vanta contract sits around $20,000 per year based on aggregated procurement-platform data, with the full range running from about $10,000 for a lean startup to $80,000 and beyond for a multi-framework enterprise. There is also one cost that most analyses miss: the actual audit fee, which is not included in the Vanta subscription price. This breakdown covers every tier, every hidden line item, and the levers that actually move the number down.

How Much Does Vanta Cost

Vanta Pricing at a Glance

Vanta sells five named tiers, each aligned to a company stage or GRC maturity level. The figures below come from customer-reported benchmarks aggregated by procurement and price-intelligence platforms such as Vendr and PriceLevel, since no list prices exist publicly. Treat them as ranges, not quotes. The audit, paid to an independent firm, sits on top of all of these and typically adds $10,000 to $50,000 depending on framework and scope.

PlanTypical Annual Cost

Best For

Core~$10,000Startups, single framework
Plus$15,000–$30,000Growing teams needing access reviews and questionnaire automation
Growth$25,000–$50,000Scaling companies running multiple frameworks
Scale$50,000–$80,000Formalised GRC or security teams
Enterprise$80,000+Multi-entity, IPO-level, or highly complex environments

Reach SOC 2 Compliance in 6 Weeks or Less

Get 20% to 30% Off Vanta Through Our Partner Discount

Vanta Pricing Plans Explained

Core Plan: Entry-Level Compliance for Startups

Core is the entry point, generally landing around $10,000 per year, with reported deals clustering between roughly $7,500 and $14,000. It covers one framework, usually SOC 2 or ISO 27001, with automated evidence collection, ready-made policy templates, basic integrations, a public-facing Trust Center, and access to Vanta’s network of approved audit firms. Smaller teams pursuing a single framework land at the low end of that range. It is built for the first-time compliance journey, not for running compliance as an ongoing operational function.

Plus Plan: Advanced Features for Growing Teams

Plus typically runs $15,000 to $30,000 per year. It adds the capabilities Core leaves out: automated access reviews, approval workflows, and a capped allowance of automated security-questionnaire responses, commonly cited at 25 per year. That questionnaire cap is the detail that catches growing teams off guard, and it is covered in the hidden-fees section below.

Growth Plan: Built for Scaling GRC Programs

Growth, sometimes sold as the Professional tier, ranges from roughly $25,000 to $50,000 per year and is Vanta’s most commonly sold plan for scaling companies. It supports multiple frameworks, advanced integrations, customisable risk-management workflows, custom monitoring tests for non-standard controls, automated access reviews, advanced reporting, and a far larger questionnaire allotment, often cited at 144 per year. This is the tier for organisations treating compliance as a service and a real business function, rather than a one-time checkbox.

Scale Plan: Expanded Compliance Coverage

Scale pricing starts where Growth tops out and can reach up to $80,000 per year. It is aimed at companies with formalised GRC or security teams, many connected assets, and several frameworks running in parallel. SCIM-based user provisioning and deeper automation across onboarding and offboarding tend to appear at this level.

Enterprise Plan: Fully Custom Pricing

Enterprise is entirely bespoke, starting above $80,000 and quoted case by case. It bundles a dedicated customer success manager, priority support, custom integrations, and tailored implementation. It becomes relevant for organisations managing multiple legal entities, thousands of assets, strict SLA requirements, or IPO-level scrutiny.

Insider note: Vanta’s plan names shift over time and between sales reps. You will see Core called Essentials, and Growth called Professional, in different quotes and on different comparison sites. Anchor your evaluation to what the plan actually includes, frameworks supported, questionnaire allowance, access review automation, rather than the label on the proposal, because the label is the least stable thing about it.

How Much Does Vanta Cost Per Year?

Annual Cost by Company Size and Stage

For a startup under 50 employees chasing a single framework, expect roughly $10,000 to $12,000 per year. Most growing companies pay between $25,000 and $55,000. Larger organisations running multiple frameworks commonly land between $50,000 and $110,000 or more once add-ons and headcount are factored in. The median across all reported deals stays near $20,000, which tells you most buyers sit in the Core-to-Growth band rather than at the extremes.

How Pricing Scales With Company Size and Complexity

Vanta prices primarily on employee count and framework count. Add an employee bracket, and the per-seat-driven base creeps up. Add a framework, and you pay again for the incremental coverage. Complexity compounds this: more cloud accounts, more vendors to assess, and more integrations all push you toward higher tiers and more add-ons. Two companies of identical headcount can pay very different amounts purely on framework count and the modules they bolt on.

How to Negotiate Vanta Pricing

Buy Through a Certified Partner

Certified partners can frequently pass through discounts of 20 to 40 percent off list on multi-year contracts, alongside faster onboarding and implementation support. As a certified Vanta partner, Axipro secures clients 25% off Vanta pricing, and that discount applies on top of the platform’s standard multi-year terms rather than instead of them. The saving is only part of the value. Axipro folds the licence into a consultant-led compliance program, so you get the negotiated rate plus hands-on implementation, framework scoping, and audit preparation, rather than a cheaper login and a blank dashboard. For a team weighing a $25,000 quote, a quarter off the platform cost covers a meaningful slice of the audit fee that Vanta’s subscription never includes.

Negotiate Multi-Year Discounts

A two or three-year commitment is the most reliable discount lever. Vanta will trade a lower annual rate for a longer term and committed future growth. If you expect to add headcount or frameworks, name that expansion in the negotiation and use it to pull the rate down now.

Bundle Frameworks You’ll Need Later

If ISO 27001 or HIPAA is on your roadmap, negotiate for them in the initial deal rather than adding them piecemeal later. Per-framework add-ons bought mid-contract rarely come with the leverage you have during a fresh negotiation.

Time Your Negotiation Around Quarter-End

Sales teams carry quotas, and quotas reset on a calendar. Quarter-end and especially year-end create real pressure to close, which translates into flexibility on price. Time your final conversation accordingly rather than signing whenever the trial of patience runs out.

Defer Add-Ons Until You Truly Need Them

Do not buy Vendor Risk Management or expanded modules on day one because the demo made them look essential. Start with the framework you need to close deals, prove the program, and add modules only when a concrete business requirement appears. Deferred add-ons are deferred cost, and many never become necessary.

Is Vanta Worth the Cost?

Reported ROI and Time Savings

The case for any compliance automation platform rests on time reclaimed, not just certification achieved. Manual evidence collection, control monitoring, and questionnaire responses consume engineering and leadership hours that automation takes back. Customers across the category routinely report saving the equivalent of dozens of hours per month and compressing audit-readiness timelines from quarters into weeks. According to a Forrester Total Economic Impact study commissioned by Vanta, customers reported significant reductions in time spent on compliance activities and faster enterprise sales cycles as a direct result of having a completed SOC 2 report. Faster readiness means faster deals: a completed report can shorten enterprise procurement cycles meaningfully.

Cost Considerations for Startups vs. Enterprise

For a startup, the question is rarely whether to automate but whether the premium tier is justified. A lean team chasing one framework gets most of the value from the entry tier paired with a good auditor. For an enterprise, the calculus flips: the platform cost is small relative to the headcount it saves and the deal velocity it unlocks, and the premium support and multi-framework mapping start to pay for themselves.

What Real Customers Say About Vanta Pricing

Sentiment is broadly positive on the product and more mixed on the commercials. Buyers on review platforms such as G2 and Gartner Peer Insights praise the integration depth, the polished interface, and the auditor experience. The recurring complaints are predictable: opaque quoting, add-ons that inflate the base, and renewal increases. The median reported contract near $20,000 suggests most buyers find the value defensible, but few describe the pricing process as transparent.

Reach SOC 2 Compliance in 6 Weeks or Less

Get 20% to 30% Off Vanta Through Our Partner Discount

Does Vanta Have a Free Plan or Free Trial?

No. Vanta offers neither a permanent free plan nor a public self-serve free trial. Every engagement starts with a demo and a custom-quoted proposal built around your company size, frameworks, and needs. The closest thing to a trial is a guided demo environment arranged through sales. Budget for a paid annual commitment from day one, because that is the only way in.

 

Additional Costs Beyond the Base Subscription

Audit Fees Not Included in Vanta Pricing

This is the single biggest budgeting trap. Vanta’s subscription buys the automation platform, not the certification. The actual audit is performed by an independent CPA firm (for SOC 2) or an accredited certification body (for ISO 27001), and it is billed separately. A SOC 2 Type 1 audit commonly runs $5,000 to $20,000, while a Type 2 report runs $8,000 to $50,000 or more, often quoted around $12,000 to $15,000 for a standard scope. The SOC 2 standard is maintained by the AICPA.

Per-Framework Pricing

Vanta charges per framework. Industry insiders peg each additional framework at roughly $5,000 on top of your base, though the figure scales with company size. A company that starts with SOC 2 and later layers on ISO 27001 and HIPAA is effectively buying three coverage lines, not one. This is why a Core plan quoted at $10,000 can quietly become a $30,000 bill once a second and third framework are added.

Add-On Modules and Features

Several capabilities that buyers assume are core turn out to be paid modules. Customer-reported figures put the Trust Center at around $6,000 per year and Vendor Risk Management at around $11,200 per year. Risk assessment, advanced reporting, and custom monitoring can also sit behind higher tiers or separate line items. Each one is individually reasonable, collectively they reshape the total.

Premium Support and Platform Channels

Standard tiers come with standard support, which in practice means community resources and slower response times. Priority support, a dedicated customer success manager, and direct platform channels generally appear only at Scale and Enterprise. If hands-on guidance matters to a lean team, that need can push you a full tier higher than the feature set alone would justify.

Important: When you compare Vanta quotes against a SOC 2 budget, separate the platform line from the audit line. An all-in first-year SOC 2 program, platform, readiness work, and the CPA audit commonly totals $45,000 to $70,000 for a startup, and more for mid-market environments. The platform subscription is often the smallest of the three numbers, so judging Vanta on that figure alone understates what compliance actually costs.

Vanta vs Top Competitors

Hidden Fees Vanta Doesn’t Advertise

Questionnaire Limits That Scale Costs

Automated security-questionnaire responses are capped by tier. Plus commonly includes 25 per year, and Growth around 144. For a company actively closing enterprise deals, 25 responses evaporates fast. Once you hit the cap, you either upgrade a tier or buy additional questionnaire credits, both of which raise your effective annual cost beyond the headline quote.

Vendor Reviews and Add-On Upsells

Vendor risk reviews, additional user seats, and expanded asset coverage are frequent mid-contract upsells. The platform is engineered to surface gaps in your program, which is genuinely useful, but each surfaced gap tends to map to a module you can purchase to close it. Expect a steady drip of upgrade prompts as your program matures inside the tool.

 

Framework-Specific Vanta Pricing

SOC 2 Costs: Platform and Audit Combined

SOC 2 is the most common starting point. The Vanta platform for a single SOC 2 framework lands near $10,000 for a startup, and the separate Type 2 audit typically adds $8,000 to $50,000. Add a readiness assessment ($5,000 to $15,000) and penetration testing ($10,000 to $15,000), both frequently expected by enterprise buyers, and the realistic all-in first-year figure climbs well past the platform price alone. An internal audit ahead of the formal assessment can also surface gaps before they become findings, and is worth budgeting for separately.

ISO 27001 Pricing and Added Complexity

ISO 27001 carries more structural overhead than SOC 2 because certification involves a two-stage external audit and a three-year certification cycle with annual surveillance audits. The Vanta platform cost is broadly comparable to SOC 2, but the certification-body fees and recurring surveillance audits make the multi-year total higher. The standard itself is published by the International Organization for Standardization.

HIPAA Pricing Depending on Use Case

HIPAA is usually added as a secondary framework rather than bought alone, so its cost shows up as incremental framework pricing on top of an existing SOC 2 or ISO 27001 program. There is no single HIPAA certification audit in the way there is for SOC 2, which changes the cost shape: more of the spend goes to controls, documentation, and risk analysis than to a one-off attestation. The compliance obligations themselves are defined by the U.S. Department of Health and Human Services.

 

Vanta Pricing vs. Top Competitors

Drata and Secureframe are Vanta’s most direct competitors. All three price on employee count and framework count, all three quote custom, and all three keep audit fees separate. The differences show up at the edges: starting price, pricing transparency, and where each platform invests its product development.

Vanta vs. Drata Pricing

Drata’s Foundation tier starts a little lower than Vanta’s Core, around $7,500 to $15,000 for one framework under 50 employees, but its average contract value runs higher than Vanta’s, reflecting a customer base that skews toward larger, multi-framework deals. Drata is frequently cited for class-leading multi-framework mapping and a strong auditor experience. The practical takeaway: similar list ranges, with Drata sometimes cheaper to start and pricier at scale.

Vanta vs. Secureframe Pricing

Secureframe is the transparency outlier, publishing a baseline starting price (around $7,500 to $12,000 for SOC 2) when the rest of the category hides everything behind a sales call. Its median contract matches Vanta’s at roughly $20,000, and it leans hardest into white-glove, managed implementation. For a team with no internal compliance bandwidth, that hands-on support is the differentiator more than the headline price.

The Bottom Line on Vanta’s Cost

Vanta costs most companies somewhere between $10,000 and $80,000 per year for the platform, with a median near $20,000, and the audit adds another $10,000 to $50,000 on top. The headline tier price is only the starting point: frameworks, questionnaire limits, add-on modules, and renewal uplifts all move the real number.

Treat the published-looking ranges as opening positions, separate the platform cost from the audit cost in every comparison, and use multi-year terms, framework bundling, quarter-end timing, and partner discounts to bring the total down. The platform is strong; the work is in making sure you pay for what you actually need.

Frequently Asked Questions

How much does Vanta cost per year?

Vanta starts at approximately $10,000 per year for the Core plan with one framework. Plus typically runs $15,000 to $30,000, Growth $25,000 to $50,000, Scale up to $80,000, and Enterprise above $80,000 with fully custom pricing. The median reported contract is around $20,000 per year.

No. The subscription covers the automation platform only. The SOC 2 or ISO 27001 audit is performed by an independent firm and costs an additional $10,000 to $50,000 depending on framework, audit type, and company size.

Yes. Multi-year commitments, framework bundling, quarter-end timing, and certified-partner channels can all reduce the rate. Partner discounts of 20 to 40 percent on multi-year contracts are commonly reported.

Four main variables: employee headcount, number of frameworks, add-on modules selected (such as Trust Center or Vendor Risk Management), and contract length. Audit fees, readiness assessments, and penetration testing add further cost outside the subscription.

Cost rises with both headcount brackets and framework count, and complexity, more cloud accounts, vendors, and integrations, pushes you toward higher tiers and more add-ons. A company that doubles headcount and adds two frameworks can see its bill multiply significantly.

Vanta offers a large integration ecosystem covering cloud providers, identity systems, and developer tools. Standard integrations are generally included in the base subscription, while advanced provisioning (such as SCIM) and certain enterprise integrations appear only at higher tiers.

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

Two compromised versions of LiteLLM sat on PyPI for roughly 40 minutes on the morning of March 24, 2026. That window was enough to capture secrets from around 434,000 CI/CD pipeline runs across nearly 2,500 organizations, including AWS, Samsung, Cisco, Salesforce, Siemens, and Deloitte. In August, researchers at CloudSEK and Hudson Rock confirmed they had obtained the raw exfiltrated data: a 153GB archive containing 433,909 files of environment variables, cloud keys, Kubernetes secrets, and API tokens harvested live from running pipelines, as covered by Help Net Security’s reporting on the credential archive. If LiteLLM runs anywhere in your stack, or you touch any AI proxy infrastructure at all, you need answers to three things: whether you were exposed, what to rotate first, and whether the rotation you did back in March actually held. That last one matters more than it sounds, because “we rotated everything” has already burned at least one very large company. How the Breach Happened The attack didn’t start with LiteLLM. On March 19, 2026, a threat group called TeamPCP compromised the build pipeline of Trivy, a vulnerability scanner half the industry runs, and pushed a poisoned release. LiteLLM’s own CI pipeline ran Trivy, so the poisoned scanner had legitimate read access to the project’s runner environment. The attackers used that to steal LiteLLM’s PyPI publishing tokens and ship two malicious releases of their own: versions 1.82.7 and 1.82.8. KICS and the Telnyx Python SDK got hit in the same campaign. The payload design is the part worth studying. The malicious package dropped a .pth startup hook into site-packages, so the code ran the moment any Python interpreter started on the machine, whether or not anything imported LiteLLM. From there it harvested environment variables, read local credential files like .aws/credentials and .kube/config, tried to move laterally across Kubernetes clusters, and installed a systemd backdoor dressed up as a generic telemetry service. InfoQ’s coverage of the PyPI compromise put downloads of the compromised release above 40,000. For scale, LiteLLM normally gets downloaded around 3 million times a day. The exfiltration had a nasty fallback, too. According to CloudSEK, stolen data was encrypted and sent to a typosquatted domain, and when that failed, the malware created a public repository inside the victim’s own GitHub account and uploaded the loot as a release asset. Some companies were publishing their own secrets to the open internet and had no idea. Worth Knowing: The malicious code only existed in the PyPI artifacts. The GitHub source repository stayed clean the whole time, so a developer reviewing the code on GitHub saw nothing wrong. Source review isn’t artifact verification. If you don’t check that what the registry serves matches the upstream source, this class of attack is invisible to you. How to Check If You Were Exposed Three checks, from quickest to most involved. 1. Confirm whether the compromised versions ever ran The malicious versions went live on PyPI at 10:39 UTC on March 24, 2026 and got quarantined about 40 minutes later. The project’s advice: treat any install from that day before 16:00 UTC as suspect. Search your lockfiles, pip caches, SBOMs, and container image histories for 1.82.7 and 1.82.8. And check your internal artifact mirrors. An Artifactory or Nexus proxy that cached the bad release in March can keep serving it internally long after PyPI pulled it. Keep the .pth mechanism in mind when you scope this. The question isn’t “which applications import LiteLLM,” it’s “which machines had the package installed at all,” because every Python process on an infected machine triggered the payload. 2. Hunt for persistence Rotation is pointless if the attacker still has a foothold. Check developer machines, CI runners, and containers for unauthorized .pth files in site-packages and for suspicious systemd units, especially anything posing as a system telemetry service. And review activity from March 24 onward, not just the 40-minute window. Persistence is there so the access outlives the infection. Pro Tip: Don’t limit the persistence hunt to live machines. Base container images rebuilt in late March may have baked the payload into every image derived from them since. Scan your image registry for the affected LiteLLM versions and for unexpected .pth files, then trace which running workloads came from flagged images. 3. Check whether your secrets are in the dump Hudson Rock has published a domain lookup tool and is running ethical disclosures for affected organizations, and CloudSEK maintains a high-confidence victim list. Use them, but know their limits. Attribution in this dataset is genuinely hard. One dump with a siriusxm.com committer email actually traced, through its self-hosted GitLab endpoints, to AdsWizz, a SiriusXM subsidiary. And a large share of the dumps are generic pipeline configurations with no identifying domain, email, or server name at all. Absence from a victim list is not evidence of absence. If your pipelines ran the compromised versions, assume exposure no matter what a lookup tool tells you. What to Rotate, in What Order The guidance from both research teams is blunt: treat every secret the LiteLLM environment could reach as compromised. That covers secrets on disk, in memory, injected into CI jobs, and anything retrievable through instance metadata services. Work down by blast radius: Priority Credential type Why it comes first 1 Cloud IAM keys (AWS, GCP, Azure) Direct control of infrastructure, data stores, and billing. This is where attackers monetize fastest. 2 GitHub and GitLab PATs, package publishing tokens These let an attacker poison your releases and turn your company into the next link in the supply chain. 3 Kubernetes service account tokens and kubeconfigs Lateral movement across clusters was built into the payload, not a theoretical risk. 4 Database passwords and third-party API keys Dumped in plain text in the archive, often with no attribution, so nobody will warn you they leaked. 5 AI provider API keys Billing abuse, quota theft, and access to whatever data flows through your LLM routing layer. One word matters more than the rest of this article: revoke, don’t just rotate. That

The EU AI Act names recruitment AI as high-risk. Annex III explicitly lists AI systems used for recruitment, candidate selection, and employment decisions, which pulls CV screeners, video interview platforms, and assessment tools into the most demanding compliance regime the Act contains. The original compliance date for these systems was August 2, 2026. In June 2026, the EU’s Digital Omnibus moved the deadline to December 2, 2027, a 16-month extension that has led many HR and talent teams to shelve the topic entirely. That’s a mistake, for two reasons. First, one rule that directly affects recruitment technology is already in force: the ban on emotion recognition in the workplace has applied since February 2, 2025, and it catches features still shipping in some video interview products today. Second, the deferred obligations didn’t shrink. Conformity assessments, human oversight design, bias monitoring, and documentation all still arrive in full, and the practical work of auditing a recruitment stack, renegotiating vendor contracts, and training hiring teams routinely takes a year or more. Here’s what the EU AI Act actually requires of employers and vendors using recruitment tools, on the timeline that now applies. Why Recruitment Tools Are Classified as High-Risk Under the EU AI Act​ Definition of High-Risk AI Systems in Hiring​ The Act takes a list-based approach. Annex III, point 4, designates as high-risk any AI system intended for the recruitment or selection of natural persons, including placing targeted job advertisements, analyzing and filtering applications, and evaluating candidates. The same point covers AI used for decisions on promotion, termination, task allocation, and monitoring of workers, so the classification follows the tool through the entire employment lifecycle, not just the hiring funnel. The reasoning is straightforward: hiring decisions shape access to livelihoods, and algorithmic discrimination in hiring is well documented. The European Commission’s regulatory framework for AI treats employment as one of the areas where an AI error or bias causes serious harm to fundamental rights. That’s the test for the high-risk tier. Types of Recruitment Tools Affected In practice, the high-risk classification captures most of the modern recruitment stack: CV and resume screeners that rank or filter applicants, video interview platforms that score responses or delivery, psychometric and skills assessment tools that produce scores feeding a hiring decision, sourcing and matching algorithms that decide which candidates a recruiter sees, and programmatic job ad targeting systems that determine who sees a vacancy at all. If the system’s output materially influences who advances and who does not, assume high-risk until proven otherwise. Important: Emotion recognition is not high-risk in the workplace. It is prohibited. Article 5 bans AI systems that infer emotions of people in the workplace (outside narrow medical and safety cases), and that ban has applied since February 2025 with the Act’s top penalty tier attached. If your video interview vendor markets “engagement scoring” or “sentiment analysis” of candidates, that feature needs to be switched off for EU hiring now, not in 2027. Recruitment Tools That May Fall Outside High-Risk Classification Not everything in the HR stack qualifies. The Act carves out systems performing narrow procedural tasks that do not materially influence decision outcomes. An applicant tracking system that stores applications, schedules interviews, and sends templated emails is a database with a workflow, not a high-risk AI system. The same goes for tools that transcribe interviews without scoring them, deduplicate candidate records, or generate first drafts of job descriptions for a human to edit. The line is decision influence: the moment a tool ranks, scores, filters, or recommends candidates, it crosses into Annex III territory. Deployers who rely on an exemption must be able to document that assessment, so “we decided it doesn’t count” needs to exist on paper. Extraterritorial Scope: Which Employers Are Covered The Act applies to providers placing AI systems on the EU market and to deployers established in the EU, but it also reaches further: it covers providers and deployers located outside the EU where the output of the system is used in the EU. For recruitment, the consequence is blunt. A US or UK company with no EU entity that uses an AI screener to filter applicants for roles based in Berlin or Dublin, or that screens candidates located in the EU, is using the system’s output in the Union. Brexit doesn’t move UK employers out of scope when they hire into or from the EU. Providers vs. Deployers of Recruitment AI Tools The Act splits obligations between the provider (the vendor that develops the tool and places it on the market) and the deployer (the employer using it). Most employers are deployers, and deployer obligations are lighter but real. One common trap: an employer that substantially modifies a high-risk system, or puts its own name on it, can be reclassified as a provider and inherit the full provider stack. Heavy customization of a screening model, or fine-tuning it on your own hiring data, can be enough to trigger this. Key Obligations for Employers Using AI Recruitment Tools Human Oversight in Automated Hiring Decisions Deployers must assign oversight of the system to people with the competence, training, and authority to intervene. That last word matters. A recruiter who rubber-stamps whatever the ranking algorithm produces, because nobody has time to review 800 rejected CVs, doesn’t count as oversight. Regulators and courts will look at whether the human could genuinely override the system and whether they ever did. Designing review checkpoints where a person can meaningfully change the outcome, and logging when they do, is the core of compliant deployment. Transparency Requirements Toward Candidates Employers must inform workers and their representatives before putting a high-risk AI system into use at work, and candidates subjected to such a system must be told it is being used. In countries with works councils, such as Germany, this obligation lands on top of existing co-determination rights, so employee representatives may need to be consulted before the tool goes live rather than just told afterward. Burying an AI disclosure in a privacy policy paragraph is unlikely to survive scrutiny.

A green dashboard is not an audit opinion. Compliance automation platforms like Vanta, Drata, Secureframe, and Hyperproof have made SOC 2 readiness faster and cheaper, but every audit cycle produces the same pattern: controls that sat at “passing” for months come back from the auditor with exceptions or requests for re-testing. The four controls below account for a disproportionate share of those rejections, and they all fail for the same underlying reason. The tool confirmed that evidence exists. The auditor tested whether the control actually operated. This article walks through each of the four: what auditors reject, why, and how to fix the evidence before fieldwork starts. Why Compliance Tools Show “Passing” But Auditors Still Reject Controls​ The Gap Between Automated Checks and Auditor Judgment Compliance platforms run continuous control monitoring: API calls that check whether a configuration exists, a document is uploaded, or a task is marked done. That’s real value. It catches drift, keeps evidence in one place, and saves weeks of screenshot collection. An audit is a different exercise. A SOC 2 examination is an attestation performed by a CPA firm under AICPA standards, and the auditor’s job is to form an independent opinion on whether your controls met the Trust Services Criteria. That opinion rests on professional judgment, not on whether an API integration returned a 200 response. What “Passing” Actually Means in Your Compliance Dashboard​ When a control shows “passing,” the platform is telling you one narrow thing: at the moment of the last scan, an automated test found the artifact or setting it was programmed to look for: MFA enforced in the identity provider, a policy document uploaded, a training campaign sitting at 100%. The test says nothing about whether the underlying process ran the way your control narrative claims it did, or whether it ran that way across the whole audit period. How Auditors Evaluate Controls Beyond the Checkbox Auditors test two dimensions. Design effectiveness asks whether the control, as described, would meet the criterion if it worked as intended. Operating effectiveness, the core of a SOC 2 Type 2 report, asks whether it actually did throughout the audit period. To answer that, the auditor pulls a population (every access review, every change, every new hire in the period), selects a sample, and inspects the evidence item by item. A dashboard status feeds into that process. It doesn’t replace it. Insider Note: Auditors increasingly ask for evidence outside the compliance platform precisely because they know what the platform auto-collects. If every artifact you produce comes from the same tool export, expect the auditor to independently pull the population from the source system and compare. Discrepancies between the two are one of the fastest routes to an exception. Control #1: Access Reviews That Automation Marks Complete but Auditors Reject Why Auditors Reject Automated Access Review Evidence​ User access reviews sit under the logical access criteria (CC6.1 through CC6.3), and they are the single most common source of audit exceptions we see. The typical failure: the platform generated a user list, someone clicked “complete,” and the dashboard turned green. The auditor then asks a simple question the evidence can’t answer: what did the reviewer actually decide? The Missing Element: Documented Reviewer Judgment​ An access review is a judgment control. Someone with knowledge of the system must look at each account and confirm the access is still appropriate for the person’s role. A timestamped task closure proves the task was closed. It doesn’t prove anyone assessed anything, and an “approve all” review completed in ninety seconds gets exactly the skepticism it deserves. What Auditors Actually Want to See in Access Review Evidence Auditors look for four things: The full population of accounts at the time of review (including service accounts and admin roles), Evidence of who reviewed it and when, explicit dispositions per account or group (retain, modify, revoke), and Proof that flagged access was actually removed. That last item, the deprovisioning ticket showing revocation within a defined window, is the piece most companies can’t produce. How to Fix Your Access Review Control Before the Audit​ Assign a named control owner per in-scope system, run reviews quarterly, and require reviewers to record a disposition for every line, not a blanket approval. When access is revoked, link the removal ticket to the review record. If a quarter was missed, don’t backfill it. Document it honestly and show the remediation, because auditors treat fabricated retroactive evidence far more severely than a disclosed gap. Control #2: Change Management Approvals That Pass Automated Scans​ Why Ticket Closure Isn’t Proof of Approval​ Change management (CC8.1) automation typically verifies that production changes link to a ticket and the ticket is closed. Auditors test something stricter: that each sampled change was approved by an authorized person before deployment. An approval added after the merge, or a ticket closed by the same engineer who wrote the code, fails that test even though every automated check came back green. The Segregation of Duties Problem Automation Misses Segregation of duties is the requirement that no single person can develop, approve, and deploy the same change. NIST’s SP 800-53 control catalog treats it as a foundational access control principle, and SOC 2 auditors apply the same logic. Small engineering teams trip on this constantly. Self-approved pull requests, admins who can bypass branch protection, direct pushes to main: a scanner sees “changes with tickets” while an auditor sees SoD violations. Emergency Changes and Retroactive Approvals: Common Rejection Triggers​ Every audit period contains hotfixes. Auditors don’t reject emergency changes. They reject emergency changes with no documented post-hoc review. If your policy says urgent changes get retroactive approval within two business days, the auditor will sample your emergency changes and check exactly that. No policy, or a policy nobody followed, produces an exception. Rebuilding Change Management Evidence Auditors Will Accept​ Enforce the control technically: branch protection requiring at least one independent reviewer, no admin bypass, and deploy pipelines that only run from protected branches. Then write the emergency change procedure down and generate the review artifact every time it fires.