UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

SQL Server must protect data at rest and ensure confidentiality and integrity of data.


Overview

Finding ID Version Rule ID IA Controls Severity
V-40911 SQL2-00-021300 SV-53265r1_rule Medium
Description
This control is intended to address the confidentiality and integrity of information at rest in non-mobile devices and covers user information and system information. Information at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive, tape drive) within an organizational information system. Applications and application users generate information throughout the course of their application use. User-generated data, as well as, application-specific configuration data, needs to be protected. Configurations and/or rule sets for firewalls, gateways, intrusion detection/prevention systems, filtering routers, and authenticator content are examples of system information likely requiring protection. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate. If the confidentiality and integrity of SQL Server data is not protected, the data will be open to compromise and unauthorized modification.
STIG Date
Microsoft SQL Server 2012 Database Instance Security Technical Implementation Guide 2014-01-05

Details

Check Text ( C-47566r2_chk )
Ensure the data on secondary devices is encrypted. If full-disk encryption is being used, this is not a finding.

Ensure the data is encrypted before being put on the secondary device by executing:
SELECT * FROM [master].sys.databases

For each user database, ensure the Is_encrypted column is set to 1. If it is not set to 1, this is a finding.
Fix Text (F-46193r2_fix)
Apply appropriate controls to protect the confidentiality and integrity of data on a secondary device. This can be done by full-disk encryption or by database encryption. To enable database encryption, create a master key, create a database encryption key, and protect it by using mechanisms tied to the master key, and then set encryption on.