Free Assessment

Table of Contents

Reach SOC 2 Compliance in 6 Weeks or Less.

Request a Demo

Home

  /

  / Vanta Agent Explained: Monitoring, Limitations & MDM Alternatives

Vanta Agent Explained: Monitoring, Limitations & MDM Alternatives

Picture of Pedro Dias
Copy Link

The Vanta agent checks four things on a laptop: whether the disk is encrypted, whether a password manager is installed, whether antivirus is running, and whether the screen locks on its own. That is the entire job. It is a lightweight background program that reports those signals back to Vanta so your compliance evidence stays current without anyone emailing screenshots to an auditor.

Most of the confusion around it comes from one of two directions: people expect it to manage their fleet like a full device-management platform, or they worry it reads far more than it does. Neither is true, and the gap between those two assumptions is where this guide lives.

What follows covers what the agent collects, what it deliberately ignores, how it talks to the Vanta platform, how it stacks up against a full MDM, and which compliance frameworks the evidence ends up supporting.

Vanta Agent Explained

What Is the Vanta Agent?

The Vanta agent is a small program installed on employee computers to continuously confirm that each device meets a short list of security requirements. If you have seen it referred to as the Vanta Device Monitor, that is the same product under an earlier name. The two terms are interchangeable.

Under the hood, it runs a hardened build of osquery, an open-source framework that exposes operating system state as a queryable SQL database. Vanta ships a modified version that strips out the tables it considers risky, which is why the agent can read a disk-encryption flag but cannot pull your browser history or SSH keys.

It is read-only by design. It inspects configuration and reports back; it never changes a setting on the machine. Vanta positions it primarily for smaller fleets, generally companies running fewer than about 75 devices, where standing up a full management platform would be overkill.

Reach SOC 2 Compliance in 6 Weeks or Less

Schedule Your Free SOC 2 Assessment Today

Schedule

What Does the Vanta Agent Do?

The agent exists to turn a recurring manual chore — proving that every laptop is configured securely — into something that happens quietly in the background.

Continuous Device Monitoring

Once installed, the agent keeps tabs on the device’s security posture on an ongoing basis rather than at a single point in time. This matters because audits care about whether a control held throughout the period, not whether it happened to be true the morning someone took a screenshot. Continuous checks caught the laptop with encryption switched off last Tuesday.

Automated Compliance Checks

Each signal the agent gathers maps to a control your auditor wants evidence for. Instead of chasing employees for proof that their disk is encrypted, the check runs automatically, and the result flows into Vanta as evidence. The work that used to eat days of an onboarding cycle collapses into a background process.

Real-Time Security Posture Tracking

The findings appear in Vanta as pass or fail states against each requirement, so a security lead can see fleet-wide compliance at a glance. A device that drifts out of compliance surfaces quickly, which shortens the window between a problem appearing and someone noticing it.

What Information Does the Vanta Agent Collect?

This is the question employees actually care about, and the honest answer is reassuring: the agent collects security configuration, not content. It does not transmit passwords, environment variables, SSH keys, emails, or browsing history. It reads whether protections are switched on, not what you are doing with the machine.

Insider Note: The reason the agent cannot snoop even if someone wanted it to is architectural, not a policy promise. Vanta deploys a modified osquery build that removes the tables capable of reading sensitive content. The dangerous queries are not blocked at the dashboard; they are absent from the binary. That distinction is worth raising directly when an employee pushes back on installation.

Operating System and Version Details

The agent records the OS and version so Vanta can confirm the device runs a supported, patchable platform. An end-of-life operating system is a control failure in its own right, and this is how it gets flagged.

Disk Encryption Status

It checks whether full-disk encryption is active — FileVault on macOS and BitLocker on Windows. This is the single most universally required device control across every major framework, which is also why it is the one Linux check the agent does support.

Screen Lock and Password Policies

The agent verifies that the screen locks automatically after a period of inactivity and that a password or equivalent is required to get back in. An unlocked laptop left on a train is a textbook breach, and this control is the cheapest defense against it.

Antivirus and Firewall Status

It confirms that antivirus or endpoint protection software is installed and running. The point is not to endorse a particular product but to prove that some recognized protection is active and has not been quietly disabled.

Installed Software and Auto-Update Settings

To detect the controls above, the agent reads the list of installed applications — for example, to confirm a password manager is present — along with update-related settings. It is reading the inventory to verify protections exist, not building a behavioral profile of the user.

Reach SOC 2 Compliance in 6 Weeks or Less

Schedule Your Free SOC 2 Assessment Today

Schedule

How Does the Vanta Agent Work?

