Detections
Analytics

SQL6-D0-014800 - SQL Server must generate audit records when successful and unsuccessful logons or connection attempts occur.

Information

For completeness of forensic analysis, it is necessary to track who/what (a user or other principal) logs on to SQL Server. It is also 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.

Satisfies: SRG-APP-000503-DB-000350, SRG-APP-000503-DB-000351, SRG-APP-000506-DB-000353

Solution

Add both 'SUCCESSFUL_LOGIN_GROUP' and 'FAILED_LOGIN_GROUP' to the server audit specification.
USE [master];
GO

ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION WITH (STATE = OFF);
GO

ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SUCCESSFUL_LOGIN_GROUP);
GO

ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (FAILED_LOGIN_GROUP);
GO

ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION 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-hand side.
- Select 'Both failed and successful logins'.
- Click 'OK'.

See Also

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

Item Details

Category: AUDIT AND ACCOUNTABILITY

References: 800-53|AU-12c., CAT|II, CCI|CCI-000172, Rule-ID|SV-214014r1167488_rule, STIG-ID|SQL6-D0-014800, STIG-Legacy|SV-93995, STIG-Legacy|V-79289, Vuln-ID|V-214014

Plugin: MS_SQLDB

Control ID: 66fa1632d33e79110c46b7dce25007aa1de172c013dda4d8f6d6b5959d96d8c2