SlideShare utilise les cookies pour améliorer les fonctionnalités et les performances, et également pour vous montrer des publicités pertinentes. Si vous continuez à naviguer sur ce site, vous acceptez l’utilisation de cookies. Consultez nos Conditions d’utilisation et notre Politique de confidentialité.
SlideShare utilise les cookies pour améliorer les fonctionnalités et les performances, et également pour vous montrer des publicités pertinentes. Si vous continuez à naviguer sur ce site, vous acceptez l’utilisation de cookies. Consultez notre Politique de confidentialité et nos Conditions d’utilisation pour en savoir plus.
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
Requirements for storing, processingor 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 5
Data Security Key Areas of FocusBuild andMaintain aSecure NetworkProtectCardholder Data Information NetworkMaintain a Security SecurityVulnerability PoliciesManagementProgram PCI EncryptionImplement Strong Remediation Logging Key Management Log ReviewAccess Control Strategy Access ControlMeasures & ManagementMaintain anInformation File IntegritySecurity Policy MonitoringRegularly Monitorand Test Networks Vulnerability Management 02/28/2012 6
• 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 1 Ponemon Institute and PGP study customer record. In the U.S., the cost is $6.65 million or Insider threats matter! $208 per customer record. 02/28/2012 7
PCI compliance is required,however meeting compliance has Scope Specifictraditionally placed a high cost intime and money on organizations.– Only 21% of companies Fail One Low achieve PCI compliance their Control, Regard Fail for Risk first time through the process. Audit Process– PCI is not something that can be “crossed off the list” once your organization attains an Vendors Costly initial certification. Regular Manage Point in time audit, but not Audit point in time governance! 02/28/2012 8
Document • Determine the payment Card card data entry, processing, storage andLocations exit points • Map the logical flow of Map Data data throughout the Flow environment • Includes all Identify systems, apps, Infrastructure DBs, and network devices supporting the data flows 02/28/2012 10
• Process Evaluation: Do we needRequirements to retain the full PAN? • Outsourcing: Can someone else Reduction handle the transactions and compliance burden? • Environment Redesign: Can we consolidate our payment Scope environment? • Tokenization Reduction • Network Segmentation • Point-to-Point Encryption 02/28/2012 14