← ← Back to all products
PCI-DSS
Active
StandardsLatest Version: 4.0.1Latest Release: N/A
PCI DSS is the Payment Card Industry Data Security Standard for organizations handling credit card data.
Support summary
PCI-DSS currently has supported cycles. Track the next EOL date and validate upgrades before your change window.
What do EOL and support statuses mean?Next EOL
No announced EOL date is currently listed.
Supported cycles
1
0 lts
Versions
5
Latest Version
4.0.1
Active Support
1
EOL
4
Lifecycle Timeline
Today ↓
4.0.1
4.0.1
4.0
4.0
3.2.1
3.2.1
3.2
3.2
3.1
3.1
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 4.0.1 | Jun 11, 2024 | Yes | No | 4.0.1 | No | Active |
| 4.0 | Mar 31, 2022 | No | Dec 31, 2024 | 4.0 | No | EOL |
| 3.2.1 | May 1, 2018 | No | Mar 31, 2024 | 3.2.1 | No | EOL |
| 3.2 | Apr 1, 2016 | No | Dec 31, 2018 | 3.2 | No | EOL |
| 3.1 | Apr 1, 2015 | No | Oct 31, 2016 | 3.1 | No | EOL |
Data sources
Sources
Frequently Asked Questions
Which versions of PCI-DSS have reached end of life?
The following PCI-DSS versions have reached end of life and no longer receive security updates: 4.0, 3.2.1, 3.2, 3.1. It is recommended to upgrade to a supported version.
Is it safe to continue using PCI-DSS 4.0?
PCI-DSS 4.0 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of PCI-DSS?
The latest version of PCI-DSS is 4.0.1, released in the 4.0.1 release cycle.
How many versions of PCI-DSS are currently supported?
PCI-DSS currently has 1 actively supported version(s): 4.0.1.
When does PCI-DSS 4.0.1 reach end of life?
PCI-DSS 4.0.1 does not have a specific end-of-life date announced yet.
What should I do when PCI-DSS reaches end of life?
When a PCI-DSS version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.