PCI (Payment Card Industry Security Standard)
Do not use vendor-supplied defaults for system passwords and other security measures
Req 2.1.1
2.1.1 For wireless environments connected to the cardholder data environment or transmitting cardholder data change all wireless vendor defaults at installation including but not limited to default wireless encryption keys passwords and SNMP community strings.
If wireless networks are not implemented with sufficient security configurations (including changing default settings) wireless sniffers can eavesdrop on the traffic easily capture data and passwords and easily enter and attack the network. In addition the key-exchange protocol for older versions of 802.11x encryption (Wired Equivalent Privacy or WEP) has been broken and can render the encryption useless. Firmware for devices should be updated to support more secure protocols.
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!