The Guerilla CISO blog has some amusing points posted about the dismal (nine Fs) 2007 FISMA report:

I can’t believe it, but DHS scored a “B” against all odds. =) And of course, by now the response to the report card is all rote–everybody wonders what the letters really mean […] I guess it just goes to prove what we say about the classified world: the people who know don’t talk and the people who talk don’t know. In this case, everybody attacks the metric because, well, it’s a bad metric–what action are we supposed to take because of what the results are? It’s also pretty much ignored by this point anyway except for the witty sound bites from some of my “favorite people”, so it’s nothing to get all hot and bothered about.

I always felt the same way about my report cards. Go ahead, ask him what he thinks about SANS and Gartner opinions on the report.

Go Jen King! Awesome paper by a former colleague:

Professor Alan Westin has pioneered a popular “segmentation” to describe Americans as fitting into one of three subgroups concerning privacy: privacy “fundamentalists” (high concern for privacy), “pragmatists” (mid-level concern), and the “unconcerned” (low or no privacy concern). When compared with these segments, Californians are more likely to be privacy pragmatists or fundamentalists, and less likely to be unconcerned about privacy. Fundamentalists were much more likely to be correct in their views of privacy rules. In light of this finding, we question Westin’s conclusion that privacy pragmatists are well served by self-regulatory and opt-out approaches, as we found this subgroup of consumers is likely to misunderstand default rules in the marketplace.

At some point security becomes so expensive and time-consuming that only an elite can afford privacy. Is there a case to be made that regulation of the data market is needed to bring the cost down?

A question I often wonder about is what real costs do we bear today if we want to control our data and who benefits most from generating entropy (or lack of individual awareness/control)?

CompTIA Research has published “Trends in Information Security”:

Information security is seen as a key risk among firms, with 80% of US respondents indicating that it is considered top priority by management. Nearly two-thirds of US firms, more than half of UK and Chinese firms, and two-fifths of Canadian firms have implemented written IT security policies.

Impressive, sort of. Is that a top ten or top five priority? What kind of survey asks about top priorities without qualifying how long the list actually runs? Another way of asking might be “what size font does your powerpoint presentation use for priority lists?” Ok, joking aside, here is some hard data:

The percentage of their IT budget that companies dedicate to security is growing year after year. In the US, companies earmarked 12% of their IT budget in 2007 for security purposes – up from only 7% in 2005. The bulk of these dollars are used to procure security-related technologies.

Companies spend substantial amounts on prevention because security breaches can be costly if they occur. In the past year, US firms shelled out an average of over $200,000 as a result of security breaches, a third of which was attributed to the loss of employee productivity. Moreover, in the last year in the US, Canada and UK, IT staff members spent over 10% of their time dealing with security breaches, and in China, almost 20% of their time.

I suspect that earthquake is going to seriously drive up the numbers for China this year.

12%!! Holy smokes. I remember when executives were practically choking to death on 10% budget requests. How will anyone survive spending 12% on security…unless it becomes integrated into the business logic and bottom line calculations of the company? Consider this number:

Security training has saved US organizations upwards of $2.2 million in total, much of which is due to a reduction of server/network downtime and fewer impacts to employee productivity.

That’s correct, uptime is security. Let’s hear it for the availability metrics.

Speaking of which, the survey goes on to reveal that 31 percent of breaches are from combined human error and/or technical malfunction, 29 percent are due to human error alone and 14 percent from technical malfunction alone. Another 10 percent are described as intentional internal breaches, with the remaining16 percent from the outside.

In other words, 26 percent of “breaches” are intentional and the rest are malfunctions by humans or the technology they manage. I guess I am supposed to say it comes from technical malfunction, but I am not exactly sure yet how that differs from human error. The survey clarifies that 45 percent of human error is caused by a failure to follow security procedures while 25 percent is from and a lack of security knowledge.

This report should help security managers make the case for monitoring uptime as part of their remit and let them report downtime, even for potential incidents, as a breach.