Quantcast StorefrontBacktalk » Blog Archive » Can Remote Access And PCI Co-Exist?
advertisement
advertisement

Can Remote Access And PCI Co-Exist?

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

Budget cutbacks and office closings have been pressuring retailers to pursue remote access approaches for tech support. And yet, PCI security concerns have made any kind of external access frightening in the extreme. Will fear or cheapness win?

One of the more pervasive challenges today is that remote site access has been around for decades, but the security needs have sharply changed. No longer, for example, does a firewall have to be pierced to permit remote site access.

“Remote support tools do not jeopardize a firm’s PCI compliance efforts. Bad implementation does,” said George Hamilton, senior product manager for LogMeIn, a remote access and support software company based in Boston.

Hamilton cites a typical problem with many of today’s remote access setups, referencing a conversation he had with a retailer at a recent tradeshow and an employee who left the chain. “When one of their technicians left the company, it took them six hours to go onto all of the individual systems and remove their login credentials,” he said. “During that entire six-hour period, that person who no longer worked for the company, he had access to critical POS systems. That is something you want to control centrally.”

StorefrontBacktalk held a podcast this week on PCI and remote access, with Hamilton as guest. To listen to the podcast, please click here.


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