Introduction and Overview
Track Data Changes
The course is part of this learning path
In the Information age data is the new currency and like anything valuable, it needs to be protected. Azure SQL and its environment provide a range of mechanisms for protecting your data from a multitude of hazards. The potential threats range from bad actors trying to steal information to unintentional human error corrupting your data. To cover all eventualities Azure provides pre-emptive protection in the form of network security, several types of data encryption, data classification, and vulnerability assessment services. After the fact protection is available in the form of built-in data change tracking. This course shows not only tells you about what protection is available for your database but also how to implement it.
If you have any feedback relating to this course, feel free to contact us at firstname.lastname@example.org.
- Learn what security components are available within Azure SQL
- Understand how these elements work together to provide a secure environment
- Learn how to implement infrastructure security
- Learn how to secure your data from external and internal hazards
- Learn how to implement data change tracking
- Anyone who wants to learn how to implement secure Azure SQL databases
- Those preparing for Microsoft’s DP-300 exam
To get the most out of this course, you have should a general understanding of the fundamentals of Microsoft Azure. Experience using databases — especially SQL Server — would also be beneficial.
The GitHub repository for this course can be found here: https://github.com/cloudacademy/azure-sql-data-security-dp-300
Because you don’t have access to the hard drive with Azure SQL and SQL managed instance, encryption is implemented at the database page level. Transparent data encryption is the process of encrypting and decrypting database pages when written to and read from long-term storage, i.e. the disk in real-time. All Azure SQL and SQL managed instance databases use transparent data encryption TDE, by default. Unless specified otherwise they use a service managed key. For Azure SQL the key is set at the server level, and for SQL managed instance it is set at the server instance level. You can change the service managed key to a customer-managed key in a process very similar to that we have just seen for an encrypted disk key. If you go into the server and under security go into transparent data encryption you can set the customer-managed keys there. You can either select your key from a vault or enter the URL to your key. Here I have selected the same disk encryption key as I previously used. In this case, Azure will automatically grant the appropriate permissions for your key. If we go back to the key vault and look under access policies, we can see the newly added DB monitor policy, which has the same get, wrap key, and unwrap key permissions as we saw for myDiskEncryptSet.
Hallam is a software architect with over 20 years experience across a wide range of industries. He began his software career as a Delphi/Interbase disciple but changed his allegiance to Microsoft with its deep and broad ecosystem. While Hallam has designed and crafted custom software utilizing web, mobile and desktop technologies, good quality reliable data is the key to a successful solution. The challenge of quickly turning data into useful information for digestion by humans and machines has led Hallam to specialize in database design and process automation. Showing customers how leverage new technology to change and improve their business processes is one of the key drivers keeping Hallam coming back to the keyboard.