One of the most important elements of any good information security program is the ability to generate good, consumable reporting. The dilemma that most organizations face around this subject are as follows:
1) What type of reports do I need, and what should they include, and with what level of detail?
2) How can I use this reporting to make informed decisions?
Let me touch on each of these areas:
What type of reporting do I need, and what level of detail should it include? Well…if you look at information security on broad scale, there are some very specific reports that I would categorize are the most important. They are as follows:
Patch Status Report – This report should include an assessment of your entire environment – inclusive of both virtual and non-virtual machines, and provide a sense for your patch posture – covering all Microsoft OS’s, Microsoft Applications, Non-Microsoft Applications, and any Unix or Linux systems. The level of frequency should be no less than once a month.
Firewall Logs – This report should clearly illustrate the level of both inbound and outbound traffic, any alerts that were triggered, and any URL attacks that may have been discovered. This type of report should be reviewed on a daily basis, with separate alerts sent if any form of malicious behavior is detected.
Anti-Virus Status – This is another report that should be created on a daily basis. It should provide you with a listing of the top threats that were discovered and removed, it should also illustrate if any user’s .dat file is not up-to-date. Additionally, if for any reason there’s any unusual activity or traffic volume detected, you should set the application to provide you with the appropriate alerts.
Intrusion Detection – In this particular category, reporting is critical. The type of reports you should create should illustrate; 1) how often did hackers attempt to attack You. 2) What parts of your network were they targeting. 3) What kind of attack was it? And, 4) Was the network breached? These types of reports should be reviewed at a minimum on a daily basis. You should also create (if available) a set of automated alerts, if any type of anomalous behavior is detected.
Configuration Status – One of the most overlooked areas of information security centers around system hardening and security configuration settings. The type of report that you should create should include an assessment of “current state” against your current baseline. It should also include detail regarding any settings that have drifted from what established policy is. This type of reporting should be done at a minimum monthly.
Moving on…so how should you use this information to make informed decisions. By simply having a consistent stream of information (consistent with what I mentioned above), you will have the necessary data to make rational decisions on any issues or challenges that may arise. I would also encourage you to consider the use of some form of IT policy framework (i.e.; ISO, ITIL, NIST, etc.) as a basis for your security policy and baseline development…because it will enhance the recommended reports that I described…but provide added measurability.
In summary…be proactive with your reporting, and don’t settle for less than what you need! You can protect yourself from what you’re not aware of…!
Dave Eike
Shavlik Technologies