Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-214487 | IISW-SI-000254 | SV-214487r508659_rule | Medium |
Description |
---|
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. |
STIG | Date |
---|---|
Microsoft IIS 8.5 Site Security Technical Implementation Guide | 2021-03-24 |
Check Text ( C-15696r505336_chk ) |
---|
Note: If the IIS Application Pool is hosting Microsoft SharePoint, this is Not Applicable. If this IIS 8.5 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. Open the IIS 8.5 Manager. Perform the following for each Application Pool: Click "Application Pools". Highlight an Application Pool and click "Advanced Settings" in the "Action" Pane. Scroll down to the "Recycling" section and verify the value for "Private Memory Limit" is set to a value other than "0". If the "Private Memory Limit" is set to a value of "0", this is a finding. |
Fix Text (F-15694r505337_fix) |
---|
Open the IIS 8.5 Manager. Click "Application Pools". Perform the following for each Application Pool: Highlight an Application Pool and click "Advanced Settings" in the "Action" Pane. Scroll down to the "Recycling" section and set the value for "Private Memory Limit" to a value other than "0". |