Credential and password rotation
The shortest fixed clock in these texts is 2,160 hours (90 days), set by PCI DSS 8.3.9. Paste one job that feeds this consumer, for example service_password_rotation, weekly, and the register reads its period against the clocks below, names the gap in hours, and carries the question for its owner.
Matched on the job name or the consumer column by these words: password, rotation, secret rotation, key rotation, credential rotation, rotate, secret rotation.
The clock each rule sets
| Regime | Clock | Clause |
|---|---|---|
| PCI DSS | 2,160h | PCI DSS 8.3.9 Single-factor passwords changed every 90 days or dynamic analysischanged at least every 90 days |
| SP 800-53 | no clock | SP 800-53 AC-2 Account managementa defined frequency |
Questions this page answers
How often does PCI DSS v4.0 require credential and password rotation?
90 days (2,160 hours): PCI DSS 8.3.9, Single-factor passwords changed every 90 days or dynamic analysis. If user access relies on a password or passphrase alone (any single-factor implementation), one of these must hold: the password or passphrase is replaced no less often than every 90 days; or account security posture is assessed dynamically, with access to resources decided automatically and in real time from that assessment. The guidance notes that dynamic analysis may weigh data points such as device integrity, location, access times and resources requested. Applicability: does not apply to in-scope components where MFA is used; not intended for point-of-sale terminal user accounts that are limited to a single card number per transaction. Customer accounts of service providers are excluded, while accounts used by service provider staff are included. Objective under the customized approach: an undetected compromised password or passphrase cannot be used indefinitely.
How often does NIST SP 800-53 Rev 5 require credential and password rotation?
The text of SP 800-53 AC-2 (Account management) sets no fixed period: a defined frequency. Requires accounts to be managed across their full life cycle: permitted and prohibited account types defined, account managers assigned, membership prerequisites and approvals required, accounts created, modified, disabled and removed under documented criteria, usage monitored, and access reauthorized on a defined frequency.
What does the register ask the owner of a credential and password rotation job?
Which of these credentials are the only factor on their account, and do those meet the 90 days?
The clauses in full
If user access relies on a password or passphrase alone (any single-factor implementation), one of these must hold: the password or passphrase is replaced no less often than every 90 days; or account security posture is assessed dynamically, with access to resources decided automatically and in real time from that assessment. The guidance notes that dynamic analysis may weigh data points such as device integrity, location, access times and resources requested. Applicability: does not apply to in-scope components where MFA is used; not intended for point-of-sale terminal user accounts that are limited to a single card number per transaction. Customer accounts of service providers are excluded, while accounts used by service provider staff are included. Objective under the customized approach: an undetected compromised password or passphrase cannot be used indefinitely.
What an assessor asks to see: Inventory of in-scope systems using password-only authentication; Maximum password age setting of 90 days or less on those systems; Or configuration and decision logs of the dynamic, risk-based access engine; Documentation of which option applies to each system. Where it usually falls short: Password expiry disabled on systems that still rely on passwords alone
Requires accounts to be managed across their full life cycle: permitted and prohibited account types defined, account managers assigned, membership prerequisites and approvals required, accounts created, modified, disabled and removed under documented criteria, usage monitored, and access reauthorized on a defined frequency.
What an assessor asks to see: Account type register showing which account types are permitted and which are prohibited; Provisioning and deprovisioning tickets carrying documented approval by the responsible party; Leaver reconciliation between the human resources record and account disablement dates; Periodic account recertification results with evidence that revocations were executed. Where it usually falls short: Shared and service accounts sit outside the joiner mover leaver process entirely
Requirement text is our own statement of each clause, from the standards published at compliance.theartofservice.com, the same publisher as this register, read against the published text of each standard: our statement of each clause, not the instrument verbatim. Run this job through the register