SQL Server 2016 New Security Features

transcript

#SQLSAT454

Gianluca Sartori@spaghettidba

#SQLSAT454

Sponsors

#SQLSAT454

Gianluca Sartori Independent SQL Server consultant

SQL Server MVP, MCTS, MCITP, MCT

Works with SQL Server since version 7

DBA @ Scuderia Ferrari

Blog: spaghettidba.com Twitter: @spaghettidba

#SQLSAT454

Agenda Security Boundaries Always Encrypted Row Level Security Dynamic Data Masking

#SQLSAT454

Why New Security Features? SQL Server has plenty security features

TDE Protects database files and backups at rest

Cell-Level Encryption Encrypts single values in database tables

SSL Protects data on the network

#SQLSAT454

Security Boundaries – Open

Database

Developer DBA

Manager User

Software VendorUnauthorized

#SQLSAT454

Security Boundaries – Non Sensitive

Database

Developer

Manager User

Software Vendor

Unauthorized Users

#SQLSAT454

Security Boundaries – Sensitive

Database

Developer

Manager User

Software Vendor

Unauthorized Users

#SQLSAT454

ALWAYS ENCRYPTED

#SQLSAT454

Always Encrypted – Key FeaturesPrevents Data Disclosure End-to-end encryption of individual columns in a table with keys that are never given to the database system.

Queries on Encrypted DataSupport for equality comparison, incl. join, group by and distinct operators.

Application TransparencyMinimal application changes via server and client library enhancements.

#SQLSAT454

Always Encrypted Sensitive data is encrypted at column

level Data is protected from high-privileged

users DBAs System Admins Hackers

Data is stored securely outside security boundaries The database never sees unencrypted data

Cloud providers Third-parties

#SQLSAT454

Always Encrypted – How it worksApp

SELECT Name FROM Patients WHERE SSN=@SSN@SSN='198-33-0987'

Column Encryption

Jane Doe

Name1x7fg655se2e

SSNUSA

Country

Jim Gray 0x7ff654ae6d USA

John Smith 0y8fj754ea2c USA

dbo.Patients

Result Set

Jim Gray

Application - Trusted SQL Server - Untrusted

SELECT Name FROM Patients WHERE SSN=@SSN

@SSN=0x7ff654ae6d

EnhancedADO.NET

Library

SQL Server Native Client

.NET 4.6

Column

MasterKey

#SQLSAT454

Encryption Types Deterministic Encryption

Same plaintext value Same encrypted valueSupports indexing, equality comparison, JOINs, DISTINCT

Randomized EncryptionSame plaintext value Different encrypted valueSupports retrieval of encrypted dataNo SQL operations supported

#SQLSAT454

DEMOWorking with Always Encrypted

#SQLSAT454

TDE vs Always EncryptedAlways Encrypted TDEColumn level Database levelClient encryption Server encryptionServer doesn’t know encryption keys

Server knows encryption keys

Data in memory is encrypted

Data in memory is in plaintext

Data travels the network encrypted

Data travels the network in plaintext

#SQLSAT454

Custom encryption vs Always EncryptedAlways Encrypted Custom EncryptionSlight application changes

Needs obtrusive changes

Disallows saving plaintext data

Plaintext data can be saved by accident

Allows indexing of cyphertext *

* depending on encryption algorithm

#SQLSAT454

Always Encrypted - Limitations Deterministic encryption needs _BIN2

collation Not all datatypes supported Partial support for triggers Unsupported features:

Full-text search Replication Change Data Capture In-Memory OLTP Stretch Database

#SQLSAT454

What changes for Applications? ConnectionString must include new key:Column Encryption Setting=enabled;

Ad-hoc queries not supportedSELECT SomeColumn FROM SomeTable WHERE EncrypedColumn = 'SomeValue';

Needs correctly parameterized queriesSELECT SomeColumn FROM SomeTable WHERE EncrypedColumn = @param;

#SQLSAT454

Always Encrypted for Existing Data Existing columns must be encrypted client

