Tenable Addendum to VMware Product Applicability Guide. for. Payment Card Industry Data Security Standard (PCI DSS) version 3.0

Transcription

1 Tenable Product Applicability Guide For Payment Card Industry (PCI) Partner Addendum VMware Compliance Reference Architecture Framework to VMware Product Applicability Guide for Payment Card Industry Data Security Standard (PCI DSS) version 3.0 June 2014 Product Applicability Guide

2 Table of Contents INTRODUCTION... 3 OVERVIEW OF PCI AS IT APPLIES TO CLOUD/VIRTUAL ENVIRONMENTS... 7 SUMMARY OF RELEVANT CHANGES FROM PCI DSS 2.0 TO TENABLE PCI COMPLIANCE SOLUTION TENABLE PCI REQUIREMENTS MATRIX OVERVIEW TENABLE PCI REQUIREMENTS MATRIX (BY PRODUCT) NESSUS ENTERPRISE CLOUD NESSUS VULNERABILITY SCANNER PASSIVE VULNERABILITY SCANNER SECURITYCENTER CONTINUOUS VIEW SECURITYCENTER SUMMARY Product Applicability Guide 2

3 Introduction Virtualization offers the benefits of hardware consolidation and rapid provisioning and deployment of services to increase business agility and improve efficiency. It also brings new security and compliance challenges such as virtual machine sprawl, a more dynamic environment, and an attack surface that encompasses physical hosts, virtual images, and applications running on top. However, with proper tools that provide continuous monitoring of vulnerabilities and threats, organizations can achieve and maintain adherence to compliance standards and secure their physical and virtual infrastructure from configuration errors, ensure security software is enabled and updated, and monitor for changes in the virtual and physical infrastructure that impact risk and compliance status. Tenable Network Security offers a variety of solutions that enable your organization to safely implement virtualization while maintaining compliance with the Payment Card Industry Data Security Standard and protect your systems from threats. Tenable s solutions provide the following capabilities for physical, virtual, and hybrid environments: Discovers physical and virtual systems as well as mobile devices Performs compliance auditing, including PCI DSS Identifies vulnerabilities on detected assets and infrastructure Detects malware and advanced threats to protect critical physical and virtual servers as well as clients Performs network behavioral analysis to continuously monitor for changes to virtual and physical infrastructure that impact compliance status Collects and analyzes logs from virtual and physical assets Continuous Monitoring Malware Detection Compliance & Patch Monitoring Network Behavioral Analysis Log Collection Forensic Analysis Incident Response Mobile, Virtual, Cloud Coverage Product Applicability Guide 3

4 Tenable Scanning Solutions To protect physical and virtual environments and demonstrate compliance, Tenable offers two families of solutions - the Nessus family and the SecurityCenter family. The Nessus family consists of Nessus and PVS products which offer active vulnerability scanning and passive monitoring for organizations that are interested in individual scanner deployments. The SecurityCenter solutions offer centralized administration of distributed scanners (Nessus, Passive Vulnerability Scanner (PVS), and Log Correlation Engine (LCE)) for continuous, real-time vulnerability, compliance, and threat management. Pre-configured and customizable scanning and audit policies ( plugins ) as well as extensive dashboards and reports through its security app store provide the flexibility to meet an organization s unique requirements for identifying vulnerabilities, monitoring event logs, and confirming compliance. Figure 1: Tenable Solution Overview VMware Approach to PCI Compliance The Payment Card Industry Data Security Standard (PCI DSS) is applicable to all types of environments that Store, Process, or Transmit Card Holder Data. This includes information such as Personal Account Numbers (PAN), as well as any other information that has been defined as Card Holder Data by the PCI DSS v3.0. Cloud computing is no exception to the PCI DSS audit process, and many of the cloud s advantages over earlier paradigms -- sharing of resources, workload mobility, consolidated management plane, etc. themselves necessitate that adequate controls are adopted to help meet the PCI DSS audit. PCI considerations are essential for assessors to help to understand what they might need to know about an environment in order to be able to determine whether a PCI DSS requirement has been met. If payment card data is stored, processed or transmitted in a cloud environment, PCI DSS will apply to that environment, and will typically involve validation of both the infrastructure and the applications running in that environment. Product Applicability Guide 4

5 Many enterprise computing environments in various vertical industries are subject to PCI DSS compliance, and generally those that deal in any kind of financial transaction for exchanging goods and services rely on VMware and VMware Technology Partner solutions to deliver those enterprise computing environments. As such, these enterprises seek ways to reduce overall IT budget while maintaining an appropriate overall risk posture for the in-scope environment. One of the greatest challenges in hosting the next generation enterprise computing environment is consolidating many modes of trust required such as those required for a Cardholder Data Environment (CDE) and a Non-Cardholder Data Environment. For these reasons VMware has enlisted its Audit Partners such as Coalfire, a PCI DSS-approved Qualified Security Assessor, to engage in a programmatic approach to evaluate VMware products and solutions for PCI DSS control capabilities and then to document these capabilities in a set of reference architecture documents. The first of these documents is this Product Applicability Guide, which contains a mapping of the VMware products and features that should be considered for implementing PCI DSS controls. The next two documents that, together with this Guide, comprise the PCI DSS Reference Architecture are the Architecture Design Guide and the Validated Reference Architecture, which will provide guidance on the considerations to be made when designing a vcloud environment for PCI DSS as well as a lab validation exercise analyzing an instance of this reference architecture which utilizes the concepts and approaches outlined therein. For more information on these documents and the general approach to compliance issues please review VMware's Approach to Compliance. In addition, VMware and Coalfire are engaged with VMware Technology Partners such as Tenable Network Security to analyze their products and solutions (available on VMware Solution Exchange) with the goal of providing continuing examples to the industry. While every environment is unique, together VMware and its partners can provide a solution that potentially addresses over 70% of the PCI DSS technical requirements. Figure 2: PCI Requirements Product Applicability Guide 5

