Title: The DBMS must allow designated organizational personnel to select which auditable events are to be audited by the database.
Vulnerability ID: V-32363
IA Controls: None
Description: The list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating audit records (i.e., auditable events, timestamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked).
If the list of auditable events is not configurable, events that should be caught by auditing may be missed. This may allow malicious activity to be overlooked.
Check Text: Check DBMS settings and documentation to determine whether designated personnel are able to select which auditable events are being audited. If designated personnel are not able to configure auditable events, this is a finding.
Fix Text: Configure the DBMS’s settings to allow designated personnel to select which auditable events are audited.[divider]
In SQL Server, those granted the proper level of permission on the instance are able to configure SQL Server’s native Audit capabilities. These people do not need to be full sysadmin level.
The level of permission that needs to be assigned to a role for the individual to configure audits are as follows:
To create, modify, delete, and enable server audit objects the user or role must be granted the ALTER ANY SERVER AUDIT or CONTROL SERVER permission
To be able to configure database audit specifications, as this STIG requires, the user or role must be granted the ALTER ANY DATABASE AUDIT, ALTER, or CONTROL permissions on the audited database.
Remember that is is preferred to create roles for the individual to be a member of, rather than granting specific permissions to the individual accounts.