The alarm hits when audit logs reveal stale credentials. Old passwords linger. Attack surfaces expand. Compliance slips.
Password rotation policies are not optional for regulated environments. They are a defined compliance requirement in standards like NIST 800-53, ISO 27001, PCI DSS, and HIPAA. These frameworks demand periodic password changes to reduce the risk of compromised accounts being exploited over time.
Rotation frequency is set by policy. PCI DSS, for example, mandates password changes every 90 days. HIPAA requires “reasonable” timeframes aligned with organizational risk assessment. NIST now recommends rotation triggered by suspected compromise, but many companies still enforce fixed schedules to meet overlapping regulatory demands.
Compliance means more than raw rotation intervals. Password history rules must prevent reuse. Multi-factor authentication must complement rotation to defend against stolen passwords. Audit trails must log every rotation event. In many jurisdictions, policy enforcement must be automated and verifiable to pass external audits.