6 Figure 3: VMware + Partner Product Capabilities for a Trusted Cloud Product Applicability Guide 6

7 Overview of PCI as it applies to Cloud/Virtual Environments The PCI Security Standards Council (SSC) was established in 2006 by five global payment brands (American Express, Discover Financial Services, JCB International, MasterCard Worldwide, and Visa Inc.). The payment brands require through their Operating Regulations that any merchant or service provider must be PCI compliant. Merchants and service providers are required to validate their compliance by assessing their environment against nearly 300 specific test controls outlined in the Payment Card Industry Data Security Standards (DSS). Failure to meet PCI DSS requirements may lead to fines, penalties, or inability to process credit cards, in addition to potential reputational loss. The PCI DSS has six categories with twelve total requirements as outlined below: Table 1: PCI Data Security Standard The PCI SSC specifically began providing formalized guidance for cloud and virtual environments in October, These guidelines were based on industry feedback, rapid adoption of virtualization technology, and the move to cloud computing environments. Version 3.0 (and version 2.0) of the Data Security Standard (DSS) specifically mentions the term virtualization (previous versions did not use the word virtualization ). This was followed by an additional document explaining the intent behind the PCI DSS v2.0, Navigating PCI DSS. These documents were intended to clarify that virtual components should be considered as components for PCI, but did not go into the specific details and risks relating to virtual environments. Instead, they address virtual and cloud specific guidance in an Information Supplement, PCI DSS Virtualization Guidelines, released in June 2011 by the PCI SSC s Virtualization Special Interest Group (SIG). Product Applicability Guide 7

8 Figure 4: Navigating PCI DSS The existing virtualization supplement was written to address a broad set of users (from small retailers to large cloud providers) and remains product agnostic (no specific mentions of vendors and their solutions). * VMware solutions are designed to help organizations address various regulatory compliance requirements. This document is intended to provide general guidance for organizations that are considering VMware solutions to help them address such requirements. VMware encourages any organization that is considering VMware solutions to engage appropriate legal, business, technical, and audit expertise within their specific organization for review of regulatory compliance requirements. It is the responsibility of each organization to determine what is required to meet any and all requirements. The information contained in this document is for educational and informational purposes only. This document is not intended to provide legal advice and is provided AS IS. VMware makes no claims, promises or guarantees about the accuracy, completeness, or adequacy of the information contained herein. Nothing that you read in this document should be used as a substitute for the advice of competent legal counsel. Summary of Relevant Changes from PCI DSS 2.0 to 3.0 With the recent release of the PCI DSS (Data Security Standard) 3.0, while little additional guidance has been released with regard to virtualization specifically, there have been a number of enhancements and clarifications that may potentially have significant design & operational considerations above and beyond those which were required for compliance with the PCI DSS 2.0. It should be noted that none of the new PCI DSS 3.0 requirements or considerations are inconsistent with or materially different from those found in version 2.0, but rather are simply additions, enhancements, and clarifications. An updated Navigating PCI DSS document for version 3.0 has not been released by the PCI SSC (Security Standards Council) as of the time of this writing. With every iteration of the PDI DSS and the associated changes & updates, particularly when new requirements are presented, organizations are given additional time to implement these controls through the Sunrise process. While entities can choose to manage their cardholder data environments under the PCI DSS 2.0 until December 31, 2014 at the latest, after this point all PCI DSS programs and audits must adhere to version 3.0. Additionally, many of the new requirements under the PCI DSS 3.0 are considered best practices until July 1, 2015, giving organizations additional time to prepare to meet these new requirements in an appropriate manner. Product Applicability Guide 8

