PCI Requirement 10.2.6 – Initialization, Stopping, or Pausing of the Audit Logs
PCI Requirement 10.2 – Implement Automated Audit Trails for all System Components
PCI Requirement 10.2.7 – Creation and Deletion of System-Level Objects
The PCI Compliant Database
PCI Requirement 10.6 – Review Logs and Security Events for All System Components
PCI Requirement 9.6 – Maintain Control Over the Internal/External Distribution of Any Kind of Media
PCI Requirement 10.2.5 – Use of and Changes to Identification Accounts with Root Privileges
PCI Requirement 10.2.4 – Invalid Logical Access Attempts
PCI Requirement 10.3.6 – Identity or Name of Affected Data, System Component, or Resource
PCI Requirement 10.2.1 – All Individual User Accesses to Cardholder Data
PCI Requirement 10.2.2 – All Actions Taken by Any Individual with Root or Administrative Privileges
PCI Requirement 10.5 – Secure Audit Trails so They Cannot Be Altered
PCI Requirement 10.5.1 – Limit Viewing of Audit Trails to Those with a Job-Related Need
PCI Requirement 10.5.2 – Protect Audit Trail Files from Unauthorized Modifications
PCI Requirement 10.5.5 – Use File-Integrity Monitoring or Change-Detection Software on Logs
PCI Requirement 10.3.1 – User Identification
PCI Requirement 11.4 – Use Intrusion-Detection and/or Intrusion-Prevention Techniques
PCI Requirement 3.6.1 Generation of Strong Cryptographic Keys
PCI Requirement 10.5.3 – Promptly Back Up Audit Trail Files to a Centralized Log Server
