Table of Contents

Reach SOC 2 Compliance in 6 Weeks or Less.

  /

  / CMMC Certification Cost: Complete Pricing Breakdown 2026

CMMC Certification Cost: Complete Pricing Breakdown 2026

CMMC certification costs between $4,000 and $30,000 at Level 1, $30,000 to $300,000 or more at Level 2, and $100,000 to well over $1 million at Level 3. Most contractors expect the audit fee to be the big number. It isn’t. The formal assessment typically accounts for only 25% to 40% of total spend, with preparation, remediation, and technology upgrades consuming the rest.

The stakes changed in late 2025. The final 48 CFR acquisition rule took effect on November 10, 2025, which means CMMC requirements now appear directly in Department of Defense (DoD) solicitations and contracts. Starting in November 2026, Phase 2 of the rollout gives contracting officers the authority to require third-party certification for Level 2 work. If you handle Controlled Unclassified Information (CUI), certification is no longer optional, and the cost question becomes a budgeting exercise rather than a hypothetical.

This guide breaks down every major cost category, what moves your number up or down, and how to keep the total under control.

What Is CMMC Certification and Why Does Cost Vary?

The Cybersecurity Maturity Model Certification (CMMC) is the DoD’s framework for verifying that companies in the Defense Industrial Base (DIB) actually protect the sensitive information they handle. The program, codified in 32 CFR Part 170, builds on the security requirements of NIST SP 800-171 and, at the top tier, selected controls from NIST SP 800-172.

Costs vary so widely because you can’t buy CMMC off a shelf. Your environment has to reach a certain state and then stay there. A 15-person machine shop with one well-scoped CUI enclave faces a fundamentally different project than a 500-person prime contractor with CUI flowing through a dozen systems. Your starting security posture, the scope of your assessment boundary, and whether you build internally or hire help all move the total by six figures in either direction.

Let Axipro help you build a business continuity plan that's practical, compliant, and audit-ready.

Schedule Your Free Assessment Today

Average CMMC Certification Cost at a Glance

The DoD’s own published estimates are instructive. A triennial Level 2 certification assessment, including affirmations, is projected at roughly $105,000 for small entities and $118,000 for larger ones. Those figures cover only assessment and affirmation activities, though. The DoD excludes implementation costs from its estimates on the grounds that NIST SP 800-171 compliance has been contractually required under DFARS 252.204-7012 since 2017. Your real budget has to cover both.

CMMC Certification Cost

CMMC Certification Cost by Level

CMMC Level 1 (Foundational) Cost: $5,000 – $30,000

Level 1 covers Federal Contract Information (FCI) and requires 15 basic safeguarding practices drawn from FAR 52.204-21. Because Level 1 permits an annual self-assessment with no third-party auditor, the costs are internal labor, basic tooling, and documentation. Small contractors with reasonable IT hygiene often land near the bottom of the range. The DoD estimates annual Level 1 assessment and affirmation activity at around $6,000 for a small entity, with the remainder of the range driven by any remediation needed to attest honestly.

CMMC Level 2 (Advanced) Cost: $50,000 – $300,000+

Level 2 is where most of the DIB lands and where budgets get serious. It requires full implementation of all 110 security requirements in NIST SP 800-171, assessed across 320 individual objectives. For most contracts, a C3PAO (Certified Third-Party Assessor Organization) accredited by the Cyber AB has to conduct the assessment every three years.

Market data puts C3PAO assessment fees at $30,000 to $100,000 depending on scope, site count, and complexity. Preparation dwarfs that figure for most organizations. Companies starting from a low maturity baseline routinely spend three to four times the assessment fee on readiness work before an auditor ever shows up.

CMMC Level 3 (Expert) Cost: $300,000 – $1,000,000+

Level 3 adds 24 enhanced requirements from NIST SP 800-172 on top of a completed Level 2 certification, and the assessment is conducted by the government’s DIBCAC rather than a commercial C3PAO. DIBCAC charges no assessment fee, but don’t mistake free for cheap. The DoD estimated roughly $41,000 in additional implementation cost for the 800-172 controls alone, and total triennial assessment-related costs in the $146,000 to $159,000 range. Real-world totals run far higher once you account for the advanced tooling, threat hunting capability, and organizational changes Level 3 demands. Only contractors supporting the most sensitive programs need this tier.

Worth Knowing: You can't skip to Level 3.

You can't skip to Level 3. A final Level 2 certification with all POA&M items closed is a prerequisite for the same assessment scope, so Level 3 budgets always include a full Level 2 project first.

CMMC Certification Cost Breakdown by Expense Category

Gap Assessment and Readiness Planning Costs

