With a few minutes to kill before hosting the board meeting for my condo, I decided to leaf through last month's print edition of SC Mag that has been sitting on my counter since its conference last month here in NYC. While (Editor in Chief) Ilena Armstrong deserves credit for some definite layout and content improvements over the past few years, I'm sad to say that by page 13, I was confused over how to digest conflicting information.
A graph on the bottom corner of page 10 cites an RSA report that showed a sharp spike in phishing activity in August, while on page 12, a news brief mentions a recent X-Force security report that asserts phishing attacks in spam declined from 0.5 percent in 2008 to .01 percent in the first half of 2009. HOWEVER . . . in that same X-Force report (and SC Mag's summary of it), states that "between 2008 and the first half of this year, the number of new malicious web links rose by 508 percent."So — let me see if I got this right -- according to the report, there has been a decline in phishing attacks in spam but within that smaller sample, the amount of malicious links in phishing emails has gone up by...508%?
As someone who regularly churns out similar stats trumpeting the growth of young companies, I can tell you that when you see a stat about 508% growth in one year, that context is everything. If 500 percent of those links never see the light of day, then what is the relevance of the number? While doing some last minute research, I found yet another SC Mag phishing story based on a MarkMonitor report, which also revealed an uptick in phishing. While the reporter acknowledged the conflicting information, I still walked away confused, and unable to draw my own conclusion.
While it is easy for bloggers to bash the media (click here to read Mr. Preach Security Raf Los' thrashing of a Slate.com reporter), there is a wider problem of sifting through a greater volume of "legitimate” information, which without proper context can be misleading, inaccurate, or in SC Mag's case, contradictory.
On a related note, last week there has been quite a buzz about a so-called flaw in SSL that allows malware to be injected into HTTPS traffic during a time when some applications require the authentication process be "renegotiated." Now, crypto has never been my strong suit, but I did speak with a couple of folks about this who have been working with SSL a long time and are frustrated with the media coverage playing up the protocol’s “flaw.”
My understanding is, that the vulnerability - while valid - is NOT an issue with the protocol itself but in the authentication “renegotiation” process between SSL and the application that allows for the possibility of a man-in-the-middle attack.Apparently, some feel that it might be much easier (emphasis on the MUCH) to eliminate the vulnerability from the application side, rather than re-do SSL.
Researchers are stepping up to comment on the various ways the vulnerability could be exploited. Frank Heidt, CEO of Leviathan Security Group was quoted in a recent IDG News story was quoted as saying “Many high-profile banking and e-commerce Web sites will not return this 302 redirect message in a way that can be exploited, but a "huge number" of sites could be attacked “
So how bug a deal is it, really? Is there some sort of rating system we can attach to this to provide a clear level set of the likelihood and outcome other than FUD-ish references to the potential for great harm?
A special thanks to Lynn Terwoerds, former Microsoft security strategist and security architect at Barclays for her crypto-for-dummies schooling. Kudos to Kelly Jackson at DarkReading for providing a balanced view, at least compared to other stories I read about it.
Funny that for an industry that preaches risk management, there are few shades of gray in security. The take-away, as far as I'm concerned, is that reality is subjective and context is everything. And while that might seem like a no-brainer, that context piece is what often gets lost in translation, and the result is all kinds of backpedaling and level setting on the back end.
It reminds me of the whole “building-security-in-rather-than-bolting-it-on” conundrum, except applied to communication. Maybe this is a big deal, maybe it isn’t – two weeks after the disclosure its still not clear. If many banking or e-commerce sites are immune, than who isn't and what are the possible outcomes?
If it’s too soon to say, then that should be clear. But the buck needs to stop somewhere, or we can go on spinning indefinitely.
So.. Is phishing up, or down? If the answer is both, then why?
Inquiring minds want to know....

Recent Comments