The Payment Card Industry Data Security Standard (PCI DSS) ensures protection for credit cardholders against securities fraud. Depending on where your business is in the payment stream, PCI DSS and all of the changing security accommodations that come with it can be a lot to stay on top of every year. If you are trying to achieve PCI DSS compliance and staring at Requirement 10, wondering what to do, you’re not alone. This requirement presents some of the biggest challenges to organizations who are trying to become PCI compliant. According to Verizon, more than 90% of companies who have been breached fail to meet the requirements in this section.
However, Requirement 10 shouldn’t derail your compliance goals. You simply need a way to collect, analyze, store, and report on the “who, what, where, and when” of users who access sensitive data in your Cardholder Data Environment (CDE).
AlienVault® Unified Security Management™ (USM) delivers PCI log management capabilities and much more as a unified security monitoring and compliance management solution. AlienVault USM is affordable, easy to use, and fast to deploy, so you can accelerate compliance for your on-premises, cloud, and hybrid environments—even for the most challenging PCI requirements.
AlienVault USM delivers robust PCI log management and monitoring capabilities as part of a unified security monitoring and compliance management solution. With USM, you can readily –
Even if your organization was not required to be PCI compliant, PCI DSS Requirement 10 is an important security monitoring best practice. Log management and monitoring is essential to understand what’s happening in your environment.
Furthermore, when a breach does occur, your raw log data is your paper trail of all the activities that led to the breach, giving you the forensic data you need to determine the root cause of the breach and to take corrective actions to prevent another. It’s important (and mandated in Requirement 10) to securely store raw log data for a one-year minimum.
Requirement 10 requires you to know who was logged into a system at any given point in time, what they did on the system, and how they accessed it through continuous log monitoring. However, if you have more than a handful of systems in your environment that generate log data, it’s not practical to monitor those logs individually. Instead, you need a way to collect, normalize, and analyze log data from all your critical cloud and on-premises infrastructure.
One of AlienVault USM’s core capabilities is its ability to collect and analyze event log data from its built-in detection capabilities, as well as logs from other devices in your environment. AlienVault USM monitors and correlates the log data against the latest threat intelligence, alerting you to any threats facing your environment.
Once you’ve defined the boundaries of your cardholder data environment (CDE), the next step towards realizing PCI logging requirements is to find and identify the critical assets from which you want to collect event logs. You need to ask, “which assets process, store, or in any way ‘touch’ cardholder data?” You also need to import log data from the network infrastructure devices that provide and control access to these devices.
If you're not sure which devices are within the scope of your PCI audit, an automated asset discovery scan is a good place to start. AlienVault USM includes built-in asset discovery and inventory that scans your environments to identify all the IP-enabled devices that are online, as well as the running services on those systems and any known vulnerabilities associated with them. In addition, you can create asset groups to identify which assets are within scope of your PCI audit and run vulnerability scans on those specific groups.
One of the main use cases for log monitoring is to support incident investigations and response activities. It's easy to understand why. Any access to cardholder data that results in a security breach will require an in-depth forensic analysis follow-up in addition to remediation of the exposures that led to the breach. In addition, it should be easy to search based on any variable to track down root causes of potential threats and exposures.
USM performs log collection from your critical applications, systems, and devices, both in your on-premises and cloud environments. The data is parsed, normalized, and immediately available as events to search on and run reports to analyze what individual users are doing across your infrastructure. Event data is connected to information about your assets, vulnerabilities, and the latest threat intelligence, giving you all the information you need in a single pane of glass to investigate an incident and respond quickly.
For any IT security incident or forensic investigation, it's critical to ensure that the raw log data is aggregated and stored securely, and that it has not been altered in any way. In fact, Requirement 10.7 requires you keep audit history for at least one year, with a minimum of three months immediately available for analysis.
The AlienVault USM platform helps you maintain the integrity of your long-term log storage. It stores data online for 90 days, making it immediately available to view, analyze, and report on the data as required by PCI DSS. In addition, it includes a full year of long-term data storage, with an option to store the data for longer if needed. Logs are stored with a write once, read many (WORM) method, making them tamper-proof. And because the AlienVault USM platform is certified compliant for PCI DSS, you can be assured of secure log monitoring and storage in the AlienVault Secure Cloud.
Another key aspect of Requirement 10 is to review logs on a daily basis (10.6.1). In fact, the standard specifically requires this daily log review for all systems that perform security functions, including IDS, firewalls, and authentication services. Yet, doing a manual daily log review of all your critical systems would be extremely tedious and would leave you without any time to do actual work. Besides, without security context, it’s not apparent which events are significant or how multiple, disparate events are related to each other.
This is where the automated SIEM event correlation capabilities of AlienVault USM deliver tremendous value.
In addition to providing essential security functions like intrusion detection (IDS) and vulnerability assessment, the AlienVault USM platform receives continuous threat intelligence updates from the AlienVault Labs Security Research Team. These updates help you to stay in continuous compliance, ensuring that the USM platform has the ability to detect new and updated threats through the latest correlation rules.
The AlienVault Labs Security Research Team tracks millions of malicious URLs, attacker techniques, tools, and profiles and uses this data to continuously deliver threat intelligence updates directly and automatically to the USM platform. This team leverages threat data shared by the global cybersecurity community on the AlienVault Open Threat Exchange® (OTX™), so your monitoring of logs and events to detect threats and anomalies stays up to speed with the ever-evolving global threat landscape.
This alleviates the burden of having to conduct your own threat research and then comparing that to your log data to identify threats. Instead, you get seamless, actionable threat intelligence that you can use to maintain effortless, continuous compliance.
PCI Sections AlienVault USM Addresses
How AlienVault USM Helps
1. Install and maintain a firewall configuration to protect cardholder data.
1.1, 1.2, 1.3
2. Do not use vendor-supplied defaults for system password and other security parameters.
2.1, 2.2, 2.3, 2.4, 2.6
3. Protect stored cardholder data
4. Encrypt transmission of cardholder data across open, public networks
5. Protect all systems against malware and regularly update antivirus software or programs
5.1, 5.2, 5.3, 5.4
6. Develop and maintain secure systems and applications
7. Restrict access to cardholder data by business need to know
8. Identify and authenticate access to system components
8.1, 8.2, 8.5
9. Restrict pysical access to cardholder data
10. Track and monitor all access to network resources and cardholder data
10.1, 10.2, 10.3, 10.4, 10.5, 10.6, 10.7, 10.8
11. Regularly test security systems and processes
11.1, 11.2, 11.4, 11.5, 11.6
12. Maintain a policy that addresses information security for all personnel
12.1, 12.5, 12.8