SOC 2 ControlsAccess ReviewsCC6IAMAutomationSOC 2

Automating User Access Reviews for SOC 2 CC6.3

How to run quarterly access reviews that satisfy SOC 2 CC6.3, reduce manual effort, and generate clean audit evidence automatically.

SecureSpect Team··7 min read

What SOC 2 CC6.3 Requires

CC6.3 requires that your organization implements controls to restrict logical access to systems and data to authorized individuals, and that you periodically review access rights to ensure they remain appropriate. In practice, this means:

  • A documented process for granting access (provisioning)
  • A documented process for revoking access (de-provisioning)
  • Periodic reviews — at least quarterly for privileged access, annually for standard access
  • Why Access Reviews Fail in Practice

    Most access review failures are operational, not conceptual. Companies know they need to run reviews but:

    • No one owns the process
    • The review is done via email with no structure
    • Results aren't documented with enough detail for auditors
    • Reviews are run once before the audit, not quarterly as required

    The fix is a structured, automated workflow that removes the friction.

    What a Proper Access Review Captures

    For each access review cycle:

    • Date the review was initiated and completed
    • Reviewer identity (name + role)
    • List of users reviewed (name, role, access level)
    • Decision per user (approved, modified, or revoked)
    • Actions taken (confirmation that revocations were executed)
    The auditor needs to see this documentation for every review cycle during the observation period.

    Setting Up Automated Reviews in SecureSpect

    SecureSpect imports your user-application access data from connected identity providers (Okta, Entra ID, Google Workspace) and creates structured review campaigns:

  • Go to Access Reviews → Create Review Campaign.
  • Select the scope: All production systems or specific integrations.
  • Set the recurrence: Quarterly (Jan / Apr / Jul / Oct).
  • Assign reviewers: manager per user, or system owner.
  • Set completion deadline: 10 business days.
  • When the campaign launches, reviewers receive an email with a link to their review list. They approve or revoke each access entry in the SecureSpect UI. All decisions are timestamped and attributed.

    Handling Orphaned Accounts

    Orphaned accounts — accounts belonging to users no longer at the company — are one of the most common audit findings. SecureSpect flags accounts where:

    • The user is not in your HR system (Rippling, BambooHR integration)
    • The user has not logged in for 90+ days
    • The user has no active account in your SSO provider but still has direct service access

    These accounts appear as high-priority items in each access review campaign.

    Evidence for Auditors

    After each review cycle, SecureSpect generates a PDF summary:

    • Campaign name, date range, and scope
    • Number of users reviewed
    • Breakdown: approved / modified / revoked
    • List of actions taken with timestamps
    • Reviewer attestation

    This PDF is automatically attached to the relevant SOC 2 control evidence record.

    Automate your SOC 2 evidence collection

    Connect your AWS and GitHub environments and start collecting audit-ready evidence today. Free to start.

    Start Free →More Articles