PCI (Payment Card Industry Security Standard)
Do not use vendor-supplied defaults for system passwords and other security measures
2.2.1 Implement only one primary function per server to prevent functions that require different security levels from co-existing on the same server. (for example web servers database servers and DNS should be implemented on separate servers.) Note: where virtualization technologies are in use implement only one primary function per virtual system component.
If server functions that need different security levels are located on the same server the security level of the functions with higher security needs would be reduced due to the presence of the lower-security functions. Additionally the server functions with a lower security level may introduce security weaknesses to other functions on the same server. By considering the security needs of different server functions as part of the system configuration standards and related processes organizations can ensure that functions requiring different security levels don’t co-exist on the same server.
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