| title | SQL Server encryption | |||
|---|---|---|---|---|
| description | Use these resources to understand how SQL Server uses encryption to enhance security for your databases. | |||
| author | jaszymas | |||
| ms.author | jaszymas | |||
| ms.reviewer | vanto, randolphwest | |||
| ms.date | 09/16/2024 | |||
| ms.service | sql | |||
| ms.subservice | security | |||
| ms.topic | concept-article | |||
| ms.custom |
|
|||
| helpviewer_keywords |
|
|||
| monikerRange | =azuresqldb-current || >=sql-server-2016 || >=sql-server-linux-2017 || =azuresqldb-mi-current || =fabric-sqldb |
[!INCLUDE SQL Server Azure SQL Database Azure SQL Managed Instance FabricSQLDB]
Encryption is the process of obfuscating data by the use of a key or password. This process can make the data useless without the corresponding decryption key or password. Encryption doesn't solve access control problems. However, it enhances security by limiting data loss even if access controls are bypassed. For example, if the database host computer is misconfigured and a hacker obtains sensitive data, that stolen information might be useless if it's encrypted.
Although encryption is a valuable tool to help ensure security, it shouldn't be considered for all data or connections. When you're deciding whether to implement encryption, consider how users access data. If users access data over a public network, data encryption might be required to increase security. However, if all access involves a secure intranet configuration, encryption might not be required. Any use of encryption should also include a maintenance strategy for passwords, keys, and certificates.
Note
The latest information about Transport Level Security (TLS 1.2) is available at TLS 1.2 support for Microsoft SQL Server. For more information about TLS 1.3, see TLS 1.3 support.
You can use encryption in [!INCLUDE ssNoVersion] for connections, data, and stored procedures. The following articles contain more information about encryption in [!INCLUDE ssNoVersion].
-
Information about the encryption hierarchy in [!INCLUDE ssNoVersion].
-
Choose an encryption algorithm
Information about how to select an effective encrypting algorithm.
-
Transparent data encryption (TDE)
General information about how to encrypt data at rest.
-
SQL Server and Database Encryption Keys (Database Engine)
In [!INCLUDE ssNoVersion], encryption keys include a combination of public, private, and symmetric keys that are used to protect sensitive data. This section explains how to implement and manage encryption keys.
-
Ensure on-premises database administrators, cloud database operators, or other high-privileged, but unauthorized users, can't access the encrypted data. Expand Always Encrypted with Always Encrypted with secure enclaves to enable in-place encryption and richer confidential queries.
-
Limit sensitive data exposure by masking it to nonprivileged users.
-
SQL Server Certificates and Asymmetric Keys
Information about using Public Key Cryptography.
- Securing SQL Server
- An overview of Azure SQL Database security capabilities
- Cryptographic functions (Transact-SQL)
- ENCRYPTBYPASSPHRASE (Transact-SQL)
- ENCRYPTBYKEY (Transact-SQL)
- ENCRYPTBYASYMKEY (Transact-SQL)
- ENCRYPTBYCERT (Transact-SQL)
- sys.key_encryptions (Transact-SQL)
- SQL Server and Database Encryption Keys (Database Engine)
- Back up and restore SQL Server Reporting Services (SSRS) encryption keys
- Configure SQL Server Database Engine for encrypting connections
- Microsoft TechNet: SQL Server TechCenter: SQL Server 2012 Security and Protection