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

SQL Server and Windows must enforce access restrictions associated with changes to the configuration of the SQL Server instance or database(s).

DISA Rule

SV-82391r1_rule

Vulnerability Number

V-67901

Group Title

SRG-APP-000380-DB-000360

Rule Version

SQL4-00-033900

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

Configure SQL Server to enforce access restrictions associated with changes to the configuration of the SQL Server instance and database(s).

Check Contents

Review the security configuration of the SQL Server instance and database(s).

If unauthorized Windows users can start the SQL Server Configuration Manager or SQL Server Management Studio, this is a finding.

If SQL Server does not enforce access restrictions associated with changes to the configuration of the SQL Server instance or database(s), this is a finding.

- - - - -

To assist in conducting reviews of permissions, the following views and permissions are defined in the supplemental file Permissions.sql, provided with this STIG:
database_permissions
database_role_members
server_permissions
server_role_members
database_effective_permissions('<database user/role name>')
database_roles_of('<database user/role name>')
members_of_db_role('<database role name>')
members_of_server_role('<server role name>')
server_effective_permissions('<server login/role name>')
server_roles_of('<server login/role name>')

Permissions of concern in this respect include the following, and possibly others:
- any server permission except CONNECT SQL, but including CONNECT ANY DATABASE
- any database permission beginning with "CREATE" or "ALTER"
- CONTROL
- INSERT, UPDATE, DELETE, EXECUTE on locally-defined tables and procedures designed for supplemental configuration and security purposes.

Vulnerability Number

V-67901

Documentable

False

Rule Version

SQL4-00-033900

Severity Override Guidance

Review the security configuration of the SQL Server instance and database(s).

If unauthorized Windows users can start the SQL Server Configuration Manager or SQL Server Management Studio, this is a finding.

If SQL Server does not enforce access restrictions associated with changes to the configuration of the SQL Server instance or database(s), this is a finding.

- - - - -

To assist in conducting reviews of permissions, the following views and permissions are defined in the supplemental file Permissions.sql, provided with this STIG:
database_permissions
database_role_members
server_permissions
server_role_members
database_effective_permissions('<database user/role name>')
database_roles_of('<database user/role name>')
members_of_db_role('<database role name>')
members_of_server_role('<server role name>')
server_effective_permissions('<server login/role name>')
server_roles_of('<server login/role name>')

Permissions of concern in this respect include the following, and possibly others:
- any server permission except CONNECT SQL, but including CONNECT ANY DATABASE
- any database permission beginning with "CREATE" or "ALTER"
- CONTROL
- INSERT, UPDATE, DELETE, EXECUTE on locally-defined tables and procedures designed for supplemental configuration and security purposes.

Check Content Reference

M

Target Key

2639

Comments