'In Azure policy assigning an Azure Security Benchmark initiave for version 2 is not working
After assigning the Azure Security Benchmark initiative to a brand new subscription, it seems that the compliance results are based on security controls v3 and not on v2 version. When assigning the initiative we can clearly see it mentions v2 version
Still when looking into the "Initiave Complaince" section the results we have there all seem to be based on v3.
Example LT-1
V2: Enable threat detection for Azure resources
V3: Enable threat detection capabilities (This is what appears on Portal)
Even if i use Az CLI or Powershell the result is the same.
Is this a Bug? Is it possible to change? For me it's really importante, because i have lots of work done using the version 2 of security controls.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|