STIGQter STIGQter: STIG Summary: MS SQL Server 2014 Instance Security Technical Implementation Guide Version: 1 Release: 10 Benchmark Date: 24 Apr 2020:

Where SQL Server Trace is in use for auditing purposes, SQL Server must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be traced.

DISA Rule

SV-82255r1_rule

Vulnerability Number

V-67765

Group Title

SRG-APP-000090-DB-000065

Rule Version

SQL4-00-011300

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

Create a server role specifically for audit maintainers, and give it permission to maintain traces, without granting it unnecessary permissions:
USE master;
GO
CREATE SERVER ROLE SERVER_AUDIT_MAINTAINERS;
GO
GRANT ALTER TRACE TO SERVER_AUDIT_MAINTAINERS;
-- Next line only if required:
GRANT CREATE TRACE EVENT NOTIFICATION TO SERVER_AUDIT_MAINTAINERS;
GO
(The role name used here is an example; other names may be used.)

Use REVOKE and/or DENY and/or ALTER SERVER ROLE ... DROP MEMBER ... statements to remove the ALTER TRACE and CREATE TRACE EVENT NOTIFICATION permissions from all logins.

Then, for each authorized login, run the statement:
ALTER SERVER ROLE SERVER_AUDIT_MAINTAINERS ADD MEMBER <login name>;
GO

Check Contents

If SQL Server Trace is not in use for audit purposes, this is not a finding.

Obtain the list of approved audit maintainers from the system documentation.

Review the server roles and individual logins that have the following permissions, all of which enable the ability to create and maintain audit definitions (the views and functions provided in the supplemental fine Permissions.sql can assist in this):
ALTER TRACE
CREATE TRACE EVENT NOTIFICATION

The functions and views provided in the supplemental file Permissions.sql can assist in this review. In the following, "STIG" stands for the schema where you have deployed these views and functions. To see which logins and server roles have been granted these permissions:
SELECT
*
FROM
STIG.server_permissions P
WHERE
P.[Permission] IN
(
'ALTER TRACE',
'CREATE TRACE EVENT NOTIFICATION'
);

To see what logins and server roles inherit these permissions from the server roles reported by the previous query, repeat the following for each one:
SELECT * FROM STIG.members_of_server_role(<server role name>);

To see all the permissions in effect for a server principal (server role or login):
SELECT * FROM STIG.server_effective_permissions(<principal name>);

If designated personnel are not able to configure auditable events, this is a finding.

If unapproved personnel are able to configure auditable events, this is a finding.

Vulnerability Number

V-67765

Documentable

False

Rule Version

SQL4-00-011300

Severity Override Guidance

If SQL Server Trace is not in use for audit purposes, this is not a finding.

Obtain the list of approved audit maintainers from the system documentation.

Review the server roles and individual logins that have the following permissions, all of which enable the ability to create and maintain audit definitions (the views and functions provided in the supplemental fine Permissions.sql can assist in this):
ALTER TRACE
CREATE TRACE EVENT NOTIFICATION

The functions and views provided in the supplemental file Permissions.sql can assist in this review. In the following, "STIG" stands for the schema where you have deployed these views and functions. To see which logins and server roles have been granted these permissions:
SELECT
*
FROM
STIG.server_permissions P
WHERE
P.[Permission] IN
(
'ALTER TRACE',
'CREATE TRACE EVENT NOTIFICATION'
);

To see what logins and server roles inherit these permissions from the server roles reported by the previous query, repeat the following for each one:
SELECT * FROM STIG.members_of_server_role(<server role name>);

To see all the permissions in effect for a server principal (server role or login):
SELECT * FROM STIG.server_effective_permissions(<principal name>);

If designated personnel are not able to configure auditable events, this is a finding.

If unapproved personnel are able to configure auditable events, this is a finding.

Check Content Reference

M

Target Key

2639

Comments