9 Many of the new controls and changes in PCI DSS 3.0 reflect the growing maturity of the Payment Card Industry, and the need to focus more on a risk-based approach and deal with the threats and associated risks which most commonly lead to incidents involving the compromise of cardholder data. Along with the new controls and focus areas, version 3.0 provides PCI organizations and assessors with additional guidance and flexibility around designing, implementing, and validating the requisite PCI DSS controls. It should also be noted that with increased guidance and flexibility in the standard and individual controls, a greatly increased level of stringency is required in the validation of those controls and the risk-based approach to managing PCI DSS requirements. At a high level, the updates to version 3.0 of the DSS include: Providing stronger focus on some of the greater risk areas in the threat environment Providing increased clarity on PCI DSS & PA-DSS requirements Building greater understanding on the intent of the requirements and how to apply them Improving flexibility for all entities implementing, assessing, and building to the Standards Driving more consistency among assessors Helping manage evolving risks / threats Aligning with changes in industry best practices Clarifying scoping and reporting Eliminating redundant sub-requirements and consolidate documentation We also have several key themes around managing PCI DSS 3.0 and taking a proactive business-as-usual approach to protecting cardholder data, and focusing primarily on security, as opposed to pure compliance, which have been updated in the latest version, and for which the PCI Security Standards Council has provided guidance. The following is guidance from the PCI DSS Version 3.0 Change Highlights document regarding these high-level concepts and how they apply to PCI DSS 3.0: Education and awareness Lack of education and awareness around payment security, coupled with poor implementation and maintenance of the PCI Standards, gives rise too many of the security breaches happening today. Updates to the standards are geared towards helping organizations better understand the intent of requirements and how to properly implement and maintain controls across their business. Changes to PCI DSS and PA-DSS will help drive education and build awareness internally and with business partners and customers. Increased flexibility Changes in PCI DSS 3.0 focus on some of the most frequently seen risks that lead to incidents of cardholder data compromise such as weak passwords and authentication methods, malware, and poor self-detection providing added flexibility on ways to meet the requirements. This will enable organizations to take a more customized approach to addressing and mitigating common risks and problem areas. At the same time, more rigorous testing procedures for validating proper implementation of requirements will help organizations drive and maintain controls across their business. Security as a shared responsibility Securing cardholder data is a shared responsibility. Today s payment environment has become ever more complex, creating multiple points of access to cardholder data. Changes introduced with PCIDSS focus on helping organizations understand their entities PCI DSS responsibilities when working with different business partners to ensure cardholder data security. Product Applicability Guide 9

