STIGQter: STIG Summary: Microsoft Azure SQL Database Security Technical Implementation Guide Version: 2 Release: 3 Benchmark Date: 02 Jul 2025:

Azure SQL Database must implement cryptographic mechanisms preventing the unauthorized disclosure of organization-defined information at rest on organization-defined information system components.

DISA Rule

SV-255322r1018559_rule

Vulnerability Number

V-255322

Group Title

SRG-APP-000429-DB-000387

Rule Version

ASQL-00-003400

Severity

CAT I

CCI(s)

• CCI-002476 - Implement cryptographic mechanisms to prevent unauthorized disclosure of organization-defined information at rest on organization-defined system components.

Weight

10

Fix Recommendation

If Azure SQL Database Transparent Data Encryption is disabled, use the Set-AzSqlDatabaseTransparentDataEncryption command to enable.

$LogicalServerName = "myServerName"
$RGname = "myResourceGroup"
$DBName = "myDatabaseName"

$TDEstate = "Enabled"

Set-AzSqlDatabaseTransparentDataEncryption -ResourceGroupName $RGname -ServerName $LogicalServerName -DatabaseName $DBname -State $TDEstate

Check Contents

Review the system documentation to determine whether the organization has defined the information at rest that is to be protected from modification, which must include, at a minimum, PII and classified information.

If no information is identified as requiring such protection, this is not a finding.

Review the configuration of the Azure SQL Database to ensure data at rest protections are implemented.

If any of the information defined as requiring cryptographic protection from modification is not encrypted in a manner that provides the required level of protection, this is a finding.

Retrieve Transparent Data Encryption status:
$LogicalServerName = "myServerName"
$RGname = "myResourceGroup"
$DBName = "myDatabaseName"

Get-AzSqlDatabaseTransparentDataEncryption -ServerName $LogicalServerName -ResourceGroupName $RGname -DatabaseName $DBname

Vulnerability Number

V-255322

Documentable

False

Rule Version

ASQL-00-003400

Severity Override Guidance

Review the system documentation to determine whether the organization has defined the information at rest that is to be protected from modification, which must include, at a minimum, PII and classified information.

If no information is identified as requiring such protection, this is not a finding.

Review the configuration of the Azure SQL Database to ensure data at rest protections are implemented.

If any of the information defined as requiring cryptographic protection from modification is not encrypted in a manner that provides the required level of protection, this is a finding.

Retrieve Transparent Data Encryption status:
$LogicalServerName = "myServerName"
$RGname = "myResourceGroup"
$DBName = "myDatabaseName"

Get-AzSqlDatabaseTransparentDataEncryption -ServerName $LogicalServerName -ResourceGroupName $RGname -DatabaseName $DBname

Check Content Reference

M

Target Key

5500