I was not sure what to expect as I started reading IT Security Metrics (ISM). I had just discarded another new book, published in July 2010, supposedly about security metrics but really about nothing useful to anyone anchored in the operational IT world. Would ISM be another disappointment? Since Andrew Jaquith published Security Metrics in 2007, no other book had appeared to help security professionals measure their worlds. Thankfully, I can strongly recommend Lance Hayden's ISM as a very strong contributor to the discussion on security metrics. ISM's subtitle, "A Practical Framework for Measuring Security & Protecting Data," really does explain the purpose and value of this great new book.
One aspect of ISM that made a distinct impression was its justification of qualitative measurement. It's fashionable in the security metrics community to focus almost exclusively on quantitative measurement. This usually means focusing on data that is already in numeric form. One of the primary lessons in ISM is that qualitative data has immense value. The challenge is rendering qualitative data in a form that can be counted. On p 141 Hayden says "the heart of qualitative analytical techniques is the concept of coding, or assigning themes and categories to the data and increasingly specific levels of analysis." Hayden explains how to perform this analysis, as well as how to incorporate other crucial data sources such as process maps and documentation. While I was familiar with this approach I had basically discounted it due to the prevailing mindset in the security metrics community. Now I will try to incorporate qualitative analysis my metrics program.
ISM also succeeds by helping the reader focus on simple yet effective approaches such as Goal - Question - Metric. Many of us jump straight to "metric" and then try to imagine what question the metric is supposed to answer and what goal is served. I also very much appreciated Hayden's focus on information security as a *business process* and not a way to achieve a "state." No one asks "how HR are we today?" like someone might ask "how secure are we today?"
I will conclude my endorsement of ISM by noting that I thought the honest discussion in some case studies was very powerful. For example, in chapter 3 Cisco admitted having 1000 bot victims and a four month period where their network monitoring platform missed traffic, due to SPAN port misconfiguration! You don't usually see that level of detail and "naming names" in security books, so I applaud the authors.
Overall, if you want to introduce a comprehensive security metrics program in your environment, ISM will very skillfully offer one way to accomplish that goal. It's immensely practical and grounded in reality, and it will help you.