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 last published in March 2005

Dig Deeper on Windows Server and Network Security

PRO+

Content

Find more PRO+ content and other member only offers, here.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

-ADS BY GOOGLE

SearchServerVirtualization

SearchCloudComputing

SearchExchange

SearchSQLServer

SearchWinIT

SearchEnterpriseDesktop

SearchVirtualDesktop

Close