Simplifying PCI on a PaaS Environment
19
Engine Yard - Confidential
-
Upload
engine-yard -
Category
Technology
-
view
812 -
download
0
description
Achieving PCI compliance can be a complex, time-consuming, and expensive undertaking. However, with the right approach it can be substantially less burdensome. In this webcast, we will provide background and recommendations to help you make the best possible decisions regarding PCI for your PaaS-based application. If you currently accept, or are contemplating accepting a payment card on your web application, this webcast is for you. In this presentation you will learn about: -An overview of PCI -How to scope your environment for PCI compliance -Ways to make compliance more manageable, and -Things to consider when approaching PCI compliance on a PaaS provider. To view the full webcast on-demand: http://pages.engineyard.com/an-introduction-to-pci-compliance-on-a-paas.html
Transcript of Simplifying PCI on a PaaS Environment
Engine Yard - Confidential
02/28/2012
• Overview of PCI • Make PCI Manageable • Scope Effectively • PCI on PaaS • Q&A
3
02/28/2012 4
02/28/2012 5
Requirements for storing, processing or transmitting payment card data
Endorsed by the major card brands
Four levels of validation depending on transaction volume
Enforced through incentives, fines or termination of privileges
02/28/2012
Build and Maintain a Secure Network
Maintain a Vulnerability Management Program
Protect Cardholder Data
Implement Strong Access Control Measures
Regularly Monitor and Test Networks
Maintain an Information Security Policy
PCI Remediation
Strategy
6
Key Areas of Focus Data Security
Access Control & Management
Encryption
Key Management
File Integrity Monitoring
Log Review Logging
Information Security Policies
Vulnerability Management
Network Security
02/28/2012
1 Ponemon Institute and PGP study
• Being PCI compliant does not provide assurances that a data breach will not occur. Of the card accepting merchants that sustained a data breach in 2009, 21% of them had previously been validated as PCI-compliant.
• The average cost of a data breach globally is $3.43 million -- or $142 per customer record. In the U.S., the cost is $6.65 million or $208 per customer record.
7
Insider threats matter!
02/28/2012 8
PCI compliance is required, however meeting compliance has traditionally placed a high cost in time and money on organizations. – Only 21% of companies
achieve PCI compliance their first time through the process.
– PCI is not something that can be “crossed off the list” once your organization attains an initial certification.
Specific Scope
Fail One Control,
Fail Audit
Low Regard for Risk Process
Costly Vendors
Regular Audit Manage Point in time audit, but not
point in time governance!
02/28/2012 9
02/28/2012 10
Document Card
Locations
• Determine the payment card data entry, processing, storage and exit points
Map Data Flow
• Map the logical flow of data throughout the environment
Identify Infrastructure
• Includes all systems, apps, DBs, and network devices supporting the data flows
02/28/2012 11
02/28/2012 12
http://www.engineyard.com/partner/braintree
02/28/2012 13
02/28/2012 14
• Process Evaluation: “Do we need to retain the full PAN?”
• Outsourcing: “Can someone else handle the transactions and compliance burden?”
Requirements Reduction
• Environment Redesign: “Can we consolidate our payment environment?” • Tokenization • Network Segmentation • Point-to-Point Encryption
Scope Reduction
02/28/2012 15
02/28/2012
I expect a certain level of security in my environment.
Your Customers Regulators
Can I meet my customer’s security requirements in the Cloud?
The Platform
IaaS Provider
16
02/28/2012 17
Your Data
Roles & Responsibilities
Security Capabilities
Access Controls
Logging & Monitoring
Risk Evaluation, Roadmap, & Improvement
PaaS Provider
02/28/2012 18
02/28/2012
More Information: • PCI Council http://ey.io/PCI-council • Cloud Security Alliance http://ey.io/cs-alliance • Engine Yard PCI whitepaper http://ey.io/paaspci
Feedback / Questions: • Ryan Gurney - [email protected]
19
