IISW-SI-000209 - The IIS 8.5 website must produce log records that contain sufficient information to establish the outcome (success or failure) of IIS 8.5 website events - success or failure of IIS 8.5 website events


Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined.

Ascertaining the success or failure of an event is important during forensic analysis. Correctly determining the outcome will add information to the overall reconstruction of the logable event. By determining the success or failure of the event correctly, analysis of the enterprise can be undertaken to determine if events tied to the event occurred in other areas within the enterprise.

Without sufficient information establishing the success or failure of the logged event, investigation into the cause of event is severely hindered. The success or failure also provides a means to measure the impact of an event and help authorized personnel to determine the appropriate response. Log record content that may be necessary to satisfy the requirement of this control includes, but is not limited to, time stamps, source and destination IP addresses, user/process identifiers, event descriptions, application-specific events, success/fail indications, file names involved, access control, or flow control rules invoked.


Follow the procedures below for each site hosted on the IIS 8.5 web server:

Select the website being reviewed.

Under 'IIS', double-click the 'Logging' icon.

Configure the 'Format:' under 'Log File' to 'W3C'.

Select the 'Fields' button.

Under 'Custom Fields', select the following fields:

Request Header >> Connection

Request Header >> Warning

Click 'OK'.

Select 'Apply' from the 'Actions' pane.

See Also


Item Details


References: 800-53|AU-3, CAT|II, CCI|CCI-000134, Rule-ID|SV-214451r879567_rule, STIG-ID|IISW-SI-000209, STIG-Legacy|SV-91485, STIG-Legacy|V-76789, Vuln-ID|V-214451

Plugin: Windows

Control ID: 09645a9c2cedb3964ba216e5f724e41e519d7a0f0007dcb6856039b44468bb6c