10 Cloud Computing Cloud computing and virtualization have continued to grow significantly every year. There is a rush to move applications and even whole datacenters to the cloud, although few people can succinctly define the term cloud computing. There are a variety of different frameworks available to define the cloud, and their definitions are important as they serve as the basis for making business, security, and audit determinations. VMware defines cloud or utility computing as the following ( Cloud computing is an approach to computing that leverages the efficient pooling of on-demand, self-managed virtual infrastructure, consumed as a service. Sometimes known as utility computing, clouds provide a set of typically virtualized computers which can provide users with the ability to start and stop servers or use compute cycles only when needed, often paying only upon usage.. Figure 5: Cloud Computing There are commonly accepted definitions for the cloud computing deployment models and there are several generally accepted service models. These definitions are listed below: Private Cloud The cloud infrastructure is operated solely for an organization and may be managed by the organization or a third party. The cloud infrastructure may be on-premise or off-premise. Public Cloud The cloud infrastructure is made available to the general public or to a large industry group and is owned by an organization that sells cloud services. Hybrid Cloud The cloud infrastructure is a composition of two or more clouds (private and public) that remain unique entities, but are bound together by standardized technology. This enables data and application portability; for Product Applicability Guide 10

11 example, cloud bursting for load balancing between clouds. With a hybrid cloud, an organization gets the best of both worlds, gaining the ability to burst into the public cloud when needed while maintaining critical assets on-premise. Community Cloud The cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (for example, mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party, and may exist on-premise or off premise. To learn more about VMware s approach to cloud computing, review the following: VMware Cloud Computing Overview VMware s vcloud Architecture Toolkit When an organization is considering the potential impact of cloud computing to their highly regulated and critical applications, they may want to start by asking: Is the architecture a true cloud environment (does it meet the definition of cloud)? What service model is used for the cardholder data environment (SaaS, PaaS, IaaS)? What deployment model will be adopted? Is the cloud platform a trusted platform? The last point is critical when considering moving highly regulated applications to a cloud platform. PCI does not endorse or prohibit any specific service and deployment model. The appropriate choice of service and deployment models should be driven by customer requirements, and the customer s choice should include a cloud solution that is implemented using a trusted platform. VMware is the market leader in virtualization, the key enabling technology for cloud computing. VMware s vcloud Suite is the trusted cloud platform that customers use to realize the many benefits of cloud computing, including safely deploying business critical applications. Figure 6: VMware Software Defined Data Center Products Product Applicability Guide 11

12 Figure 7: VMware End User Computing VMware provides an extensive suite of products designed to help organizations support security and compliance needs. The solutions collective functionality features, and specific PCI DSS requirements are addressed in the VMware Applicability Guide for PCI, which provide detail information about VMware s support for PCI DSS v3. If you are an organization or partner that is interested in more information on the VMware Compliance Program, please us at compliance-solutions@vmware.com Figure 8: Tenable s Virtual Environment Monitoring Product Applicability Guide 12

13 Tenable PCI Compliance Solution Tenable Nessus and SecurityCenter product offerings provide comprehensive vulnerability scanning, monitoring, and reporting, including pre-configured scanning policies for PCI DSS v3 internal and external scanning requirements. ** Organizations can use Tenable products to continually monitor PCI compliance using pre-configured and customized scanning policies to provide for ongoing, continual vulnerability monitoring. Table 2: Tenable Solutions Solution Description Nessus Enterprise Cloud Nessus Enterprise Cloud provides cloud-based vulnerability management. Nessus Enterprise Cloud customers have the ability to manage all internal and external scanning from the cloud. Nessus Enterprise Cloud acts as the Primary Nessus Scanner and can control multiple secondary Nessus scanners whether they are located on premise within your corporate network, production environment, data center, remote locations, or in the cloud. Nessus Enterprise Cloud meets PCI DSS 11.2 requirements for quarterly scanning requirements. Tenable s PCI Scanning Service is an Approved Scanning Vendor solution. Nessus Vulnerability Scanner Nessus Vulnerability Scanner is a vulnerability scanner that supports PCI DSS internal scanning requirements including pre-configured PCI scanning scripts, while allowing for organization configurable scanning policies that meet specific needs of the organization. Use Nessus to perform configuration and compliance audits and to monitor numerous technical controls to capture issues before regularly scheduled scans and/or PCI DSS compliance assessments allowing for an organization to remain continuously compliant and address issues prior to the arrival of QSAs. Used in conjunction with SecurityCenter or SecurityCenter CV, enhanced reporting, and a web-based dashboard, an organization can obtain a comprehensive and easily readable view into the state of the enterprise or drill down to view the state of the cardholder data environment or other critical network zones. This enables continuous monitoring of the organization s compliance with the PCI security standards. Passive Vulnerability Scanner Tenable Passive Vulnerability Scanner (PVS ) continuously monitors for vulnerabilities, and new or transient assets. PVS analyzes network traffic for insight into services, suspicious network relationships, and compliance violations. Using pre-configured or custom built scanning policies, an organization can have real-time monitoring. PVS detects transmission of unencrypted cardholder data. It can also be used to continuously monitor the integrity of the cardholder data environment. Used in conjunction with SecurityCenter CV, enhanced reporting and a web-based dashboard an organization can obtain a comprehensive and easily readable view into the state of the enterprise or drill down to view the state of the cardholder data environment or other critical network zones. PVS is available as a subscription or as part of SecurityCenter CV. SecurityCenter For organizations that have deployed multiple Nessus vulnerability scanners to meet periodic vulnerability scanning needs requirements, SecurityCenter accelerates and Product Applicability Guide 13

14 simplifies vulnerability and compliance management. SecurityCenter provides a single console for managing distributed Nessus vulnerability scanners and provides advanced analytics with its dashboards. SecurityCenter Continuous View SecurityCenter Continuous View (CV) brings real-time monitoring and integrated log analysis for vulnerability management, allowing organizations to continuously monitor for advanced threats and compliance violations. SecurityCenter CV offers the benefits of Nessus periodic scanning with passive network monitoring to provide continuous evaluation of the network and security information and event management (SEIM) to deliver centralized event storage; log monitoring, analysis, and correlation; and file integrity monitoring capabilities. SecurityCenter CV centralizes asset discovery with complete and continuous vulnerability assessment by integrating data from the following Tenable Products: SecurityCenter management console Unlimited Nessus vulnerability scanners Unlimited Passive Vulnerability Scanners Log Correlation Engine Nessus Enterprise Cloud (optional) Used as part of an organization s operational and auditing procedures, SecurityCenter CV provides information from scanning activities and its Log Correlation Engine that support security administration activities and sound vulnerability management decisions. Product Applicability Guide 14

15 N U M B E R O F P C I S N U M B E R O F C O N T R O L S M E T B Y N E S S U S E N T E R P R I S E C L O U D N U M B E R O F C O N T R O L S M E T B Y N E S S U S V U N E R A B I L I T Y S C A N N E R N U M B E R O F C O N T R O L S M E T B Y P A S S I V E V U L N E R A B I L I T Y S C A N N E R N U M B E R O F C O N T R O L S M E T B Y S E C U R I T Y C E N T E R - C O N T I N U O U S V I E W N U M B E R O F C O N T R O L S M E T B Y S E C U R I T Y C E N T E R T O T A L N U M B E R O F M E T O R A U G M E N T E D B Y T E N A B L E ** VMware Compliance Reference Architect Framework Tenable PCI Requirements Matrix Overview Tenable s PCI DSS Compliance Solution includes extensive vulnerability scanning, log analysis, and reporting using preconfigured scanning policies and providing the capability for client defined scanning policies for organization specific customization. When properly deployed and configured, the Tenable solution either fully meets or augments the following PCI DSS requirements: Table 3: Tenable PCI DSS Requirements Matrix for PCI DSS v3 PCI DSS REQUIREM ENT Requirement 1: Install and maintain a firewall configuration to protect cardholder data Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters Requirement 3: Protect stored cardholder data Requirement 4: Encrypt transmission of cardholder data across open, public networks Requirement 5: Protect all systems against malware and regularly update anti-virus software or programs Requirement 6: Develop and maintain secure systems and applications Requirement 7: Restrict Access to cardholder data by business need to know Requirement 8: Identify and authenticate access to system components Requirement 9: Restrict physical access to cardholder data Requirement 10: Track and monitor all access to network resources and cardholder data Requirement 11: Regularly test security systems and processes * Requirement 12: Maintain a policy that addresses the information security for all personnel Requirement A.1: Shared hosting providers must protect the cardholder data environment TOTAL ** Notes: When comparing partner tables, be aware that some VMware partner applicability whitepapers could be assessed using PCI DSS v2. * Includes requirements addressed by Nessus Enterprise Cloud which is an optional offering with SecurityCenter CV. ** Note that there is some duplication of DSS v3 requirements addressed across multiple Tenable products. Product Applicability Guide 15

16 Tenable PCI Requirements Matrix (By Product) Nessus Enterprise Cloud Nessus Enterprise Cloud enables remote, cloud-based management and sharing of multiple Nessus scanners, scan schedules, scan policies, and, most importantly, scan results. It is easy to share vulnerability and compliance information with users and groups: system owners, IT or Security Analysts, Internal Audit, and risk & compliance auditors. Users connect to the Nessus Enterprise Cloud console to access all Nessus scanners and scan results. Users may also perform external scans of their Internetfacing IPs for network and web application vulnerabilities. Figure 9: Nessus Enterprise Cloud Nessus Enterprise Cloud provides the following key capabilities: Scans your Internet-facing systems Unlimited scans of unlimited IP addresses Web application vulnerability assessments External network scans according to current PCI DSS standards Executive, attestation, and detailed reports offering proof of compliance Submission of reports to an acquiring bank, card brand, or merchant customer Receive quarterly PCI ASV attestation from Tenable s PCI-certified experts Nessus Enterprise Cloud customers have the ability to manage all internal and external scanning from the cloud. Nessus Enterprise Cloud acts as the Primary Nessus Scanner and can control multiple secondary Nessus Scanners whether they are located on premise within the corporate network, production environment, data center, remote locations, or in the cloud. Optionally, Nessus Enterprise Cloud can be managed by SecurityCenter CV. Product Applicability Guide 16

17 Tenable provides solutions to support or meet PCI DSS controls. Additional policies, processes or technologies are needed to be used in conjunction with Tenable s solutions to fully comply with PCI DSS. The following product matrix explains which PCI controls are supported or supplemented by Nessus Enterprise Cloud. Product Applicability Guide 17

18 Table 4: Applicability of PCI DSS v3.0 Controls to Nessus Enterprise Cloud P C I D S S V 3. 0 A P P L I C A B I L I T Y M A T R I X N E S S U S E N T E R P R I S E C L O U D Requirement 1: Install and maintain a firewall configuration to protect cardholder data N/A No controls in this PCI requirement are addressed by Nessus Enterprise Cloud. Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters Requirement 3: Protect stored cardholder data Requirement 4: Encrypt transmission of cardholder data across open, public networks Requirement 5: Protect all systems against malware and regularly update anti-virus software or programs Requirement 6: Develop and maintain secure systems and applications N/A N/A 4.1.a, 4.1.c, and 4.1.d N/A 6.1.a, 6.2.a, 6.5.d, 6.5.1, 6.5.2, 6.5.4, 6.5.5, 6.5.7, 6.5.8, 6.5.9, , 6.6 No controls in this PCI requirement are addressed by Nessus Enterprise Cloud. No controls in this PCI requirement are addressed by Nessus Enterprise Cloud. Nessus Enterprise Cloud can be used by an organization to verify required safeguards are in place and appropriately configured for transmitting sensitive cardholder data (4.1.a) over open, public networks by scanning all web portals or internet access points used for transmitting credit card data to collect information about allowed protocols and other encryption parameters (4.1.c & 4.1.d) such as of host names related to SSL keys, and age of SSL keys to ensure they are up-to-date. No controls in this PCI requirement are addressed by Nessus Enterprise Cloud. Nessus Enterprise Cloud can support an organization s vulnerability and patch management procedures by providing the organization the ability to scan external facing systems for vulnerabilities (6.1.a) and the status of patching (6.2.a) on those systems. Organizations that develop custom software for their cardholder data environment are required to ensure that secure coding practices, such as those identified in OWASP, are used. Nessus Enterprise Cloud can be used as part of the software development and testing processes to test for common coding vulnerabilities identified during external scanning. Implemented into a test environment that simulates the production environment, Tenable products can be used with other testing tools to check for well-known Product Applicability Guide 18

19 P C I D S S V 3. 0 A P P L I C A B I L I T Y M A T R I X N E S S U S E N T E R P R I S E C L O U D vulnerabilities (6.5.d) before being introduced into production. Nessus Enterprise Cloud can: be used to monitor live websites to look for errors that might be indicative of an injection flaw (such as SQL injection, OS command injection, LDAP and XPath injection flaws) (6.5.1) Nessus can check for a variety of SQL injection flaws in web applications. (6.5.1) be used to identify well known vulnerabilities, including buffer overflows(6.5.2) perform checks for communication over a variety of protocols and can recognize and report on insecure communication protocols(6.5.4) observe responses to web probes return a catch all error page or error codes that can provide information that could be used to breach the system (6.5.5) observe responses to web probes and return a catch all error page or error codes that can provide information that could be used to breach the system (6.5.5) check for well-known attacks against web applications, operating systems, and other software. Nessus Enterprise Cloud scans provide CVSS2 scores and criticality risk rankings which can be used to identify high risk vulnerabilities that need to be addressed prior to deployment of code changes (6.5.6) check for cross-site scripting vulnerabilities (6.5.7) perform checks for known access control vulnerabilities such as directory traversals and authentication bypass issues (6.5.8) can perform checks for cross-site request forgery vulnerabilities (6.5.9) can perform checks for broken authentication and session management vulnerabilities (6.5.10) Requirement 7: Restrict access to cardholder data by business need to know Requirement 8: Identify and authenticate access to systems components Requirement 9: Restrict physical access to cardholder data N/A N/A N/A While Tenable does not evaluate web application source code, Nessus, PVS and the Log Correlation Engine can be customized to identify changes to web applications for changes. Management can use information provided to determine if changes are significant and if an application security review is appropriate as required by DSS 6.6. No controls in this PCI requirement are addressed by Nessus Enterprise Cloud. No controls in this PCI requirement are addressed by Nessus Enterprise Cloud. No controls in this PCI requirement are addressed by Nessus Enterprise Cloud. Product Applicability Guide 19

20 P C I D S S V 3. 0 A P P L I C A B I L I T Y M A T R I X N E S S U S E N T E R P R I S E C L O U D Requirement 10: Track and monitor all access to network resources and cardholder data Requirement 11: Regularly test security systems and processes. Requirement 12: Maintain a policy that addresses the information security for all personnel. Requirement A.1: Shared hosting providers must protect the cardholder data environment N/A a, b, c, a, b, c 12.2.a, N/A No controls in this PCI requirement are addressed by Nessus Enterprise Cloud. Tenable supports the following specific controls: Nessus Enterprise Cloud supports the PCI DSS external vulnerability scanning requirements and can be scheduled to automatically run quarterly and thus guaranteeing an organization four quarterly external scans ( a) occurring in the last 12 month period and provides for rescanning after addressing identified vulnerabilities ( b). To fully achieve this testing procedure, an organization must hire an Approved Scanning Vendor (ASV), such as Tenable, to perform external scans ( c). As part of an organizations change control process, Nessus Enterprise Cloud meet PCI DSS a requirements for running vulnerability scans when significant changes are introduced into the environment. Identified high vulnerabilities ( b) can be addressed and scans rerun until vulnerabilities have been resolved. While use of an ASV is not required for non-quarterly scans, Tenable ASV ( c) are available for assisting with these scans when qualified internal resources are not available. Nessus Enterprise Cloud external scan results can (and should) be included in risk assessment processes, and should also be reviewed to support incident response monitoring and review: Along with other organizations risk management processes and tools, Nessus Enterprise Cloud can be used to identify critical external facing vulnerabilities requiring management s attention (12.2.a) As part of an organizations incident response plan, critical and high risk vulnerabilities identified during scanning activities can be used to assist in the incident response process, provide information about vulnerabilities that might have been exploited, or used to monitor for possible incidents that need to initiate a response. ( ) No controls in this PCI requirement are addressed by Nessus Enterprise Cloud. Product Applicability Guide 20

21 Nessus Vulnerability Scanner Nessus vulnerability scanners can be deployed as a hardware appliance or software solution, providing vulnerability scanning capabilities within an organization s corporate network, production or cardholder data environments, cloud based networks, and across networks. Figure 10: Nessus Vulnerability Scanner Nessus scanners provide on-premise vulnerability scanning capability for: Network devices: Juniper, Cisco, Palo Alto Networks, firewalls, printers, and more Virtual hosts: VMware ESX, ESXi, vsphere, vcenter Operating systems: Windows, Mac OS X, Linux, Solaris, BSD, Cisco ios, IBM iseries Databases: Oracle, SQL Server, MySQL, DB2, Informix/DRDA, PostgreSQL Web applications: Web servers, web services, OWASP vulnerabilities Compromise detection: Viruses, malware, backdoors, hosts communicating with botnet-infected systems, web services linking to malicious content Networks: IPv4/IPv6/hybrid networks Nessus Vulnerability Scanner is an internal vulnerability scanner that supports PCI DSS internal scanning requirements including pre-configured PCI scanning scripts, while allowing for organization configurable scanning policies that meet specific vulnerability scanning needs of the organization. Use Nessus to perform configuration and compliance audits and to monitor numerous technical controls to capture issues before regularly scheduled mandated scans and/or PCI DSS compliance audits allowing for an organization to remain continuously compliant and address issues prior to the arrival of auditors. Tenable Network Security also offers an evaluation version of the Nessus Vulnerability Scanner as well as a free home version limited to personal use in a non-commercial environment. This whitepaper describes the full enterprise version of Nessus which provides unlimited scanning of unlimited IP addresses/ranges and full functionality including credentialed checks for monitoring ongoing PCI compliance. Product Applicability Guide 21

22 Used in conjunction with SecurityCenter or SecurityCenter CV, enhanced reporting, and a web-based dashboard, an organization can obtain a comprehensive and easily readable view into the state of the enterprise or drill down to view the state of the cardholder data environment or other critical network zones. Tenable provides solutions to support or meet PCI DSS controls. Additional policies, processes or technologies are needed to be used in conjunction with Tenable s solutions to fully comply with PCI DSS. The following product matrix explains which PCI controls are supported or supplemented by Nessus Vulnerability Scanner. Product Applicability Guide 22

23 Table 5: Applicability of PCI DSS v3.0 Controls to Nessus Vulnerability Scanner P C I D S S V 3. 0 A P P L I C A B I L I T Y M A T R I X - N E S S U S Requirement 1: Install and maintain a firewall configuration to protect cardholder data Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters c, b, c, a, b, b, 1.4.b, a, 2.1.b, 2.1.c, b, e, 2.2.a, a, b, a, 2.2.3, b, a, 2.3.b, 2.4.a Nessus Vulnerability Scanners can be used by network administrators to ensure that their organization s policies and procedures are appropriately implemented with Tenable provided and custom developed scans: Ensure that documented processes for approving changes to networks are in place and operating appropriately by using audit scan results to confirm that identified changes match change control documents. (1.1.1.c) Monitor firewall configurations to ensure that devices are configured to meet organization established policies and PCI DSS requirements for restricting connections between untrusted networks and systems components in the cardholder data environment are in place. (1.2.1.b) and that all other inbound and outbound traffic is specifically denied (1.2.1.c). Monitor router configurations to verify the configurations are secured from unauthorized access (1.2.2.a) and that router configurations are synchronized (1.2.2.b) Monitor firewalls between cardholder environment and wireless networks deny traffic or only allow authorized traffic (1.2.3.b) Using customized Nessus configuration audits, Nessus can be used to audit devices used to access the organization s network remotely to ensure that the required software is installed, running, and configured correctly. (1.4.b). Organizations can supplement network documentation when administrators include management of configuration policies scripted in Nessus Vulnerability Scanner with the organization s documented configuration policies and its change control processes, thus providing a means for verifying that firewalls are configured as documented. (1.5) Nessus Vulnerability Scanner augments the following specific controls: By scanning for the use of default passwords, systems administrators can implement procedures for ensuring that newly installed systems are not using default passwords (2.1.a and b) and inappropriate default security parameters or accounts (2.1.c)). Checking for common SNMP and login settings on wireless devices to ensure that all wireless vendor defaults have been changed (2.1.1.b). Additionally, Nessus can audit the active wireless domain of each Windows device to develop a complete list of all wireless devices. (2.1.1.e) Configured with an organization s approved configuration standards to allow for audit policies to log into Windows, Unix, Linux, Mac OS X, AIX, HP-UX, and other systems to confirm compliance to organizational standards (2.2.a) or to profile systems ( a and b), discover open ports (2.2.2.a), identify security features and parameters implemented (2.2.3 and b), and identify Product Applicability Guide 23

24 Requirement 3: Protect stored cardholder data Requirement 4: Encrypt transmission of cardholder data across open, public networks Requirement 5: Protect all systems against malware and regularly update anti-virus software or programs Requirement 6: Develop and maintain secure systems and applications 3.1.b 4.1.a, 4.1.c, 4.1.d, 4.1.e, 4.1.f, 4.1.g 5.1, 5.2.a, 5.2.b, 5.2,c, a, 6.2.b, 6.5.d, 6.5.1, 6.5.2, 6.5.3, 6.5.4, 6.5.6, 6.5.6, 6.5.7, 6.5.8, 6.5.9, , 6.6 P C I D S S V 3. 0 A P P L I C A B I L I T Y M A T R I X - N E S S U S vulnerabilities (2.2.5.a). Used to look for any non-encrypted services on organization-specified assets that are required to use SSH or SSL for administration (2.3.b). Create asset inventory, including systems and software, using the asset discovery information that can be provided by Nessus scans. (2.4.a) Nessus can be used by an organization to identify the occurrence of unencrypted PAN (primary account numbers) 3.1.b and to monitor protection of encryption keys. As part of risk assessment process to identify all occurrences of PAN, organizations can use information provided by Nessus scanners to determine whether all instances of PAN storage are needed by the business and drill down to secure the data. Nessus Vulnerability Scanner can be used by an organization to verify safeguards are in place and appropriately configured for transmitting sensitive cardholder data (4.1.a) over open, public networks by scanning all web portals or internet access points used for transmitting credit card data to collect information about allowed protocols and other encryption parameters (4.1.c and 4.1.d). Nessus Vulnerability Scanner tests all SSL systems for compliance with PCI DSS, using periodic or continual scans to identify issues; such verification of host names related to SSL keys, secure protocols enabled when cardholder data is transmitted, and strength and age of SSL keys to ensure they are up-todate. (4.1.e, 4.1.f, & 4.1.g) Nessus Vulnerability Scanner can supplement as part of a comprehensive malware prevention program to safeguard an organization from malware by supporting procedures for ensuring ongoing compliance. Nessus scans can be configured to scan for anti-virus instances on system types susceptible to malware software, verify that AV protection is installed on all systems, and check that it is appropriately configured and up-to-date.(5.1 & 5.2.a, b, c) Organizations can supplement anti-virus policies and procedures supporting controls 5.1 and 5.2 to ensure that documented procedures are current and processes for supporting policies and procedures are working as documented. (5.4) Tenable updates Nessus Vulnerability Scanner regularly for new vulnerabilities. In conjunction with other external resources, Nessus scanners can support the vulnerability (6.1.a) and patch management (6.2.b) processes by continuously scanning the network, allowing the organization to identify new vulnerabilities provided in Tenable updates or as vulnerabilities are introduced into the network. Nessus provides CVSS2 scores for vulnerabilities identified, assigning a risk ranking to any vulnerabilities identified (6.1.a), which can be used in an organization s risk ranking process. Organizations that develop custom software for their cardholder data environment are required to ensure Product Applicability Guide 24

25 Requirement 7: Restrict access to cardholder data by business need to know 7.1.a, b, 7.1.3, 7.2.1, 7.2.2, P C I D S S V 3. 0 A P P L I C A B I L I T Y M A T R I X - N E S S U S that secure coding practices, such as those identified in OWASP, are used. Nessus Vulnerability Scanners can be used as part of the software development and testing processes to test for common coding vulnerabilities (6.5.d). Implemented into a test environment that simulates the production environment, Tenable can be used with other testing tools to check for well-known vulnerabilities before being introduced into production: Nessus scans can be used to monitor live websites to look for errors that might be indicative of an injection flaw (such as SQL injection, OS command injection, LDAP and XPath injection flaws) (6.5.1) Nessus can check for a variety of SQL injection flaws in web applications. (6.5.1) Nessus can be used to identify well known vulnerabilities, including buffer overflows. ( 6.5.2) Nessus can be used as a discovery tool to identify content of files by looking for cardholder data to determine whether encryption is required (6.5.3) Nessus scans check for communication over a variety of protocols and can recognize and report on insecure communication protocols (6.5.4) Nessus will observe responses to web probes and return a catch all error page or error codes that can provide information that could be used to breach the system (6.5.5) Nessus can be used to check for well-known attacks against web applications, operating systems, and other software. Nessus can provide CVSS2 scores and criticality risk rankings which can be used to identify high risk vulnerabilities that need to be addressed prior to deployment of code changes (6.5.6) Nessus scanners can check for cross-site scripting vulnerabilities (6.5.7) Nessus can perform checks for known access control vulnerabilities such as directory traversals and authentication bypass issues (6.5.8) Nessus can perform checks for cross-site request forgery vulnerabilities (6.5.9) Nessus can perform checks for broken authentication and session management vulnerabilities. (6.5.10) While Tenable does not evaluate web application source code, Nessus, PVS and the Log Correlation Engine can be customized to identify changes to web applications for changes. Management can use information provided to determine if changes are significant and if an application security review is appropriate as required by DSS 6.6. While Nessus Vulnerability Scanner does not actively perform access control functionality, Nessus compliance checks can supplement an organization s Access Control Processes and Procedures by providing information that can be used to assess compliance and alert an administrator when access control processes could be weak or out of compliance. Using Nessus compliance checks can be used to audit user accounts and provide information about: Linux and Windows servers and desktops, including information about access control lists implemented to meet an organization s requirements, provide a list of users authorized to access Product Applicability Guide 25

26 P C I D S S V 3. 0 A P P L I C A B I L I T Y M A T R I X - N E S S U S Requirement 8: Identify and authenticate access to systems components Requirement 9: Restrict physical access to cardholder data Requirement 10: Track and monitor all access to network resources and cardholder data Requirement 11: Regularly test security systems and processes , 8.1.2, a, 8.1.7, 8.2, a, a, a, 8.3.a, 8.5.a, 8.5.1, 8.7.a N/A a system, and how authentication is performed and logged. (7.1.a, b, 7.1.3) Audit security parameters to ensure that access control settings meet PCI requirements, including ensuring that access controls systems are in place ( ), that privileged access is assigned to individuals based upon job classifications, and that access is denied to all unless explicitly allowed. Provide data necessary to support access control operational procedures, including management review of access rights as part of periodic access monitoring (7.3) An organization can use Nessus to supplement identification management procedures by auditing account and password configuration parameters and auditing log records for compliance, including: Nessus scans can augment account administration activities by providing management with information that can be used for monitoring/assessing account administration activities, including reviewing account lists for possible shared accounts (8.1.1), and reviewing access rights are assigned based upon roles (8.1.2). Operating system account and password security parameters can be audited using Nessus scans, including whether lockout thresholds and duration are set as required by DSS a and Nessus scans that audit Unix and Windows operating systems can be used to ensure that each user is configured per organization policy, including ensuring that passwords or another authentication method is required (8.2), ensuring that password files are encrypted (8.2.1.a), password construction parameters are set to ensure complex passwords (8.2.3.a), require password changes at least every 90 days (8.2.4.a), and do not allow any of the last 4 passwords to be used when a passwords is changed (8.2.5.a). Nessus configuration audits ensure that generic or shared accounts are not used (8.5.a) including checking that passwords are not used across a service provider's customers (8.5.1). Nessus can be used to audit database (Oracle, SQL Server, MySQL, DB2, Informix/DRDA, PostgreSQL) configurations to ensure that users are required to authenticate prior to access (8.7.a) No controls in this PCI requirement are addressed by the Tenable solution , 10.4, b Nessus can supplement control by auditing log settings to identify compliance issues, for instance if all systems are configured to log failed access attempts as well as allowed access attempts b,, 11.1.d, 1.1.1, a, b, c, a, An organization can use Nessus scans to monitor for use of time synchronization technologies and determine if they are current. (10.4, b) Quarterly internal and external scanning supports PCI DSS 11 requirements. Tenable supports the following specific controls: Product Applicability Guide 26