PCI DSS Myths 2009: Myths and Reality


Published on

PCI DSS Myths 2009: Fiction and Reality

The presentation will cover PCI DSS-related myths and misconceptions that are common among some organizations dealing with PCI DSS challenges. Myths related to technical and process side of PCI, self-assessment and audits as well as PCI validation requirements will be discussed.
The information will be useful to all organizations dealing with credit card information and thus struggling with PCI DSS mandates

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

PCI DSS Myths 2009: Myths and Reality

  1. 1. PCI DSS Myths 2009: Fiction and Reality Dr. Anton Chuvakin Security Warrior Consulting www.securitywarriorconsulting.com November 2009
  2. 2. Agenda <ul><li>What is PCI DSS? </li></ul><ul><li>When does PCI DSS apply? </li></ul><ul><li>PCI DSS myths </li></ul><ul><li>Compliance vs validation </li></ul><ul><li>Conclusions </li></ul>
  3. 3. What is PCI DSS or PCI? <ul><li>Payment Card Industry Data Security Standard </li></ul><ul><li>Payment Card = </li></ul><ul><li>Payment Card Industry = </li></ul><ul><li>Data Security = </li></ul><ul><li>Data Security Standard = </li></ul>
  4. 4. PCI DSS is based on basic data security practices! <ul><li>Protect stored data </li></ul><ul><li>Encrypt transmission of cardholder data and sensitive information across public networks </li></ul>Protect Cardholder Data <ul><li>Maintain a policy that addresses information security </li></ul>Maintain an Information Security Policy <ul><li>Track and monitor all access to network resources and cardholder data </li></ul><ul><li>Regularly test security systems and processes </li></ul>Regularly Monitor and Test Networks <ul><li>Restrict access to data by business need-to-know </li></ul><ul><li>Assign a unique ID to each person with computer access </li></ul><ul><li>Restrict physical access to cardholder data </li></ul>Implement Strong Access Control Measures <ul><li>Use and regularly update anti-virus software </li></ul><ul><li>Develop and maintain secure systems and applications </li></ul>Maintain a Vulnerability Management Program <ul><li>Install and maintain a firewall confirmation to protect data </li></ul><ul><li>Do not use vendor-supplied defaults for system passwords and other security parameters </li></ul>Build and Maintain a Secure Network
  5. 5. Ceiling vs Floor <ul><li>PCI is the “floor” of security </li></ul><ul><li>This is fundamental reality of PCI DSS! </li></ul><ul><li>However, many prefer to treat it as a “ceiling” </li></ul><ul><li>Result: </li></ul><ul><li>security breaches </li></ul>
  6. 6. M1 - PCI just doesn’t apply to us … <ul><li>Myth : PCI just doesn’t apply to us , because… </li></ul><ul><li>“… we are small, a University, don’t do e-commerce, outsource “everything”, not permanent entity, etc” </li></ul>Reality: PCI DSS DOES apply to you if you “ accept, capture, store, transmit or process credit and debit card data ”, no exceptions! At some point, your acquirer will make it clear to you!
  7. 7. M2 - PCI is confusing <ul><li>Myth : PCI is confusing and not specific ! </li></ul><ul><li>“ We don’t know what to do, who to ask, what exactly to change” </li></ul><ul><li>“ Just give us a checklist and we will do it. Promise!” </li></ul>Reality: PCI DSS documents explain both what to do and how to validate it; take some time to read and understand it. <- Also, read our book on PCI! 
  8. 8. M3 - PCI is too hard <ul><li>Myth : PCI is too hard … </li></ul><ul><li>“… too expensive, too complicated, too burdensome, too much for a small business, too many technologies or even unreasonable” </li></ul>Reality: PCI DSS is basic, common sense, baseline security practice; it is only hard if you were not doing it before. It is no harder than running your business or IT – and you’ve been doing it!
  9. 9. M4 - Breaches prove PCI irrelevant <ul><li>Myth : Recent breaches prove PCI irrelevant </li></ul><ul><li>“ We read that ‘media and pundits agree – massive data losses “ prove ” PCI irrelevant’” </li></ul>Reality: Data breaches prove that basic PCI DSS security is not enough, but you have to start from the basics. PCI is actually easier to understand than other advanced security and risk matters. Start there!
  10. 10. M5 – PCI is Easy : Just Say “YES” <ul><li>Myth : PCI is easy : we just have to “say Yes” on SAQ and “get scanned” </li></ul><ul><li>“ What do we need to do - get a scan and answer some questions?” </li></ul>Reality: Not exactly - you need to: a) Get a scan – and then resolve the vulnerabilities found b) Do the things that the questions refer to – and prove it c) Keep doing a) and b) forever!
  11. 11. M6 – My tool is PCI compliant <ul><li>Myth : My network, application, tool is PCI compliant </li></ul><ul><li>“ The vendor said the tool is ‘PCI compliant’” </li></ul><ul><li>“ I use PA-DSS tools, thus I am PCI OK” </li></ul>Reality: There is no such thing as “PCI compliant tool, network”, PCI DSS compliance applies to organizations . PCI DSS combines technical AND process, policy, management issues; awareness and practices as well.
  12. 12. M7 – PCI Is Enough Security <ul><li>Myth : PCI is all we need to do for security </li></ul><ul><li>“ We worked hard and we passed an ‘audit’; now we are secure!” </li></ul>Reality: PCI is basic security, it is a necessary baseline, but NOT sufficient (floor – not the ceiling!) PCI is also about cardholder data security , not the rest of private data, not your intellectual property, not SSNs, etc. It also covers confidentiality , and NOT integrity and availability. There is more to security than PCI!
  13. 13. M8 – PCI DSS Is Toothless <ul><li>Myth : Even if breached and also found non-compliant, our business will not suffer. </li></ul><ul><li>“ We read that companies are breached and then continue being profitable; so why should we care?” </li></ul>Reality: Possible fines + lawsuits + breach disclosure costs + investigation costs + CC rate increases + contractual breaches + cost of more security measures + cost of credit monitoring = will you risk ALL that?
  14. 14. Summary: Eight Common PCI Myths <ul><li>PCI just doesn’t apply to us , because… </li></ul><ul><li>PCI is confusing and not specific ! </li></ul><ul><li>PCI is too hard </li></ul><ul><li>Recent breaches prove PCI irrelevant </li></ul><ul><li>PCI is easy : we just have to “say Yes” on SAQ and “get scanned” </li></ul><ul><li>My network, application, tool is PCI compliant </li></ul><ul><li>PCI is all we need to do for security! </li></ul><ul><li>Even if breached and then found non-compliant, our business will not suffer </li></ul>
  15. 15. Your Approach To PCI DSS <ul><li>Understand your merchant level (1-4) </li></ul><ul><li>Review the applicable requirements </li></ul><ul><li>Identify the gap between your current and required state </li></ul><ul><li>Implement changes to technology and policies! </li></ul><ul><li>Validate requirements and attest to it (via SAQ or QSA) </li></ul><ul><li>Key : continue to maintain secure-thus-compliant state! </li></ul>
  16. 16. Continuous Compliance vs Validation <ul><li>Reminder : PCI DSS compliance does NOT end when a QSA leaves or SAQ is submitted. </li></ul><ul><li>Q: What to do “after your QSA leaves”? </li></ul><ul><li>Use what you built for PCI to reduce risk </li></ul><ul><li>“ Own” PCI DSS; make it the basis for your policies </li></ul><ul><li>Think beyond credit card data and grow your security! </li></ul><ul><li>Note : a good QSA will check whether you are “wired” for continuous compliance. Pick one of that sort! </li></ul>
  17. 17. PCI and Security Today <ul><li><- This is the enemy! </li></ul><ul><li>This is NOT the enemy! -> </li></ul><ul><li>Remember: </li></ul><ul><li>security first , compliance as a result. </li></ul>
  18. 18. Conclusions and Action Items <ul><li>PCI is common sense, basic security; stop complaining about it - start doing it! </li></ul><ul><li>After validating that you are compliant, don’t stop: continuous compliance AND security is your goal , not “passing an audit.” </li></ul><ul><li>Develop “security and risk” mindset , not “compliance and audit” mindset. </li></ul>
  19. 19. Get More Info! <ul><li>“ PCI Compliance” by Anton Chuvakin and Branden Williams </li></ul><ul><li>Useful reference for merchants, vendors – and everybody else </li></ul><ul><li>Out in December 2009! </li></ul>
  20. 20. About Anton Chuvakin <ul><li>Dr. Anton Chuvakin </li></ul><ul><li>Email: [email_address] </li></ul><ul><li>Site: http://www.chuvakin.org </li></ul><ul><li>Blog: http://www.securitywarrior.org </li></ul><ul><li>LinkedIn: http://www.linkedin.com/in/chuvakin </li></ul><ul><li>Twitter: @anton_chuvakin </li></ul><ul><li>C onsulting: www.securitywarriorconsulting.com </li></ul>For more: http://www.chuvakin.org
  21. 21. More on Anton <ul><li>Book author: “Security Warrior”, “PCI Compliance”, “Information Security Management Handbook”, “Know Your Enemy II”, “Hacker’s Challenge 3”, etc </li></ul><ul><li>Conference speaker: SANS, FIRST, GFIRST, ISSA, CSI, Interop , many, many others worldwide </li></ul><ul><li>Standard developer: CEE, CVSS, OVAL, etc </li></ul><ul><li>Community role: SANS, Honeynet Project, WASC, CSI, ISSA, OSSTMM, InfraGard, ISSA, others </li></ul><ul><li>Past roles: Researcher, Security Analyst, Strategist, Evangelist, Product Manager, now Consultant </li></ul>
  22. 22. Security Warrior Consulting Services <ul><li>Logging and log management policy </li></ul><ul><ul><li>Develop logging policies and processes , log review procedures, workflows and periodic tasks as well as help architect those to solve organization problems </li></ul></ul><ul><ul><li>Plan and implement log management architecture to support your business cases; develop specific components such as log data collection, filtering, aggregation, retention, log source configuration as well as reporting, review and validation </li></ul></ul><ul><ul><li>Customize industry “best practices” related to logging and log review to fit your environment, help link these practices to business services and regulations </li></ul></ul><ul><ul><li>Help integrate logging tools and processes into IT and business operations </li></ul></ul><ul><li>Content development </li></ul><ul><ul><li>Develop of correlation rules, reports and other content to make your SIEM and log management product more useful to you and more applicable to your risk profile and compliance needs </li></ul></ul><ul><ul><li>Create and refine policies, procedures and operational practices for logging and log management to satisfy requirements of PCI DSS, HIPAA, NERC, FISMA and other regulations </li></ul></ul><ul><li>More at www.SecurityWarriorConsulting.com </li></ul>