Azure Security Lab
Security-by-design lab in Azure using Terraform, network segmentation, Entra ID and RBAC, managed identities, Key Vault, and private PostgreSQL configuration. Work in progress, with a locally tested API for monitoring events and CrowdStrike integration planned.
- Focus
- Cloud infrastructure
- Scope
- in progress
- Source
- Public repository
The purpose
Explore security by design in Azure: define infrastructure with Terraform, apply identity and network controls, and prepare application events for security monitoring.
How it fits together
- 01
Terraform configuration
- 02
Separate backend and database subnets / NSGs
- 03
App Service configuration / managed identity / Key Vault reference
- 04
Private PostgreSQL configuration / private DNS / Entra authentication
Engineering choices
Define infrastructure in code
Terraform captures the network and workload configuration so the intended environment can be reviewed before deployment.
Control network and identity boundaries
Separate subnets and network security groups control traffic. The workload configuration uses managed identity, a Key Vault secret reference, and private database connectivity.
Keep deployment costs explicit
App Service and PostgreSQL remain disabled through deploy_workloads=false to preserve Azure credits while the API is tested locally.
What the project documents
The README documents Terraform network configuration and a locally tested API for authentication and request events.
Azure UI screenshots accompany earlier Entra ID, RBAC, RBAC-change alerting, and public-IP policy exercises. Those exercises are outside the current Terraform code.
Current scope & limitations
In progress. Database connectivity and Key Vault permissions still need work. CrowdStrike is not connected; event ingestion and detection testing are planned once trial access is available. Configured workloads should not be read as a fully deployed environment.