|
Guest Columnist Ed Adams argues that PCI has a long way to go and that the PCI Security Council isn’t helping very much. “The PCI Security Standards Council is made up of seemingly smart folks from the credit card brands and security industry. Unfortunately, this group of misfits is saddled with a myriad of competitive conflicts of interest and, worst of all, a complete misunderstanding of how to best protect card data and consumer identity,” writes Adams. Read more. |
March 21st, 2008 at 8:10 am
We, at RSR have had an epiphany this week. Why in heaven’s name is it the banking commumity’s responsibility to set security standards and validate that they’ve been adhered to?
Responsible parties for operating system security are the OS vendors, not some odd 3rd party. Banks are good at banking (at least we hope so). They’re not meant to be security-standard-bearers. Shouldn’t it be the same way with networks?
March 21st, 2008 at 8:40 am
While I agree that there needs to be much more done an=bout application security, bemoaning the attention paid to data storage and transportion as missing the biggest threat to customer data is misguided.
Retailers need to take care of the basic fundamentals before they can move on to the more advanced areas of application development. Where have the largest data breaches to date occurred?
While the jury is out on the Hannaford breach, TJX and countless other massive breaches have not occurred through applications at all. They have occurred through exploitation of security holes in the network and insecure data storage.
That isn’t to say that application development doesn’t need to be looked at - but you have to take care of the basics first.
March 21st, 2008 at 1:33 pm
Not so re. the exploitation of security holes in the network — with TJX this was only how the thieves got in the front door… it was then a SQL injection and db (app) misconfiguration and app-layer vulnerability that allowed them to siphon off millions of credit card numbers over the course of months and months. I agree that the basics need to be taken care of first, but I don’t think that’s the netowrk… if you have a properly written web application, you don’t need a firewall or IDS system at all.