Auditing in Azure Sql Data Warehouse First article in a series on “Security Intelligence in Azure PaaS” inspired me to write about auditing in Azure Sql Data Warehouse. Auditing to put it simply for person new to GRC (which stands for Governance, Risk Management, Compliance) is just like logging, but in expensive suite and a tie. Business tends to understand its purpose, requirements and is aware of attached price tag. Azure Sql Data Warehouse is relatively new MPP (after Massively Parallel Processing architecture) database offering based on Parallel Data Warehouse with generation 2 (optimised compute) generally available.
Taking opportunity just before #MSBuild2018 kicks off here is my wishlist for security improvements that I’d like to see in Azure: Azure Sql Managed Instance GA announcement Azure Sql Auditing native support in Log Analytics VNET service endpoints support for hybrid scenarios VNET service endpoints support for multi-region servers Azure Sql DB/DW native VNET support Azure Sql Datawarehouse Always Encrypted Soft-Delete support in portal for Key Vault Always Encrypted Secure Enclaves Azure Confidential Computing Practical use cases for blockchain in context of InfoSec and of course - Quantum Commuting which always goes up to 11.
Long awaited version of SSMS 17.4 was released few days ago and with it - new shiny Vulnerability Assessment. I decided to include it in my Autonomous Databases presentation and spend some time with it. Definitely useful but … Disappearing checks - high risk My first VA scan contained 52 tests results which is 12 more than in Azure Sql DB version (changed from 39 to 40 recently). Next scan that I run for different database showed just 50 tests - number mysteriously decreased by 2.