I’m still learning about Azure SQL Data Warehouse (ADW, cause I’m lazy). ADW is a deceptively deep topic. Initially, you think that it’s just SQL Server, what’s the big deal. Then you start to understand the underlying architecture and things get complicated. Then you begin to understand the implications of the architecture and things get downright arcane. However, I’d like to talk about some relatively easy concepts around security in your Azure SQL Data Warehouse. For lots more detail, see the excellent documentation provided by Microsoft.
The single most important aspect of security in and around Azure is the fact that for the public facing aspects (and the database stuff is public facing), there is a built-in firewall. This firewall is enabled by default and actually can’t be disabled, although you can choose to completely bypass it (why you would choose this is beyond me, but you can choose to eat lead paint too, so….).
Let’s say that someone knew that you had an Azure SQL Server (the container for both Azure SQL Database (ADB, lazy again) and ADW, not to be confused with an instance of the SQL Server boxed product) out there named “securitytestdw.” If they knew anything about Azure, they’d know that the string to connect to this is “securitytestdw.database.windows.net” which gives them an attack vector of sorts. However, with a hole in the firewall, the best they get is an error stating “Your client IP address does not have access to the server.” In short, they’re not getting in if you haven’t allowed for their IP address.
Now, can you shoot yourself in the foot and expose your server to all IP addresses? Yes.
However, you’d have to intentionally do this. Don’t. Then you avoid the problem.
You have two core choices on logins. First, you have to create a SQL login at the server level for both Azure SQL Database and Azure SQL Data Warehouse. You can’t remove this or disable it (to my knowledge, and I’ve tried), so make the password a good one (and don’t lose it). You can then create other SQL logins, but this is not a recommended best practice. In fact, I wouldn’t do it at all unless I was forced because of some third party product (few of which currently support Azure anyway).
The next choice, the preferred choice, is to set up Azure Active Directory. With Azure AD you get all the functionality you’re used to with your local AD. Further, you can federate Azure AD with your local AD to control and manage the logins from within your network. You also get multi-factor authentication with Azure AD. We are talking real security here. Read through the documentation on setting up authentication to get it right. You can do the whole thing using Powershell commands, so there’s no excuse on automating it.
Auditing and Threat Detection are services that you pay for. They’re off by default. You can set them for the server or for individual databases. You’ll have to add storage for the audit logs. The threat detection looks for SQL injection and SQL injection vectors are anomalous client logins. Remember, if you set this for a server, it includes all the databases under by default. You can change the databases individually through Powershell, or here in the GUI:
The basics of security within Azure SQL Data Warehouse are pretty clear and easy to understand. Leave that default firewall in place and only poke the holes through it that you actually need to, and you’ll be fine. Get Azure Active Directory set up so that you can use that (along with multi-factor authentication) to completely lock things down. Finally, you can pay for the audit and threat detection. With all these options, you can secure your Azure SQL Data Warehouse properly.