How the Agent Communicates with the Vanta Platform

After installation, the employee registers the device against your Vanta account, which links that machine to its owner. From then on the agent runs its checks locally and sends only the results — the pass or fail signals — up to Vanta over an encrypted connection. The raw system queries stay on the device. What travels is the verdict, not the underlying data.

How Often the Vanta Agent Runs Checks

The agent uses osquery’s scheduled-query model, meaning each check runs on a recurring interval in the background rather than continuously hammering the system. Results sync to Vanta periodically through the day, and the platform’s tests re-evaluate on a regular cadence so a freshly remediated device clears its failing check without anyone forcing a manual refresh. In practice, a fixed laptop usually shows green within hours, not at the next audit.

Install Vanta Agent

Getting Started with the Vanta Agent

Supported Operating Systems and Versions

The agent supports current versions of macOS and Windows, plus several Linux distributions — primarily Ubuntu and close relatives — on the condition that the device exposes a stable, unique hardware identifier. There is one significant caveat on Linux: the agent can only check disk encryption there. Screen lock, antivirus, and password-manager detection are not available on Linux, so those controls will need manual evidence or MDM coverage on Linux machines.

How to Install the Vanta Agent

Installation is a per-device download. The employee logs into Vanta during onboarding, downloads the installer for their operating system, runs it with administrator rights, and completes a short browser-based registration that ties the device to their account. No additional configuration is needed; the agent arrives ready to work with your account.

Pro Tip: Two avoidable issues cause most failed installs. The installer needs administrator permissions, so run it as admin from the start. It also opens a browser window to finish registration, which means a machine with no default browser set will hang and time out. Set a default browser before you begin, and temporarily pause aggressive antivirus that may block the install.

Assigning Device Monitoring Tasks to Personnel

Rather than chasing installs individually, you assign a “Require device monitoring” task to the relevant employee group in Vanta. With the prompt option enabled, employees are walked through installing the agent themselves, and the task passes automatically once their computer registers. For teams using an MDM instead, you can assign the same requirement without prompting for the agent.

Reach SOC 2 Compliance in 6 Weeks or Less

Schedule Your Free SOC 2 Assessment Today

Schedule

Vanta Agent vs. Mobile Device Management (MDM) Solutions

The agent and an MDM solve overlapping problems with very different scope. The agent is a compliance-evidence sensor. An MDM is a management platform that can also enforce and remediate. Understanding where that line sits will save you from reaching for the wrong tool.

The agent reads configuration and reports it; it cannot push a fix. An MDM can lock a device remotely, enforce a policy centrally, and wipe a machine that has gone missing. At the same time, an MDM typically requires more infrastructure, more administrative overhead, and meaningful per-seat cost. The agent, by contrast, is included in Vanta’s platform and takes minutes to deploy.

The practical dividing line is fleet size and risk appetite. For a team of twenty, the agent usually provides everything a SOC 2 auditor needs at the device level. For a team of two hundred spread across multiple office locations, the inability to remotely enforce or remediate becomes a genuine gap — and that is where a full MDM earns its keep.

When to Use the Vanta Agent

Reach for the agent when you are a smaller or earlier-stage company that needs solid compliance evidence without the cost and administrative weight of a management platform. It is also the right tool for filling coverage gaps — such as the Windows laptops your macOS-only MDM cannot see.

When to Use an MDM Integration Instead

As the fleet grows, the limits of a read-only sensor start to show. An MDM lets you enforce configuration rather than just observe it, push fixes centrally, and manage devices at a scale where chasing individual installs stops being realistic. Larger organizations and anyone needing remote lock or wipe should lean on an MDM as the system of record.

Using Both Together

These are not mutually exclusive. A common pattern is to run an MDM as the primary monitoring source and keep the agent as a secondary option for devices the MDM does not cover. If a computer reports through both, Vanta simply shows both sources. You get the enforcement of the MDM where it reaches and the agent’s coverage everywhere else.

Integrating the Vanta Agent with Your Existing Tools

MDM Integrations Supported by Vanta

Vanta connects with several widely used MDM platforms, including Jamf, Kandji, and JumpCloud, configured from the Integrations page in your dashboard. When an MDM is connected, devices it manages stay visible for monitoring without the agent installed, and unmonitored-device tracking adjusts accordingly. The choice between sources is yours to set per task.

Viewing and Managing Company Computers in Vanta

The Computers page is the single view of every device under monitoring, whether the data comes from the agent or an MDM. Each row shows a machine, its owner, and a column of check marks or X’s — one per security control. A green check means the control is met; an X means it is not. Clicking a user opens their fuller profile, including onboarding and access status alongside their device details.

