what encryption encoding is typically used for cardholder information in order to be PCI compliant?

Security and Identity

Introduction to PCI Compliance and Encryption

To be compliant with the Payment Card Industry Data Security Standard (PCI DSS), organizations must use strong cryptography to render the Primary Account Number (PAN) unreadable anywhere it is stored. The PCI Security Standards Council (PCI SSC) defines strong cryptography as being based on industry-tested and accepted algorithms with an effective key strength of at least 112 bits, though 128-bit or higher is strongly preferred.

Typical Encryption Algorithms for PCI Compliance

When cardholder data is stored in databases, log files, or backups, the following symmetric and asymmetric encryption standards are typically used:

  • AES (Advanced Encryption Standard): Considered the global gold standard for large-volume data encryption at rest, with AES-128 or AES-256 being the most common implementations for PCI compliance.
  • RSA: Frequently used for asymmetric encryption and secure key exchanges, requiring a minimum key length of 2048 bits for compliance.
  • ECC (Elliptic Curve Cryptography): Used for high-security environments requiring lighter compute loads, with compliance at 224 bits or higher.
  • TDES/TDEA (Triple Data Encryption Standard): Although historically used, modern implementations heavily favor switching to AES due to security and performance advantages.

Alternative Methods to Render Data Unreadable

Per Requirement 3 of PCI DSS, full encryption is not the only way to safeguard Primary Account Numbers. Alternative methods include:

  • Tokenization: Replacing live cardholder data with a non-sensitive, randomly generated equivalent (a "token"), which takes the underlying database out of compliance scope.
  • Truncation: Deleting a segment of the card number so that only a portion (e.g., the last 4 digits) is retained in the system.
  • One-Way Hashing: Using strong cryptographic hash functions (like SHA-256) to index the data, with keyed cryptographic hashes and associated key management required to prevent brute-force correlation attacks under current standards like PCI DSS 4.0.

Transmission Protocols for Data in Transit

When sending cardholder data over open or public networks (Requirement 4), static encryption algorithms are wrapped in secure communication tunnels:

  • TLS (Transport Layer Security): TLS 1.2 or TLS 1.3 are required, with older protocols like SSL and TLS 1.0/1.1 explicitly forbidden as they no longer provide "strong cryptography".
Back to all articles