You are here:About>Business & Finance>Business Security> Security Testing> Network Security Testing> Security Logging
About.comBusiness Security
Newsletters & RSSEmail to a friendSubmit to Digg

The QAD (Quick and Dirty) Checklist for the Security Audit of a Windows Server

From Ryan Groom,
Your Guide to Business Security.
FREE Newsletter. Sign Up Now!

Security Logging

Logging is the only way you can determine what is happening on your network. When something goes wrong, like an unauthorized network access or an unacceptable use from an employee, the logs is what shows the trail of these events.

The following list is a set of items that should be reviewed when creating an security audit of your logging effectiveness.

  • Is auditing enabled for security events such as logon events, object access, policy change, process tracking and system events?
  • Are log sizes set to meet or exceed organizational standards and ensure that the size of the log files will enable administrators to review sufficient log history in a security incident?
  • Are the log files retained or archived in a manner that will allow for retrieval and review following a security event?
  • Are log files protected in a manner that aides in protecting the integrity of the log files such as remote logging or frequent archival?
  • Are the log files reviewed on a frequent basis to detect security incidents?
  1. Server Accounts
  2. Server Operating System
  3. Security Logging
  4. Software Currency
  5. Disaster Recovery
  6. Authentication
  7. Anti-Virus

<< Previous | Next >>

 All Topics | Email Article | | |
Advertising Info | News & Events | Work at About | SiteMap | Reprints | HelpOur Story | Be a Guide
User Agreement | Ethics Policy | Patent Info. | Privacy Policy©2008 About, Inc., A part of The New York Times Company. All rights reserved.