PCI (Payment Card Industry Security Standard)
Develop and maintain secure systems and applications
6.3.1 Examine written software-development procedures and interview responsible personnel to verify that preproduction and/or custom application accounts user IDs and/or passwords are removed before an application goes into production or is released to customers.
Development test and/or custom application accounts user IDs and passwords should be removed from production code before the application becomes active or is released to customers since these items may give away information about the functioning of the application. Possession of such information could facilitate compromise of the application and related cardholder data.
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