SOC 2: what it asks of an account list
The SOC 2 common criteria CC6.1 to CC6.3 cover logical access: every kind of account in scope, including system and service accounts (CC6.1), registration and authorisation before credentials are issued and removal once access is no longer authorised (CC6.2), and access by role with least privilege and periodic review (CC6.3). The criteria set no number of days; the periods here are the ones you set.
When to tick it: tick it when the company is audited against the SOC 2 criteria.
Named, not quoted, beside it: Sarbanes-Oxley section 404 and the IT general controls over access to programs and data; the PCAOB auditing standard for an audit of internal control over financial reporting (AS 2201); ISO/IEC 27002:2022, the guidance behind each Annex A control.
Findings that cite it
| Finding | Clause |
|---|---|
| 1. A leaver's own account is still enabled | SOC 2 CC6.3 (every account type) SOC 2 CC6.2 (every account type) |
| 2. Owner has left, or owner not recognised | SOC 2 CC6.2 (every account type) |
| 3. No owner named, or a team named with no accountable person | SOC 2 CC6.1 (every account type) |
| 5. Privileged, and orphaned or dormant | SOC 2 CC6.3 (every account type) |
| 10. Not reviewed within the interval | SOC 2 CC6.2 (every account type) SOC 2 CC6.3 (every account type) |
| 11. AI agent credential with no owner or no review | SOC 2 CC6.1 (every account type) |
| 12. Created with no approval recorded | SOC 2 CC6.2 (every account type) |
SOC 2: every clause cited
3 of the 61 heldThe requirement text is our statement of each clause, read from the published text and cited so you can check it against the official text; it is not the instrument verbatim.
SOC 2 CC6.1Logical access security over protected information assetsAccess security software, infrastructure and architecture are in place over protected information assets to guard them against security events. Points of focus: information assets are inventoried, classified and managed; logical access to hardware, data at rest, in processing and in transit, software, admin rights, mobile devices, output and offline components is limited through access control software and rules; users, devices and software prove who they are before they get in, locally or remotely; networks are segmented so unrelated parts are isolated; external points of access and the data and users passing through them are inventoried and managed; access rules combine classification, data separation, port and protocol limits, identity and certificates; identification and authentication requirements are defined and managed; new infrastructure and software are registered and authorised before receiving credentials, which are removed when no longer needed; encryption protects data at rest where risk warrants; and keys are protected from generation to destruction. The 2022 revision adds: new system architectures are security-assessed before they go live; restricted components expressly include servers, storage, network elements, APIs and endpoints, with standard hardening applied; stronger authentication such as multifactor is used where the risk strategy calls for it; isolation may use zero trust designs and other techniques beyond network segmentation; cryptographic modules, algorithms, key lengths and designs suit the risk strategy; and, where confidentiality or privacy is in scope, access to confidential or personal information is limited to the purposes identified and to personnel who need it.
SOC 2 CC6.2Registering and authorising users before issuing credentialsBefore system credentials are issued and access is granted, internal and external users whose access the organisation administers are registered and authorised; their credentials are removed once their access is no longer authorised. Points of focus (2022 revision): every kind of credential, for employees, contractors, vendors, partner staff, systems and software, is issued only after authorisation; credentials are reviewed periodically for continued validity, including inappropriate system or service accounts; and credentials that are no longer valid are disabled, destroyed or otherwise blocked from use.
SOC 2 CC6.3Role-based access, least privilege and segregation of dutiesRights over data, programs, functions and other protected assets is granted, changed or removed according to roles, responsibilities or system design and changes, applying least privilege and segregation of duties. Points of focus: access is created or modified on the asset owner's authorisation; it is removed when no longer needed; access structures (role-based, for example) limit privileges and separate incompatible functions; and roles and access rules are reviewed periodically for people who no longer need them (staff, contractors, vendors, partner personnel) and for system or service accounts that should not exist, and adjusted.