8.2.2 Group, shared, or generic IDs, or other shared authentication credentials are only used when necessary on an exception basis, and are managed as follows: • ID use is prevented unless needed for an exceptional
Group, shared, or generic IDs, or other shared authentication credentials are only used when necessary on an exception basis, and are managed as follows: • ID use is prevented unless needed for an exceptional.
5
artefacts
1
held by a system
2
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Records showing individual user identity is confirmed before use of a shared ID, and the actions taken are attributable · Document repository
periodic reviewEvidence produced at each review
- Evidence use is prevented unless needed and limited to the time needed for that circumstance · Document repository
- Evidence shared credentials are changed when someone with knowledge of them leaves · Identity provider / directory
governing documentDocuments that govern the control
- User account lists and documentation identifying every group, shared or generic ID and other shared authentication credential in use · Policy repository / GRC workspace
- The exceptional circumstance justifying each, with management approval · Document repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Document repository on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Shared administrative accounts used routinely rather than on an exception basis, with the exception rationale written once
- Credential not changed after a holder departs, so the account remains usable by them
- Use of the shared ID not linked back to an individual, so no attribution exists for the period of use
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet8.2.1 All users are assigned a unique ID before access to system components or cardholder data is allowed · 8.2.3 Additional requirement for service providers only: Service providers with remote access to customer premises use unique authentication factors for each customer premises