Vanta Compliance Frameworks

Which Compliance Frameworks Does the Vanta Agent Support?

A clarification first, because this is where expectations run ahead of reality. The agent does not “support a framework” the way a product supports a file format. It supplies one category of evidence — endpoint security configuration — that maps to specific controls inside many frameworks. The frameworks themselves are far broader, covering policies, access management, vendor risk, and much more that has nothing to do with a laptop.

SOC 2

SOC 2, defined by the AICPA, is built around five Trust Services Criteria, and the device controls the agent checks feed directly into the Security criterion. Encryption, access control, and endpoint protection evidence are routine asks in a SOC 2 audit, and the agent automates the device-level portion of that.

ISO 27001

ISO/IEC 27001 is the international standard for information security management systems. Its Annex A controls include explicit expectations around endpoint security and cryptography, and the agent’s encryption and protection checks line up with those control objectives.

HIPAA

For organizations handling protected health information, the HIPAA Security Rule, administered by the U.S. Department of Health and Human Services, requires safeguards for electronic PHI. Device encryption and access controls are core technical safeguards, and the agent provides ongoing evidence that they are in place.

GDPR

The General Data Protection Regulation requires appropriate technical measures to protect personal data, with encryption named explicitly as an example in Article 32. The agent’s monitoring helps demonstrate that devices touching EU personal data meet that bar on an ongoing basis.

FedRAMP

FedRAMP governs cloud services used by U.S. federal agencies and is the most demanding of the group by a wide margin. Worth flagging: in 2026 the program shifted its core terminology, now describing approved services as FedRAMP certified rather than authorized. The agent’s device evidence is a small input into a far larger continuous-monitoring obligation here — not anything close to the whole picture.

Important: Installing the agent and turning every check green does not make you compliant with any of these frameworks. The device controls are one slice of evidence among dozens. Treating a fully green Computers page as “we passed SOC 2” is the most common misread of what the agent actually buys you.

Reach SOC 2 Compliance in 6 Weeks or Less

Schedule Your Free SOC 2 Assessment Today

Schedule

Conclusion

The agent is a focused tool that does one job well: it keeps your device-security evidence current and honest without manual effort. It reads configuration, never changes it, and reports only verdicts rather than content. For smaller fleets it can carry the device-monitoring load on its own; for larger ones it works best as a complement to an MDM. Match it to your fleet size and your framework’s real requirements, and it quietly removes one of the more tedious parts of staying audit-ready.

Frequently Asked Questions About the Vanta Agent

Is the Vanta Agent the Same as the Vanta Device Monitor?

Yes. They are two names for the same software. Older documentation and some installers refer to the Vanta Device Monitor, while the agent is the current name. There is no functional difference.

No. It does not transmit passwords, emails, browsing history, environment variables, or SSH keys. It reads security-configuration flags — such as whether encryption is on — and reports the results. The sensitive osquery tables are removed from the build entirely.

Yes, and this is a useful point to share with skeptical staff. Because the agent runs osquery, a technically inclined employee can inspect the exact set of queries it executes on their machine using the agent’s command-line tools. Nothing about what it checks is hidden.

The device shows an X against the failing control on the Computers page, and the corresponding Vanta test flags as failing. Remediation is usually straightforward — for example, switching encryption back on — and once the agent’s next check picks up the fix, the status clears on its own.

Partially. The agent runs on several Linux distributions, mainly Ubuntu and close variants, but it can only check disk encryption there. Screen lock, antivirus, and password-manager detection are not supported on Linux, so those controls need manual evidence or an MDM for Linux devices.

The agent includes a built-in diagnostic tool — run via its command-line interface as vanta-cli doctor — which checks for common problems and reports what it finds. On Windows you run it from an administrator command prompt. The device also appearing on your Computers page is the simplest confirmation that it is reporting.

It can be pushed to many machines, including through MDM-delivered install scripts, but Vanta recommends it mainly for fleets under roughly 75 devices. Beyond that size, a dedicated MDM is the better backbone, with the agent filling gaps the MDM cannot reach. Scale is exactly the line where most teams graduate from the agent to an MDM-first setup.

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.
Copy Link

Blog Highlights

Explore More Articles

Read More Blogs

LiteLLM Supply-Chain Breach: How to Check If You’re Exposed and What to Rotate

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

Read more

EU AI Act Recruitment Rules: What to Know for 2027

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.

Read more

4 SOC 2 Controls Auditors Reject Even When Your Compliance Tool Says Passing

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.

Read more