« Security fatigue and predictions for 2009 | Main | How not to prevent data theft »

Keeping the reports effective

KingS

Security metrics and dashboards are on my mind at the moment. It's time to review the effectiveness of my regular reports to the board and work on keeping them effective and, most importantly, relevant.

It's a mistake to think that once you've hit on a decent format you can then sit back and churn out the same report for months and years on end. Reality is that your program has changed, business risks have changed, and your experience has grown. Reports can quickly start to look tired and their effectiveness diminishes over time.

I've been reviewing a number of different resources for some new inspiration. Mike Rothman's essential guide for anyone in security management, The Pragmatic CSO, has some good guidance on the subject and states that we should be including things that are 1) Important to Senior Management and 2) Important to running your business. I also came across a good white paper written by fellow CW blogger David Lacey entitled Top 10 Tangible Measures for Effective Security Management (download it from here). This paper details ten events, issues and indicators that can be physically and technically measured.

Having a decent set of reportable metrics is essential for measuring success. However, like everything else, report formats are subject to atrophy and need to be refreshed from time to time.

Bookmark and Share


TrackBack

TrackBack URL for this entry:
http://www.computerweekly.com/cgi-bin/mt/mt-tb.cgi/32886

Comments (1)

Stef Treloar:

I agree that relevant and efficient reporting is important, however we must be wary not to overreport..... which can easily happen. This can have a counter effect, and takes security staff from "on the job" tasks, which are equally important.

Sometimes, time can easily be eaten up in an attempt to create the utopian report, which of course never exists.

I think vendors have now realised this fact, and there has been a huge improvement in the quality of automated dashboard software being released. If used wisely, this could free up valuable time the poor security engineer would usually use, manually creating one.

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

About

This page contains a single entry from the blog posted on August 13, 2008 9:00 PM.

The previous post in this blog was Security fatigue and predictions for 2009.

The next post in this blog is How not to prevent data theft.

Many more can be found on the main index page or by looking through the archives.