PCI 3:: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 32: | Line 32: | ||
:::* Strong cryptography, such as Triple-DES 128-bit or AES 256-bit with associated key management processes and procedures. | :::* Strong cryptography, such as Triple-DES 128-bit or AES 256-bit with associated key management processes and procedures. | ||
<br> | <br> | ||
::* '''The MINIMUM account information that needs to be rendered unreadable is the payment card account number.''' | :::* '''The MINIMUM account information that needs to be rendered unreadable is the payment card account number.''' | ||
<br> | <br> | ||
---- | ---- |
Revision as of 16:53, 28 February 2007
Requirement 3: Protect stored data.
- Note that this does not apply to those employees and other parties with a specific need to see full credit card numbers.
- PCI-3.2 Do not store sensitive authentication data subsequent to authorization (not even if encrypted):
- Note that this does not apply to those employees and other parties with a specific need to see full credit card numbers.
- One-way hashes (hashed indexes), such as SHA-1
- Truncation
- Index tokens and PADs, with the PADs being securely stored
- Strong cryptography, such as Triple-DES 128-bit or AES 256-bit with associated key management processes and procedures.
- The MINIMUM account information that needs to be rendered unreadable is the payment card account number.
- PCI-3.5 Protect encryption keys against both disclosure and misuse.
- PCI-3.6 Fully document and implement all key management processes and procedures, including:
--Mdpeters 08:33, 26 June 2006 (EDT)