Catbird Addendum to VMware Product Applicability Guide … · catbird 6.0 solution Catbird 6.0 brings policy and compliance out of the filing cabinet and into the cloud age, with

Catbird Product Applicability Guide For Payment Card Industry (PCI) Partner Addendum

Product Applicability Guide – Catbird Addendum

VMware Compliance Reference Architecture Framework

Catbird Addendum to

VMware Product Applicability Guide

for

Payment Card Industry Data Security Standard

(PCI DSS) version 3.0

August 2014

Catbird Addendum

Product Applicability Guide – Catbird Addendum 2

VMware Compliance Reference Architect Framework

Table of Contents

INTRODUCTION .............................................................................................................................................................. 3

OVERVIEW OF PCI AS IT APPLIES TO CLOUD/VIRTUAL ENVIRONMENTS ............................................................ 8

SUMMARY OF RELEVANT CHANGES FROM PCI DSS 2.0 TO 3.0 ............................................................................ 9

CATBIRD® PCI REQUIREMENTS MATRIX OVERVIEW ............................................................................................. 15

CATBIRD 6.0 ................................................................................................................................................................. 16

SUMMARY ..................................................................................................................................................................... 23

Catbird Addendum



Introduction The virtualization and cloud revolution has brought unprecedented levels of agility and automation to IT infrastructure. Cloud systems leverage real-time, API driven provisioning and configuration engines. Applications scale up and out, down and in automatically based on utilization, performance and any other parameter desired. Data migrates across data centers for reasons of availability, resiliency and performance. Yet policy and compliance has largely remained static, a dusty three-ring binder in a world of big data. Traditional network security devices and approaches don’t secure virtualized infrastructure. Virtual Machines depend on network interfaces that can’t be controlled or monitored by existing physical network security. Traditional infrastructure boundaries have been blurred and virtualized. Configuration changes that used to require data center credentials, punch-down tools and screwdrivers can now be implemented in a few lines of code. Recent virtualization security guidelines published by PCI and NIST have become formal requirements and auditors are increasingly enforcing them. In a world where infrastructure has become dynamic – increasing audit scope, complexity and duration — compliance will need to become continuous; automated, instrumented, enforced and audited. CATBIRD 6.0 SOLUTION

Catbird 6.0 brings policy and compliance out of the filing cabinet and into the cloud age, with a comprehensive cloud policy solution that automates, enforces and audits for continuous compliance. Automation of enforcement against third-party standards reduces the cost and complexity of assuring control and maintaining compliance in virtual and cloud-based data centers and eliminates potential objections from auditors and CISOs that can stall or stop cloud transformation. Catbird transforms dynamic, self-scaling environments into compliance-aware systems through policy-based security and continuous monitoring and measurement against standards like PCI.

Catbird Addendum



Figure 2: Catbird architectural elements:

Catbird VMAs are deployed as a mesh of sensors implemented as virtual machines appliances (VMAs), configured in a classic hub and spoke architecture where the Control Center is the central process hub. Catbird TrustZones®, Policy and Compliance depend on technical controls for monitoring and enforcement. The technical controls reside within each VMA and consist of the following control components:

Virtual Infrastructure Monitoring (VIM)

Catbird is fully integrated with the VMware virtual infrastructure. The Catbird Virtual Infrastructure Monitor is the security operator’s eye into the virtual infrastructure, providing a real time view of relevant network security virtual machine and switch configurations. When a policy has been violated, the Catbird Virtual Infrastructure Monitor can perform response actions, including disconnecting a virtual machine from the network or powering off the virtual machine. The Virtual Infrastructure Monitor restores the principle of separation of duties in virtual infrastructure by providing the security operator real-time monitoring of the virtual infrastructure administrator’s activities as they relate to network security.

Firewall Management

Catbird integrates with VMware® vCloud Networking and Security App firewall (vCNS) and NSX Distributed Firewall app giving the security architect the power of the native firewall in an easy to use and automated configuration methodology.

Vulnerability Scanning, SCAP Checks

Catbird includes a network based vulnerability scanner for vulnerability management. Understanding the network-accessible vulnerabilities in virtualized infrastructure is the first step to tightening security posture and implementing a vulnerability management program for compliance. Catbird enables the security architect to view detected vulnerabilities from the same tool that configures the firewall and Intrusion Prevention System, for a holistic view of the enterprise security posture. Catbird 6.0 expands its continuous monitoring capabilities to include extensive configuration checks based on Security Content Automation Protocol (SCAP). Integration with Service Composer compatible, third party vulnerability and SCAP configuration scanning services is available through the NSX/Service composer API set.

