feat(compliance): add MITRE D3FEND Azure compliance mapping

[s1ns3nz0]

Context

MITRE D3FEND is a knowledge graph of cybersecurity countermeasure techniques — the defensive counterpart to MITRE ATT&CK. While Prowler already maps ATT&CK offensive techniques, this PR adds D3FEND to map Azure checks to defensive countermeasures.

Related to #10801 (Shin-723's D3FEND MVP with 4 techniques). This PR expands coverage to 18 techniques across 5 D3FEND tactics, mapping 164 of 167 Azure checks (98.2%).

Co-authored with @Shin-723.

Description

Adds prowler/compliance/azure/mitre_d3fend_azure.json with 18 D3FEND techniques:

Tactic	Techniques	Checks
Harden (7)	MFA, Credential Rotation, Disk/File/Message Encryption, Software Update, App Config Hardening	52
Detect (4)	Platform Monitoring, Network Traffic Analysis, OS Monitoring, User Behavior Analysis	51
Isolate (5)	Inbound Traffic Filtering, Network Isolation, User Account Permissions, Executable Allowlisting, Encrypted Tunnels	45
Model (1)	Asset Vulnerability Enumeration	10
Restore (1)	Restore Object	7

All technique IDs and descriptions validated against the official D3FEND ontology at https://d3fend.mitre.org/.

Uses Generic_Compliance_Requirement_Attribute model — no code changes needed beyond the JSON file and tests.

Tests adapted from #10801:

• test_load_mitre_d3fend_azure_framework — validates framework loading with 18 techniques
• test_get_check_compliance_azure_mitre_d3fend — validates compliance output engine

Steps to review

1. Review prowler/compliance/azure/mitre_d3fend_azure.json for technique-to-check mapping accuracy
2. Verify technique IDs at https://d3fend.mitre.org/technique/d3f:{TechniqueName}
3. Run python3 -m pytest tests/lib/check/compliance_check_test.py tests/lib/outputs/compliance/compliance_test.py -v
4. Run python3 -m prowler azure --az-cli-auth --compliance mitre_d3fend_azure --verbose

Checklist

• Review if the code is being covered by tests.
• Review if code is being documented following this specification https://github.com/google/styleguide/blob/gh-pages/pyguide.md#38-comments-and-docstrings
• Review if backport is needed.
• Review if is needed to change the Readme.md
• Ensure new entries are added to CHANGELOG.md, if applicable.

SDK/CLI

• Are there new checks included in this PR? No — this PR only adds a compliance framework JSON and tests. No new checks or permission changes.

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[github-actions]

✅ Conflict Markers Resolved

All conflict markers have been successfully resolved in this pull request.