A gap assessment maps your current environment against NIST SP 800-171 and typically costs $1,500 to $20,000 depending on depth and scope. This is the most valuable dollar you’ll spend in the entire project, because everything downstream is priced off what it finds.

Documentation and System Security Plan (SSP) Costs

The System Security Plan (SSP) is the cornerstone document of any assessment, mapping every control to your specific implementation. Professionally developed SSPs and supporting policies run $12,000 to $60,000. A weak SSP is one of the most common reasons assessments stall or fail, so this is a poor place to economize.

Remediation and Security Control Implementation Costs

Closing the gaps is usually the largest line item: $20,000 to $150,000 or more. Multi-factor authentication, logging and SIEM deployment, encryption, access control restructuring, and incident response capability all live here. Organizations with mature security postures spend far less than those starting from scratch.

Technology and Infrastructure Upgrade Costs

Many contractors move CUI into a dedicated enclave rather than securing their entire network. Enclave platforms typically cost $300 to $400 per user per month. Others upgrade endpoint protection, replace unsupported systems, or migrate to government-grade cloud environments, each with its own licensing and migration costs.

C3PAO Assessment and Audit Fees

The formal Level 2 assessment runs $30,000 to $100,000, driven by assessor-days, number of sites, and evidence quality. Well-organized evidence directly reduces assessor time and therefore your invoice.

Consulting and Advisory Fees

Specialist consultants, including Registered Practitioners (RPs) and Certified CMMC Professionals (CCPs), bill roughly $250 to $400 per hour. Engagements range from targeted advisory work to full program management. Many contractors instead retain a Managed Security Service Provider (MSSP), typically starting at $2,000 to $3,500 per month.

Staff Training and Awareness Program Costs

Security awareness training, role-based training for IT staff, and CUI handling training generally cost $2,000 to $10,000 per year. Assessors check for evidence of training, not just a policy saying it happens.

Internal Personnel and Labor Costs

The least visible cost is your own people’s time: evidence collection, interviews, remediation project management, and documentation review pull hours from billable work. Small contractors feel this hardest, with per-employee compliance costs of roughly $2,500 to $4,600 compared with $600 to $1,000 at enterprise scale.

Ongoing CMMC Costs After Certification

Annual Maintenance and Monitoring Costs

Budget $10,000 to $50,000 per year for continuous monitoring tools, vulnerability scanning, log retention, policy updates, and license renewals. Certification reflects a point in time. Your contractual obligation to stay compliant doesn’t expire between assessments.

Recertification Costs (Every 3 Years)

Level 2 certification lasts three years, after which the full C3PAO assessment repeats. Recertification is usually cheaper than the first cycle because the environment and evidence already exist, but plan for the assessment fee plus refreshed documentation and a pre-assessment review.

Continuous Compliance and Reporting Costs

Annual affirmations by a senior official must be filed in the Supplier Performance Risk System (SPRS), and your score has to stay current. False or careless affirmations carry real legal exposure under the False Claims Act, which is why many companies fund an annual internal review before signing.

Important: The affirmation requirement changes the risk calculus entirely. An executive personally attests to compliance every year, and the Department of Justice has actively pursued False Claims Act cases over cybersecurity misrepresentations. Treat annual affirmations as a compliance event with evidence behind them rather than a formality.

Key Factors That Influence Your CMMC Certification Cost

Company Size and Number of Employees

More users mean more endpoints, more accounts, more training seats, and more assessment hours. Costs scale with headcount, though per-employee cost falls as fixed expenses spread across more staff.

Scope of Controlled Unclassified Information (CUI)

Scope is the single biggest cost driver. CUI touching every system means every system is in scope. CUI confined to a tight enclave means the assessment boundary, and the bill, shrinks accordingly.

Existing Cybersecurity Maturity and Posture

A contractor already operating close to NIST SP 800-171, perhaps with SOC 2 or ISO 27001 in place, inherits significant control overlap and spends far less on remediation than one starting cold.

Cloud vs. On-Premise Environment

Cloud environments with strong compliance inheritance, particularly FedRAMP-authorized services, reduce the number of controls you need to build yourself. Legacy on-premise infrastructure often requires expensive upgrades or segmentation.

Internal Resources vs. Outsourced Support

In-house expertise converts consulting fees into salary you already pay. Most small and mid-size contractors blend the two: internal ownership of the program, external specialists for gap assessment, SSP development, and mock audits.

Timeline and Urgency

Compressed timelines cost more. Rushed remediation means premium consulting rates, expedited procurement, and less time to optimize scope. With C3PAO capacity tightening ahead of the November 2026 Phase 2 milestone, late movers will also face scheduling backlogs.

 

Hidden and Often Overlooked CMMC Costs

