SOC 2

SOC 2 Access Controls: Managing User Access, Reviews and Audit Evidence

In this article
  1. What Are the SOC 2 Access Controls?
  2. What Do Auditors Expect for Joiners, Movers and Leavers?
  3. Joiners
  4. Movers
  5. Leavers
  6. How Do You Implement Least Privilege and Privileged Access?
  7. Are User Access Reviews Required for SOC 2 and ISO Audits?
  8. A Practical Access Review Process
  9. SOC 2 and ISO 27001 Access Control Mapping
  10. What Is a SOC 2 Type 2 Audit, and How Does It Test Access?
  11. What Types of Audit Evidence Apply to Access Controls?
  12. What Evidence Should You Keep for SOC 2 Access Controls?
  13. How Do EU Rules Relate to Access Control?
  14. Five Access Control Mistakes That Cause SOC 2 Exceptions
  15. How AnnexOps Helps With SOC 2 Access Controls
  16. Ready to Make Access Reviews Audit-Ready?
  17. Related Reading
  18. November 2026 SOC 2 Standards Update
  19. Build a More Audit-Ready Access Control Process
  20. Related Reading
  21. Sources Referenced

SOC 2 access controls determine who can access your systems and data, how that access is approved and reviewed, when permissions must be changed or removed, and how your organisation demonstrates that these activities are working. They are primarily addressed under the Common Criteria CC6, Logical and Physical Access Controls.

For SaaS companies, access management involves more than creating employee accounts. It includes managing administrator privileges, reviewing service accounts, securing production environments and maintaining records of joiner, mover and leaver activities.

Auditors may examine actual access events, including new employee onboarding, role changes, employee departures and privileged account activity. This guide is part of our SOC 2 readiness guide for SaaS companies and explains how engineering, IT and security teams can organise access management and maintain supporting audit evidence.

Are quarterly access reviews still a spreadsheet, a Slack chase and a folder of screenshots?

AnnexOps provides registers for access and vendor reviews linked to CC6, CC7 and CC9 activities. Its evidence collection uses read-only, metadata-based records with hash-chained logs, and its CPA Audit Room provides scoped, read-only access for audit review.

In a 30-minute discussion, your team can review its in-scope systems and identify potential gaps in CC6 evidence.

What Are the SOC 2 Access Controls?

SOC 2 Security criteria include eight Common Criteria under CC6, covering logical and physical access controls. These criteria address how organisations protect systems, manage user permissions, secure physical assets and prevent unauthorised access or software.

The following table summarises the CC6 criteria and examples of controls that SaaS companies may implement.

CriterionWhat it coversTypical SaaS control
CC6.1Implementing logical access security over protected information assetsSSO, MFA, identity management and access security policies
CC6.2Registering and authorising users before granting access, and removing credentials when access is no longer authorisedApproved access requests, onboarding and offboarding workflows
CC6.3Authorising, modifying and removing access based on roles, responsibilities, least privilege and segregation of dutiesRole-based access, privileged access management and access reviews
CC6.4Restricting physical access to facilities and protected information assetsOffice access controls, visitor records and data centre security
CC6.5Discontinuing protections over physical assets only after data and software can no longer be read or recoveredSecure device disposal, media sanitisation and data destruction
CC6.6Protecting against threats originating outside system boundariesFirewalls, boundary protection and additional authentication
CC6.7Restricting and protecting the transmission, movement and removal of informationEncryption in transit, secure transfer and data loss prevention
CC6.8Preventing or detecting unauthorised or malicious softwareEndpoint protection, application controls and malware detection

The criteria should be evaluated against your organisation’s actual systems, services and control design. A single technical measure does not automatically satisfy an entire criterion.

For example, enabling MFA may support logical access security, but the organisation still needs to consider user authorisation, privileged access, credential management and access removal.

Your SOC 2 control mapping should connect the applicable criteria with the controls your organisation operates and the evidence supporting them.

What Do Auditors Expect for Joiners, Movers and Leavers?

