PCI Compliance for Linux

This guide helps you set up Sumo Logic Collectors, install the PCI Compliance for Linux App, and create dashboards from samples so you can begin monitoring your usage and determine if you are meeting Compliance benchmarks.

Collect Logs for PCI Compliance for Linux

The PCI Compliance for Linux App works with your existing Linux logs to identify any compliance issues.

To collect Linux logs, you'll need:

• An Installed Collector. Choose the one right for your host environment.
• A Linux Source, depending on your environment.
  • Local File Source
  • Remote File Source
  • Syslog Source

Required Logs for Ubuntu

The following logs, located in your Linux machine's /var/log folder, are required for using the Sumo Logic app for Linux with Ubuntu:

• auth.log
• syslog
• daemon.log
• dpkg.log
• kern.log

Required Logs for CentOS, Amazon Linux, and Red Hat

The following logs, located in your Linux machine's /var/log folder, are required for using the Sumo Logic app for Linux with CentOS, Amazon Linux, and most Red Hat forks:

• audit/audit.log
• secure
• messages
• yum.log

Installing the PCI Compliance for Linux App

Now that you have set up collection, install the Sumo Logic App for PCI Compliance for Linux to use the preconfigured searches and dashboards that provide insight into your data.

To install the app:

1. From the Sumo Logic nav, select App Catalog.
2. Search for and select your app.
   
3. (Optional) To see a preview of the dashboards included with the app, scroll down to the Dashboard Preview section.
4. If the app has multiple versions - not all apps do - select the version of the service you're using, then click Add Integration.
5. On the next configuration page, under Select Data Source for your App, complete the following fields:
   • Data Source. Select one of the following options:
     • Choose Source Category and select a source category from the list; or
     • Choose Enter a Custom Data Filter, and enter a custom source category beginning with an underscore. For example, _sourceCategory=MyCategory.
   • Folder Name. You can retain the existing name or enter a custom name of your choice for the app.
   • All Folders (optional). Default location is the Personal folder in your Library. If desired, you can choose a different location and/or click New Folder to add it to a new folder.
6. Click Next.
7. You'll see a dialog confirming that the app was installed successfully.
   

Once an app is installed, it will appear in your Personal folder, or other folder that you specified. From here, you can share it with your organization.

Panels will start to fill automatically. It's important to note that each panel slowly fills with data matching the time range query and received since the panel was created. Results won't be available immediately, but within 20 minutes, you'll see full graphs and maps.

Viewing PCI Compliance for Linux Dashboards

Account, User, System Monitoring

Dashboard description: This dashboard meets PCI Requirements 02, 07, 08 and 10 by monitoring user accounts and services. It presents information about user accounts created and deleted, stopped services, running services active services over time, unique services running, and running services, and more.

Use case. Use this dashboard to monitor administrative actions (create, delete users) performed by end users, ensure proper services are running on all systems, detect attempts to change the system time, and verify that critical systems are up and running.You can also monitor excessive failed login attempts to detect attempts to break into the system.

Login Activity

Dashboard description: This dashboard meets PCI Requirements 02 and 10 by tracking login activity. It provides information about failed and successful user logins, and failed and successful super-user logins.

Use case: Use this dashboard to monitor access to the cardholder data environment. You can monitor failed and successful user logins.

Privileged Activity

Dashboard description: This dashboard meets PCI Requirement 10. It provides information about total sudo attempts, failed sudo attempts, the top 10 users and hosts that have issued sudo attempts, recent sudo attempts, and sudo attempts over time.

Use case. Use this dashboard to monitor successful and failed access attempts to systems, especially with administrative privileges. It also helps you to monitor actions performed by users with administrative privileges.