⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All Security & DevSecOps Interview Questions Scenario 24 of 55 in Security & DevSecOps
Senior DevOps / SRE [L2] Security Production Scenario [L2]

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.

#Security #L2 #DevSecOps #Compliance #IAM
🎙️ Candidate Opening & Architectural Context
""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.""
Advertisement
🛡️
⚡ Recommended DevSecOps Track

Master cloud-native security and container runtime defense: Prepare with KodeKloud's CKS course with live browser-based terminal sandboxes.

Prepare with KodeKloud's CKS Course →

🛠️ 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."

1️⃣

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.
2️⃣

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:

💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Enforce strong, complex passwords or passphrases initially.."
⚡ 60-Second Elevator Pitch Talking Points
  • 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.
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. 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.
  2. 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.
  3. 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 inspect or Kubernetes API queries, leaking sensitive API tokens to developers.
  4. 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.
Advertisement
Want more Security & DevSecOps scenarios?
Explore our complete collection of scenario-based Security & DevSecOps interview runbooks.
Browse All Security & DevSecOps Questions →