What evidence do auditors commonly ask for on PSS-08 Roles and Rights Concept?

Published roles and rights concept listing a rights profile per service function; Mapping of each profile to the individual permissions it confers; Guidance identifying profile combinations that undermine separation of duties; Customer documentation explaining how profiles are assigned and revoked.

What is the most common gap auditors find on PSS-08?

Only broad administrator and read only profiles offered, forcing over privileging

BSI C5 (121-criteria catalogue) · C5: Product Safety and Security

`PSS-08` Roles and Rights Concept

Give cloud users a roles and rights concept for managing access, describing the rights profiles available for each service function so that permissions can follow least privilege and need to know, and operational duties can be kept separate from controlling ones.

Source: BSI C5 (121-criteria catalogue), PSS-08. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open BSI C5 (121-criteria catalogue) in the compliance library.

The edition of the catalogue is not stamped here; check the edition your attestation is issued against.

artefacts

held by a system

at each review

hard

to go live

Policy repository / GRC workspace

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

Published roles and rights concept listing a rights profile per service function · Policy repository / GRC workspace
Mapping of each profile to the individual permissions it confers · Policy repository / GRC workspace
Guidance identifying profile combinations that undermine separation of duties · Document repository
Customer documentation explaining how profiles are assigned and revoked · Document repository

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Only broad administrator and read only profiles offered, forcing over privileging
Rights profiles undocumented, so customers cannot apply least privilege
Operational and controlling permissions bundled into a single profile
Concept not extended when new service functions were released

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 sheet

PSS-07 Confidentiality of Authentication Information · PSS-09 Authorisation Mechanisms