Tip

Don't overwrite security log events

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.

    Requires Free Membership to View

This was first published in March 2005

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
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
Sort by: OldestNewest

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:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.