DoD STIGs – V-32394

Overview:

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

Vulnerability ID: V-32394

STIG ID:

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 modification.

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 and limiting log data locations.

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

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

Modification 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 modification. 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 modification, whether stored in the database itself or at the OS level.

[divider]

Interpreting V-32394:

This is performed at the OS level when it comes to SQL Server’s native auditing tools.

SQL Server Audit can write to a file in a directory, the security log or the application log, each of which should have access controlled appropriately.

Other third party tools most likely work in the same ways, so the same checks for appropriate access by approved users should be verified.

 

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.