Firewall.cx Newsletter

Receive Free notification on new articles!
***************

Firewall.cx Forums

Community Forums

Facebook Fans

Show your support for Firewall.cx!

Social Media Channels

Facebook-icon LinkedIn-icon Twitter-icon  rssfeed-icon
advert-banner-routing
advert-banner-voice

System Login



Login With Facebook

More Articles

Who's Online

We have 164 guests online

Statistics

Members : 5832
Content : 789
Web Links : 12
Content View Hits : 102199257

Top Website Visitors

37.4%United States United States
16.9%India India
7.3%United Kingdom United Kingdom
5.7%Australia Australia
4.3%Canada Canada
3.4%Germany Germany

Today: 3200
Yesterday: 8225
This Week: 18693
Last Week: 46096
This Month: 96102
Last Month: 232158
Total: 3356826

Gold Cisco Lab Partners

logo-gfi



logo-datavision

Securing Windows 2000 with Event Log Monitoring Print Email
(0 votes, average 0 out of 5)
Written by Administrator   
Saturday, 16 July 2011 14:58
AddThis Social Bookmark Button

Introduction


The problem with the information provided is that it’s difficult to easily get a sense for which events are absolutely critical, and which represent a user forgetting their password. To get a perspective on how difficult security log management can be, multiply the events that you find on one system by the number of systems on your network.

As you can see, the mountain of data quickly becomes unmanageable, and certainly makes responding to critical incidents difficult. This is a large part of the reason why some companies disable the auditing feature of Windows 2000 almost as quickly as they turn it on.

While Windows 2000 Security logs provide reams of valuable information, it’s up to you as the administrator to collect, analyze and assess the information they provide. Not only is this next to impossible in a large environment, it could easily be a full-time job all by itself.

To read more of this article, please Click Here.

 
Subscribe To Receive Free Article Updates!

SIMILAR TOPICS THAT MIGHT INTEREST