PCI (Payment Card Industry Security Standard)
Install and maintain a firewall configuration to protect cardholder data
1.3 Prohibit direct public access between the internet and any system component in the cardholder data environment.
While there may be legitimate reasons for untrusted connections to be permitted to DMZ systems (e.g. to allow public access to a web server) such connections should never be granted to systems in the internal network. A firewall’s intent is to manage and control all connections between public systems and internal systems especially those that store process or transmit cardholder data. If direct access is allowed between public systems and the CDE the protections offered by the firewall are bypassed and system components storing cardholder data may be exposed to compromise.
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