A security audit of a city CI account finds long-lived IAM access keys embedded in pipeline workers that can deploy across production accounts. What strategy best remediates this secrets and credentials risk?
Select an answer to reveal the explanation.
Short Explanation
Long-lived keys in CI are like a master badge taped to the break-room wall—convenient until someone photographs it. OIDC or assumed roles hand out time-boxed tickets, and Secrets Manager holds what still must be a secret. Rotate the pattern, not just the password on a sticky note.
Full Explanation
Secure credential management for continuous improvement favors eliminating long-lived access keys in favor of federated or role-based temporary credentials (for example OIDC to IAM roles for GitHub Actions or CodeBuild service roles) and centralizing remaining secrets in Secrets Manager with rotation. Monthly rotation of static keys left in plaintext still leaves standing credentials; Git storage and broader AdministratorAccess enlarge blast radius. Architects should evaluate CI identity and secret stores as a single strategy.