side Easiest way: Import / Export wizard Ad-hoc wizard

In SSMS 2016?

#SQLSAT454

Performance Impact

#SQLSAT454

Space Usage Impact

#SQLSAT454

Questions?

#SQLSAT454

DYNAMIC DATA MASKING

#SQLSAT454

Dynamic Data Masking – Key FeaturesLimits Sensitive Data Exposure Sensitive data is masked.Administrators designate how much of the sensitive data to reveal.

Useful for ComplianceHelps adhering to privacy standards imposed by regulation authorities.

Application TransparencyNo application changes. Existing queries keep working.

#SQLSAT454

Dynamic Data Masking

Database

Non-Privileged User

Privileged User

Unmasked Data

Jane Doe

Name062-56-4651

SSN2.500

Salary

Jim Gray 915-12-9845 2.350

John Smith 354-21-9184 1.500

dbo.Employees062-56-4651SSN

Masked Data

XXX-XX-XXXX

#SQLSAT454

Dynamic Data Masking Obfuscates data using 3 masking functions

Default: depends on data type Email: aXXX.XXXX.com Partial: prefixXXXXXXsuffix

Data is stored unmasked Masking happens on resultset formation

GRANT UNMASK to disclose data

Works in Azure SQL Database (preview)

#SQLSAT454

Dynamic Data Masking - Limitations Not all datatypes supported Not intended as a complete protection feature

for sensitive data Ad-Hoc queries disclose data. Ex: WHERE Salary >

2000 INSERT…SELECT does not preserve masking Some quirks

Not suitable for handing out copies of the database to software vendors or third-parties

#SQLSAT454

DEMOWorking with Dynamic Data Masking

#SQLSAT454

Questions?

#SQLSAT454

ROW-LEVEL SECURITY

#SQLSAT454

Row Level Security – Key FeaturesFine-grained access control In multi-tenant databases, limits access by other users who share the same tables.

Centralized Security LogicPredicate-based access control logic resides inside the database and is schema-bound to the tables it protects.

Application TransparencyNo application changes. Existing queries keep working.

#SQLSAT454

Row-Level Security

LATAM Salesperson

EMEA Salesperson

Evil Inc.

NameEMEA

Area2.500

Budget

Wealthy Corp. LATAM 2.350

Greedy Corp. APAC 1.500

dbo.Customer

Manager

APAC Salesperson

#SQLSAT454

Row-Level Security - Concepts Predicate function

User-defined inline iTVF implementing access control logic.Can be arbitrarily complicated

Security predicateApplies a predicate function to a particular table (APPLY)Two types: filter predicates and blocking predicates

Security policyCollection of security predicates Manages security across multiple tables

#SQLSAT454

Row-Level Security – How it works

EMEA Salesperson

Evil Inc.

NameEMEA

Area2.500

Budget

Wealthy Corp. LATAM 2.350

Greedy Corp. APAC 1.500

dbo.Customer

Security Policy

SELECT *FROM Customer

SELECT *FROM CustomerAPPLY itvf_securityPredicate()

#SQLSAT454

DEMOWorking with Row-Level Security

#SQLSAT454

Row-Level Security - Limitations SCHEMABINDING: all tables in the predicate

function must reside in the database Performance impact: queries are rewritten When authenticating the application,

CONTEXT_INFO() can be used to filter on real user

Not really secure if users can run ad-hoc queries

Don’t lock out the DBA!

#SQLSAT454

Questions?

#SQLSAT454

ResourcesAlways Encrypted on MSDNGetting Started With Always EncryptedPerformance impact of Always Encrypted

Dynamic Data Masking on MSDNUsing Dynamic Data Masking

Row-Level Security on MSDNIntroduction to Row-Level SecurityRow-Level Security Limitations

#SQLSAT454

Evaluations Don’t forget to compile evaluations

form here http://speakerscore.com/sqlsat454

#SQLSAT454

THANKS!

#sqlsat454

SQL Server 2016 New Security Features

Technology