|
[PCI DSS 3.0] 2.6 Shared hosting providers must protect each entity’s hosted environment and cardholder data. Thes
|
|
0
|
2331
|
September 22, 2014
|
|
[PCI DSS 3.0] 2.5 Ensure that security policies and operational procedures for managing vendor defaults and other
|
|
0
|
2309
|
September 22, 2014
|
|
[PCI DSS 3.0] 2.4 Maintain an inventory of system components that are in scope for PCI DSS.
|
|
0
|
3304
|
September 22, 2014
|
|
[PCI DSS 3.0] 2.3 Encrypt all non-console administrative access using strong cryptography. Use technologies such a
|
|
0
|
4427
|
September 22, 2014
|
|
[PCI DSS 3.0] 2.2.5 Remove all unnecessary functionality, such as scripts, drivers, features, subsystems, file sys
|
|
0
|
2814
|
September 22, 2014
|
|
[PCI DSS 3.0] 2.2.4 Configure system security parameters to prevent misuse.
|
|
0
|
4687
|
September 22, 2014
|
|
[PCI DSS 3.0] 2.2.3 Implement additional security features for any required services, protocols, or daemons that a
|
|
0
|
2010
|
September 22, 2014
|
|
[PCI DSS 3.0] 2.2.2 Enable only necessary services, protocols, daemons, etc., as required for the function of the
|
|
0
|
2072
|
September 22, 2014
|
|
[PCI DSS 3.0] 2.2.1 Implement only one primary function per server to prevent functions that require different sec
|
|
0
|
3071
|
September 22, 2014
|
|
[PCI DSS 3.0] 2.2 Develop configuration standards for all system components. Assure that these standards address a
|
|
0
|
1963
|
September 22, 2014
|
|
[PCI DSS 3.0] 2.1.1 For wireless environments connected to the cardholder data environment or transmitting cardhol
|
|
0
|
2020
|
September 22, 2014
|
|
[PCI DSS 3.0] 2.1 Always change vendor-supplied defaults and remove or disable unnecessary default accounts before
|
|
0
|
2174
|
September 22, 2014
|