10.1 Establish a process for linking all access to system
components (especially access done with administrative privileges such as
root) to each individual user.
|
10.2 Implement automated audit trails to reconstruct the
following events:
all individual user accesses to
cardholder data, all actions taken by any individual with root or
administrative privileges, access to all audit trails, invalid logical access
attempts, use of identification and authentication mechanisms, initialization
of the audit logs, and creation and deletion of system-level objects.
|
10.3 Record at least the following audit trail entries for all
system components for each event: user identification, type of event, date
and time, success or failure indication, origination of event, and identity
or name of affected data, system component, or resource.
|
10.4 Synchronize all critical system clocks and times.
|
10.5 Secure audit trails so they cannot be altered.
|
10.6 Review logs for all system components at least daily. Log
reviews must include those servers that perform security functions like
intrusion detection system (IDS) and authentication, authorization, and
accounting protocol (AAA) servers (for example, RADIUS).
|
10.7 Retain audit trail for at least one year, with a minimum
of three months available online.
|
Thursday, January 2, 2014
PCI DSS Requirement (Section 10): Track and monitor all access to network resources and cardholder data
10. Track and monitor all access to network resources and cardholder data