STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to MS SQL Server 2014 Instance Security Technical Implementation Guide

V-213854

CAT II (Medium)

SQL Server must be configured to separate user functionality (including user interface services) from database management functionality.

Rule ID

SV-213854r961095_rule

STIG

MS SQL Server 2014 Instance Security Technical Implementation Guide

Version

V2R4

CCIs

CCI-001082

Discussion

Information system management functionality includes functions necessary to administer databases, network components, workstations, or servers and typically requires privileged user access. The separation of user functionality from information system management functionality is either physical or logical and is accomplished by using different computers, different central processing units, different instances of the operating system, different network addresses, combinations of these methods, or other methods, as appropriate. An example of this type of separation is observed in web administrative interfaces that use separate authentication methods for users of any other information system resources. This may include isolating the administrative interface on a different domain and with additional access controls. If administrative functionality or information regarding DBMS management is presented on an interface available for users, information on DBMS settings may be inadvertently made available to the user.

Check Content

Check SQL Server permission settings to verify that administrative functionality is kept separate from user functionality.  The views and functions provided in the supplemental file Permissions.sql can help with this review.

If administrator and general user functionality are not separated either physically or logically, this is a finding.

Fix Text

Establish one or more locally-defined server roles and one or more locally-defined database roles for organizing administrative permissions.  Grant administrative permissions to these roles.  Assign the appropriate administrative users to these roles.  Do not grant the roles and permissions to general users.