SQL6-D0-004600 - SQL Server must generate audit records when successful/unsuccessful attempts to retrieve privileges/permissions occur.

Information

Under some circumstances, it may be useful to monitor who/what is reading privilege/permission/role information. Therefore, monitoring must be possible. DBMSs typically make such information available through views or functions.

This requirement addresses explicit requests for privilege/permission/role membership information. It does not refer to the implicit retrieval of privileges/permissions/role memberships that SQL Server continually performs to determine if any and every action on the database is permitted.

To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

Satisfies: SRG-APP-000091-DB-000066

NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.

Solution

Deploy an audit to audit the retrieval of privilege/permission/role membership information. See the supplemental file 'SQL 2016 Audit.sql'.

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_MS_SQL_Server_2016_Y24M07_STIG.zip

Item Details

Category: AUDIT AND ACCOUNTABILITY

References: 800-53|AU-12c., CAT|II, CCI|CCI-000172, Rule-ID|SV-213939r960885_rule, STIG-ID|SQL6-D0-004600, STIG-Legacy|SV-93845, STIG-Legacy|V-79139, Vuln-ID|V-213939

Plugin: MS_SQLDB

Control ID: ce10b6acc9d72c3f04bfd2f66d7e293cecfa536b9a2a1704759d4705bdbdff9e