--- name: azure-waf-security metadata: category: WellArchitectedFramework description: >- Generates security guidance for Azure workloads based on the Security pillar of the Azure Well-Architected Framework and the Zero Trust model. Use when evaluating workloads, identifying security requirements, and recommending identity, network, data protection, secrets and security operations controls. --- # Azure Well-Architected Framework skill for the Security pillar ## Overview The Security pillar protects the confidentiality, integrity and availability of a workload, aligned with Zero Trust: verify explicitly, use least privilege, and assume breach. Segmentation, identity and encryption are decided in the design, and threat detection and response are planned before the workload runs. ## Core principles The recommendations below follow the published framework. Written for this agent from Microsoft's published design review checklist. Codes are Microsoft's. - **Establish a security baseline** (SE:01): Align to compliance requirements, industry standards and platform recommendations, and measure against it regularly. Grounding document: https://learn.microsoft.com/azure/well-architected/security/establish-baseline - **Secure the development lifecycle** (SE:02): Build security into design, coding, build and release. Grounding document: https://learn.microsoft.com/azure/well-architected/security/secure-development-lifecycle - **Classify data** (SE:03): Label data and the systems that process it, and let classification drive the design. Grounding document: https://learn.microsoft.com/azure/well-architected/security/data-classification - **Segment deliberately** (SE:04): Create perimeters across networks, roles, workload identities and resource organization. Grounding document: https://learn.microsoft.com/azure/well-architected/security/segmentation - **Control identity and access** (SE:05): Make access strict, conditional and auditable for users, operators and components, granting only what is necessary. Grounding document: https://learn.microsoft.com/azure/well-architected/security/identity-access - **Control network traffic** (SE:06): Isolate and filter ingress and egress, east-west and north-south, with defense in depth. Grounding document: https://learn.microsoft.com/azure/well-architected/security/networking - **Encrypt data** (SE:07): Use modern standard methods scoped to classification, preferring platform encryption. Grounding document: https://learn.microsoft.com/azure/well-architected/security/encryption - **Harden resources** (SE:08): Reduce surface area and tighten configuration to raise an attacker's cost. Grounding document: https://learn.microsoft.com/azure/well-architected/security/harden-resources - **Protect secrets** (SE:09): Harden storage, restrict and audit access, and rotate regularly, with an emergency path. Grounding document: https://learn.microsoft.com/azure/well-architected/security/application-secrets - **Monitor for threats** (SE:10): Use platform-integrated detection that alerts and feeds security operations. Grounding document: https://learn.microsoft.com/azure/well-architected/security/monitor-threats - **Test security** (SE:11): Combine prevention, validation of controls and tests of detection. Grounding document: https://learn.microsoft.com/azure/well-architected/security/test - **Prepare incident response** (SE:12): Define and rehearse procedures for localized issues through to disaster recovery, with named owners. Grounding document: https://learn.microsoft.com/azure/well-architected/security/incident-response ## Relevant products The following are _examples_ of products relevant to this pillar: - **Identity**: Microsoft Entra ID, managed identities, Azure RBAC, Privileged Identity Management, Conditional Access - **Network**: Virtual networks, network security groups, Azure Firewall, Private Link, Azure DDoS Protection, Web Application Firewall - **Data**: Azure Key Vault, Managed HSM, customer-managed keys, Microsoft Purview - **Detection**: Microsoft Defender for Cloud, Microsoft Sentinel - **Governance**: Azure Policy, management groups ## Workload assessment questions Ask appropriate questions to understand the requirements and constraints of the workload and the organization. Choose from this list: - Which compliance frameworks and data residency rules apply? - How is data classified, and where is the most sensitive data? - Who needs access, how do they authenticate, and how is privileged access controlled? - How do workload identities authenticate, and are any long-lived secrets in use? - What is exposed to the internet, and how is egress controlled? - Who manages encryption keys, and how are they rotated? - How are threats detected, and who responds? - How is the software supply chain secured? ## Validation checklist Use this checklist to evaluate the architecture against this pillar: - A security baseline is named and measured against. - Data is classified, and the classification drives controls. - Workload identities are managed identities where the service supports them. - Role assignments follow least privilege at the narrowest scope. - Public endpoints are justified, and PaaS services use Private Link where needed. - Ingress and egress are filtered and logged. - Data is encrypted at rest and in transit, and key ownership is stated. - Secrets are held in Key Vault, with rotation. - Defender for Cloud and central logging cover the workload. - Incident response has named owners and is rehearsed.