Skip to content
Cloud Security Risk Assessment

Do workloads get cloud access through attached roles, managed identities or workload identity federation instead of stored secrets?

Question 4 of the assessment asks: Do workloads get cloud access through attached roles, managed identities or workload identity federation instead of stored secrets? A workload that receives short-lived credentials from the platform has nothing to leak from a repository or a build log.

Start the assessment ยท All 40 questions

Why it matters

A workload that receives short-lived credentials from the platform has nothing to leak from a repository or a build log.

Answers and what each is worth

AnswerValue
Yes, for all workloads1
For some workloads0.5
No or not known0

How to check it in each cloud

AWS
Check that EC2, ECS, EKS and Lambda use execution or instance roles and that CI systems use OIDC federation to assume roles instead of stored access keys.
Azure
Check that apps use system-assigned or user-assigned managed identities or federated credentials on app registrations instead of client secrets.
Google Cloud
Check that workloads use attached service accounts or workload identity federation, and that the iam.disableServiceAccountKeyCreation org policy is enforced.

The fix

Move each workload to platform-issued identities and remove the stored secret it used before. Effort: high.

Where it comes from

Sources

  1. Microsoft cloud security benchmark IM-3, read 16 Nov 2026
  2. NIST SP 800-53 Rev. 5 IA-5, read 16 Nov 2026

Last reviewed 16 Nov 2026.