Several costs rarely appear in initial budgets.

  • Flow-down requirements mean prime contractors increasingly demand proof of compliance from subcontractors before the government does, sometimes on short notice.
  • External Service Providers (ESPs) that touch your CUI can fall within your assessment scope, adding coordination and evidence-gathering work. Productivity dips during remediation, assessment scheduling delays, and re-assessment fees for failed controls all add up.
  • So does the cost of closing POA&M (Plan of Action and Milestones) items within the mandated 180-day window after a conditional certification.

Insider Note: Only 431 organizations held a final Level 2 certification as of October 2025, against roughly 80,000 companies the DoD expects to need one. That mismatch between assessor capacity and demand is a cost factor in itself. Contractors who book C3PAO slots early are already negotiating from a stronger position than those who wait for a contract clause to force the issue.

Let Axipro help you build a business continuity plan that's practical, compliant, and audit-ready.

Schedule Your Free Assessment Today

CMMC Cost Estimates for Small vs. Mid-Size vs. Large Contractors

These are first-cycle figures including preparation. Contractors with strong existing postures can land below these ranges. Those discovering years of deferred IT investment can exceed them.

How to Reduce CMMC Certification Costs

Limit and Segment Your Compliance Scope

Isolate CUI into a defined enclave with strict boundaries. Every system you keep out of scope is a system you neither remediate nor pay an assessor to examine. Scoping decisions made before remediation begins are worth more than any discount negotiated afterward.

Use a Government Community Cloud (GCC High) Environment

Microsoft 365 GCC High and comparable government cloud environments are built for CUI and ITAR data, so you inherit controls instead of building them yourself. Licensing costs more than commercial tiers, but the inherited compliance typically outweighs the premium for CUI-heavy organizations.

Use Compliance Automation Tools

Governance platforms that automate evidence collection, control monitoring, and documentation reduce both consultant hours and internal labor, and they make the triennial re-assessment much cheaper by keeping evidence current year-round.

Use Pre-Built Policy Templates and Documentation

Starting policies and the SSP from proven templates instead of a blank page cuts documentation costs substantially. Templates still require tailoring, and assessors can tell when they haven’t been, but the drafting effort drops by half or more.

Choose the Right C3PAO and Consultants

Get quotes from multiple C3PAOs listed on the Cyber AB Marketplace and compare methodology, not just price. A cheap assessor who drags out the engagement or fails controls that a readiness review would have caught costs more in the end. The same logic applies to consultants: defense-sector experience matters more than hourly rate.

Pro Tip: Ask any Prospective C3PAO

Ask any prospective C3PAO for their assessment-day estimate in writing, broken down by control family, before signing. The spread between quotes usually comes from differing scope assumptions rather than differing rates, and surfacing those assumptions early prevents mid-engagement change orders.

How to Budget for CMMC Certification: A Step-by-Step Approach

Start by confirming which level your contracts actually require, then commission a gap assessment to establish your baseline. Price remediation from the gap findings, not from generic benchmarks, and phase the work so quick wins land first. Reserve the C3PAO engagement early, then hold 15% to 20% contingency for the findings every project surfaces. Finally, build the ongoing annual costs into your indirect rate structure so maintenance is funded before it’s needed rather than scrambled for afterward.

CMMC Certification Cost FAQs

How much does a CMMC Level 2 audit cost?

The C3PAO assessment itself typically costs $30,000 to $100,000, depending on scope, sites, and complexity. The DoD’s own estimate for the full triennial assessment and affirmation cycle is roughly $105,000 for small entities. Preparation and remediation sit on top of that figure.

Small businesses pursuing Level 2 typically spend $50,000 to $140,000 for a first certification cycle, including gap assessment, remediation, documentation, and the C3PAO fee. Level 1 self-assessment usually costs $5,000 to $30,000.

There’s no direct reimbursement program, but compliance costs are generally allowable indirect costs and can be built into your rates. Talk to your DCAA-savvy accountant about structuring them properly.

Level 2 and Level 3 certifications last three years, so the assessment cost recurs on a triennial cycle. Annual affirmations in SPRS and ongoing maintenance costs continue every year in between.

Only where your contract allows it. Level 1 always permits self-assessment, and a subset of Level 2 contracts accept a self-assessment filed in SPRS, at a fraction of C3PAO cost. Most Level 2 work involving sensitive CUI requires third-party certification, especially from Phase 2 onward.

Most Level 2 projects take 6 to 18 months from gap assessment to certificate. Longer timelines spread costs and allow cheaper, deliberate remediation. Compressed timelines inflate consulting fees and procurement costs, and assessor scheduling backlogs make last-minute certification increasingly expensive as the November 2026 milestone approaches.

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.