UCF STIG Viewer Logo

The amount of private memory an application pool uses must be set.


Overview

Finding ID Version Rule ID IA Controls Severity
V-13707 WA000-WI6026 IIS7 SV-46349r3_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
IIS 7.0 WEB SITE STIG 2017-12-21

Details

Check Text ( C-32856r5_chk )
Note: Recycling Application Pools can create an unstable environment in a 64-bit Sharepoint environment. If operational issues arise, with supporting documentation from the ISSO this check can be downgraded to a Cat III.

1. Open the IIS Manager.
2. Click the Application Pools.
3. Highlight an Application Pool and click Advanced Settings in the Action Pane.
4. Scroll down to the recycling section and ensure the value for Private Memory Limit is set to a value other than 0. If not, this is a finding.

Fix Text (F-28991r1_fix)
1. Open the IIS Manager.
2. Click the Application Pools.
3. Highlight an Application Pool and click Advanced Settings in the Action Pane.
4. Scroll down to the recycling section and set the value for Private Memory Limit to a value other than 0.