How to automate network security for your Azure functions
summary
Shows an automated system that keeps Azure Functions network-restricted by using Azure Event Grid to detect function creation/scale, Azure Resource Graph to read outbound IP ranges, and Cosmos DB to store a dependency graph; a central dotnet Azure function generates and applies access-restriction rules via the Azure REST API. Demonstrations include an Azure CLI deploy script, local debugging with ngrok, and hitting the 512-rule limit and changing consumption-plan IP ranges as real problems. Prototype runs but needs cleanup logic for deletions and rule pruning.
AI-written summary · about
chapters (30)
- 0:00Introduction
- 1:16About me
- 2:25Who we are
- 3:27Platform
- 5:54Azure Functions
- 7:15Why access restriction
- 8:15Demo
- 11:50Ecosystem
- 12:43Scaling
- 14:23Solution
- 15:43IP Range
- 16:11What do we need
- 17:13The selected technologies
- 17:41Azure Event Grid
- 21:13Azure System Topics
- 24:39Subject
- 25:24Visual Studio
- 27:30Debugging
- 27:50Postman
- 29:25Copy URL
- 29:50Confirm Selection
- 30:55Demos
- 32:44Azure Resource Graph
- 36:00Properties
- 37:46Complexities
- 41:15Solution Overview
- 42:54Conclusion
- 44:01Extras
- 44:35Access Restrictions
- 44:55Thank you
related talks
48mAutomate(d) security with Azure Security Center
01h 04mProtect Your Applications with Azure WAF and Application Gateway
28mSecure your cloud automation
01h 01mDos and Don'ts for Serverless and Azure Functions
47mWorking with data using Azure Functions
47mSecuring Serverless Applications in Azure
56mEnter the Matrix: Securing Azure’s Assets
42mServer-less compute with .NET based Azure Functions