FAQ #1308 Published

Version History

How can an entity ensure that hashed and truncated versions cannot be correlated, as required in PCI DSS Requirement 3.4?

Date Title Actions
How can an entity ensure that hashed and truncated versions cannot be correlated? view diff from previous
How can an entity ensure that hashed and truncated versions cannot be correlated, as required in PCI DSS Requirement 3.4?