19.06.2014 Views

Windows Server 2003 Recommended Baseline Security

Windows Server 2003 Recommended Baseline Security

Windows Server 2003 Recommended Baseline Security

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Unclassified ITSG for <strong>Windows</strong> <strong>Server</strong> <strong>2003</strong><br />

4.5.1.3 Maximum system log size<br />

MaximumLogSize = 76800 (in [System Log] section<br />

The ‘MaximumLogSize’ determines the size of the System event log. The setting ‘76800’ creates<br />

a 76800 KB log file. With an average of 500 bytes per event, this log file will accommodate over<br />

153,000 events. This allows the system to run for an extended period-of-time without having to<br />

roll the log file.<br />

NOTE:<br />

Due to the wide variety of event loads, we recommend monitoring the log files during<br />

the initial operational period.<br />

4.5.2 Guest Access<br />

4.5.2.1 Prevent local Guests group from accessing Applications, <strong>Security</strong>, and System<br />

logs<br />

RestrictGuestAccess = 1(in [Application Log] or [<strong>Security</strong> Log] or [System Log] section)<br />

The ‘RestrictGuestAccess’ keyword determines if accounts with ‘guest’ access can access the<br />

log. The setting ‘1’ disallows guest access to the log. Access to log information provides an<br />

attacker with valuable information to mount attacks on the system or users. As a result, only<br />

users who are authenticated are given access to the log files.<br />

4.5.3 Retention Method<br />

4.5.3.1 Retention method for application log<br />

AuditLogRetentionPeriod = 2(in [Application Log] or [<strong>Security</strong> Log] or [System Log] section)<br />

The ‘AuditLogRetentionPeriod’ keyword determines the system behaviour when the log is full.<br />

The setting ‘2’ shuts the system down if the log cannot be written. Use of this setting should be<br />

consistent with departmental log retention policy.<br />

4.6 System Services<br />

A large number of services are disabled in this guide. With each disabled service, we provide<br />

justification for the recommendation. In some cases, a more flexible approach may be needed.<br />

It is important to note that a disabled service may only be required occasionally. For example,<br />

the Performance Logs and Alerts service is disabled. However, to help fulfill a specific<br />

temporary need, the Administrator could enable a service, resolve an issue, and return the service<br />

to the original configuration.<br />

70 March 2004 <strong>Server</strong> Policy Files

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!