Gary Palgon
Vice President, Product Management
nuBridges
The Payment Card Industry’s Security Standards Council issued a clarification about audio recordings on January 22, 2010 noting that card validation codes and values must not be stored under usual circumstances to be considered PCI DSS compliant. PANs in the recording, of course, must be encrypted following the current standards as well.
- Much like audio recordings, scanned images that contain the PAN and card validation codes must be addressed as well.
- Requirement 3.3 specifically states that “displays of PAN (for example, on screen, on paper receipts) … are masked when displayed ...”
- Requirement 9.6 notes: “Physically secure all paper and electronic media that contain cardholder data.”
- Like the audio recordings, track data should not be stored based on Requirement 3.2 : “Do not store sensitive authentication data after authorization (even if encrypted).”
- Images containing credit cards will need to be encrypted as required by Requirement 3.4: “Render PAN, at minimum, unreadable anywhere it is stored (including on portable digital media, backup media, in logs).”
Don’t be caught off guard as you make your way though a PCI DSS compliance audit – trace all input sources of credit cards and follow the card “information supply chain” to make sure you’ve addressed all occurrences of this sensitive data.
Are there any other areas of input that you’ve seen frequently missed during audits?
Regards,
Gary
PS... If you have not already registered, I am co-presenter for live webinar being held February 24, 2010 at 2pm EST. Brian Grafsgaard of QBS and I will discuss "Applying PCI Best Practices to Protect PII" Click here to register: https://www1.gotomeeting.com/register/314351497
Recent Comments