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.
4
artefacts
0
held by a system
2
at each review
hard
to go live
Vendor register / contract repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- External ID enforcement evidence · Vendor register / contract repository
- Revocation evidence · Vendor register / contract repository
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
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
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