Azure / Azure/azure-policy

In Azure policy assigning an Azure Security Benchmark initiave for version 2 is not working

Open
#945 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

azure-security-center
Dominant language
Open Policy Agent
Stars
1.7k
Forks
1.2k
Avg merge
2d 54m
Merged PRs (30d)
3

Description

Hello i created a question in both microsoft qa and stack overflow about this subject
https://docs.microsoft.com/en-us/answers/questions/826951/in-azure-policy-assigning-an-azure-security-benchm.html
https://stackoverflow.com/questions/72015018/in-azure-policy-assigning-an-azure-security-benchmark-initiave-for-version-2-is

Basically, my problem is that when i assign the Azure Security Benchmark iniciative
https://github.com/Azure/azure-policy/blob/master/built-in-policies/policySetDefinitions/Azure%20Government/Security%20Center/AzureSecurityCenter.json
If we look into the description it mentions v2, but if we look into the policyDefinitionGroups it returns values of v3.

That's bad, in my case i have all of the previous work using v2 version.

Is it possible to either use v2 in this initiavie, or create a new one for v2?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with policySetDefinitions/Azure Government/Security Center/AzureSecurityCenter.json, linked in the issue. Compare its description with the policyDefinitionGroups values and review the referenced Microsoft Q&A and Stack Overflow reports for context. Done means Azure Security Benchmark v2 can be assigned, either through this initiative or a separate v2 initiative.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud, security
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.