Built a secure Azure environment focused on network segmentation, secure administrative access, and continuous security monitoring using Microsoft Defender for Cloud.
The project simulates common infrastructure misconfigurations and validates how Microsoft Defender for Cloud detects and reports security risks.
| Component | Configuration |
|---|---|
| Resource Group | rg-intern-sec-01 |
| Virtual Network | vnet-intern-sec-01 |
| Subnets | web, db, mgmt |
| Virtual Machine | vm-sec-mgmt01 |
| Operating System | Windows Server 2019 |
| VM Size | Standard B1s |
| Secure Access | Azure Bastion |
| Monitoring | Defender for Cloud Plan 2 |
- Network segmentation using dedicated subnets
- Bastion-only administrative access
- Removal of public IP exposure
- NSG-based traffic filtering
- Defender for Cloud security posture monitoring
- Microsoft Defender for Endpoint (MDE) auto-provisioning
| Scenario | Defender Response |
|---|---|
| RDP exposed to the internet | Security recommendation and alert generated |
| Windows Updates disabled | Missing patch recommendation detected |
The project includes Azure Bicep templates and PowerShell deployment automation.
bicep/
├── main.bicep
└── parameters.json
scripts/
└── deploy.ps1- Resource Group
- Virtual Network
- Subnets
- NSGs
- Virtual Machine
- Azure Bastion
The images/ folder includes:
- Azure Bastion access
- NSG configuration
- Defender for Cloud recommendations
- Security alerts and findings
Additional project documentation:
docs/implementation-guide.mddocs/findings-and-remediation.mddocs/troubleshooting.mddocs/lessons-learned.md
- Reduced external attack surface
- Secure administrative access through Azure Bastion
- Improved visibility into infrastructure security posture
- Continuous monitoring of cloud configuration risks
- Detection and remediation of insecure configurations
- Network segmentation improves workload isolation
- Removing direct RDP exposure significantly reduces risk
- Defender for Cloud provides valuable posture visibility
- NSG configuration plays a critical role in Azure security
- Infrastructure monitoring should be continuous and proactive
Completed — continuously expanding with additional security monitoring and hardening scenarios.



