Information
Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restriction of privileges could go undetected. Elevated privileges give users access to information and functionality that they should not have; restricted privileges wrongly deny access to authorized users.
In an SQL environment, modifying permissions is typically done via the GRANT, REVOKE, and DENY commands.
To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.
Satisfies: SRG-APP-000495-DB-000328
Solution
Add the following events to the SQL Server Audit that is being used for the STIG compliant audit.
DATABASE_OBJECT_OWNERSHIP_CHANGE_GROUP
DATABASE_OBJECT_PERMISSION_CHANGE_GROUP
DATABASE_OWNERSHIP_CHANGE_GROUP
DATABASE_PERMISSION_CHANGE_GROUP
DATABASE_ROLE_MEMBER_CHANGE_GROUP
SCHEMA_OBJECT_OWNERSHIP_CHANGE_GROUP
SCHEMA_OBJECT_PERMISSION_CHANGE_GROUP
SERVER_OBJECT_OWNERSHIP_CHANGE_GROUP
SERVER_OBJECT_PERMISSION_CHANGE_GROUP
SERVER_PERMISSION_CHANGE_GROUP
SERVER_ROLE_MEMBER_CHANGE_GROUP
See the supplemental file 'SQL 2016 Audit.sql'.
Reference:
https://msdn.microsoft.com/en-us/library/cc280663.aspx