Skip to main content

SOC 2 CC6 audit preparation

A CC6 Checklist Built From Real Audit Findings

Prepare for your next SOC 2 Type II examination using the exceptions practitioners see again and again.

Every audit turns into a frantic evidence-gathering scramble.

You know the controls are in place, but when fieldwork starts the real work is reconstructing evidence that survives a test of controls. Access was granted, reviews were run, accounts were disabled, yet the artifacts do not line up with what the auditor asks for. CC6 generates more audit exceptions than any other trust services criteria category, and most of those exceptions trace back to controls that exist on paper but are not embedded in day-to-day operations. The gap between having a control and proving it operated is where programs break down.

Free 25-page industry report

Get the report

State of SOC 2 Access Control Findings: What Auditors Flag Under CC6. A practitioner analysis of the access-control exceptions that surface most often in SOC 2 Type II examinations, mapped to the CC6 criteria, with the evidence auditors expect and a ranked plan to reduce findings before the next audit.
  • Priority fix list ranked by finding frequency
  • The CC6 points of focus auditors benchmark against
  • A structured CC6.1-CC6.8 checklist to validate before fieldwork
State of SOC 2 Access Control Findings

Send me the report

Instant access, straight to your inbox.

Verifying you're human...

CC6.1-CC6.8
Each criterion is a distinct control objective tested independently, so strength in one area does not offset weakness in another.
1 in 25
A single missing approval ticket in a 25-item sample can be enough to produce a noted deficiency.
24 hours
A common involuntary-termination revocation window; one account live beyond it can fail the deprovisioning control.
9 chapters
Findings analyzed across the full access lifecycle, from provisioning through deprovisioning and physical access.

What the auditor will actually pull and flag.

The report walks through how a test of controls produces a documented exception: the auditor selects a sample, traces each item to its evidence, and records a finding when the evidence is missing, reconstructed, or contradicts the control description. It shows why that same pattern recurs across engagements, and critically, it separates design deficiencies from operating-effectiveness failures. Misdiagnosing one as the other wastes remediation effort and produces another exception in the next cycle.

INSIDE THE REPORT
A priority fix list ranked by finding frequency, with the minimum acceptable remediation per category
The CC6 points of focus auditors benchmark your control design against
What a defensible evidence chain looks like for provisioning, access reviews, and deprovisioning
Why deprovisioning is the highest-priority fix and largely technical to close
How to build continuous evidence collection so the audit sprint disappears
A structured CC6.1-CC6.8 checklist to validate before fieldwork

Walk in knowing where the findings will land

You can anticipate the specific evidence gaps auditors test for instead of discovering them during fieldwork.

Remediate in the order that moves the needle

You sequence fixes by how often each category appears and how quickly remediation affects the outcome.

Fix the right type of problem the first time

You respond to a design deficiency with a control change and an operating failure with process correction, not the reverse.

Replace the sprint with a routine

You structure provisioning, review, and deprovisioning evidence to be captured automatically, so the last-minute scramble stops repeating.

Real SOC 2 Type II examinations

Drawn from SOC 2 Type II examinations across SaaS, managed services, healthcare technology, and financial services organizations.

Mapped to the Trust Services Criteria

Mapped to the AICPA Trust Services Criteria CC6.1 through CC6.8 and their points of focus.

ISO/IEC 27001 reference framework

Incorporates ISO/IEC 27001 Annex A control 8.2 (Privileged Access Rights) as a reference framework.

A six-category priority fix table

Includes a six-category priority fix table with minimum acceptable remediation per finding type.

No. It is a pattern analysis of practitioner-observed exceptions across a non-statistical sample. Use the categories as a structured checklist, and confirm specific requirements against the current AICPA Trust Services Criteria and your appointed auditor.

Instant access, straight to your inbox

Walk into fieldwork knowing exactly what gets pulled

Close the gaps in the order that matters most, before your next SOC 2 Type II examination.