PCI Seminar, July 22nd 2009 <ul><li>Introduction </li></ul><ul><li>An auditor’s view </li></ul><ul><li>Ritchie Jeune - Evo...
Welcome <ul><li>Mark Hopwood </li></ul><ul><li>Technology & Operations Director </li></ul><ul><li>Pod1 </li></ul>
PCI - Pod1’s perspective <ul><li>Why is PCI important? </li></ul><ul><li>How we view PCI </li></ul><ul><li>A brief history...
Why is PCI important? <ul><li>It’s mandatory </li></ul><ul><li>It’s good for business </li></ul><ul><li>It’s a trojan hors...
How we view PCI
A brief history of eCommerce at Pod1 <ul><li>2001 to 2008 </li></ul><ul><li>2008 onwards </li></ul>
Gutenberg - a Pod1 developed eCommerce solution
Magento - supported open source eCommerce <ul><li>Developed by Varien </li></ul><ul><li>Thriving open source community </l...
Pod1’s plans for PCI compliance <ul><li>Aiming to be a PCI compliant organisation this Autumn: </li></ul><ul><li>Rackspace...
Pod1’s plans for PCI compliance <ul><li>Internal change to support this: </li></ul><ul><li>Stronger processes </li></ul><u...
Suggested next steps <ul><li>Speak to your account management team </li></ul><ul><li>Conduct your own self-assessment </li...
Thank you [email_address]
Upcoming SlideShare
Loading in …5
×

Pci Seminar Mh

417 views

Published on

Pod1 and PCI

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

Pci Seminar Mh

  1. 1. PCI Seminar, July 22nd 2009 <ul><li>Introduction </li></ul><ul><li>An auditor’s view </li></ul><ul><li>Ritchie Jeune - Evolution Systems Limited </li></ul><ul><li>PCI compliant web hosting </li></ul><ul><li>Francis Ofungwu - Rackspace </li></ul><ul><li>PCI compliant payment handling </li></ul><ul><li>John Fitchett - Sagepay </li></ul><ul><li>Pod1’s perspective </li></ul><ul><li>Mark Hopwood - Pod1 </li></ul><ul><li>Panel discussion </li></ul><ul><li>Close & drinks </li></ul>
  2. 2. Welcome <ul><li>Mark Hopwood </li></ul><ul><li>Technology & Operations Director </li></ul><ul><li>Pod1 </li></ul>
  3. 3. PCI - Pod1’s perspective <ul><li>Why is PCI important? </li></ul><ul><li>How we view PCI </li></ul><ul><li>A brief history of eCommerce at Pod1 </li></ul><ul><li>Gutenberg - a Pod1 developed eCommerce solution </li></ul><ul><li>Magento - supported open source eCommerce </li></ul><ul><li>Our plans for PCI compliance </li></ul>
  4. 4. Why is PCI important? <ul><li>It’s mandatory </li></ul><ul><li>It’s good for business </li></ul><ul><li>It’s a trojan horse </li></ul>
  5. 5. How we view PCI
  6. 6. A brief history of eCommerce at Pod1 <ul><li>2001 to 2008 </li></ul><ul><li>2008 onwards </li></ul>
  7. 7. Gutenberg - a Pod1 developed eCommerce solution
  8. 8. Magento - supported open source eCommerce <ul><li>Developed by Varien </li></ul><ul><li>Thriving open source community </li></ul><ul><li>Forrester Research “One to Watch” </li></ul><ul><li>Enterprise Version launched May 2009 </li></ul><ul><li>Pod1 now has 6 live Magento clients with more on the way </li></ul><ul><li>Varien committed to PA-DSS compliance for Magento </li></ul>
  9. 9. Pod1’s plans for PCI compliance <ul><li>Aiming to be a PCI compliant organisation this Autumn: </li></ul><ul><li>Rackspace PCI compliant infrastructure </li></ul><ul><li>PCI compliant payment service providers, including Sagepay </li></ul><ul><li>Varien pursuing PA-DSS for Magento </li></ul><ul><li>Plans for all of our Gutenberg clients </li></ul><ul><li>... allowing all our clients to become PCI compliant without the need to audit Pod1 </li></ul>
  10. 10. Pod1’s plans for PCI compliance <ul><li>Internal change to support this: </li></ul><ul><li>Stronger processes </li></ul><ul><li>Regular internal code reviews </li></ul><ul><li>Better tools for testing and deployment </li></ul><ul><li>Separate staging from live </li></ul><ul><li>Applies to all clients </li></ul>
  11. 11. Suggested next steps <ul><li>Speak to your account management team </li></ul><ul><li>Conduct your own self-assessment </li></ul><ul><li>Start raising internal awareness, if you haven’t already </li></ul><ul><li>Get in touch with the experts </li></ul>
  12. 12. Thank you [email_address]

×