Joiner, mover and leaver processes are important parts of user access management. They help organisations ensure that employees and other authorised users receive appropriate permissions and lose access when those permissions are no longer required.

Joiners

When a new employee or contractor joins, access should be requested and approved by an authorised person before credentials are issued.

Evidence may include:

  • Access request or onboarding ticket.
  • Manager or system-owner approval.
  • Assigned role and permission details.
  • Provisioning record and relevant timestamps.

Movers

When an employee changes departments, responsibilities or job roles, their existing permissions should be reviewed.

The organisation should remove access that is no longer necessary and document newly approved permissions. Simply adding new permissions without reviewing existing ones can result in excessive access.

Leavers

When an employee or contractor leaves, access should be disabled or removed according to the organisation’s established procedures and applicable requirements.

Evidence may include:

  • HR termination or departure record.
  • Offboarding ticket.
  • Identity-provider account disablement record.
  • System-specific access removal timestamps.
  • Records of any approved exceptions or delays.

During a SOC 2 examination, the auditor may select samples from the populations of joiners, movers and leavers during the examination period.

The evidence requirements differ by event. A joiner needs an approved access request and provisioning record. A mover needs evidence of authorised permission changes. A leaver needs records showing when access was disabled or removed.

Reconcile HR records with identity-provider and system records where applicable. Any delays or discrepancies should be investigated and documented.

How Do You Implement Least Privilege and Privileged Access?

CC6.3 addresses access authorisation, modification and removal based on roles and responsibilities, while considering least privilege and segregation of duties.

For a SaaS company, these principles should be reflected in everyday access management.

1. Manage access through an identity provider

Use centralised identity management and role-based groups wherever practical. This helps teams apply consistent permissions and makes access reviews easier to organise.

2. Separate administrator and everyday accounts

Users with administrative responsibilities should have appropriately restricted privileged access. Apply MFA, record approvals and maintain logs of privileged activities.

3. Cover production and cloud environments

Production systems, cloud consoles, databases and deployment environments often contain sensitive information or provide access to critical business operations. Define who can access them and under what conditions.

4. Inventory non-human accounts

Service accounts, API keys, application identities and access tokens also require ownership and appropriate controls. Document their purpose, permissions, responsible owner and review requirements.

5. Apply segregation of duties

Separate responsibilities where combining them could allow an individual to bypass important controls. For example, the person who develops a production change should not automatically have sole authority to approve and deploy it.

Document access rules for each in-scope system, including exceptions, approvers and expiry dates where applicable.

Are User Access Reviews Required for SOC 2 and ISO Audits?

Yes. Both frameworks address access-right management and review, although their requirements are not identical.

In SOC 2, CC6.2 includes periodic review of access credentials, while CC6.3 includes periodic review of access roles and rules. These reviews help organisations identify unnecessary or inappropriate access and make changes where required.

ISO/IEC 27001:2022 addresses access rights under Annex A control 5.18. The control covers the allocation, review, modification and removal of access rights.

Quarterly reviews are a common organisational practice, particularly for important or privileged systems. However, neither framework establishes a universal quarterly frequency. Organisations should define a review schedule based on risk, document the rationale and retain evidence of completed reviews and resulting changes.

A Practical Access Review Process

A consistent review process should include the following steps:

  1. Define the scope. Identify all in-scope applications, infrastructure, databases and privileged accounts.
  2. Export current user lists. Obtain records directly from the relevant systems or identity provider rather than relying on manually maintained lists.
  3. Assign appropriate reviewers. System owners, managers or data owners should review permissions relevant to their responsibilities.
  4. Reconcile employee records. Compare access records with HR information to identify leavers, role changes and unknown accounts.
  5. Record review decisions. Document whether access should be retained, modified or removed, together with the reviewer and review date.
  6. Track corrective actions. Record required changes, assign owners and deadlines, and retain evidence once the actions are completed.

A review that identifies an access issue should document the finding, assign a remediation owner and deadline, and retain evidence of corrective action. Unresolved issues should be tracked and evaluated against the organisation’s control requirements.

SOC 2 and ISO 27001 Access Control Mapping

