STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 4 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Microsoft IIS 10.0 Site Security Technical Implementation Guide

V-218742

CAT II (Medium)

The IIS 10.0 website must produce log records containing sufficient information to establish the identity of any user/subject or process associated with an event.

Rule ID

SV-218742r1022679_rule

STIG

Microsoft IIS 10.0 Site Security Technical Implementation Guide

Version

V2R15

CCIs

CCI-001487

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 Content

Note: If this server is hosting WSUS, this requirement is Not Applicable.

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

Access the IIS 10.0 web server IIS 10.0 Manager.

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

Verify the "Format:" under "Log File" is configured to "W3C".

Select "Fields".

Under "Standard Fields", verify "User Agent", "User Name", and "Referrer" are selected.

Under "Custom Fields", verify the following fields have been configured: 

Request Header >> Authorization

Response Header >> Content-Type

If any of the above fields are not selected, this is a finding.

Fix Text

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

Access the IIS 10.0 web server IIS 10.0 Manager.

Select the website being reviewed.

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

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

Select "Fields".

Under "Standard Fields", select "User Agent", "User Name", and "Referrer".

Under "Custom Fields", select the following fields:

Request Header >> Authorization

Response Header >> Content-Type

Click "OK".

Select "Apply" from the "Actions" pane.