Detections
Analytics

SQLI-22-007900 - If DBMS authentication using passwords is employed, SQL Server must enforce the DOD standards for password complexity and lifetime.

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

Windows Authentication is the default authentication mode and is much more secure than SQL Server Authentication. Windows Authentication uses Kerberos security protocol, provides password policy enforcement regarding complexity validation for strong passwords, provides support for account lockout, and supports password expiration. A connection made using Windows Authentication is sometimes called a trusted connection, because SQL Server trusts the credentials provided by Windows.

By using Windows Authentication, Windows groups can be created at the domain level, and a login can be created on SQL Server for the entire group. Managing access at the domain level can simplify account administration.

OS/enterprise authentication and identification must be used (SRG-APP-000023-DB-000001). Native SQL Server authentication may be used only when circumstances make it unavoidable and must be documented and authorizing official (AO)-approved.

The DOD standard for authentication is DOD-approved PKI certificates. Authentication based on User ID and Password may be used only when it is not possible to employ a PKI certificate and requires AO approval.

In such cases, the DOD standards for password complexity and lifetime must be implemented. DBMS products that can inherit the rules for these from the operating system or access control program (e.g., Microsoft Active Directory) must be configured to do so. For other DBMSs, the rules must be enforced using available configuration parameters or custom code.

Satisfies: SRG-APP-000164-DB-000401, SRG-APP-000700-DB-000100

Solution

Ensure check of policy and expiration are enforced when SQL logins are created.

Use the command below to set CHECK_EXPIRATION and CHECK_POLICY for any login found to be noncompliant:

ALTER LOGIN [LoginnameHere] WITH CHECK_EXPIRATION=ON;
ALTER LOGIN [LoginNameHere] WITH CHECK_POLICY=ON;

New SQL authenticated logins must be created with CHECK_EXPIRATION and CHECK_POLICY set to ON.

CREATE LOGIN [LoginNameHere] WITH PASSWORD = 'ComplexPasswordHere', CHECK_EXPIRATION = ON, CHECK_POLICY = ON;

See Also

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

Item Details

References: CAT|I, CCI|CCI-003627, CCI|CCI-004066, Rule-ID|SV-271307r1109241_rule, STIG-ID|SQLI-22-007900, Vuln-ID|V-271307

Plugin: MS_SQLDB

Control ID: a62d630373239d921997b04e11f80323d0012e819332c7fc70d8f32f82446ee9