Netflow

Visualizing network topology is a powerful tool used by security architects to configure network based security controls. With an innovative network flow visualization display, Catbird provides the best possible view into network activity giving the security architect the capacity to easily configure access controls, manage vulnerabilities, or respond to security incidents. Netflow information can also be captured from NSX/Service Composer platform

Intrusion Prevention System (IPS)

Positioned on the virtual switch fabric, Catbird is in the optimal position to provide deep packet inspection for its Intrusion Prevention System. Monitoring all traffic traversing the virtual switch, Catbird can detect hostile traffic entering the virtual data center, and more importantly, all hostile traffic between virtual machines themselves. By virtualizing the Intrusion Prevention System, Catbird’s software defined security approach provides a scalable solution for Intrusion Detection and Prevention. Integration with third party, Service Composer compatible IDS/IPS control vendors is available through the NSX/Service composer API set.

Catbird Addendum



Network Access Control (NAC)

Catbird not only provides a combination of network based security controls on the virtual switch fabric, but helps to protect physical infrastructure as well. The virtual switches in the hypervisor can be connected to physical switches that interconnect physical devices that may be on the same layer-2 network as the virtualized asset. With Catbird’s Network Access Control (NAC), the security architect knows at all times what is directly connected at layer-2 on the physical switches, optionally giving them the power to implement logical zoning inclusive of these directly connected assets.

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.

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 in the solution framework series that, together with this Guide, comprise the PCI DSS Reference

Architecture are the Architecture Design Guide and the Validated Reference Architecture, which are intended to 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.

This Product Applicability Guide Addendum builds upon the base VMware control mapping and alignment for PCI DSS 3.0, which

is documented in the VMware Product Applicability Guide for PCI-DSS 3.0 on the VMware Solutions Exchange.

In addition, VMware and Coalfire are engaged with VMware Technology Partners such as Catbird Networks, Inc. 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.

https://solutionexchange.vmware.com/store/products/vmware-approach-to-compliance-v2-0

https://solutionexchange.vmware.com/store/products/vmware-pci-v3-0-compliance-documents

https://solutionexchange.vmware.com/store/category_groups/technology-partners?technology_type_category_id%5b%5d=142&q=

Catbird Addendum



Figure 3: PCI Requirements

Figure 4: VMware + Partner Product Capabilities for a Trusted Cloud

Catbird Addendum



Figure 5: VMware + Catbird Capabilities for a Trusted Cloud

Catbird Addendum



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, 2010. 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).

Catbird Addendum



Figure 6: 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.

Catbird Addendum



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.

Catbird Addendum



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

