Title: The DBMS must protect audit tools from unauthorized access.
Vulnerability ID: V-32397
IA Controls: None
Description: Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data.
Depending upon the log format and application, system and application log tools may provide the only means to manipulate and manage application and system log data. It is, therefore, imperative that access to audit tools be controlled and protected from unauthorized access.
Applications providing tools to interface with audit data will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order make access decisions regarding the access to audit tools.
Audit tools include, but are not limited to, OS provided audit tools, vendor provided audit tools, and open source audit tools needed to successfully view and manipulate audit information system activity and records.
If an attacker were to gain access to audit tools he could analyze audit logs for system weaknesses or weaknesses in the auditing itself. An attacker could also manipulate logs to hide evidence of malicious activity.
Check Text: Review access permissions to tools used to view or modify audit log data. These tools may include the DBMS itself or tools external to the database. If appropriate permissions and access controls to prevent unauthorized access are not applied to these tools, this is a finding.
Fix Text: Add or modify access controls and permissions to tools used to view or modify audit log data. Tools must be accessible by authorized personnel only.[divider]
When using SQL Server’s native audit capabilities you can specify what access users have to the audit configurations and logs.
You will want to make sure only authorized individuals have access to create, review and run audits within SQL Server.
In SQL Server, those granted the proper level of permission on the instance are able to configure SQL Server’s native Audit capabilities including log access.
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.
To view an Audit log requires the CONTROL SERVER permission
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.