Quantcast StorefrontBacktalk » Blog Archive » ExxonMobil Discovers That A PCI Deadline Is A Deadline, Unless It Isn’t
advertisement
advertisement

ExxonMobil Discovers That A PCI Deadline Is A Deadline, Unless It Isn’t

Written by Evan Schuman
May 26th, 2010
Like this story? Share it
To share this story with people in your social network, please click on the network icons below.

PCI deadlines are to be taken seriously, unless you’re $285 billion ExxonMobil with it approximately 2,200 gas stations in the U.S. Then it’s more like a suggestion.

Visa has given ExxonMobil branded retailers an extension from July 1, 2010, until Dec. 31, 2010, to update their EPOS systems, according to a report in NACS (National Association of Convenience Stores) Online. Exxon Branded Wholesale Manager Chris Mahoney is quoted saying Visa and the oil company’s acquiring bank “recognize the challenges you face to be PCI-compliant by July 1, 2010, and have agreed to extend your compliance date.”

The story adds: “The new deadline means that POS devices that are designated ‘end-of-life’ by Exxon (Gilbarco G-Sites, Ruby without Sapphire and the Omni 3300) must be replaced or upgraded by December 31 with certified devices (Wayne Nucleus, Gilbarco Passport, Ruby Sapphire, Allied Pinnacle, AlliedRetalix or Vx570). All other POS devices that do not meet PCI requirements must be upgraded by August 1, 2012.”

It goes on to say ExxonMobil has to continually show progress: “Failure to demonstrate appropriate progress may result in fines or penalties from Visa which may be passed on.”

This change is a big part of the perception problem with PCI enforcement. Deadline exceptions need to be rare. But when they happen, they should be announced by the card brands—not via a leaked letter—along with the specific reasons for the extension.

Such an approach will make retailers more hesitant to seek an extension—who waits to air their dirty compliance delay laundry? But, more importantly, it will help other retailers take the deadlines seriously. Rumors of favored players getting inconsistent extensions are not going to be helpful to the cause.


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...