SOC 2 People and Access Controls — What Evidence Supports the Assessment?
An access review can look complete while missing the people who matter most. Contractors may sit outside the HR register, service accounts may have no named owner, and a departed employee may retain access through a separate support tool.
For SOC 2 preparation, explain how people and identities enter, change within and leave the described service. An assessor needs a traceable account of the activity, population, decisions and follow-up. The number of screenshots collected is a less useful starting point.
The SCS evidence guide covers the wider record inventory. This article follows identity and personnel events through their supporting evidence.
Establish the relevant identities and responsibilities
Identify employees, contractors, administrators and machine identities that can affect the service. Map the important systems and the sources used to identify their users. An HR list, identity directory and application-user export may have different populations for legitimate reasons that still need explanation.
Record who owns access decisions and who implements them. Where the team is small, explain the actual review arrangements rather than showing a separation of duties that does not exist.
The NIST security and privacy control catalogue provides useful reference material on identity, personnel and access topics. Its controls are not automatically a mandatory SOC 2 checklist; the engagement concerns the applicable criteria and the organisation's described controls.
Trace joiners movers and leavers
|
Event |
Evidence connection |
Assessment question |
|
New starter |
Authorised request, role and provisioning record |
Was the granted access consistent with the decision? |
|
Role change |
Changed duties and revised permissions |
Were incompatible or unnecessary permissions considered? |
|
Departure |
Confirmed trigger and removal records |
Which systems and credentials were addressed? |
|
Contractor renewal |
Current assignment and approved access duration |
Was continued access still justified? |
|
Service account change |
Owner, purpose and permissions |
Who approved and can explain the machine identity? |
Avoid treating a ticket marked complete as sufficient explanation where the system record tells a different story. Reconcile the action requested with the access actually granted or removed, keeping the relevant dates visible.
Show how periodic reviews reach the full population
Retain the population source, its date and the review boundaries. Explain filters, excluded accounts and how application-level permissions relate to the central directory.
Record decisions that lead to changes, exceptions or confirmation of continued access. Identify who reviewed privileged users and whether the reviewer could make a meaningful judgement. Preserve evidence of follow-up rather than stopping at the reviewer's signature.
Where an export omits a support group, investigate whether the group belongs in the population. Correcting the export should be accompanied by a record of what was checked and what the omission meant for the activity.
Make privileged and emergency access explainable
Separate normal administration from temporary exceptional access. For an emergency event, identify the reason, authorisation arrangements, access used, duration, relevant logs and subsequent review.
The appropriate arrangement depends on the service and risk. This article does not prescribe a universal password, review frequency or emergency-access design. It asks whether the described approach can be supported with reliable operating evidence.
Include service accounts, API keys and automation identities in the discussion where they affect the service. A machine credential still needs a purpose, responsible owner and relevant control arrangements even though it is absent from the employee register.
Connect competence and awareness to the work
Retain records appropriate to the responsibilities people actually hold. A course attendance list can show participation, while an operational authorisation or observed-work record can answer a different question about assigned duties.
For contractors and overseas support, explain onboarding, confidentiality arrangements, role instructions, access oversight and the end of the assignment. Keep personal information shared for assessment proportionate and agree secure access to sensitive records.
An illustrative support-team review
A fictional managed service provider in Malaysia uses an Indian support team. Its central directory review is complete, but a separate customer-support application contains active contractor accounts not present in the export.
The organisation maps the application population to assignments, investigates access still in use and records the decisions and actions. It then checks whether its review procedure reaches the systems relevant to the described service.
This is an illustrative evidence trail, not a conclusion about effectiveness or a prescription for every provider. The existing Malaysia SOC 2 guide and India SOC 2 guide provide broader enquiry context.
Prepare the assessment discussion
Provide the identity-source map, relevant personnel events, review records, machine-identity ownership and known exceptions. Explain changes during the proposed period and identify information still being reconciled.
Confirm the proposed service and examination arrangements before providing a large collection of employee records. A SOC 2 examination remains the work of the relevant independent practitioner under the applicable engagement; AICPA's SOC resources explain the professional context.
Contact SCS with the service, operating locations and current people/access evidence status to discuss the appropriate scope and support route.
Need ISO Certification for Your Business?
Speak with our certification specialists to understand certification requirements, audit process, implementation timelines and accredited certification services.