What evidence do auditors commonly ask for on SEC02-BP06 Employ user groups and attributes?

Group and permission set design; ABAC tag policy; Direct user policy attachment exception list.

What is the most common gap auditors find on SEC02-BP06?

policies attached directly to users

AWS Well-Architected Security Pillar · Identity & Access Management

`SEC02-BP06` Employ user groups and attributes

Assign permissions via groups, permission sets or attribute-based access control rather than to individual users to simplify management and reduce permission sprawl.

Source: AWS Well-Architected Security Pillar, SEC02-BP06. 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 AWS Well-Architected Security Pillar in the compliance library.

artefacts

held by a system

at each review

moderate

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

Direct user policy attachment exception list · Policy repository / GRC workspace

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

Group and permission set design · Policy repository / GRC workspace
ABAC tag policy · Policy repository / GRC workspace

First move

Start with the 1 of 3 artefacts that already live in a system (Policy repository / GRC workspace); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

policies attached directly to users
no tagging strategy for ABAC
permission set sprawl

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

SEC02-BP05 Audit and rotate credentials periodically · SEC03-BP01 Define access requirements