IIST-SI-000252 - The maximum number of requests an application pool can process for each IIS 10.0 website must be explicitly set.

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

IIS application pools can be periodically recycled to avoid unstable states possibly leading to application crashes, hangs, or memory leaks. By default, application pool recycling is overlapped, which means the worker process to be shut down is kept running until after a new worker process is started. After a new worker process starts, new requests are passed to it. The old worker process shuts down after it finishes processing its existing requests, or after a configured time-out, whichever comes first. This way of recycling ensures uninterrupted service to clients.

Solution

Open the IIS 10.0 Manager.

Click 'Application Pools'.

Highlight an Application Pool and click 'Advanced Settings' in the 'Action' Pane.

Scroll down to the 'Recycling section' and set the value for 'Request Limit' to greater than '0'.

Click 'OK'.

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_MS_IIS_10-0_Y23M04_STIG.zip

Item Details

References: CAT|II, CCI|CCI-000366, Rule-ID|SV-218772r879887_rule, STIG-ID|IIST-SI-000252, STIG-Legacy|SV-109369, STIG-Legacy|V-100265, Vuln-ID|V-218772

Plugin: Windows

Control ID: 3030e694ca30c17fe677dac9649cbfcfca20164466439cc4ec4006092b7309ae