Screenata
All SOC 2 Policy Templates
AICPA CC6.1AICPA CC6.2AICPA CC6.3SOC 2ISO 27001HIPAA

SOC 2 Access Control Policy Template (CC6.1)

Quick Summary

A SOC 2 Access Control Policy defines how your company grants, reviews, and revokes access to production infrastructure, source code, and customer data. It is the core policy behind AICPA CC6.1, CC6.2, and CC6.3, and the control family where auditors most frequently ask for both API logs and UI screenshots of admin panels.

Free Markdown Template

Copy or download the access control policy

Replace bracketed [PLACEHOLDERS] with your actual stack

soc-2-access-control-policy.mdMarkdown
# Access Control Policy (SOC 2 CC6.1 – CC6.3)

**Document Owner:** [Security / Engineering Lead]  
**Approved By:** [CEO / CTO]  
**Effective Date:** [YYYY-MM-DD]  
**Review Cadence:** Annual  
**Applies To:** All employees, contractors, service accounts, and production systems

---

## 1. Purpose
This policy defines how [Company Name] authenticates users, enforces least-privilege role-based access control (RBAC), provisions new accounts, conducts periodic access reviews, and revokes access upon role change or termination.

## 2. Authentication and Identity Standards
1. **Single Sign-On (SSO):** All supported business and engineering applications authenticate centrally through [Okta / Google Workspace / Entra ID].
2. **Multi-Factor Authentication (MFA):** MFA is mandatory for all identity provider accounts, cloud consoles ([AWS / GCP / Azure]), source code repositories ([GitHub]), production databases, and remote access tools.
3. **Unique User IDs:** Shared administrative accounts are prohibited unless technically unavoidable; any break-glass account uses hardware MFA, vaulted credentials in [1Password / Secrets Manager], and alerts on use.
4. **Password Standards:** Where SSO is unavailable, passwords must be unique, at least [14] characters long, and stored in the company password manager.

## 3. Provisioning and Role-Based Access Control (CC6.2)
1. Access to production infrastructure, customer data, and repositories follows **least privilege** based on job function.
2. All access requests beyond default birthright tools require documented manager or system-owner approval in [Jira / Linear / Slack approval workflow] before provisioning.
3. Production database write access and cloud admin privileges are restricted to designated [Infrastructure / Senior Engineering] roles and reviewed every quarter.

## 4. Periodic Access Reviews (CC6.1 / CC6.2)
1. [Security / Engineering Lead] conducts formal user access reviews on a **quarterly** basis across all in-scope systems:
   - Identity Provider ([Okta / Google Workspace])
   - Cloud Infrastructure ([AWS IAM / GCP IAM])
   - Source Code ([GitHub Organization & Admin Roles])
   - Production Application Admin Panel & Databases
2. Reviewers verify that every active account belongs to a current team member and holds appropriate permissions.
3. Unneeded or excessive privileges identified during a review are revoked within [5] business days, and review sign-off records are archived as audit evidence.

## 5. Offboarding and Access Revocation (CC6.3)
1. HR or People Ops notifies [IT / Security] immediately upon planned or involuntary termination via [HRIS / Offboarding Ticket].
2. Access to SSO, email, Slack, GitHub, cloud consoles, VPN, and production systems is revoked within **[24] hours** of termination (and immediately for involuntary terminations).
3. Offboarding completion is recorded with timestamp and reviewer confirmation.

## 6. Service Accounts and API Keys
- Machine-to-machine credentials use short-lived OIDC tokens or IAM roles wherever supported.
- Static API keys and secrets are stored in [AWS Secrets Manager / Vault], never committed to source code, and rotated at least annually or upon personnel departure with access.

## 7. Review
This policy is reviewed annually by [Security Owner] and approved by [Executive Leadership].

Evidence Mapping

What auditors test beyond this policy

A signed policy document only satisfies design intent. During SOC 2 fieldwork, your CPA auditor samples operating evidence against each clause below:

Policy RequirementControlEvidence Your Auditor Requests
MFA & SSO enforced across in-scope systemsCC6.1IdP MFA policy config, AWS IAM / GitHub 2FA enforcement checks, and screenshots of custom admin panel login/RBAC screens.
Access request approvals for new hires & role changesCC6.2Sample of new-hire onboarding tickets showing manager approval before production or admin access was granted.
Quarterly access reviews completed & remediatedCC6.1 / CC6.2Dated quarterly access review exports showing reviewer sign-off, user lists, and proof that flagged permissions were removed.
24-hour offboarding SLACC6.3Population of all terminated employees matched against IdP/GitHub/AWS deactivation logs showing revocation within 24 hours.
Common Audit Exceptions to Avoid
  • Reviewing only Okta/Google Workspace during quarterly access reviews while forgetting custom internal admin panels, Stripe, or direct Postgres users.
  • Promising 'immediate' offboarding for every departure when voluntary departures actually get deactivated later that afternoon. Use 'within 24 hours (immediately for involuntary terminations)' instead.
  • Leaving ex-contractors or stale service accounts with admin permissions in GitHub or AWS IAM.

Related guide: CC6.1 evidence guide: the screenshots auditors actually need

Frequently Asked Questions

Access Control Policy FAQ

How often do SOC 2 access reviews need to happen?
Quarterly is the standard cadence auditors expect for production systems, cloud consoles, GitHub, and your identity provider. Some very small teams review semi-annually for low-risk tools, but quarterly reviews across core systems avoid pushback from enterprise buyers.
Do auditors need screenshots for CC6.1 access controls?
Yes, for any tool without an API integration, especially your own internal admin panel or back-office RBAC screens. API checks cover AWS and Okta, while visual screenshots prove role enforcement inside your application.
What counts as valid access approval evidence for a 10-person startup?
A lightweight Jira/Linear ticket or a structured Slack approval thread timestamped before access is granted is sufficient, as long as it records who requested access, who approved it, what role was granted, and the date.

Skip manual fill-in-the-blank edits

Draft this policy directly from your real infrastructure.

Screenata scans your AWS, GCP, GitHub, and identity provider read-only, writes auditor-ready policies tied to real controls, and collects signed evidence automatically.