STIGUI
V-222479CAT II — Medium severitySV-222479r960909_rule

The application must implement transaction recovery logs when transaction based.

Rule version APSC-DV-001040 · STIG v6 · 2026-08-25

Discussion

Without required logging and access control, security issues related to data changes will not be identified. This could lead to security compromises such as data misuse, unauthorized changes, or unauthorized access.

Transaction logs contain a sequential record of all changes to the database. Using a transaction log helps with maintaining application availability and aids in speedy recovery. Transactional logging should be enabled whenever the application database offers the transactional logging capability.

Check

Review the application documentation and interview the application administrator. Have the application administrator provide configuration settings that demonstrate transaction logging is enabled.

Review configuration settings for the location of transaction specific logs and verify transaction logs exist and the log records access and changes to the data.

If the application is not configured to utilize transaction logging, this is a finding.

Fix

Configure the application database to utilize transactional logging.

Identifiers

Group ID
V-222479
Group title
SRG-APP-000101
Rule ID
SV-222479r960909_rule
Check ID
C-24149r493345_chk
Fix ID
F-24138r493346_fix