Skip to content

securing-sql-server.md

Latest commit

 

History

History
165 lines (127 loc) · 15.5 KB

securing-sql-server.md

File metadata and controls

165 lines (127 loc) · 15.5 KB
title Securing SQL Server | Microsoft Docs
description Use these articles to create and implement an effective security plan in SQL Server. Learn about the platform, authentication, objects, and applications.
ms.custom
ms.date 06/21/2019
ms.prod sql
ms.prod_service security
ms.reviewer
ms.technology security
ms.topic conceptual
f1_keywords
Security [SQL Server]
helpviewer_keywords
database objects [SQL Server], security
SQL Server, security
operating systems [SQL Server], security
security [SQL Server], planning
applications [SQL Server], security
ms.assetid 4d93489e-e9bb-45b3-8354-21f58209965d
author VanMSFT
ms.author vanto

Securing SQL Server

[!INCLUDE SQL Server]

Securing [!INCLUDEssNoVersion] can be viewed as a series of steps, involving four areas: the platform, authentication, objects (including data), and applications that access the system. The following topics will guide you through creating and implementing an effective security plan.

You can find more information about [!INCLUDEssNoVersion] security at the SQL Server Web site. This includes a best practice guide and a security checklist. This site also contains the latest service pack information and downloads.

Platform and Network Security

The platform for [!INCLUDEssNoVersion] includes the physical hardware and networking systems connecting clients to the database servers, and the binary files that are used to process database requests.

Physical Security

Best practices for physical security strictly limit access to the physical server and hardware components. For example, use locked rooms with restricted access for the database server hardware and networking devices. In addition, limit access to backup media by storing it at a secure offsite location.

Implementing physical network security starts with keeping unauthorized users off the network. The following table contains more information about networking security information.

For information about See
[!INCLUDEssEW] and network access to other [!INCLUDEssNoVersion] editions "Configuring and Securing the Server Environment" in [!INCLUDEssEW] Books Online
   

Operating System Security

Operating system service packs and upgrades include important security enhancements. Apply all updates and upgrades to the operating system after you test them with the database applications.

Firewalls also provide effective ways to implement security. Logically, a firewall is a separator or restrictor of network traffic, which can be configured to enforce your organization's data security policy. If you use a firewall, you will increase security at the operating system level by providing a chokepoint where your security measures can be focused. The following table contains more information about how to use a firewall with [!INCLUDEssNoVersion].

For information about See
Configuring a firewall to work with [!INCLUDEssNoVersion] Configure a Windows Firewall for Database Engine Access
Configuring a firewall to work with [!INCLUDEssISnoversion] Integration Services Service (SSIS Service)
Configuring a firewall to work with [!INCLUDEssASnoversion] Configure the Windows Firewall to Allow Analysis Services Access
Opening specific ports on a firewall to enable access to [!INCLUDEssNoVersion] Configure the Windows Firewall to Allow SQL Server Access
Configuring support for Extended Protection for Authentication by using channel binding and service binding Connect to the Database Engine Using Extended Protection
   

Surface area reduction is a security measure that involves stopping or disabling unused components. Surface area reduction helps improve security by providing fewer avenues for potential attacks on a system. The key to limiting the surface area of [!INCLUDEssNoVersion] includes running required services that have "least privilege" by granting services and users only the appropriate rights. The following table contains more information about services and system access.

For information about See
Services required for [!INCLUDEssNoVersion] Configure Windows Service Accounts and Permissions
   

If your [!INCLUDEssNoVersion] system uses Internet Information Services (IIS), additional steps are required to help secure the surface of the platform. The following table contains information about [!INCLUDEssNoVersion] and Internet Information Services.

For information about See
IIS security with [!INCLUDEssEW] "IIS Security" in [!INCLUDEssEW] Books Online
[!INCLUDEssRSnoversion] Authentication Authentication in Reporting Services
[!INCLUDEssEW] and IIS access "Internet Information Services Security Flowchart" in [!INCLUDEssEW] Books Online
   

SQL Server Operating System Files Security

[!INCLUDEssNoVersion] uses operating system files for operation and data storage. Best practices for file security requires that you restrict access to these files. The following table contains information about these files.

