The Payment Card Industry Security Standards Council (PCI SSC) maintains, evolves, and promotes Payment Card Industry standards for the safety of cardholder data across the globe. The PCI SSC provides technical and operational requirements for organizations accepting or processing payment transactions, and for software developers and manufacturers of applications and devices used in those transactions.
The Payment Card Industry Data Security Standard (PCI DSS) helps entities understand and implement standards for security policies, technologies, and ongoing processes that protect their payment systems from breaches and theft of cardholder data. The standards have historically been revised on a 2-3 year cycle, but the PCI SSC is transitioning to a posture of revising the PCI DSS as required based on changes to the current threat landscape. The current standard revision is PCI DSS Version 3.2 released in April 2016. Any organization that handles payment card information has to comply with the PCI DSS and must demonstrate compliance annually. Tenable's Tenable.sc Continuous View (CV) is able to help organizations monitor ongoing PCI DSS compliance by integrating with Tenable Nessus, Tenable Nessus Network Monitor (NNM), and Tenable Log Correlation Engine (LCE).
Cardholder data (CHD) is an important piece of intellectual property that organizations are required by PCI DSS rules to protect and defend in both “at-rest” and “in-flight”. Protecting data requires different parts of an organization to be up to the task of securing data no matter where the data travels. This dashboard provides analysts with opportunities to see changes in the infrastructure and monitor the CHD. Analysts can drill down into these components to research further the detected changes to the infrastructure to validate appropriate changes were made.
With this dashboard, organizations can assess their level of adherence with PCI requirements focusing on data protection. The PCI requirements covered within this dashboard are highly focused on the goals of PCI security requirements 3, 4, and 6. The goals of these PCI security requirements address data protection within the cardholder data environment. The dashboard also covers additional PCI security requirements such as 10.6, 11.3, and 11.5 to provide analysts with additional PCI security requirement coverage.
The components of this dashboard allow analysts to see changes in the environment but also alert when cardholder data (CHD) is detected. The detected CHD can help analysts spot potential exfiltration of data through data leakage and remote access components. The data leakage components can also be configured to detect when organizational specific files are also detected in motion or at rest within the organization. The remote access components can assist analysts by quickly showing them indications when remote activity is detected. Analysts can monitor data to help ensure they comply not only PCI DSS requirements, but other regulatory requirements with these capabilities. Changes to any system in an organization should typically be a controlled process with multiple parties in an organization aware of the change. When a change to a system occurs, analysts are alerted with information relating to the change to assist them in their investigation. Vulnerability information within the organization is also provided at a high level to provide analysts with topical information such as severity, exploitability, and if patches are available.
Organizations can configure repositories or asset lists in order to tailor the focus of the dashboard. When the dashboard is added from the Tenable.sc Feed, the appropriate assets, IP addresses, or repositories can be specified. Assigning one of the options to the dashboard will update all filters in the components. By creating static or combination asset lists that include all systems in the Cardholder Data Environment (CDE), each component can be filtered to display results directly related to ongoing PCI security. Using an asset list filter will also allow traffic into and out of the CDE to be monitored. In order to accurately measure an organization’s PCI security posture, asset lists need to be applied as filters to provide results focused on the CDE.
This dashboard is available in the Tenable.sc Feed, a comprehensive collection of dashboards, reports, Assurance Report Cards, and assets. The dashboard can be easily located in the Tenable.sc Feed under the category Compliance & Configuration Assessments. The dashboard requirements are:
- Tenable.sc 5.3.1
- Nessus 8.5.1
- NNM 5.9.0
- LCE 6.0.0
Tenable's Tenable.sc Continuous View (CV) provides continuous network monitoring, vulnerability identification, risk reduction, and compliance monitoring. Tenable.sc is continuously updated with information about advanced threats and zero-day vulnerabilities, and new types of regulatory compliance configuration audits. Tenable Nessus Network Monitor (NNM) performs deep packet inspection to enable discovery and assessment of operating systems, network devices, hypervisors, databases, tablets, phones, web servers, cloud applications, and critical infrastructure. Tenable Log Correlation Engine (LCE) performs deep log analysis and correlation to continuously discover and track systems, applications, cloud infrastructure, trust relationships, and vulnerabilities. By integrating with Nessus, NNM, and LCE, Tenable.sc CV’s continuous network monitoring is able to detect systems and vulnerabilities across the enterprise.
This dashboard contains the following components:
- File Integrity Monitoring - File and Directory Change Event Details - Past 7 Days: The File and Directory Change Event Details – Past 7 Days table lists the events related to file changes detected in the past 7 days by count
- Daily Usage Summary - Configuration Changes: This component collects the top 10 configuration changes hourly
- Understanding Accepted Risk - Most Prevalent: This table presents the most prevalent vulnerabilities found to exist in the environment that have been marked as accepted risks
- Track Mitigation Progress - Vulnerability Summary by Severity: Tenable.sc records when vulnerabilities are discovered, when patches are issued, and when vulnerabilities are mitigated. This component assists in tracking vulnerability mitigations.
- CSF - Network Changes: This component displays a list of network event changes from infrastructure devices and services
- Data Leakage Monitoring - Top 10 Most Prevalent Events (Last 72 Hours): This table presents the most prevalent logged data leakage events in the last 72 hours
- Vulnerability Summary - Exploitable Vulnerabilities: This matrix displays warning indicators for exploitable vulnerabilities actively and passively detected on the network
- Verizon DBIR - Remote Access: The Verizon DBIR notes that it is important to restrict remote access to systems. This matrix assists the organization in monitoring its remote access.
- Understanding Accepted Risk - Details by Severity: This matrix presents details by severity on vulnerabilities found to exist in the environment that have been marked as accepted risks
- Detect Changes - Changes in Last 72 Hours: This component assists in maintaining up-to-date inventories and detecting changes. The matrix presents indicators for network changes detected in the last 72 hours.
- Data Leakage Monitoring - Indicators: This component presents warning indicators to draw attention to types of data that may have been leaked and methods whereby data may be leaking