PCI (Payment Card Industry Security Standard)
Protect stored cardholder data
3.2.1 Do not store the full contents of any track (from the magnetic stripe located on the back of a card equivalent data contained on a chip or elsewhere) after authorization. This data is alternatively called full track track track 1 track 2 and magnetic-stripe data. Note: in the normal course of business the following data elements from the magnetic stripe may need to be retained: – The cardholder’s name – Primary account number (PAN) – Expiration date – Service code
To minimize risk store only these data elements as needed for business.
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
- 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
- CIS Framework Controls V8