Why Compliance Matters
Organizations don’t just want security; they must also prove compliance with industry and regional regulations. Azure provides compliance certifications and tooling to help architects align cloud designs with standards like ISO 27001, HIPAA, PCI DSS, GDPR, and NIST.
For the AZ-305 exam, expect scenario-based questions where a business requirement maps to a compliance-driven solution (e.g., healthcare → HIPAA, payments → PCI DSS).
1. Key Compliance Frameworks
-
ISO 27001 / 27018
-
General international security standard.
-
Covers information security management systems (ISMS).
-
Azure services are certified under ISO 27001.
-
-
HIPAA (Health Insurance Portability and Accountability Act)
-
US healthcare compliance standard.
-
Requires data confidentiality, encryption, auditing.
-
Use cases: patient data, EMRs, healthcare SaaS.
-
-
PCI DSS (Payment Card Industry Data Security Standard)
-
For credit card data handling.
-
Requires encryption, monitoring, and strict access controls.
-
Use cases: e-commerce, banking apps.
-
-
GDPR (General Data Protection Regulation)
-
EU regulation for personal data.
-
Requires explicit consent, data residency, right to erasure.
-
Use cases: any app processing EU citizen data.
-
-
NIST Cybersecurity Framework (CSF)
-
US government framework.
-
Covers identify, protect, detect, respond, recover.
-
Many US federal and defense contractors follow this.
-
2. Azure Tools Supporting Compliance
-
Microsoft Defender for Cloud → Regulatory Compliance Dashboard.
-
Azure Policy → enforce compliance at resource level (e.g., only deploy in EU).
-
Azure Blueprints → prepackaged templates for compliance standards.
-
Key Vault (CMK) → meet encryption requirements for PCI, HIPAA.
-
Sentinel + Defender Integration → detect and respond to compliance violations.
3. Example Enterprise Scenarios
Scenario 1 – Healthcare SaaS
Requirement: Must comply with HIPAA.
Design: Enable TDE + Always Encrypted, store keys in Key Vault, enforce Azure Policy for auditing.
Scenario 2 – Online Retail
Requirement: Must comply with PCI DSS for payments.
Design: Use NSGs, Firewalls, APIM policies, encrypt with CMK, enable Defender for Cloud PCI DSS blueprint.
Scenario 3 – European Startup
Requirement: GDPR compliance for EU data.
Design: Use region pairs within EU, restrict deployment to EU-only regions, enable Azure Policy for residency, implement user consent + right to erasure logic in app.
4. Confusion Buster
-
Azure Policy vs Blueprints
-
Policy = enforce specific rules (e.g., tagging, allowed regions).
-
Blueprints = bundle policies + RBAC + templates for compliance frameworks.
-
-
Defender for Cloud vs Sentinel
-
Defender = compliance posture monitoring.
-
Sentinel = SIEM for real-time detection.
-
-
GDPR vs HIPAA
-
GDPR = general privacy law for EU.
-
HIPAA = specific healthcare law in US.
-
5. Exam Tips
-
“Which Azure service provides regulatory compliance dashboard?” → Defender for Cloud.
-
“Which framework applies to EU personal data privacy?” → GDPR.
-
“Which framework applies to payment card transactions?” → PCI DSS.
-
“Which tool provides prepackaged compliance templates?” → Azure Blueprints.
-
“Which compliance requirement applies to healthcare in the US?” → HIPAA.
6. What to Expect in the Exam
-
Direct Q: “Which Azure service helps enforce compliance by restricting deployments to specific regions?” → Azure Policy.
-
Scenario Q: “Banking app requires PCI DSS compliance and encryption with customer-managed keys.” → Key Vault + CMK + Defender for Cloud PCI blueprint.
-
Scenario Q: “Healthcare provider requires DB encryption and restricted admin access for HIPAA compliance.” → TDE, Always Encrypted, PIM.
-
Scenario Q: “EU startup requires personal data stored only in Europe.” → Azure Policy + EU-only regions.
-
Trick Q: “Sentinel provides compliance dashboards for HIPAA/PCI.” → False (Defender for Cloud does).