Title

The application must implement transaction recovery logs when transaction based. (Cat II impact)

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 Content

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 Text

Configure the application database to utilize transactional logging.

Additional Identifiers

Rule ID: SV-222479r879569_rule

Vulnerability ID: V-222479

Group Title: SRG-APP-000101

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.