Access topicSOC 2ISO/IEC 27001:2022
User provisioning and removalCC6.25.18 Access rights
Role-based access and least privilegeCC6.35.15 Access control; 5.18 Access rights
Privileged accessCC6.1 and CC6.38.2 Privileged access rights
Periodic access reviewsCC6.2 and CC6.35.18 Access rights

This mapping is indicative rather than a declaration of equivalence. Organisations should assess each framework’s requirements independently.

If your organisation already operates an ISO 27001 compliance programme, some access-review records and supporting controls may be reusable for SOC 2 where they meet the applicable criteria.

What Is a SOC 2 Type 2 Audit, and How Does It Test Access?

A SOC 2 Type 2 examination evaluates whether relevant controls are suitably designed and operated effectively over a defined period.

Unlike a Type 1 report, which evaluates control design and implementation as of a particular date, Type 2 includes testing of operating effectiveness across the examination period.

For access management, a CPA may examine populations such as:

  • New users who received system access.
  • Employees and contractors whose roles changed.
  • Users who left during the period.
  • Privileged and administrator accounts.
  • Completed periodic access reviews.

The auditor selects samples and evaluates whether the relevant control operated as described. For example, a leaver sample may be checked against the termination record, access-removal evidence and the organisation’s stated offboarding procedure.

If a leaver retains access beyond the timeframe established in your policy, the delay may represent a control exception. Its significance depends on the circumstances, duration, systems involved and the auditor’s evaluation of the control.

Organisations should identify and investigate gaps while the examination period is open, document corrective actions and communicate relevant matters to their CPA firm.

What Types of Audit Evidence Apply to Access Controls?

Auditors use different procedures to obtain and evaluate evidence. Common auditing procedures include inspection, observation, inquiry, reperformance, analytical procedures, external confirmation and recalculation.

The following examples show how these procedures may apply to access management.

Audit procedureExample for user access
InspectionReviewing access tickets, approvals, review records and system-generated user lists
ObservationObserving an administrator disable a user account
InquiryAsking a system owner or security lead about access-review procedures
ReperformanceRepeating a leaver check against identity-provider records
Analytical proceduresExamining trends in access changes, dormant accounts or review completion
External confirmationObtaining confirmation from a relevant supplier about access to its system
RecalculationRechecking a calculated measure, such as the percentage of reviews completed on time

The auditor determines which procedures are appropriate for the control and evidence being tested. Inspection, inquiry and reperformance are particularly relevant to many access-control tests.

System-generated records can provide useful evidence because they show account activity and timestamps. However, their reliability also depends on completeness, accuracy, system configuration and the surrounding control process.

What Evidence Should You Keep for SOC 2 Access Controls?

Maintaining evidence throughout the examination period helps organisations avoid last-minute requests and incomplete records.

For access controls, consider retaining:

  • Access management policies and system-specific access rules.
  • Joiner, mover and leaver populations for the examination period.
  • Access requests and approvals.
  • Provisioning records and account creation timestamps.
  • Access removal records reconciled with HR departure information.
  • MFA settings for production and administrator access.
  • Privileged account inventories, owners and approvals.
  • Service account, API key and token inventories.
  • Completed access reviews with reviewer names, dates and decisions.
  • Evidence of permission changes and completed removals.
  • Exception records, including approvers and expiry dates.
  • System exports or queries used to generate user and access lists.

Each record should have enough context to establish what it represents, which system it relates to, who owns it and when it was created or reviewed.

A structured SOC 2 evidence collection process can connect these records with the criteria and controls they support.

How Do EU Rules Relate to Access Control?

SOC 2 is not a European regulatory requirement, but its access-control practices are relevant to discussions with European customers and business partners.

GDPR Article 32: Requires controllers and processors to implement appropriate technical and organisational measures to protect personal data, taking account of the risks and context of processing. Access management can form part of these measures.

NIS2 Article 21: Includes access control policies among the cybersecurity risk-management measures required for entities within its scope.

