Quantcast StorefrontBacktalk » Blog Archive » Missed A Vulnerability Scan? The PCI Council Just Threw You A Lifeline
advertisement
advertisement

Missed A Vulnerability Scan? The PCI Council Just Threw You A Lifeline

Written by Walter Conway
February 24th, 2010
Like this story? Share it
To share this story with people in your social network, please click on the network icons below.

A 403 Labs QSA, PCI Columnist Walt Conway has worked in payments and technology for more than 30 years, 10 of them with Visa.

The PCI Council may have thrown a compliance lifeline to retailers that are missing a required quarterly external vulnerability scan. This means you might—just might—be deemed PCI compliant even if through accident, poor planning or sheer blockheadedness you manage to screw things up and miss a vulnerability scan. Passing isn’t easy, and a successful result is not guaranteed. But if you do everything else right, your QSA may be able to assess you as compliant in spite of yourself. Then again, did the Council both offer an option and take it away?

During an onsite assessment, QSAs confirm that merchants have met PCI Requirement 11.2 by examining the passing vulnerability scans for each of the last four quarters. The problem is, what if the merchant has missed a scan? If this happens, is the merchant noncompliant until it can get four quarters of passing scans? Ouch.

Noncompliance could lead to trouble with your acquirer, fines or worse while you wait for the calendar to come around. Unlike a previous suggestion that your only recourse was to get hold of Dr. Who and travel back in time to order the missing scans, the PCI Council may let you still be deemed compliant.

QSAs are taught at our training that merchants need to pass four quarterly external scans to be compliant. The Council’s FAQ on the topic (#8709) states: “To be considered PCI DSS Compliant, an entity is required to pass each quarterly ASV [Approved Scanning Vendor] Scan.” That sounds pretty cut-and-dried. But QSAs also are taught that for any PCI Requirement (except 3.2–storing sensitive authentication data) there can be a compensating control. So now the question becomes, what would a compensating control for missing vulnerability scans look like?

A starting point is the November 2009 PCI Council guidance with which your QSA will be familiar. It provides some idea of how a merchant can be compliant while missing a quarterly scan. Specifically, if your QSA believes you met the intent of Requirement 11.2 and your risk has been sufficiently addressed through your practices, the QSA can assess you as compliant even though you did not meet 11.2 exactly as stated (i.e., the four quarterly passing scans).


advertisement

Leave a Reply

Newsletter

Quickly catch-up on the latest in E-Commerce and Retail Tech with our free weekly newsletter, with urgent bulletins as news merits.
advertisement

Most Recent Comments

Kill All The Passwords

This article does mention, but does not give enough attention to, the fact that the attacks discussed are only feasible when the encrypted password file can be copied and subjected to an offline attack. The trick is to have authentication performed on a separate, much more strongly secured host - such as an Active Directory Domain Controller, or a Kerberos server, or a NIS+ server, or even using something as banal as an LDAP-over-SSL authentication dialog. In these environments, the odds of the "password file" being stolen and subjected to an offline attack go to near zero, and only online attacks may be carried out by the attacker. With sensible exponential backoff between failed password attempts, lockout after a modest number of failed attempts on a single account, and pattern detection, that minimum 7 character password is quite secure enough. Passwords aren't dead yet for security purposes, and they will be with us for a very long while to come for practical purposes. The trick is to employ them correctly. Read more...
The possibilities you describe are years away from being implemented at best, so for the moment passwords are an ugly reality. Luckily, password managers can easily manage hundreds of passwords of any length. The only thing a user needs to remember is the master password. It seems like an easier task to educate users on how to use password managers rather than implement complex security technology on a global basis. Read more...