Win2k3 Audit

Overview

Version	Date	Finding Count (4)			Downloads
6	2013-06-10	CAT I (High): 0	CAT II (Med): 3	CAT III (Low): 1	Excel	JSON	XML

STIG Description
The Windows 2003 Security Technical Implementation Guide (STIG) is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements were developed from Federal and DoD consensus, as well as the Windows 2003 Security Guide and security templates published by Microsoft Corporation. Comments or proposed revisions to this document should be sent via e-mail to the following address: disa.letterkenny.FSO.mbx.stig-customer-support-mailbox@mail.mil.

STIG Description

The Windows 2003 Security Technical Implementation Guide (STIG) is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements were developed from Federal and DoD consensus, as well as the Windows 2003 Security Guide and security templates published by Microsoft Corporation. Comments or proposed revisions to this document should be sent via e-mail to the following address: disa.letterkenny.FSO.mbx.stig-customer-support-mailbox@mail.mil.

Available Profiles

Classified	Public	Sensitive
Audit and Audit Log Checks	I - Mission Critial Classified	I - Mission Critial Public	I - Mission Critial Sensitive	II - Mission Support Classified	II - Mission Support Public	II - Mission Support Sensitive	III - Administrative Classified	III - Administrative Public	III - Administrative Sensitive

Findings (MAC Audit and Audit Log Checks)

Finding ID	Severity	Title	Description
V-1080	Medium	File-auditing configuration does not meet minimum requirements.	Improper modification of the core system files can render a system inoperable. Further, modifications to these system files can have a significant impact on the security configuration of the...
V-6850	Medium	Auditing must be configured as required.	Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. ...
V-1118	Medium	Event log sizes do not meet minimum requirements.	Inadequate log size will cause the log to fill up quickly and require frequent clearing by administrative personnel.
V-1091	Low	System does not halt once an event log has reached its maximum size.	If the security log is full, it becomes possible for some events to not be logged. Selecting this option will halt the computer when the log is full to prevent losing any events. If the system...