3.5.1.3 Disk encryption access independent of OS authentication

When whole-disk or partition encryption, rather than database file, column or field encryption, makes PAN unreadable, it must be managed so that: (1) logical access is managed apart from, and independently of, the operating system's own access control and authentication mechanisms; (2) decryption keys are not linked to user accounts; and (3) any authentication factor (password, passphrase or cryptographic key) that gives access to unencrypted data is stored securely. Applicability: such encryption must still comply with the remaining encryption and key-management rules of the standard. Guidance notes that many such tools decrypt transparently after a start-up password, which offers no defence against someone who already holds a valid account. Objective under the customized approach: disk encryption is set up so that decryption needs its own authentication and logical access controls.

Source: PCI DSS v4.0.1, 3.5.1.3. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open PCI DSS v4.0.1 in the compliance library.

Version 4.0.1 is the active version; 4.0 has been retired. Appendix A1 applies only to multi-tenant service providers, A2 only to card-present POS POI terminals that still use SSL or early TLS, and A3 only when a payment brand or acquirer requires it. Which requirements apply to you follows your validation type.