Files
Jonathan Boniface bc84ee4df6
Some checks failed
check agents / check (push) Failing after 13s
Solution architecture outcome pattern: agent and its MCP servers
The cp1-solution-architecture-agent and the sa-aws/azure/gcp-cloud MCP servers, a separate
stream from the individual and sub-agent patterns.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-05 22:13:25 +00:00

5.5 KiB

name, metadata, description
name metadata description
azure-waf-security
category
WellArchitectedFramework
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.

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.