Keeping Sensitive Data Secure with Always Encrypted

Play Keeping Sensitive Data Secure with Always Encrypted
Sign in to queue


Most data breaches involve the theft of critical data such as credit card numbers or personally identifiable information. In this Data Driven session, you'll find out how Always Encrypted in SQL Server 2016 helps protect such sensitive data inside a database.



Right click to download this episode

Download captions

The Discussion

  • User profile image

    Thanks for the video Jakub!

    Great demo, good to know the high-level difference between encryption types - Deterministic v Randomised.

    Would be good to know which SQL Server versions this is available, Azure SQL too?

    What kind of security compliance regulations would drive this - PCI comes to mind, anything else?

    Is there a considerable performance hit? Just decrypting the data or it affects query performance too?

    If you want [for whatever reason] to get plain-text in SSMS - is there a way to do that?


  • User profile image

    Excellent video. Very clear, concise but yet explain essential information of the technology. Well done!

  • User profile image
    Davide Spano

    Great video.


  • User profile image

    Great video! Thanks!

  • User profile image
    thank u
  • User profile image

    Hi, Thanks a lot for your video and so so well explained it

  • User profile image

    Hello Jakub I am so tentative to decide to use this awesome tool, however I have a question, I'm working on a project with SQL Server 2017 - 14 Express Edition. And I'm pretty sure they aren't going to buy the Enterprise Edition.

    Even so, Can I use this tool? Or is there any limitation related to the final version of SQL?

    Thanks a lot.

  • User profile image

    Great video!

    What client side actions are needed to provide access to the encryption certificates?

    Can multiple master keys be applied to a single column? This is to provide custom access levels for different sets of columns. i.e. column_key_1 is in master_key_1, master_key_2; or column has column_key_1, column_key_2 applied to it, each in separate master keys?

Add Your 2 Cents