Header

Sun, 5 Apr 2009

Should InfoSec companies be betting on PCI ?
@

The United States committee on Homeland Security's Subcommittee on Emerging Threats, Cybersecurity, and Science and Technology recently held a hearing to determine if "the Payment Card Industry Data Standards Reduce Cybercrime?"

Risky Business played snippets of the hearing under the apt title: "Washington spanks PCI DSS" - Like most episodes of RB, its well worth the listen..

One of the "merchants" giving testimony made his point quite succinctly. The credit card companies require us to keep card details, and shift the burden of fraudulent transactions to the merchant. There are much better ways to handle transactions, but the current method is a cheap way for the CC vendors to shift the burden and the risk to the merchants who historically had no alternative.

Online theft of credit card details reached ridiculous proportions, and so the payment card industry had to react, but they reacted by shifting the burden (and the risk) to the merchants. Now im all for people securing their apps and networks, but when you listen to merchants complaining it becomes pretty clear that the credit card industry is threatening punishment for behavior with one hand that it is actually incentivising with its other.

Now merchants (who are no saints) were willing to grudgingly go along with this cost, but when cases like heartland pop up (guys who PCI certified ok while they were busy bleeding card info to evil hax0rs) - the merchants start baying for blood.

The InfoSec Companies: Many infosec companies saw PCI as a chance to sell more services. They rallied to the PCI flag because anything that sells more services is a good thing. This would kinda be ok (mildly excusable) if they were using PCI to sell existing services (that were created to make customers secure) but the problem got worse when PCI compliance became the goal in and of itself. Now you have a bunch of people eager to sell something to a semi captive market. The situation is built for check boxes that obey the law but miss its essence..

But this isnt new? Its not.. But listening to the merchants testifying you get the sense that they have had enough. The payment card industry has tried to fix the problem the (relatively) cheap way, by shifting the pain to the merchants but its quite clear that this approach is not going to work... it becomes clear that to fix the stolen CC problem, we are going to have to (finally) change the transaction model..

The infosec market isnt going away, but i suspect that the credit-card model we currently use, will. Now this should not scare the infosec companies who have been pointing out that compliance does not equal security, or those companies that have built a reputation working on companies and applications that care about security. For those who have built a business model on checking boxes and handing out compliance stamps, my prediction is that the writing is on the wall..

Its like building a company on the Y2k hype.. Sure you might make a whack load of money for a while, and sure there actually are problems that need solving, but sooner or later the dates going to tick over from 1999 and if all you had was the hype, then im hoping for your sake that you took the lease (not buy) option on your company assets..

/mh

*caveat-1 - SensePost holds both PCI QSA and PCI ASV certifications (because we need to make sure we understand the space). *caveat-2 - Predictions in general should be left to prophets, this posting should be taken less as prognostication, and more as prose to warn against building a business model on shaky foundations..

Blog
Video
Research
QotW
Categories
.ac.za (1)
about:us (38)
analysis (1)
auctions (1)
auditors (1)
b-sides (2)
blackhat (17)
blog (10)
broadview (4)
build-it (1)
ccdcoe (1)
cloud (12)
community (16)
conferences (70)
consulting (1)
crypto (4)
estonia (1)
fail (3)
foos (1)
fun (51)
goodbye (1)
hackrack (2)
Hope? (2)
howto (9)
imsojaded (2)
infosec-soapies (25)
infrastructure (3)
interns (1)
ios (1)
jobs (1)
local (6)
mac (15)
management (12)
materials (3)
memcached (2)
metricon (2)
metrics (3)
mindless-politics (4)
mindmaps (1)
mobile (2)
modelling (3)
PCI (2)
penny (1)
phone (1)
pickle (4)
policy (1)
post-it (1)
presentations (1)
Press (1)
privacy (6)
product (2)
programming (5)
public (319)
python (5)
qo[w|m|?] (5)
rambling (1)
README (1)
real-world (16)
Release (1)
report-info (1)
research (49)
reversing (7)
risk (2)
SAP (1)
security-fyi (8)
security-news (6)
silly-yammerings (19)
suru (1)
tech-toys (3)
threat (3)
time-waster (6)
tin-foil-hat (6)
tools (49)
training (30)
travel (2)
tricks (1)
UK (2)
Uncategorized (3)
uncon (2)
vendors (7)
videos (6)
vulnerability (10)
wasc (1)
webapps (6)
web_x.0 (2)
windows (1)
writing-advice (1)
zaprize (2)
zen-hacking (6)
Archives
December 2011 (3)
November 2011 (2)
October 2011 (6)
September 2011 (3)
August 2011 (3)
July 2011 (3)
June 2011 (2)
May 2011 (6)
March 2011 (3)
Feburary 2011 (3)
January 2011 (1)
December 2010 (2)
November 2010 (4)
October 2010 (3)
August 2010 (4)
July 2010 (1)
June 2010 (4)
May 2010 (3)
April 2010 (3)
March 2010 (7)
Feburary 2010 (2)
January 2010 (3)
December 2009 (4)
November 2009 (4)
October 2009 (3)
September 2009 (5)
August 2009 (9)
July 2009 (1)
June 2009 (5)
May 2009 (4)
April 2009 (10)
March 2009 (13)
Feburary 2009 (12)
January 2009 (11)
December 2008 (9)
November 2008 (8)
October 2008 (5)
September 2008 (5)
August 2008 (6)
July 2008 (6)
June 2008 (6)
May 2008 (2)
April 2008 (3)
March 2008 (7)
Feburary 2008 (12)
January 2008 (9)
December 2007 (8)
November 2007 (4)
October 2007 (9)
September 2007 (14)
August 2007 (18)
July 2007 (13)
June 2007 (17)
May 2007 (2)
July 2006 (1)
April 2006 (1)
August 2005 (1)
June 2005 (1)
May 2005 (2)
Blogroll
JYeti
Dominic
Junaid
Archives
Conditions of use Privacy statement
Top of Page Legal stuff