The WebSphere Application Server automatic repository checkpoints must be enabled to track configuration changes.

From IBM WebSphere Traditional V9.x Security Technical Implementation Guide

Associated with: CCI-000067

SV-95911r1_rule The WebSphere Application Server automatic repository checkpoints must be enabled to track configuration changes.

Vulnerability discussion

Without enabling repository checkpoints, you will not be able to determine the history of changes to WebSphere configuration files, and who made those changes.

Check content

Review System Security Plan documentation. Identify the required "Automatic CheckPoint Depth" setting that has been defined. From administrative console, click System administration >> Extended repository service. If "Enable automatic repository checkpoints" is not selected or if the "automatic checkpoint depth" is less than the number of saves defined in the System Security Plan, this is a finding.

Fix text

From administrative console click System administration >> Extended repository service >> Enable automatic repository checkpoints. Enter a "checkpoint depth value" according to the security plan. Restart the DMGR and all the JVMs.

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.