PCI DSS requirement 8.6: system and application accounts
By Sam Rivera, Founder, SentinelPanda · October 24, 2026 · 2 min read · PCI DSS
The account with the most access to your CDE is often one that no human logs into.
Why 4.0 added this
Earlier versions of requirement 8 were written mostly with human users in mind. In most environments, machine identities — database users, service principals, deployment keys, API credentials to processors — now outnumber people, and a shared service account with a static password is one of the most reliable routes for lateral movement. Requirement 8.6 has been assessed since 31 March 2025.
8.6.1: no interactive use by default
- Interactive login is prevented unless it is needed for an exceptional circumstance.
- When it happens, it is limited to the time needed.
- The business justification is documented and explicitly approved by management.
- The individual's identity is confirmed before access is granted.
- Every action taken is attributable to that individual.
8.6.2: no hard-coded credentials
Passwords and passphrases for these accounts must not appear in scripts, configuration or property files, or bespoke source code. The usual fix is a secrets manager such as HashiCorp Vault or a cloud provider's equivalent, and the better fix is to remove the static secret entirely by using workload identity — IAM roles, managed identities, short-lived tokens issued per workload.
Add secret scanning to your CI pipeline so new credentials are caught before merge, and scan repository history once: a password deleted in a later commit is still in the repository.
8.6.3: rotation and strength
Passwords for these accounts are changed periodically, at a frequency defined in a targeted risk analysis under 12.3.1, and whenever compromise is suspected. Their complexity must be appropriate to how often they change — a credential that lives for a year needs to be much stronger than one that lives for an hour. Short-lived, automatically issued credentials are the strongest answer, because rotation becomes continuous.
Least privilege applies too
Requirement 7.2.5 asks that application and system accounts get only the privileges they need, and 7.2.5.1 asks for a periodic review of that access, again at a frequency set by a targeted risk analysis. A reporting job with write access to the payments database is a finding regardless of how its password is stored.
Start with an inventory
- Every non-human account that touches the CDE, with an owner.
- Where its secret lives, and whether a static secret is needed at all.
- Whether it can be used to log in interactively.
- When it was last rotated, and its privileges.