Vulnerability Discussion

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

Determining user accounts, processes running on behalf of the user, and running process identifiers also enable a better understanding of the overall event. User tool identification is also helpful to determine if events are related to overall user access or specific client tools.

Log record content that may be necessary to satisfy the requirement of this control includes: time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked.

Check

Access the IIS 10.0 web server IIS Manager.
Click the IIS 10.0 web server name.
Under "IIS", double-click the "Logging" icon.
Verify the "Format:" under "Log File" is configured to "W3C".
Select the "Fields" button.
Under "Standard Fields", verify "User Agent", "User Name", and "Referrer" are selected.
Under "Custom Fields", verify the following field has been configured:
Request Header >> Authorization
Response Header >> Content-Type
If any of the above fields are not selected, this is a finding.

Fix

Access the IIS 10.0 web server IIS Manager.
Click the IIS 10.0 web server name.
Under "IIS", double-click the "Logging" icon.
Verify the "Format:" under "Log File" is configured to "W3C".
Select the "Fields" button.
Under "Standard Fields", select "User Agent", "User Name", and "Referrer".
Under "Custom Fields", select the following fields:
Click on the "Source Type" drop-down list and select "Request Header".
Click on the "Source" drop-down list and select "Authorization".
Click "OK" to add.

Click on the "Source" drop-down list and select "Content-Type".
Click on the "Source Type" drop-down list and select "Response Header".
Click "OK" to add.
Click "OK".
Click "Apply" under the "Actions" pane.