EvidenceSheet
AWS Well-Architected Security Pillar · Identity & Access Management

SEC03-BP05 Define permission guardrails for your organization

Apply Service Control Policies, resource control policies and declarative guardrails at the organisation or OU level to enforce non-negotiable security boundaries.

Source: AWS Well-Architected Security Pillar, SEC03-BP05. 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.

4
artefacts
1
held by a system
1
at each review
moderate
to go live
Document repository
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

  • SCP catalogue with rationale · Document repository

periodic reviewEvidence produced at each review

  • Deny region or service evidence · Document repository

governing documentDocuments that govern the control

  • RCP definitions · Document repository
  • Control Tower guardrail status · Document repository

First move

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

Common gaps auditors find

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

SEC03-BP04 Reduce permissions continuously · SEC03-BP06 Manage access based on lifecycle