[PCI DSS 3.0] 12.5.5 Monitor and control all access to data.
|
|
0
|
1833
|
September 23, 2014
|
[PCI DSS 3.0] 12.5.4 Administer user accounts, including additions, deletions, and modifications.
|
|
0
|
1620
|
September 23, 2014
|
[PCI DSS 3.0] 12.5.3 Establish, document, and distribute security incident response and escalation procedures to e
|
|
0
|
1712
|
September 23, 2014
|
[PCI DSS 3.0] 12.5.2 Monitor and analyze security alerts and information, and distribute to appropriate personnel.
|
|
0
|
1650
|
September 23, 2014
|
[PCI DSS 3.0] 12.5.1 Establish, document, and distribute security policies and procedures.
|
|
0
|
1486
|
September 23, 2014
|
[PCI DSS 3.0] 12.5 Assign to an individual or team the following information security management responsibilities
|
|
0
|
1509
|
September 23, 2014
|
[PCI DSS 3.0] 12.4 Ensure that the security policy and procedures clearly define information security responsibili
|
|
0
|
1623
|
September 23, 2014
|
[PCI DSS 3.0] 12.3.10 For personnel accessing cardholder data via remote-access technologies, prohibit the copying
|
|
0
|
2122
|
September 23, 2014
|
[PCI DSS 3.0] 12.3.9 Activation of remote-access technologies for vendors and business partners only when needed b
|
|
0
|
2041
|
September 23, 2014
|
[PCI DSS 3.0] 12.3.8 Automatic disconnect of sessions for remote-access technologies after a specific period of in
|
|
0
|
4206
|
September 23, 2014
|
[PCI DSS 3.0] 12.3.7 List of company-approved products
|
|
0
|
2893
|
September 23, 2014
|
[PCI DSS 3.0] 12.3.6 Acceptable network locations for the technologies
|
|
0
|
2388
|
September 23, 2014
|
[PCI DSS 3.0] 12.3.5 Acceptable uses of the technology
|
|
0
|
1785
|
September 23, 2014
|
[PCI DSS 3.0] 12.3.4 A method to accurately and readily determine owner, contact information, and purpose (for exa
|
|
0
|
1803
|
September 23, 2014
|
[PCI DSS 3.0] 12.3.3 A list of all such devices and personnel with access
|
|
0
|
1906
|
September 23, 2014
|
[PCI DSS 3.0] 12.3.2 Authentication for use of the technology
|
|
0
|
1639
|
September 23, 2014
|
[PCI DSS 3.0] 12.3.1 Explicit approval by authorized parties
|
|
0
|
2038
|
September 23, 2014
|
[PCI DSS 3.0] 12.3 Develop usage policies for critical technologies and define proper use of these technologies.
|
|
0
|
2098
|
September 23, 2014
|
[PCI DSS 3.0] 12.2 Implement a risk-assessment process that:
|
|
0
|
3677
|
September 23, 2014
|
[PCI DSS 3.0] 12.1.1 Review the security policy at least annually and update the policy when the environment chang
|
|
0
|
1931
|
September 23, 2014
|
[PCI DSS 3.0] 11.6 Ensure that security policies and operational procedures for security monitoring and testing ar
|
|
0
|
1977
|
September 23, 2014
|
[PCI DSS 3.0] 11.5.1 Implement a process to respond to any alerts generated by the change- detection solution.
|
|
0
|
1921
|
September 23, 2014
|
[PCI DSS 3.0] 11.5 Deploy a change-detection mechanism (for example, file-integrity monitoring tools) to alert per
|
|
0
|
2387
|
September 23, 2014
|
[PCI DSS 3.0] 11.4 Use intrusion-detection and/or intrusion-prevention techniques to detect and/or prevent intrusi
|
|
0
|
2215
|
September 23, 2014
|
[PCI DSS 3.0] 11.3.4 If segmentation is used to isolate the CDE from other networks, perform penetration tests at
|
|
0
|
2645
|
September 23, 2014
|
[PCI DSS 3.0] 11.3.3 Exploitable vulnerabilities found during penetration testing are corrected and testing is rep
|
|
0
|
2213
|
September 23, 2014
|
[PCI DSS 3.0] 11.3.2 Perform internal penetration testing at least annually and after any significant infrastructu
|
|
0
|
2081
|
September 23, 2014
|
[PCI DSS 3.0] 11.3 Implement a methodology for penetration testing that includes the following:
|
|
0
|
1599
|
September 23, 2014
|
[PCI DSS 3.0] 11.2.3 Perform internal and external scans, and rescans as needed, after any significant change. Sca
|
|
0
|
2114
|
September 23, 2014
|
[PCI DSS 3.0] 11.2.2 Perform quarterly external vulnerability scans, via an Approved Scanning Vendor (ASV) approve
|
|
0
|
2859
|
September 23, 2014
|