(http://www.vmware.com/solutions/cloud-computing/public-cloud/faqs.html):

“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 7: 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

http://www.vmware.com/solutions/cloud-computing/public-cloud/faqs.html

Catbird Addendum



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 8: VMware Software Defined Data Center Products

http://www.vmware.com/solutions/cloud-computing/index.html#tab3

http://www.vmware.com/cloud-computing/cloud-architecture/vcat-toolkit3.html

Catbird Addendum



Figure 9: 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 email us at

[email protected]

Figure 10: Catbird’s Virtual Environment Deployment

https://solutionexchange.vmware.com/store/products/vmware-compliance-framework-documents-for-pci

https://solutionexchange.vmware.com/store/products/vmware-compliance-framework-documents-for-pci

mailto:[email protected]

Catbird Addendum



Catbird® PCI Compliance Solution

All merchants, service providers, financial institutions and other entities that store, process, or transmit payment cardholder data are required by card brands to comply with the Payment Card Industry Data Security Standard (PCI DSS). The use of virtualization technology in private clouds is not exempt from requirements of PCI DSS 3.0, which raises the bar for security in a virtualized Cardholder Data Environment (CDE). Traditional physical security components that are usually deployed at the network edge make it difficult if not impossible to effectively monitor and control virtual components, so it is vital for organizations using virtual technology in the CDE to adopt tools that protect cardholder data. Catbird is a unique solution engineered to automate seamless, comprehensive network security and PCI DSS compliance for organizations with a virtual CDE. Table 2: Catbird Solution

Solution Description

Catbird 6.0

The Catbird Control Center acts as the Policy Definition Point, providing expert visualization,

workflow and reporting built on top of three management components:

Catbird TrustZones® logical zones providing automatic detection, inventory and grouping

of all VMs

Policy-based security defining how Catbird’s multi-function network security controls are

applied to TrustZones

Compliance enforces regulatory requirements in virtualized infrastructure by monitoring

and capturing security events and measuring them in real-time against the leading compliance frameworks, including PCI.

The Catbird Virtual Machine Appliances (VMA) is the collection of VMAs. A VMA is not deployed

on individual virtual machines but only on the virtual network itself – one per virtual switch. The Control Center distributes security tasks to this mesh of VMAs. By distributing the security load across the VMA mesh, Catbird can scale across multiple physical locations, and multiple virtual hosts, while executing hypervisor functions available only locally. In this way, Catbird’s model of Software-Defined Security can leverage cloud-scale economics.

The VMA sensors are the policy enforcement points tasked by the Control Center to monitor and enforce security.

VMAs are Linux virtual machines executing the technical controls including firewall management, Network Access Control (NAC), Intrusion Detection and Protection (IDS/IPS), Netflow and vulnerability/configuration monitoring – as well as executing numerous other security tasks via hypervisor interfaces.

Catbird Addendum



Catbird® PCI Requirements Matrix Overview

Catbird includes a demonstrable means for Enterprises to monitor, assess, and enforce key attributes of their Information Security

Program in context with pertinent PCI 2.0 and 3.0 Standards. When properly deployed and configured, the Catbird solution either

fully meets or augments the following PCI DSS requirements:

Table 3: Catbird PCI DSS Requirements Matrix for PCI DSS v3

PCI DSS REQUIREMENT

NUM B E R O F P C I

RE Q UI RE M E N TS

T O T AL N UM BE R O F C ON T R O LS

M E T O R AU GM E N TE D B Y

C ATB IR D*

Requirement 1: Install and maintain a firewall

configuration to protect cardholder data 35 15

Requirement 2: Do not use vendor-supplied defaults for

system passwords and other security parameters 32 8

Requirement 3: Protect stored cardholder data 44 0

Requirement 4: Encrypt transmission of cardholder data

across open, public networks 11 4

Requirement 5: Protect all systems against malware and

regularly update anti-virus software or programs 11 4

Requirement 6: Develop and maintain secure systems

and applications 42 5

Requirement 7: Restrict Access to cardholder data by

business need to know 10 2

Requirement 8: Identify and authenticate access to

system components 43 10

Requirement 9: Restrict physical access to cardholder

data 44 0

Requirement 10: Track and monitor all access to network

resources and cardholder data 41 18

Requirement 11: Regularly test security systems and

processes. 36 5

Requirement 12: Maintain a policy that addresses the

information security for all personnel. 47 4

Requirement A.1: Shared hosting providers must protect

the cardholder data environment 8 1

TOTAL

404

76

Catbird Addendum



Catbird® PCI Requirements Matrix (By Product)

Catbird 6.0 Security policy automation for private & hybrid clouds

• Logical zoning based on common trust class

• Support for leading hypervisors and SDN platforms

• Lifecycle security management for virtual machines

• Integrates existing network controls with new virtualized security controls

• Mapped to standards and audited for proof of continuous compliance

In addition to supporting DSS control requirements as outlined below, Catbird 6.0 can be used to reduce the scope for DSS

compliance by defining or isolating the “in-scope” cardholder data environment through use of TrustZones. While not required by

PCI DSS v3, isolating the cardholder data environment from other network segments can greatly reduce the scope of the network

that is required to be DSS compliant. TrustZones network configuration policies defined for an organization’s virtual CDE network

can be used to isolate the zone that processes, stores, or transmits cardholder data from other virtual network segments. Catbird

integrates with vCloud Networking and Security App firewall (vCNS) and NSX Distributed Firewall to allow the network

administrator to administer or orchestrate the virtual network firewall rules/policies using the Catbird Console’s user interface.

Using TrustZones to isolate (segment) the organization’s CDE from other virtual processing, reduces the scope of an

organization’s network that must be compliant with PCI DSS v3; and makes administration, monitoring, and auditing for PCI DSS

compliance easier for an organization. Refer to PCI DSS v3, section on Scope of PCI DSS Requirements and Network

Segmentation and Appendix D for additional information regarding scoping and network segmentation as it applies to PCI

compliance.

Figure 11: Catbird 6.0 Overview

Catbird provides solutions to support or meet PCI DSS controls. Additional policy, process or technologies may be needed to be used in conjunction with Catbird’s solutions to fully comply with PCI DSS.

Catbird Addendum



Table 4: Applicability of PCI DSS v3.0 Controls to Catbird 6.0

P CI D S S V 3 . 0 AP P L IC A B I L I T Y M AT RIX

RE Q UI RE M E N T CO N TR O LS

ADD RE S S E D

DE S C RI P TI ON

Requirement 1: Install and

maintain a firewall configuration to protect cardholder data

1.1.1.c, 1.1.2.a, 1.1.3.a, 1.1.4.c, 1.1.6.a, 1.1.6.c, 1.1.7.b, 1.2.1.a, 1.2.1.b, 1.2.1.c, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.7

Organizations are required to document and implement network policies, standards, and procedures for managing their cardholder data environment network. An organization can use Catbird to augment these policies and procedures to actually implement and monitor virtual networks and the hypervisor by using Catbird’s asset discovery capabilities, orchestrating the virtual network controlled by vShield, and using Catbird TrustZones to provide appropriate segmentation within the virtual network, and to implement intra-net routing rules to meet PCI DSS requirement. Using these tools, a network administrator can:

Support an organization’s network change control process with real-time monitoring for network assets including discovering net virtual components introduced in to the cardholder data TrustZones, which allows the organization’s change administrator to verify that all changes were introduced using the organizations authorized change control procedures (1.1.1.c)

Support creation of network and dataflow diagrams by analyzing network traffic and providing Catbird diagrams representing actual traffic to create formal network and cardholder dataflow diagrams (1.1.2.a) and verify that existing diagrams are current and include all required connections (1.1.3)

Use TrustZones to create vShield rules that isolate internal network zones from DMZ (1.1.4.c)

Facilitate implementation of an organization’s network configuration standard by providing real-time network traffic information that can be used to create (1.1.6.a) and examine (1.1.6.c) documented configuration control standards

Facilitate periodic review of virtual firewall rules by providing reports of firewall rule sets (1.1.7.b)

Define a CDE TrustZone and use the Catbird Firewall Orchestration component to create virtual firewall rules to permit necessary in-bound and out-bound traffic to the CDE zone and deny all other traffic (1.2.1.a – 1.2.1.c)

Facilitate compliance with an organizations virtual firewall configuration standards by allowing the network administrator to orchestrate (or apply) vShield firewall rules to implement rules that limit

- DMZ in-bound traffic to only systems components that authorized public ports/protocols (1.3.1)

- Inbound Internet traffic to IP addresses within the DMZ (1.3.2)

- Direct connections are prohibited between

Catbird Addendum





ADD RE S S E D

DE S C RI P TI ON

Internet and CDE (1.3.3) - Prohibit unauthorized out-bound traffic from

the CDE (1.3.4) - System components that store cardholder

data to internal network zones (1.3.7)

Use TrustZones to isolate virtual components used for cardholder data storage in to the Cardholder Data Environment (1.3.7)

Requirement 2: Do not use

vendor-supplied defaults for system passwords and other security parameters

2.1.b, 2.2.b, 2.2.c, , 2.2.2, 2.2.3, 2.2.4.b, 2.3.b, 2.4.a

Catbird provides a SCAP-based configuration checking utility that enables the enterprise with the ability to verify that system passwords and other PCI DSS configuration requirements are in place on virtual machines and hypervisors. Industry recommended changes to hardening standards are provided to organizations as introduced by NIST either automatically or upon request, so that organizations can remain current on recommended changes to hardening standards. Catbird’s SCAP-based configuration checking utility can be used by an organization to supplement the policies and procedures for administering virtual systems and hypervisors associated with the in-scope cardholder data environment to implement and monitor the virtual network components to comply with DSS Requirement 2, including:

Identifying virtual machines (VM) or hypervisors with no passwords or vendor default passwords (2.1.b)

Allowing administrator to automate compliance of NIST hardening checklists through use of NIST Tier IV checklists (2.2.c), ensuring that hardening checklists are up-to-date using Catbird’s updates for newly identified vulnerabilities (2.2.b).

Monitoring for emerging threats using Catbird’s IDS/IPS functionality which allows an organization to monitor for new vulnerabilities that need to be addressed by generating reports based upon schedules controlled by organizations (2.2.b)

Identifying actual ports/protocols using Catbird’s real-time traffic monitoring, the organization can verify that all necessary network traffic is documented in system standards(2.2.2.b), and insecure ports/protocols justified (2.2.3)

Allowing an organization to use the Tier IV hardening checklists to set or monitor security parameters for virtual systems (2.2.4.b) ensuring that unnecessary functionality is removed/ disabled.

Monitoring flow between TrustZones and using hardening checklists to verify that non-console administrative activity is over encrypted protocol(2.3.b)

Supplementing the process for creating and maintaining the asset inventory by using Catbird’s Virtual Infrastructure Manager to discover virtual machines and hypervisors running in the network (2.4.a)

Catbird Addendum





ADD RE S S E D

DE S C RI P TI ON

Requirement 3: Protect stored

cardholder data N/A Catbird does not directly contribute to this requirement.

Requirement 4: Encrypt

transmission of cardholder data across open, public networks

4.1.a, 4.1.b, 4.1.c, 4.1.e

Catbird includes inventory, flow monitoring, IDS, and IPS capabilities. Catbird enables an enterprise with the means to monitor all virtual machines and enable the appropriate IPS templates to block unauthorized traffic to and from cardholder systems. Catbird’s asset identification and flow monitoring capabilities can support an organizations process for identifying all traffic into and out of the Cardholder Data Environment, which can be identified as a TrustZone in Catbird. By analysing this information, an organization can use Catbird’s IPS templates to monitor and if appropriate block unauthorized traffic to/from cardholder data TrustZone. An organization can use Catbird to:

Identify traffic to/from cardholder data zone and other trusted zones that requires additional protection (4.1.a)

Use SCAP-based configuration checklists to monitor for vulnerability associated with transmission key or certificate (4.1.b)

Monitor flow analysis data to confirm that encrypted protocols are being used (4.1.c)

Use flow analysis, vulnerability scanning, and configuration scanning to confirm secure configuration of transmissions (4.1.e)

Requirement 5: Protect all

systems against malware and regularly update anti-virus software or programs

5.1, 5.2.a, 5.2.b, 5.2.c While not an anti-virus tool, Catbird supports the DSS requirement 5 compliance by providing SCAP-based configuration checking which enables the enterprise with the ability to verify that anti-virus (AV) programs are properly deployed, including: ensuring that AV tools are current, configured to perform periodic scans, and that AV audit logs are generated (5.2.a – 5.2.c). Catbird’s vulnerability scanning can be used to identify vulnerable components (5.1) that do not have AV software configured.

Requirement 6: Develop and

maintain secure systems and applications

6.1.a, 6.2.b, 6.4.1.b, 6.4.2, 6.4.5.b

Catbird can supplement other tools used in an organization’s security vulnerability management program and patching processes, as well as it’s organization infrastructure change management procedures by:

Supplementing vulnerability management by using Catbird’s vulnerability scanning and SCAP checklist signatures as one of the external sources used to identify new security vulnerabilities and applying CVSS risk rankings (6.1.a)

Supplementing patch management processes by using Catbird’s SCAP checklist monitoring to identify virtual machines or hypervisors that do not have the most current patches installed (6.2.b)

Establishing TrustZones for production and

Catbird Addendum





ADD RE S S E D

DE S C RI P TI ON

development/test environments and monitoring activity to ensure separation of the environments (6.4.1.b) and by monitoring individual access to analyze compliance with separation-of-duties requirements (6.4.2)

Reporting changes to the virtual network or hypervisor so that change administrators can oversee changes in the hypervisor management or virtual infrastructure configuration to verify that changes introduced comply with an organizations change control procedures (6.4.5.b)

Requirement 7:

Restrict access to cardholder data by business need to know

7.1.2.a, 7.2.3 Catbird enhances an organizations ability to restrict access into the cardholder data environment by enabling an organization to restrict access into the cardholder data environment through Catbird’s TrustZone functionality. Assets containing cardholder data may be isolated to a designated TrustZone that is distinct from all other Assets. Deny all rules can be established in Catbird to restrict access to the cardholder TrustZone from all non-administrative (authorized) zones (7.2.3). Additionally, Catbird provides role-based application access with six defined Catbird roles for administrating and using the Catbird application allowing for distribution of virtual and hypervisor network management responsibilities (71.2.a):

1. Administrator (super user for Catbird) 2. Auditor (read only) 3. Operator 4. Firewall Operator 5. IPS Operator 6. Vulnerability Scanner

Requirement 8:

Identify and authenticate access to systems components

8.1.4, 8.1.6, 8.1.7, 8.1.8, 8.2.1.b, 8.2.1.c, 8.2.3.a, 8.2.4.a, 8.2.5.a, 8.7.c

Catbird enables the enterprise with the ability to prevent the use of clear-text passwords or vulnerable services through IDS/IPS policies. Catbird provides a SCAP-based configuration checking mechanism that enables the enterprise with the ability to verify that system passwords are meeting DSS security requirements. Using Catbird’s SCAP-based configuration checking, an organization can verify that they have properly configured the virtual systems and hypervisor to meet DSS Requirement 8 control requirements, including monitoring for compliance of virtual machines including reporting when:

Accounts that have been inactive for 90 days (configurable threshold) have not been disabled (8.1.4)

Systems are not configured to lock accounts after no more than 6 invalid logon attempts (8.1.6)

Systems are not configured to lockout for a minimum of 30 minutes or until administer enables the user ID (8.1.7).

Catbird Addendum





ADD RE S S E D

DE S C RI P TI ON

Systems are not configured to require re-authentication after being idle 15 minutes (8.1.8)

Systems are not configured to use strong-encryption for password storage (8.2.1.b), during transmission (8.2.1.c)

Password control compliance requirements are not met, including: minimum password length of at least 7 characters (8.2.3.a), requiring users to change passwords at least every 90 days (8.2.4.a), and passwords cannot be changed to the same value as the previous 5 passwords (8.2.5.a)

Virtual machines hosting databases do not require authentication (8.7.c)

Note that Catbird does not support application specific authentication control compliance.

Requirement 9: Restrict physical

access to cardholder data N/A Catbird does not directly contribute to this requirement.

Requirement 10: Track and

monitor all access to network resources and cardholder data

10.1, 10.2.2, 10.2.4, 10.2.5.a, 10.2.5.b, 10.2.5.c, 10.3.1, 10.3.2, 10.3.3, 10.3.4, 10.3.5, 10.3.6, 10.4.1.a, 10.5.1, 10.5.2, 10.5.3, 10.6.1, 10.6.3

Catbird enables the organization with the ability to generate

automated audit logs for a variety of operational security

events that are pertinent to the tracking and monitoring of

virtual cardholder environment, including: .

Using Catbird to enforce SCAP hardening standards for logging or by alerting a monitor/auditor when the log settings are not appropriately configured (10.1)

Providing audit trails through Catbird for all hypervisor administration activity orchestrated through Catbird’s firewall orchestration capabilities (10.2.2), for all invalid access attempts to the hypervisor, and for all Catbird application activity (10.2.4)

Within the Catbird application, providing audit logs for use of Catbird including use of identification/authentication mechanism and changes to any account with Catbird privileges (10.2.5.a and 10.2.5.c)

Generating log records that include all PCI DSS required information including user identification, type of event, date/time, success/failure indication, origin of event, and identity of affected component (10.3.1 – 10.3.6)

Catbird can be configured to use NCP and an organization’s designated time server (10.4.1.a) Catbird provides an audit role that can be used by designated individuals that have a need to view Catbird’s audit records/reports without permitting other Catbird activities (10.5.1) Catbird provides no application function to alter Catbird audit log records, but Coalfire recommends that Catbird audit records be copied to an organization’s central log server to protect the logs (10.5.2 and 10.5.3). If an organization places their central log server in a dedicated TrustZone, Catbird can

Catbird Addendum





ADD RE S S E D

DE S C RI P TI ON

monitor access to the zone for inappropriate access. Catbird provides network log monitoring reports for monitoring hypervisor, orchestrated firewall rules, and IDS/IPS logs (10.6.1) and when defined in Catbird email alerts will be generated for exceptions and anomalies based upon thresholds established by the organization (10.6.3)

For PCI compliance, additional audit monitoring tools and

processes will be needed for systems log and application log

audit monitoring.

Requirement 11: Regularly test

security systems and processes. 11.2.1, 11.2.3, 11.4.a, 11.4.b, 11.5.a

As part of an organization’s PCI DSS required scanning program, Catbird supports the internal vulnerability scanning requirements. While not an Authorized Scanning Vendor (ASV), Catbird’s Vulnerability Scanning tool, which includes an embedded SAINTscanner® can be used to support internal scanning requirements (11.2.1) and schedule quarterly scanning with Catbird’s policy-defined frequency (11.2.3). Catbird IDS/IPS capabilities support monitoring of traffic at the perimeter of CDE defined TrustZones including:

Monitoring all perimeter traffic of the CDE and critical points within the CDE (11.4.a)

Alerting personnel when suspect activity occurs (11.4.b)

Catbird can partially support an organizations file integrity monitoring by detecting and alerting personnel when changes to critical system configuration files on virtual machines and hypervisor occur (11.5.a)

Requirement 12: Maintain a

policy that addresses the information security for all personnel.

12.3.3, 12.3.8, 12.10.3, 12.10.5

Catbird can assist management’s Acceptable Use Policy (AUP) documentation requirement 12.3.3 by discovering assets on the network and assisting in creating the device inventory list for the AUP; and can be used to confirm that systems are configured to disconnect remote access sessions after a specified period of time as required by DSS requirement12.3.8. Catbird can be a component in an organization’s Incident Response process when using Catbird vulnerability scans to cover critical network components to identify potential incidents, generate alerts based upon organization defined thresholds (12.10.5), and if appropriate, disconnect/disable impacted network interfaces and virtual machines to supplement/support personnel designated for 24/7 incident response and monitoring (12.10.3).

Requirement A.1: Shared hosting

providers must protect the cardholder data environment

A.1.2.b Catbird can assist a shared hosting provider to comply with A.1 requirements when shared hosting providers configure each customer’s environment as a separate TrustZone and monitor for any unauthorized traffic between customers’ zones (A.1.2.b)

Catbird Addendum



Summary Cloud computing and threats to sensitive data such as that covered by the Payment Card Industry under their Data Security Standards are both evolving. The benefits and maturity of cloud computing led by VMware and the Software Defined Data Center have led VMware's customers and partners to host most (and approaching all) of the enterprise applications on this platform. To answer that need VMware and its Technology and Audit partners have delivered a set of documentation pertinent to mainstream regulations such as PCI DSS version 3.0. Internalizing the information available on VMware Solution Exchange is the first step in understanding which of the VMware products can be leveraged along with features and capabilities that should be considered. This paper gives guidance on Catbird’s product suite’s applicability for addressing support of PCI DSS version 3.0 control requirements. Acknowledgements:

VMware would like to recognize the efforts of Catbird Network, Inc., and the numerous VMware teams that contributed to this paper and to the establishment of the VMware Compliance Program. VMware would also like to recognize the Coalfire Systems Inc. VMware Team www.coalfire.com/Partners/VMware for their industry guidance. Coalfire®, a leading PCI QSA firm, provided PCI guidance and control interpretation aligned to PCI DSS v.

3.0 and the Reference Architecture described herein. The information provided by Coalfire Systems and contained in this document is for educational and informational purposes only. Coalfire Systems makes no claims, promises or guarantees about the accuracy, completeness, or adequacy of the information contained herein. About Coalfire Coalfire Systems is a leading, independent information technology Governance, Risk and Compliance (IT GRC) firm that provides IT audit, risk assessment and compliance management solutions. Founded in 2001, Coalfire has offices in Dallas, Denver, Los Angeles, New York, San Francisco, Seattle and Washington, D.C., and completes thousands of projects annually in retail, financial services, healthcare, government and utilities. Coalfire has developed a new generation of cloud-based IT GRC tools under the Navis

® brand that clients use to efficiently manage IT controls and

keep pace with rapidly changing regulations and best practices. Coalfire’s solutions are adapted to requirements under emerging data privacy legislation, the PCI DSS, GLBA, FFIEC, HIPAA/HITECH, NERC CIP, Sarbanes-Oxley and FISMA. For more information, visit www.coalfire.com.

VMware, Inc. 3401 Hillview Avenue Palo Alto CA 94304 USA Tel 877-486-9273 Fax 650-427-5001 www.vmware.com

Copyright © 2013 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at

http://www.vmware.com/go/patents. VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be

trademarks of their respective companies. Item No: VMW_YYQQ_DS_ProgramName 03/13

https://solutionexchange.vmware.com/store/category_groups/technology-partners?technology_type_category_id%5b%5d=142&q=

http://www.coalfire.com/Partners/VMware

http://www.coalfire.com/

Documents

Catbird Addendum to VMware Product Applicability Guide … · catbird 6.0 solution Catbird 6.0 brings policy and compliance out of the filing cabinet and into the cloud age, with