We use cookies to provide you with a better experience. If you continue to use this site, we'll assume you're happy with this. Alternatively, click here to find out how to manage these cookies

hide cookie message
PCI Council clarifies rules for payment card data in the Cloud

PCI Council clarifies rules for payment card data in the Cloud

New guidelines for Cloud compliance are released

Article comments

Cloud providers and cloud customers now have a roadmap that defines their security responsibilities in the cloud following the release of a new set of guidelines from the PCI Security Standards Council.

Since 2004, the PCI Security Standards Council (PCI SSC) has maintained the Payment Card Industry Data Security Standard (PCI DSS), a proprietary information security standard for the handling of payment card data.

Increasingly, organisations have taken the PCI standard as a guide for implementing security, even if they don't have responsibility for customer payment card data. But the question of whether and how PCI DSS covers cloud deployments has remained up in the air.

Today, the PCI SSC took a big step toward easing the confusion with the release of the PCI DSS Cloud Computing Guidelines Information Supplement, detailing what is required to secure customer payment data and support PCI DSS compliance in the cloud.

The organisation says merchants that use or are considering using cloud technologies in their cardholder data environment will benefit from the guidance. PCI SSC says it also provides valuable guidance to third-party service providers that provide cloud services or products and to assessors reviewing cloud environments as part of a PCI DSS assessment.

"One of cloud computing's biggest strengths is its shared-responsibility model," says Chris Brenton, a PCI Cloud Special Interest Group (SIG) contributor and director of security for cloud server security platform provider CloudPassage.

"However, this shared model can magnify the difficulties of architecting a secure computing environment," Brenton says. "One of this supplement's greatest achievements is that it clearly defines the security responsibilities of the cloud provider and the cloud customer. With the PCI DSS as the foundation, this guidance provides an excellent roadmap to crafting a secure posture in both private and public cloud."

The new guidelines build on the work of the 2011 Virtualisation SIG, but also draw from other industry standards. PCI SSC says it will help organisations with the following:

  • Cloud overview. The supplement provides an explanation of common deployment and service models for cloud environments, including how implementations may vary within the different types.
  • Cloud provider/cloud customer relationships. The supplement outlines different roles and responsibilities across different cloud models and provides guidance on determining and documenting the responsibilities.
  • PCI DSS considerations. The supplement provides guidance and examples to help organisations determine responsibilities for individual PCI DSS requirements, including segmentation and scoping considerations.
  • PCI DSS compliance challenges. The supplement describes some of the challenges associated with validating PCI DSS compliance in a cloud environment.

In addition, PCI SSC says the document also includes a number of appendices that address specific PCI DSS requirements and implementation scenarios, including additional considerations to help determine PCI DSS responsibilities across different cloud service models; sample system inventory for cloud computing environments; a sample matrix for documenting how PCI DSS responsibilities are assigned between the cloud provider and client; and a starting set of questions that can help determine how PCI DSS requirements can be met in a particular cloud environment.

Share:

Comments

Advertisement
Send to a friend

Email this article to a friend or colleague:


PLEASE NOTE: Your name is used only to let the recipient know who sent the story, and in case of transmission error. Both your name and the recipient's name and address will not be used for any other purpose.


ComputerworldUK Knowledge Vault

ComputerworldUK
Share
x
Open
* *