Professional Windows Server 1002003 Security A Technical Reference [Electronic resources] نسخه متنی

اینجــــا یک کتابخانه دیجیتالی است

با بیش از 100000 منبع الکترونیکی رایگان به زبان فارسی ، عربی و انگلیسی

Professional Windows Server 1002003 Security A Technical Reference [Electronic resources] - نسخه متنی

Roberta Bragg

| نمايش فراداده ، افزودن یک نقد و بررسی
افزودن به کتابخانه شخصی
ارسال به دوستان
جستجو در متن کتاب
بیشتر
تنظیمات قلم

فونت

اندازه قلم

+ - پیش فرض

حالت نمایش

روز نیمروز شب
جستجو در لغت نامه
بیشتر
لیست موضوعات
توضیحات
افزودن یادداشت جدید







Monitor Event Logs


Several of the tools described in this chapter poll events logs and report errors. A more comprehensive plan for event log monitoring is required to spot security incidents and determine what happened during them. MOM is a product that uses event log data, and many third-party products can be used to centrally collect and even manage events. A new tool is planned as part of an update to Windows Server 2003 that will automatically centralize and analyze event log information.

Meanwhile, two helpful tools, EventcombMT and lockoutstatus, can span servers to collect and help analyze events.

Use EventCombMT


EventCombMT can be downloaded from Microsoft.

To run the tool, follow these steps:


1.

Type EventCombmt at a command prompt.

2.

Review the sample instructions, as shown in Figure 19-31, and click OK.

Figure 19-31. Most information needed to operate EventCombMT is in the sample instructions.

[View full size image]

3.

Right-click the Select To Search/Right Click to Add box and select Get DCs in domain or other listing such as GCs in the domain, all servers, all servers in a list, or select individual servers.

4.

Use the Searches menu to select a built-in search such as FRS health, account lockouts, Active Directory DNS registration failure, and so forth.

OR

Customize the log files, event types, event IDs, and timeframe to search for, as shown in Figure 19-32. If several event IDs are entered, separate them with spaces.

Figure 19-32. Customize the search using check boxes and text boxes.

[View full size image]

5.

Click the Search button. To view the results, open the text files recorded for each server monitored. The log files are saved to the temp directory, which is opened at the conclusion of the search. The motorin log is shown in Figure 19-33. (The search can take some time if many servers and large logs are a factor. In this example, event 643 was the only event identified; the search was to record any instances of an account policy being changed. The results found events.)

Figure 19-33. Review the results.

[View full size image]


Use Lockoutstatus


Another tool, the Resource Kit tool lockoutstatus.exe, can help you troubleshoot account lockout issues. One of the benefits of setting the account lockout policy is that password-cracking attacks will lock out the account. In order to diagnose whether a lockout is due to an attack or user malfunction, and to determine which computer was used in the attack, you must review data from every domain controller in the domain. In a large domain, this can be time-consuming. The Lockoutstatus.exe tool can be used to display lockout information from all DCs in the domain. To display lockout information on the fredp account in the chicago.local domain, use this command at the command line:


Lockoutstatus /u:chicago.local\fredp

Alternatively the fredp@chicago.local account format is acceptable input for the /u: parameter. A GUI displays the results, as shown in Figure 19-34. Right-clicking a DC allows you to view its event log from which you can view logon events and determine the client the user used. The tool can also be used to list account status such as max password age and current age.

Figure 19-34. Use lockoutstatus.exe to help determine why the even occurred.

[View full size image]


/ 194