Q: Your security team mandates that AWS IAM passwords must be rotated every 90 days. Why is this considered an outdated practice for human users by NIST guidelines?
Modern NIST (National Institute of Standards and Technology) guidelines advise against arbitrary periodic password rotation for human users.
Master cloud-native security and container runtime defense: Prepare with KodeKloud's CKS course with live browser-based terminal sandboxes.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "In our DevSecOps implementation, we solved this by introducing automated security quality gates. The interviewer is testing: Modern password philosophy vs legacy compliance.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
Modern NIST (National Institute of Standards and Technology) guidelines advise *against* arbitrary periodic password rotation for human users.
- Enforce strong, complex passwords or passphrases initially.
- Enforce strict MFA (hardware tokens or authenticators).
- Do not force rotation unless there is evidence of a breach or compromise.
Remediation & Permanent Safeguards
Statistically, when forced to change passwords every 90 days, humans adopt poor, predictable behaviors to cope. They use patterns (e.g., PasswordFall2023!, PasswordWinter2023!), resulting in weaker overall security that attackers can easily guess. The advised modern approach is:
- Enforce strong, complex passwords or passphrases initially.
- Enforce strict MFA (hardware tokens or authenticators).
- Do not force rotation unless there is evidence of a breach or compromise.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Revoking compromised credentials immediately without analyzing forensic audit trails for active exploitation when configuring Security security team Deactivating a compromised access key prevents abuse while preserving forensic identity for CloudTrail investigations to assess blast radius.
- Terminating compromised instances immediately during incident triage without isolating volatile RAM state when configuring Security security team Terminating compromised instances immediately destroys volatile memory evidence (RAM dumps) required to establish intrusion timelines.
-
Injecting plaintext secrets into container environment variables rather than fetching from dynamic secret vaults when configuring Security security team
Container environment variables are visible via
docker inspector Kubernetes API queries, leaking sensitive API tokens to developers. - Failing to enforce automated credential rotation for third-party SaaS integration tokens when configuring Security security team Static long-lived API tokens shared across internal services represent the highest-probability vector for supply-chain credential compromise.