How to Keep SOC 2 Controls Green After the Audit

October 30, 2026

Keeping SOC 2 controls passing means keeping a routine: check the failing-controls list weekly, run access reviews quarterly, and never let a control sit red for more than a sprint. Drata tracks all of it — what it cannot do is make someone look at the dashboard.

The failure mode is boring and predictable. Six weeks after the audit, the person who owned compliance changed jobs, nobody picked up the weekly review, and the Type 2 window filled with failed checks.

What changes between Type 1 and Type 2?

Type 1 is design at a point in time: your controls exist and are documented. Type 2 covers an observation window — typically 3, 6 or 12 months — and tests whether controls actually operated.

That is a different job. Type 1 asks “do you have an offboarding checklist?” Type 2 asks “show me all 23 offboardings in the last six months and the evidence each was completed within 24 hours.”

Drata’s continuous monitoring maps directly to Type 2. Which is why buying it for Type 1 only and then going quiet is the most expensive mistake in the process.

What is the weekly routine?

Fifteen minutes, same slot each week. Not a meeting — just someone opening the dashboard.

  1. Tests page → Failed, sorted by control. Anything red for more than seven days needs a ticket.
  2. Personnel tab. New hires not enrolled in security training, or employees whose device agent stopped reporting.
  3. Vendors. New vendors added without a review.
  4. Open risks. The risk register is the first thing an auditor opens; stale entries read as neglect.

The rule that keeps this honest: every red control gets an owner and a due date the moment it turns red, not in the monthly review.

How should access reviews work?

Quarterly, in Drata’s Access Reviews module, with the manager — not IT — approving each person’s permissions.

Managers rubber-stamp. You need friction or the review is theatre: show the actual last-login date next to each permission, and set the default answer to “revoke” rather than “keep”. Change those two settings and the pass rate drops by 10-15%, which is the point.

Drata syncs from Okta, Google Workspace or Entra ID, so the data is real. What it cannot fix is a manager who approves 40 people in 90 seconds.

Which evidence do auditors actually ask for?

Specifics, not summaries. The recurring asks:

  • Evidence a background check ran for every hire in the window, with dates.
  • A list of production changes and which had review approval.
  • The vulnerability scan results for the window — and proof criticals were remediated in your stated SLA.
  • Proof the disaster recovery plan was tested, not just written.

That last one catches most companies. “We have a DR plan” is not evidence. A test record with a date, participants and findings is.

Which integrations break and when?

  • Custom IAM roles. Change a read-only role’s policy and Drata’s checks silently stop passing. Lock the role down with a policy file in your infra repo.
  • GitHub org changes. Renaming repos or teams breaks repo-level checks. Set a naming convention and treat renames as change requests.
  • HRIS migrations. Moving from BambooHR to Rippling breaks personnel checks for days. Do it outside the audit window if you can help it.

Each integration failure shows as an unknown or failed state, not an error you will notice. A weekly glance at Integrations saves the surprise.

The honest downside of automation

Automation produces a lot of green. Green is not the same as secure. A passing MFA control says nothing about whether your admin console has four superadmins and no backup codes.

Use the dashboard for the compliance narrative, and keep one separate security review per quarter that is not Drata-shaped. Otherwise you optimise for the auditor’s checklist and let something real slide.

Key Takeaways

  • Type 1 is design at a point in time; Type 2 tests operation over a 3-12 month window.
  • Block 15 minutes weekly: failed tests, personnel, vendors, open risks.
  • Run access reviews quarterly with managers approving; show last-login dates and default to revoke.
  • Auditors want dated evidence — background checks, change approvals, scan results, a DR test record.
  • Watch integrations monthly; a renamed GitHub repo or changed IAM policy fails silently.
Tags: