STIGhubSTIGhub
STIGsSearchCompareAbout

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
  • Compare Versions

Resources

  • About
  • VPAT
  • DISA STIG Library
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to STIGs

MS SQL Server 2014 Database Security Technical Implementation Guide

Version

V1R7

Benchmark ID

MS_SQL_Server_2014_Database_STIG

Total Checks

43

Tags

database
CAT I: 1CAT II: 42CAT III: 0

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.

Export CKLExport CSVExport JSON

Checks (43)

V-213764MEDIUMSQL Server must enforce approved authorizations for logical access to information and database-level system resources in accordance with applicable access control policies.V-213765MEDIUMSQL Server must generate Trace or Audit records for organization-defined auditable events.V-213766MEDIUMWhere SQL Server Audit is in use at the database level, SQL Server must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited at the database level.V-213767MEDIUMSQL Server must be monitored to discover unauthorized changes to functions.V-213768MEDIUMSQL Server must be monitored to discover unauthorized changes to triggers.V-213769MEDIUMSQL Server must be monitored to discover unauthorized changes to stored procedures.V-213770MEDIUMDatabase objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to SQL Server, etc.) must be owned by database/DBMS principals authorized for ownership.V-213771MEDIUMIn a database owned by [sa], or by any other login having administrative privileges at the instance level, the database property TRUSTWORTHY must be OFF.V-213772MEDIUMIn a database owned by a login not having administrative privileges at the instance level, the database property TRUSTWORTHY must be OFF unless required and authorized.V-213773MEDIUMIn the event of a system failure, SQL Server must preserve any information necessary to return to operations with least disruption to mission processes.V-213774MEDIUMSQL Server must protect data at rest and ensure confidentiality and integrity of data.V-213775MEDIUMDatabase contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy.V-213776MEDIUMSQL Server must check the validity of all data inputs except those specifically identified by the organization.V-213777MEDIUMThe DBMS and associated applications must provide non-privileged users with error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.V-213778MEDIUMSQL Server must reveal detailed error messages only to the ISSO, ISSM (or their designees), SA and DBA.V-213779MEDIUMThe Database Master Key must be encrypted by the Service Master Key, where a Database Master Key is required and another encryption method has not been specified.V-213780MEDIUMDatabase Master Key passwords must not be stored in credentials within the database.V-213781MEDIUMSymmetric keys (other than the database master key) must use a DoD certificate to encrypt the key.V-213782MEDIUMThe DBMS and associated applications must reserve the use of dynamic code execution for situations that require it.V-213783MEDIUMThe DBMS and associated applications, when making use of dynamic code execution, must scan input data for invalid values that may indicate a code injection attack.V-213784MEDIUMWhen supporting applications that require security labeling of data, SQL Server must associate organization-defined types of security labels having organization-defined security label values with information in storage.V-213785MEDIUMWhen supporting applications that require security labeling of data, SQL Server must associate organization-defined types of security labels having organization-defined security label values with information in process.V-213786MEDIUMWhen supporting applications that require security labeling of data, SQL Server must associate organization-defined types of security labels having organization-defined security label values with information in transmission.V-213787MEDIUMTime stamps in database tables, intended for auditing or activity-tracking purposes, must include both date and time of day, with a minimum granularity of one second.V-213788MEDIUMSQL Server must implement and/or support cryptographic mechanisms to prevent unauthorized modification of organization-defined information at rest (to include, at a minimum, PII and classified information) on organization-defined information system components.V-213789MEDIUMWhen invalid inputs are received, SQL Server must behave in a predictable and documented manner that reflects organizational and system objectives.V-213790MEDIUMTrace or Audit records must be generated when categorized information (e.g., classification levels/security levels) is accessed.V-213791MEDIUMTrace or Audit records must be generated when unsuccessful attempts to access categorized information (e.g., classification levels/security levels) occur.V-213792MEDIUMSQL Server must generate Trace or Audit records when privileges/permissions are modified via locally-defined security objects.V-213793MEDIUMSQL Server must generate Trace or Audit records when unsuccessful attempts to modify privileges/permissions via locally-defined security objects occur.V-213794MEDIUMSQL Server must generate Trace or Audit records when locally-defined security objects are modified.V-213795MEDIUMSQL Server must generate Trace or Audit records when unsuccessful attempts to modify locally-defined security objects occur.V-213796MEDIUMTrace or Audit records must be generated when categorized information (e.g., classification levels/security levels) is created.V-213797MEDIUMTrace or Audit records must be generated when categorized information (e.g., classification levels/security levels) is modified.V-213798MEDIUMTrace or Audit records must be generated when unsuccessful attempts to create categorized information (e.g., classification levels/security levels) occur.V-213799MEDIUMTrace or Audit records must be generated when unsuccessful attempts to modify categorized information (e.g., classification levels/security levels) occur.V-213800MEDIUMSQL Server must generate Trace or Audit records when locally-defined security objects are dropped.V-213801MEDIUMSQL Server must generate Trace or Audit records when unsuccessful attempts to drop locally-defined security objects occur.V-213802MEDIUMTrace or Audit records must be generated when categorized information (e.g., classification levels/security levels) is deleted.V-213803MEDIUMTrace or Audit records must be generated when unsuccessful attempts to delete categorized information (e.g., classification levels/security levels) occur.V-213804MEDIUMSQL Server must generate Trace or Audit records when successful accesses to designated objects occur.V-213805MEDIUMSQL Server must generate Trace or Audit records when unsuccessful accesses to designated objects occur.V-265637HIGHMicrosoft SQL Server products must be a version supported by the vendor.