Update alter-database-transact-sql-set-options.md

loicmaz · MashaMSFT · commit 125febb0ee87 · 2025-12-04T10:04:00.000-08:00
diff --git a/azure-sql/includes/virtual-machines-best-practices-security.md b/azure-sql/includes/virtual-machines-best-practices-security.md
@@ -31,4 +31,4 @@ SQL Server features and capabilities provide methods of securing data at the dat
 - Use [Azure Policy](/azure/governance/policy/overview) to create business rules that can be applied to your environment. Azure Policies evaluate Azure resources by comparing the properties of those resources against rules defined in JSON format.
 - Azure Blueprints enables cloud architects and central information technology groups to define a repeatable set of Azure resources that implements and adheres to an organization's standards, patterns, and requirements. Azure Blueprints are [different than Azure Policies](/azure/governance/blueprints/overview#how-its-different-from-azure-policy).
 - Use Windows Server 2019 or Windows Server 2022 to be [FIPS](../virtual-machines/windows/security-considerations-best-practices.md#fips-compliance) compliant with SQL Server on Azure VMs. 
-- Treat restoring backups as a high-risk operation and [never restore a backup from an untrusted source](../virtual-machines/windows/security-considerations-best-practices.md#security-risks-of-restoring-backups-from-untrusted-sources). 
+- Treat restoring backups as a high-risk operation and [never restore a backup from an untrusted source](../virtual-machines/windows/security-considerations-best-practices.md#security-risk-of-restoring-backups-from-untrusted-sources). 
diff --git a/azure-sql/managed-instance/recovery-using-backups.md b/azure-sql/managed-instance/recovery-using-backups.md
@@ -5,7 +5,7 @@ description: Learn about point-in-time restore, which enables you to roll back a
 author: dinethi
 ms.author: dinethi
 ms.reviewer: wiassaf, mathoma, strrodic, mlandzic
-ms.date: 07/10/2025
+ms.date: 12/05/2025
 ms.service: azure-sql-managed-instance
 ms.subservice: backup-restore
 ms.topic: how-to
@@ -211,31 +211,9 @@ It's essential to acknowledge that geo-restore serves as an appropriate disaster
 
 For more information about business continuity choices, see [Overview of business continuity](../database/business-continuity-high-availability-disaster-recover-hadr-overview.md).
 
-## Security risks of restoring backups from untrusted sources
-
-This section outlines the security risks associated with restoring backups to Azure SQL Managed Instance from untrusted sources.
-
-### Why this matters 
-
-Restoring SQL backup files (`.bak`) introduces a potential risk if the backup originates from an untrusted source. The security risk is exacerbated further when SQL managed instances are shared by multiple applications, as it amplifies the area of threat. While backups that remain within a trusted boundary pose no security issue, restoring a malicious backup can compromise the security of the entire environment.
-
-A malicious `.bak` file can: 
-- Take over the SQL managed instance.
-- Escalate privileges and gain unauthorized access to underlying virtual machine (VMs) that hosts the SQL managed instance.
-
-This attack occurs before any validating scripts or security checks can execute, which makes it extremely dangerous. Restoring an untrusted backup is equivalent to running untrusted applications on a critical virtual machine, and introducing arbitrary code execution into your environment. 
-
-### Best practices
-
-Since Azure SQL Managed Instance is ring-fenced and isolated from other workloads, backup restore is supported, which is why extra care must be taken when restoring backups.
-
-Follow these backup security best practices to reduce the threat to Azure SQL Managed Instance:
-- Treat restoring backups as a high-risk operation.
-- Reduce the threat service area by using isolated instances.
-- Only allow trusted backups. Never restore backups from unknown or external sources.
-- Only allow backups that remained within a trusted boundary. Ensure backups originate from within the trusted boundary.
-- Do not bypass security controls for convenience.
+## Security risk of restoring backups from untrusted sources
 
+[!INCLUDE [backup-restore-security-risk](../../docs/includes/backup-restore-security-risk.md)]
 
 ## Limitations
 
diff --git a/azure-sql/virtual-machines/windows/backup-restore.md b/azure-sql/virtual-machines/windows/backup-restore.md
@@ -4,10 +4,10 @@ description: Describes backup and restore considerations for SQL Server database
 author: AbdullahMSFT
 ms.author: amamun
 ms.reviewer: mathoma, randolphwest
-ms.date: 09/17/2025
+ms.date: 12/05/2025
 ms.service: azure-vm-sql-server
 ms.subservice: backup
-ms.topic: conceptual
+ms.topic: article
 tags: azure-resource-management
 ---
 # Backup and restore for SQL Server on Azure VMs
@@ -137,28 +137,9 @@ The following table summarizes the capabilities of each backup and restore optio
 | Monitor backup jobs with SSMS or Transact-SQL scripts | Yes | Yes | Yes |
 | Restore databases with SSMS or Transact-SQL scripts | Yes | No | Yes |
 
-## Security risks of restoring backups from untrusted sources
+## Security risk of restoring backups from untrusted sources
 
-This section outlines the security risks associated with restoring backups to SQL Server on Azure VMs from untrusted sources.
-
-### Why this matters 
-
-Restoring SQL backup files (`.bak`) introduces a potential risk if the backup originates from an untrusted source. The security risk is exacerbated further when a SQL Server VM has multiple instances, as it amplifies the area of threat. While backups that remain within a trusted boundary pose no security issue, restoring a malicious backup can compromise the security of the entire environment.
-
-A malicious `.bak` file can: 
-- Take over the SQL Server on Azure VM.
-- Escalate privileges and gain unauthorized access to underlying virtual machine.
-
-This attack occurs before any validating scripts or security checks can execute, which makes it extremely dangerous. Restoring an untrusted backup is equivalent to running untrusted applications on a critical virtual machine, and introducing arbitrary code execution into your environment. 
-
-### Best practices
-
-Follow these backup security best practices to reduce the threat to SQL Server on Azure VMs: 
-- Treat restoring backups as a high-risk operation.
-- Reduce the threat service area by using isolated instances.
-- Only allow trusted backups: never restore backups from unknown or external sources.
-- Only allow backups that remained within a trusted boundary : ensure backups originate from within the trusted boundary.
-- Do not bypass security controls for convenience.
+[!INCLUDE [backup-restore-security-risk](../../../docs/includes/backup-restore-security-risk.md)]
 
 ## Related content
 
diff --git a/azure-sql/virtual-machines/windows/security-considerations-best-practices.md b/azure-sql/virtual-machines/windows/security-considerations-best-practices.md
@@ -4,7 +4,7 @@ description: This article provides general guidance for securing SQL Server runn
 author: dplessMSFT
 ms.author: dpless
 ms.reviewer: mathoma, randolphwest
-ms.date: 09/16/2025
+ms.date: 12/05/2025
 ms.service: azure-vm-sql-server
 ms.subservice: security
 ms.topic: best-practice
@@ -205,28 +205,9 @@ To be FIPS compliant with SQL Server on Azure VMs, you should be on Windows Serv
 
 SQL Server isn't currently FIPS compliant on Linux Azure VMs.
 
-## Security risks of restoring backups from untrusted sources
+## Security risk of restoring backups from untrusted sources
 
-This section outlines the security risks associated with restoring backups to SQL Server on Azure VMs from untrusted sources.
-
-### Why this matters 
-
-Restoring SQL backup files (`.bak`) introduces a potential risk if the backup originates from an untrusted source. The security risk is exacerbated further when a SQL Server VM has multiple instances, as it amplifies the area of threat. While backups that remain within a trusted boundary pose no security issue, restoring a malicious backup can compromise the security of the entire environment.
-
-A malicious `.bak` file can: 
-- Take over the SQL Server on Azure VM.
-- Escalate privileges and gain unauthorized access to underlying virtual machine.
-
-This attack occurs before any validating scripts or security checks can execute, which makes it extremely dangerous. Restoring an untrusted backup is equivalent to running untrusted applications on a critical virtual machine, and introducing arbitrary code execution into your environment. 
-
-### Best practices
-
-Follow these backup security best practices to reduce the threat to SQL Server on Azure VMs: 
-- Treat restoring backups as a high-risk operation.
-- Reduce the threat service area by using isolated instances.
-- Only allow trusted backups: never restore backups from unknown or external sources.
-- Only allow backups that remained within a trusted boundary : ensure backups originate from within the trusted boundary.
-- Do not bypass security controls for convenience.
+[!INCLUDE [backup-restore-security-risk](../../../docs/includes/backup-restore-security-risk.md)]
 
 ## Related content
 
diff --git a/docs/includes/backup-restore-security-risk.md b/docs/includes/backup-restore-security-risk.md
@@ -0,0 +1,28 @@
+---
+author: MashaMSFT
+ms.author: mathoma
+ms.date: 12/05/2025
+ms.service: sql
+ms.topic: include
+---
+This section outlines the security risk associated with restoring backups from untrusted sources to any SQL Server environment, including on-premises, Azure SQL Managed Instance, SQL Server on Azure Virtual Machines (VMs) and any other environment.
+
+### Why this matters 
+
+Restoring SQL backup files (`.bak`) introduces a potential risk if the backup originates from an untrusted source. The security risk is exacerbated further when a SQL Server environment has multiple instances, as it amplifies the area of threat. While backups that remain within a trusted boundary pose no security issue, restoring a malicious backup can compromise the security of the entire environment.
+
+A malicious `.bak` file can: 
+- Take over the entire SQL Server instance.
+- Escalate privileges and gain unauthorized access to the underlying host or virtual machine.
+
+This attack occurs before any validating scripts or security checks can execute, which makes it extremely dangerous. Restoring an untrusted backup is equivalent to running untrusted applications on a critical server or virtual machine, and introducing arbitrary code execution into your environment. 
+
+### Best practices
+
+Follow these backup security best practices to reduce the threat to your SQL Server environments: 
+- Treat restoring backups as a high-risk operation.
+- Reduce the threat service area by using isolated instances.
+- Only allow trusted backups: never restore backups from unknown or external sources.
+- Only allow backups that have remained within a trusted boundary: ensure backups originate from within the trusted boundary.
+- Do not bypass security controls for convenience.
+- Enable [server-level auditing](/sql/t-sql/statements/create-server-audit-specification-transact-sql) to capture backup and restore events and mitigate audit evasion.
diff --git a/docs/relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases.md b/docs/relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases.md
@@ -3,10 +3,10 @@ title: "Back up and Restore of SQL Server Databases"
 description: This article describes the benefits of backing up SQL Server databases and introduces backup and restore strategies and security considerations.
 author: MashaMSFT
 ms.author: mathoma
-ms.date: 08/25/2025
+ms.date: 12/05/2025
 ms.service: sql
 ms.subservice: backup-restore
-ms.topic: conceptual
+ms.topic: article
 ms.update-cycle: 1825-days
 helpviewer_keywords:
   - "disaster recovery [SQL Server], see restoring [SQL Server]"
@@ -173,6 +173,10 @@ Use advanced features like `BACKUP CHECKSUM` to detect problems with the backup
 We recommend that you document your backup and restore procedures and keep a copy of the documentation in your run book.
 We also recommend that you maintain an operations manual for each database. This operations manual should document the location of the backups, backup device names (if any), and the amount of time that is required to restore the test backups.
 
+## Security risk of restoring backups from untrusted sources
+
+[!INCLUDE [backup-restore-security-risk](../../includes/backup-restore-security-risk.md)]
+
 ## Monitor progress with XEvent
 
 Backup and restore operations can take a considerable amount of time due to the size of a database and the complexity of the operations involved. When issues arise with either operation, you can use the `backup_restore_progress_trace` extended event to monitor progress live. For more information about extended events, see [Extended Events overview](../extended-events/extended-events.md).
diff --git a/docs/t-sql/statements/alter-database-transact-sql-set-options.md b/docs/t-sql/statements/alter-database-transact-sql-set-options.md
@@ -624,6 +624,9 @@ Controls the date_correlation_optimization option.
 
   [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] maintains correlation statistics where a FOREIGN KEY constraint links any two tables in the database and the tables have **datetime** columns.
 
+  Enabling `DATE_CORRELATION_OPTIMIZATION` increases the attack surface area when restoring [untrusted backup](../../relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases.md#security-risk-of-restoring-backups-from-untrusted-sources) as the optimizer executes those objects with elevated privileges.
+
+
 - OFF
 
   Correlation statistics aren't maintained.
