Don't overwrite security log events

Never overwrite events in the security log because the log is full for a reason.

Never overwrite events in the security log because the log is full for a reason. Digital evidence is extremely

important and the security logs give a chronological sequence of events. The log could be full for a few reasons: 1) A sysadmin isn't performing their job correctly; 2) A possible malicious activity on your system; 3) A misconfigured system that generates events.

In the event you get an error that identifies that you cannot log on to either Windows 2000 or Windows XP, then contact the security manager because it means the sysadmin is not performing their job correctly.

This was first published in March 2005

Dig deeper on Windows Server and Network Security

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

SearchServerVirtualization

SearchCloudComputing

SearchExchange

SearchSQLServer

SearchWinIT

SearchEnterpriseDesktop

SearchVirtualDesktop

Close