Third-party access
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Third-party access is access that an outside company, such as a monitoring or cost vendor, holds to your cloud resources, usually through a role the vendor assumes. It extends your boundary to someone else's controls, so it needs the same scrutiny as an internal identity.
An example, sourced
AWS's documentation on the confused deputy problem describes the case where you hire a third-party company, called Example Corp, to monitor your account and help optimize costs. You use an IAM role to establish a trusted relationship between your account and the Example Corp account. AWS says one important aspect is the external ID, an optional identifier in the role's trust policy that designates who can assume the role.
Why it matters here
Vendors you onboard become part of your attack surface. Sonrai lists third-party access control as a feature of its permissions firewall, and a review of any index entry should say which outside roles the product itself needs. Keep an inventory of outside roles and their trust conditions, and review it on the same schedule as internal access.
Related pages
Sources
- https://docs.aws.amazon.com/IAM/latest/UserGuide/confused-deputy.html, read 10 Nov 2026
Last reviewed 16 Nov 2026.