|
[PCI DSS 1.x] 6.5.10 Insecure configuration management
|
|
1
|
5627
|
August 2, 2011
|
|
[PCI DSS 1.x] 1.3.1 Implement a DMZ to limit inbound and outbound traffic to only protocols that are nec
|
|
3
|
8304
|
July 31, 2011
|
|
[PCI DSS 1.x] 1.2.2 Secure and synchronize router configuration files.
|
|
1
|
6076
|
July 31, 2011
|
|
[PCI DSS 1.x] 1.3.3 Do not allow any direct routes inbound or outbound for traffic between the Internet
|
|
3
|
7433
|
July 31, 2011
|
|
[PCI DSS 1.x] 2.3 Encrypt all non-console administrative access. Use technologies such as SSH, VPN, or S
|
|
2
|
11871
|
July 29, 2011
|
|
[PA-DSS] 12.1 If the payment application sends, or facilitates sending, cardholder data over public
|
|
1
|
13559
|
June 7, 2011
|
|
[PCI DSS 1.x] 10.2 5 Use of identification and authentication mechanisms
|
|
8
|
14909
|
May 25, 2011
|
|
[PCI DSS 1.x] 1.1 Establish firewall and router configuration standards that include the following
|
|
8
|
15415
|
May 16, 2011
|
|
[PCI DSS 1.x] 5.1 Deploy anti-virus software on all systems commonly affected by malicious software (par
|
|
8
|
21661
|
May 11, 2011
|
|
[PCI DSS 1.x] 9.1 Use appropriate facility entry controls to limit and monitor physical access to systems that sto
|
|
1
|
12636
|
April 25, 2011
|
|
[PCI DSS 1.x] 3.4.1 If disk encryption is used (rather than file- or column-level database encryption),
|
|
14
|
18838
|
April 12, 2011
|
|
[PCI DSS 1.x] 10.3.1 User identification
|
|
1
|
4677
|
April 9, 2011
|
|
[PCI DSS 1.x] 4.1 Use strong cryptography and security protocols such as SSL/TLS or IPSEC to safeguard s
|
|
5
|
15786
|
March 29, 2011
|
|
[PCI DSS 1.x] 6.6 Ensure that all web-facing applications are protected against known attacks by either of the fol
|
|
4
|
6438
|
March 17, 2011
|
|
[PCI DSS 1.x] 3.3 Mask PAN when displayed (the first six and last four digits are the maximum number of
|
|
2
|
14828
|
March 11, 2011
|
|
[PCI DSS 1.x] 5.1.1 Ensure that all anti-virus programs are capable of detecting, removing, and protecti
|
|
1
|
3922
|
March 4, 2011
|
|
[PCI DSS 1.x] 1.1.3 Requirements for a firewall at each Internet connection and between any demilitarize
|
|
2
|
7421
|
February 23, 2011
|
|
[PCI DSS 1.x] 9.3 Make sure all visitors are handled as follows: (9.3.1 to 9.3.3)
|
|
1
|
3373
|
February 23, 2011
|
|
[PCI DSS 1.x] 9.4 Use a visitor log to maintain a physical audit trail of visitor activity. Retain this log for a
|
|
1
|
3970
|
February 23, 2011
|
|
[PCI DSS 1.x] 11.2 Run internal and external network vulnerability scans at least quarterly and after any signific
|
|
1
|
8258
|
February 21, 2011
|
|
[PCI DSS 1.x] 8.2 In addition to assigning a unique ID, employ at least one of the following methods to authentica
|
|
1
|
4466
|
February 17, 2011
|
|
[PCI DSS 1.x] 3.5 Protect cryptographic keys used for encryption of cardholder data against both disclos
|
|
2
|
5244
|
February 15, 2011
|
|
[PCI DSS 1.x] 3.1 Keep cardholder data storage to a minimum. Develop a data retention and disposal polic
|
|
2
|
7942
|
January 18, 2011
|
|
[PCI DSS 1.x] 3.6.1 Generation of strong cryptographic keys
|
|
1
|
3695
|
December 13, 2010
|
|
[PCI DSS 1.x] 12.10.3 Ensure the entity is PCI DSS compliant
|
|
1
|
4224
|
October 20, 2010
|
|
[PCI DSS 1.x] 1.2 Build a firewall configuration that restricts connections between untrusted networks a
|
|
6
|
6813
|
October 15, 2010
|
|
[PCI DSS 1.x] 10.2.7 Creation and deletion of system-level objects
|
|
1
|
6119
|
October 14, 2010
|
|
[PCI DSS 1.x] 1.3.5 Restrict outbound traffic from the cardholder data environment to the Internet such
|
|
10
|
15688
|
October 13, 2010
|
|
[PCI DSS 1.x] 6.3.7 Review of custom code prior to release to production or customers in order to identify any pot
|
|
1
|
3887
|
September 30, 2010
|
|
[PCI DSS 1.x] 10.5.5 Use file integrity monitoring and change detection software on logs to ensure that existing l
|
|
1
|
5120
|
September 29, 2010
|