EventLog Analyzer

EventLog Analyzer supports Payment Card Industry Data Security Standard (PCI-DSS) Requirement 10, which enables payment service providers and merchants to track and report on all access to their network resources and cardholder data through system activity logs. The presence of logs in networked environment allows thorough forensic analysis when something does go wrong. Without system activity logs it would be difficult to determine the cause of a compromise.

The types of reports that EventLog Analyzer provides for PCI Audits are as follows:

• User Logon report:
  PCI-DSS requirements 10.2.1 clearly state that all individual user accesses to the system be recorded and monitored for possible abuse. Remember, this intent is not just to catch hackers but also to document the accesses to cardholder data. In most cases, the very fact that the access is recorded is deterrent enough for malicious activity, much like the presence of a surveillance camera in a parking lot.
• User Logoff report:
  PCI-DSS requirements 10.2.1 clearly state that all individual user accesses to the system be recorded and monitored for possible abuse. Remember, this intent is not just to catch hackers but also to document the accesses to cardholder data. In most cases, the very fact that the access is recorded is deterrent enough for malicious activity, much like the presence of a surveillance camera in a parking lot.
• Logon Failure report:
  PCI-DSS requirements 10.2.4 - Invalid logical access attempts to systems be recorded and monitored for possible abuse. The user name, date and time are included in this report.
• Audit Logs Access report:
  PCI-DSS requirements 10.2.6 - Initialization of the audit logs, calls for procedures to regularly review records of information system activity such as audit logs.
• Object Access report:
  PCI-DSS requirements 10.2.7 - Creation and deletion of system level objects, identifies when a given object (File, Directory, etc.) is accessed, the type of access (e.g. read, write, delete) and whether or not access was successful/failed, and who performed the action.
• Track Audit Policy Changes report:
  PCI-DSS requirements 10.2.3 - Access to all audit trails, lets organizations to comply with internal controls by tracking the event logs for any changes in the security audit policy.
• Track Individual User Action report:
  PCI-DSS requirements 10.1, 10.2.2 - lets organizations to comply with internal controls by auditing access to system components to each individual user and tracking the actions performed by any individual.