Building a secure data solution using Azure Data Lake
summary
Azure Data Lake Gen2 is used as a secure, scalable file-system layer on top of Blob storage with hierarchical namespace and POSIX-style ACLs, enabling folder-level permissions and a data taxonomy. Demo shows an Azure Function using a managed identity granted read/execute on one folder and denied on another, proving folder ACL enforcement. Uses the multi-protocol Blob SDK plus the Data Lake SDK, supports atomic rename for safe big-data writes, encryption at rest/in transit, monitoring and immutable blobs.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 2:59Blob Storage Updates
- 7:04Performance
- 8:48Reliability
- 10:33Scalability
- 11:48Isolation of data
- 12:00Interoperability
- 14:30Cost
- 16:09Azure Active Directory
- 17:47Security Principles
- 18:13Service Principles
- 19:20Managed Identity
- 21:41Security best practices
- 26:58Encryption
- 28:14Data Taxonomy
- 29:21Advanced Threat Detection
- 31:49In practice
related talks
51mDesigning Data Architectures that InfoSec will actually approve
24mSecure and Efficient Data Sharing with Federated Cloud Storage
48mProtecting the confidentiality and integrity of your high value data with Azure SQL and SQL Server 2
31mBuilding Big Data Platforms: the Hidden Security Flaws You Need to Be Aware Of
32mDesigning secure Azure SQL Database solutions
16mSecure data processing with AMD Confidential VMs on Azure Databricks
48mFabric security: everything you need to know!
40mUnderstanding the cryptographic controls in Azure SQL Database