News for hackers. Stuff that matters.
Re: by seregine on Monday May 03, 2010 @01:19PM (#1315321)
This is somewhat misleading - a successful vulnerability scan isn't enough to say whether Spreedly is PCI DSS compliant.

Vulnerability scanning is just one component of PCI compliance - others include an audit of your architecture, security training, risk assessment, and much more.

That said, we passed the Level 1 PCI audit, which is the highest level. The lower levels may have somewhat relaxed requirements.

edit: I should also mention that we compete with Spreedly

Re: by 403labs on Monday May 03, 2010 @02:26PM (#1315581)
Thanks for clarifying, seregine. You're correct that a successful vulnerability scan is not conclusive evidence of compliance with the PCI DSS. It's one of the many components of meeting compliance with the PCI DSS. Many requirements are taken into consideration as part of any individual organization's compliance with the PCI DSS.

The Payment Card Industry Data Security Standard (PCI DSS) is an industry standard for anyone who stores, processes or transmits cardholder data (think: credit card numbers). The standard itself covers 12 key requirements for protecting cardholder data with many sub-requirements under each section.

All organizations that store, process, or transmit cardholder data are required to be compliant with the PCI DSS. Based on certain elements, primarily including transaction volume, will determine an organizations "level". Every level is required to comply with the same requirements, but each level may have a different requirement to validate their compliance. Typically, larger organizations are required to have an onsite audit conducted and smaller organizations are able to self-assess.

Re: by jmcarlin on Monday May 03, 2010 @01:32PM (#1315374)
Spreedly has fulfilled all the requirements of SAQ D. The compliance status is not just the result of vulnerability scanning. https://spreedly.com/info/faq/

Disclosure: I'm a Spreedly co-founder.

Re: by kirvero on Monday May 03, 2010 @01:20PM (#1315325)
false inference. pci dss is largely about internal process, not visible to the outside.

passing a security scan doesn't mean you're pci dss compliant. of the 12 requirements of pci dss, only 1 is even partially met by successfully passing an external scan.

Re: by knowtheory on Monday May 03, 2010 @01:09PM (#1315274)
And if anybody is interested in what PCI DSS actually means check this out!

https://www.pcisecuritystandards.org/security_standards/pci_...

Re: by mey on Monday May 03, 2010 @01:20PM (#1315326)
Yeah but what is spreedly?
Re: by knowtheory on Monday May 03, 2010 @01:27PM (#1315356)
http://spreedly.com/

They're an integrateable payment API. Basically they handle all the security junk, connect to your payment gateway of choice, and you don't have to be concerned about storing credit card details for your customers.

Re: by chaosmachine on Monday May 03, 2010 @01:28PM (#1315360)
Something funny:

https://seal.403labs.com/seal/verify/www.yahoo.com

They seem to think yahoo.com is "Precision Underground Locators LLC".

Re: by doc-film on Monday May 03, 2010 @02:02PM (#1315491)
Yes but PCI compliance still leaves people open, see this which is not covered by any of the regulations : http://www.merchant-advise.co.uk/The_Biggest_Flaw_In_The_PCI...