DORA: Establishes ICT risk-management requirements for financial entities. More specific access-control provisions appear in Commission Delegated Regulation (EU) 2024/1774, Article 21, including least privilege, segregation of duties, user accountability and procedures for granting, reviewing and revoking access rights.

A SOC 2 report can provide useful assurance information in these discussions, but it does not automatically demonstrate compliance with GDPR, NIS2 or DORA.

Five Access Control Mistakes That Cause SOC 2 Exceptions

Even organisations with established access policies can experience problems when those policies are not followed consistently.

1. Delayed removal of leavers

If accounts remain active after a person’s access is no longer authorised, the organisation may have a gap in its offboarding process. Reconcile HR departure records with access-removal timestamps.

2. Shared and orphaned accounts

Shared logins and unowned service accounts make accountability difficult. Use identifiable accounts wherever practical and assign owners to non-human identities.

3. Access reviews without follow-up

A review that identifies excessive permissions but does not result in documented corrective action may leave the underlying risk unresolved. Track findings to completion.

4. Incomplete user populations

If system exports omit applications, privileged users or service accounts, the review may not represent the complete access population. Identify all in-scope systems and validate the source of each export.

5. Reviewers approving their own access

Self-review can weaken the independence of an access review. Assign an appropriate manager, system owner or other authorised reviewer to evaluate permissions.

Addressing these issues helps organisations maintain a more consistent access-management process and produce clearer evidence for examination.

How AnnexOps Helps With SOC 2 Access Controls

Managing access reviews, evidence records and control responsibilities across separate systems can become difficult as a SaaS company grows.

AnnexOps supports SOC 2 governance operations by helping teams organise access-related activities alongside other control and evidence workflows.

Relevant capabilities include:

  • Access and vendor review registers: Organise CC6, CC7 and CC9 activities, including access-review workflows.
  • Evidence collection: Read-only, metadata-based evidence with hash-chained records designed to make changes detectable.
  • Automated control checks: 743 checks that help surface potential gaps for review. SOC 2 check-to-criterion mappings are currently draft and should not be treated as independently validated.
  • Type 2 window tracker: Organises records against the defined examination period.
  • CPA Audit Room: Provides read-only, time-limited access scoped to the SOC 2 framework.

AnnexOps does not issue SOC 2 reports or replace the independent CPA examination. Coverage figures are indicative and should not be treated as a prediction of an audit outcome.

Ready to Make Access Reviews Audit-Ready?

Access control is an important part of SOC 2 preparation because it involves real users, permissions, approvals and system activity. A single delayed offboarding action, undocumented administrator account or incomplete access review can raise questions about how effectively controls operate.

AnnexOps helps teams organise access reviews, supporting evidence and their Type 2 examination records in a more structured workflow.

  • Review on schedule: Organise dated access reviews and track them against your examination period.
  • Maintain evidence: Keep read-only, hash-chained records associated with relevant control activities.
  • Support audit handover: Provide your CPA with scoped, read-only access through the CPA Audit Room.

Book a 30-minute SOC 2 Expert Call. Review your in-scope systems and identify potential gaps in your CC6 access-control evidence.

November 2026 SOC 2 Standards Update

The AICPA has published an exposure draft proposing revisions to the SOC 2 Trust Services Criteria. The proposed changes are intended to modernise the criteria and address evolving technology and risk considerations, including AI-related considerations.

The public comment deadline is 15 January 2027. The proposed criteria are not yet final and have not replaced the current Trust Services Criteria. If approved, the proposed revisions are intended to apply to engagements beginning on or after 31 December 2027, with early adoption permitted.

The AICPA also published a separate proposed update to the SOC 2 Description Criteria on 17 November 2026. Comments on that exposure draft are also due by 15 January 2027.

For current SOC 2 preparation, organisations should continue to work with the applicable existing criteria and consult their CPA firm about any future transition.

Build a More Audit-Ready Access Control Process

Organise access reviews, track control evidence and improve visibility into your SOC 2 activities with AnnexOps.

Sources Referenced

Leave a Reply

Your email address will not be published. Required fields are marked *

AI Analyzer