MS SQL Server 2014 Instance STIG

MS SQL Server 2014 Instance Security Technical Implementation Guide

The MS SQL Server 2014 Instance Security Technical Implementation Guide (V2 R4) has 93 STIG checks. New to STIG checklists? Read What is a STIG checklist?, CKL vs CKLB, and STIG vs SCAP benchmark.

Find STIG checks

93STIG checks

Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.

Severity

Version

V2 · R4

CurrentPublished Wed Jul 24 2024 What changed in V2R4

SQL Server must generate Trace or Audit records when unsuccessful logons or connection attempts occur.

MS SQL Server 2014 Instance Security Technical Implementation Guide

Assessment Title

Rule Text

SQL Server must generate Trace or Audit records when unsuccessful logons or connection attempts occur.

Description

Discussion Text

For completeness of forensic analysis, it is necessary to track failed attempts to log on to SQL Server. While positive identification may not be possible in a case of failed authentication, as much information as possible about the incident must be captured.

Use of SQL Server Audit is recommended. All features of SQL Server Audit are available in the Enterprise and Developer editions of SQL Server 2014. It is not available at the database level in other editions. For this or legacy reasons, the instance may be using SQL Server Trace for auditing, which remains an acceptable solution for the time being. Note, however, that Microsoft intends to remove most aspects of Trace at some point after SQL Server 2016.

New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.

Objective

V-213888

Rule

SV-213888r961824_rule

Severity

medium

Rule Version

SQL4-00-037600

Documentable

false

IA Controls

NIST SP 800-53

Rev 5

Assessment Procedure

Check Text

If neither SQL Server Audit nor SQL Server Trace is in use for audit purposes, this is a finding.

If SQL Server Trace is in use for audit purposes, verify that all required events are being audited. From the query prompt:
SELECT * FROM sys.traces;
All currently defined traces for the SQL server instance will be listed.

If no traces are returned, this is a finding.

Determine the trace(s) being used for the auditing requirement.
In the following, replace # with a trace ID being used for the auditing requirements.
From the query prompt:
SELECT DISTINCT(eventid) FROM sys.fn_trace_geteventinfo(#);

The following required event ID should be among those listed; if not, this is a finding:

20  -- Audit Login Failed

If SQL Server Audit is in use, proceed as follows.

The basic SQL Server Audit configuration provided in the supplemental file Audit.sql uses the server-level audit action group FAILED_LOGIN_GROUP for this purpose. SQL Server Audit's flexibility makes other techniques possible. If an alternative technique is in use and demonstrated effective, this is not a finding.

Determine the name(s) of the server audit specification(s) in use.

To look at audits and audit specifications, in Management Studio's object explorer, expand 
<server name> >> Security >> Audits
and
<server name> >> Security >> Server Audit Specifications.
Also, 
<server name> >> Databases >> <database name> >> Security >> Database Audit Specifications.

Alternatively, review the contents of the system views with "audit" in their names.

Run the following to verify that all logons and connections are being audited:
USE [master];
GO
SELECT * FROM sys.server_audit_specification_details WHERE server_specification_id =
(SELECT server_specification_id FROM sys.server_audit_specifications WHERE [name] = '<server_audit_specification_name>')
AND audit_action_name = 'FAILED_LOGIN_GROUP';
GO

If no row is returned, this is a finding.

If the "FAILED_LOGIN_GROUP" is returned with the audited_result_column of "FAILURE" or "SUCCESS AND FAILURE", this is not a finding. 

If "FAILED_LOGIN_GROUP" is not in the active audit, determine whether "Both failed and successful logins" is enabled. 

In SQL Management Studio:
Right-click on the instance.
>> Select "Properties".
>> Select "Security" on the left side.
>> Check the setting for "Login auditing".

If "Both failed and successful logins" is not selected, this is a finding.

Implementation Procedure

Fix Text

Where SQL Server Trace is in use, define and enable a trace that captures all auditable events. The script provided in the supplemental file Trace.sql can be used to do this.

Where SQL Server Audit is in use, design and deploy a SQL Server Audit that captures all auditable events. The script provided in the supplemental file Audit.sql can be used for this.

To add the necessary data capture to an existing server audit specification, run the script:
USE [master];
GO
ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = OFF);
GO
ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> ADD (FAILED_LOGIN_GROUP);
GO
ALTER SERVER AUDIT SPECIFICATION <server_audit_specification_name> WITH (STATE = ON);
GO

Alternatively, enable "Both failed and successful logins".
In SQL Management Studio:
Right-click on the instance.
>> Select "Properties".
>> Select "Security" on the left side.
>> Select "Both failed and successful logins".
>> Click "OK".

STIG check 82 of 93 in the MS SQL Server 2014 Instance STIG checklist

← Previous · V-213887SQL Server must generate Trace or Audit records when successful logons or connections occur.Next · V-213889 →SQL Server must generate Trace or Audit records for all privileged activities or other system-level access.