|
[PCI DSS 1.x] 9.1 Use appropriate facility entry controls to limit and monitor physical access to systems that sto
|
|
1
|
12591
|
April 25, 2011
|
|
[PCI DSS 1.x] 3.4.1 If disk encryption is used (rather than file- or column-level database encryption),
|
|
14
|
18649
|
April 12, 2011
|
|
[PCI DSS 1.x] 10.3.1 User identification
|
|
1
|
4647
|
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
|
15719
|
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
|
6351
|
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
|
14776
|
March 11, 2011
|
|
[PCI DSS 1.x] 5.1.1 Ensure that all anti-virus programs are capable of detecting, removing, and protecti
|
|
1
|
3894
|
March 4, 2011
|
|
[PCI DSS 1.x] 1.1.3 Requirements for a firewall at each Internet connection and between any demilitarize
|
|
2
|
7371
|
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
|
3340
|
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
|
3923
|
February 23, 2011
|
|
[PCI DSS 1.x] 11.2 Run internal and external network vulnerability scans at least quarterly and after any signific
|
|
1
|
8224
|
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
|
4431
|
February 17, 2011
|
|
[PCI DSS 1.x] 3.5 Protect cryptographic keys used for encryption of cardholder data against both disclos
|
|
2
|
5206
|
February 15, 2011
|
|
[PCI DSS 1.x] 3.1 Keep cardholder data storage to a minimum. Develop a data retention and disposal polic
|
|
2
|
7898
|
January 18, 2011
|
|
[PCI DSS 1.x] 3.6.1 Generation of strong cryptographic keys
|
|
1
|
3661
|
December 13, 2010
|
|
[PCI DSS 1.x] 12.10.3 Ensure the entity is PCI DSS compliant
|
|
1
|
4191
|
October 20, 2010
|
|
[PCI DSS 1.x] 1.2 Build a firewall configuration that restricts connections between untrusted networks a
|
|
6
|
6714
|
October 15, 2010
|
|
[PCI DSS 1.x] 10.2.7 Creation and deletion of system-level objects
|
|
1
|
6088
|
October 14, 2010
|
|
[PCI DSS 1.x] 1.3.5 Restrict outbound traffic from the cardholder data environment to the Internet such
|
|
10
|
15567
|
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
|
3845
|
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
|
5081
|
September 29, 2010
|
|
[PCI DSS 1.x] 1.3 Prohibit direct public access between the Internet and any system component in the car
|
|
1
|
4564
|
September 23, 2010
|
|
[PCI DSS 1.x] 9.1.1 Use cameras to monitor sensitive areas. Audit collected data and correlate with other entries.
|
|
4
|
6079
|
July 29, 2010
|
|
[PCI DSS 1.x] 12.2 Develop daily operational security procedures that are consistent with requirements in this spe
|
|
5
|
9651
|
July 8, 2010
|
|
[PCI DSS 1.x] 10.2.6 Initialization of the audit logs
|
|
2
|
6788
|
June 14, 2010
|
|
[PCI DSS 1.x] 1.1.6 Requirement to review firewall and router rule sets at least every six months
|
|
4
|
7044
|
May 30, 2010
|
|
[PCI DSS 1.x] 4.2 Never send unencrypted PANs by end-user messaging technologies (for example, e-mail, i
|
|
2
|
7273
|
May 28, 2010
|
|
[PCI DSS 1.x] 1.4 Install personal firewall software on any mobile and/or employee-owned computers with
|
|
7
|
9332
|
April 10, 2010
|
|
[PCI DSS 1.x] 6.2 Establish a process to identify newly discovered security vulnerabilities (for example
|
|
2
|
5214
|
March 16, 2010
|
|
[PCI DSS 1.x] 12.1 Establish, publish, maintain, and disseminate a security policy that accomplishes the following
|
|
2
|
5143
|
November 12, 2009
|