DoD STIGs – V-32395


Title: The DBMS must protect audit information from unauthorized deletion.

Vulnerability ID: V-32395


IA Controls: None

Severity: medium

Description: If audit data were to become compromised then competent forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.

To ensure the veracity of audit data the information system and/or the application must protect audit information from unauthorized deletion. This requirement can be achieved through multiple methods which will depend upon system architecture and design.

Some commonly employed methods include: ensuring log files enjoy the proper file system permissions utilizing file system protections; restricting access; and backing up log data to ensure log data is retained.

Applications providing a user interface to audit data will leverage user permissions and roles identifying the user accessing the data and the corresponding rights the user enjoys in order make access decisions regarding the deletion of audit data.

Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity.

Deletion of database audit data could mask the theft of, or the unauthorized modification of, sensitive data stored in the database.

Check Text: Review locations of audit logs, both internal to the database, and database audit logs located at the operating system level. Verify there are appropriate controls and permissions to protect the audit information from unauthorized deletion. If appropriate controls and permissions do not exist, this is a finding.

Fix Text: Add controls and modify permissions to protect database audit log data from unauthorized deletion, whether stored in the database itself or at the OS level.


Interpreting V-32395:

When using SQL Server’s native audit capabilities you can specify a few locations that the audit information can be stored.

You can specify if you want the data to be stored in a file, the security log, or the application log. If using a file, make sure that it is stored in a secured directory and only those that need to have access to the file actually have the appropriate levels of access. The same goes for storing the data in the logs. Ensure only those that are required to, have the permission to make any changes to the logs.

Return to the DoD STIGs – Database Security Requirements Guide

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.