SEC03-BP09 Share resources securely with a third party
When granting third-party access use IAM roles with external ID, condition keys, time bound credentials and contractual controls rather than long-lived IAM users.
Source: AWS Well-Architected Security Pillar, SEC03-BP09. 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.
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
- External ID enforcement evidence · Vendor register / contract repository
- Revocation evidence · Vendor register / contract repository
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Third party access role inventory · Policy repository / GRC workspace
- Vendor contracts with security clauses · Vendor register / contract repository
First move
Common gaps auditors find
- IAM users issued to vendors
- no external ID on cross-account roles
- no expiry on vendor access
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 sheetSEC03-BP08 Share resources securely within your organization · SEC04-BP01 Configure service and application logging