For information about See
[!INCLUDEssNoVersion] program files File Locations for Default and Named Instances of SQL Server
   

[!INCLUDEssNoVersion] service packs and upgrades provide enhanced security. To determine the latest available service pack available for [!INCLUDEssNoVersion], see the SQL Server Web site.

You can use the following script to determine the service pack installed on the system.

SELECT CONVERT(char(20), SERVERPROPERTY('productlevel'));

Principals and Database Object Security

Principals are the individuals, groups, and processes granted access to [!INCLUDEssNoVersion]. "Securables" are the server, database, and objects the database contains. Each has a set of permissions that can be configured to help reduce the [!INCLUDEssNoVersion] surface area. The following table contains information about principals and securables.

For information about See
Server and database users, roles, and processes Principals (Database Engine)
Server and database objects security Securables
The [!INCLUDEssNoVersion] security hierarchy Permissions Hierarchy (Database Engine)
   

Encryption and Certificates

Encryption does not solve access control problems. However, it enhances security by limiting data loss even in the rare occurrence that access controls are bypassed. For example, if the database host computer is misconfigured and a malicious user obtains sensitive data, such as credit card numbers, that stolen information might be useless if it is encrypted. The following table contains more information about encryption in [!INCLUDEssNoVersion].

For information about See
The encryption hierarchy in [!INCLUDEssNoVersion] Encryption Hierarchy
Implementing secure connections Enable Encrypted Connections to the Database Engine (SQL Server Configuration Manager)
Encryption functions Cryptographic Functions (Transact-SQL)

Certificates are software "keys" shared between two servers that enable secure communications by way of strong authentication. You can create and use certificates in [!INCLUDEssNoVersion] to enhance object and connection security. The following table contains information about how to use certificates with [!INCLUDEssNoVersion].

For information about See
Creating a certificate for use by [!INCLUDEssNoVersion] CREATE CERTIFICATE (Transact-SQL)
Using a certificate with database mirroring Use Certificates for a Database Mirroring Endpoint (Transact-SQL)
   

Application Security

Client programs

[!INCLUDEssNoVersion] security best practices include writing secure client applications. For more information about how to help secure client applications at the networking layer, see Client Network Configuration.

Windows Defender Application Control (WDAC)

Windows Defender Application Control (WDAC) prevents unauthorized code execution. WDAC is effective way to mitigate the threat of executable file-based malware. For more information, see to Windows Defender Application Control documentation.

SQL Server Security Tools, Utilities, Views, and Functions

[!INCLUDEssNoVersion] provides tools, utilities, views, and functions that can be used to configure and administer security.

SQL Server Security Tools and Utilities

The following table contains information about [!INCLUDEssNoVersion] tools and utilities that you can use to configure and administer security.

For information about See
Connecting to, configuring, and controlling [!INCLUDEssNoVersion] Use SQL Server Management Studio
Connecting to [!INCLUDEssNoVersion] and running queries at the command prompt sqlcmd Utility
Network configuration and control for [!INCLUDEssNoVersion] SQL Server Configuration Manager
Enabling and disabling features by using Policy-Based Management Administer Servers by Using Policy-Based Management
Manipulating symmetric keys for a report server rskeymgmt Utility (SSRS)
   

SQL Server Security Catalog Views and Functions

The [!INCLUDEssDE] exposes security information in several views and functions that are optimized for performance and utility. The following table contains information about security views and functions.

For information about See
[!INCLUDEssNoVersion] security catalog views, which return information about database-level and server-level permissions, principals, roles, and so on. In addition, there are catalog views that provide information about encryption keys, certificates, and credentials. Security Catalog Views (Transact-SQL)
[!INCLUDEssNoVersion] security functions, which return information about the current user, permissions and schemas. Security Functions (Transact-SQL)
[!INCLUDEssNoVersion] security dynamic management views. Security-Related Dynamic Management Views and Functions (Transact-SQL)
   

Related Content

Security Considerations for a SQL Server Installation
Security Center for SQL Server Database Engine and Azure SQL Database
SQL Server 2012 Security Best Practices - Operational and Administrative Tasks
SQL Server Security Blog
Security Best Practice and Label Security Whitepapers
Row-Level Security
Protecting Your SQL Server Intellectual Property