PCI (Payment Card Industry Security Standard)
Protect stored cardholder data
Test 3.2.2
3.2.2 For a sample of system components examine data sources including but not limited to the following and verify that the three-digit or four-digit card verification code or value printed on the front of the card or the signature panel (CVV2 CVC2 CID CAV2 data) is not stored after authorization: – Incoming transaction data – All logs (for example transaction history debugging error) – History files -Trace files – Several database schemas- Database contents.
The purpose of the card validation code is to protect “card-not-present” transactions-Internet or mail order/telephone order (MO/TO) transactions-where the consumer and the card are not present. If this data is stolen malicious individuals can execute fraudulent Internet and MO/TO transactions.
Click here to Start your FREE trial today!
What is a Cybersecurity Compliance Framework?
You don’t need to clutter your security and privacy programs with an ever-increasing number of tools as they become more sophisticated. The Lionfish platform offers a one-stop solution to track progress and monitor any framework, from custom-built ones to highly-specialized and in-demand top security and privacy frameworks and certifications.
With the Lionfish platform, every framework is supported with guided scoping, policies, controls, automated evidence collection, and continuous monitoring, ensuring efficient preparation for audits or attestation in minimal time.
The Lionfish platform is compatible with a wide range of security and privacy frameworks, including:
- CMMC v2
- HIPAA
- NERC CIP-002 through CIP-014 Revision 6
- NIST 800-171
- NIST 800-172
- PCI (Payment Card Industry Security Standard)
- SOC 2
- NIST 800-53
- NIST SP800-161 Supply Chain Risk Management
- NIST-CSF
- CIS Framework Controls V8
Click here to Start your FREE trial today!