Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Defender for API not enabled in latest MDFC Initiative #1885

Open
robsissons-contino opened this issue Jan 15, 2025 · 1 comment
Open

Defender for API not enabled in latest MDFC Initiative #1885

robsissons-contino opened this issue Jan 15, 2025 · 1 comment
Labels
Area: Policy 📝 Issues / PR's related to Policy bug Something isn't working

Comments

@robsissons-contino
Copy link

Describe the bug
Latest version of Deploy-MDFC Initiative does not include DefenderForApis

We use the downstream CAF Enterprise Scale Terraform module (https://github.com/Azure/terraform-azurerm-caf-enterprise-scale) and our subscriptions are not registering Defender for API with the policies which are assigned as part of the module.

I raised an issue (Azure/terraform-azurerm-caf-enterprise-scale#1167) with the team who advise that all policies are taken from this repo.

Upon investigation I see that the previous version of the 'Deploy-MDFC-Config' initiative here, which is superseded by this policy did contain a policy definition to enable Defender for Apis.

Is this intentional?

Is there a plan to add defender for Api back in to the initiative?

Steps to reproduce

  1. Deploy Landing Zones using the CAF Enterprise Scale Terraform Module
  2. Create a new subscription
  3. Review Defender for Cloud settings
  4. see that Defender for API is not enabled.
@robsissons-contino robsissons-contino added the bug Something isn't working label Jan 15, 2025
@Springstone
Copy link
Member

@robsissons-contino thanks for raising this issue. This has been a gap since early 2024 when the product group changed the APIs for Defender for API as it transitioned from free public preview to a paid service. As part of this transition, the API commands were updated to require sub-plans appropriately sized for the service, and there is no free plan.

Accordingly the originally provided policy was deprecated (it doesn't work anymore): https://www.azadvertizer.net/azpolicyadvertizer/e54d2be9-5f2e-4d65-98e4-4f0e670b23d6.html

We are working with product group to provide a new policy, however, due to internal priorities this has been delayed. We are actively tracking this in our backlog, and will add the policy as soon as it becomes available.

We DO enable Defender for API on all subscriptions using sub-plan 1 (the smallest) are part of the initial landing zone deployment (we do this through ARM), however, new subscriptions that would normally be remediated using the Deploy-MDFC-Config initiative will not have Defender for API configured at this time.

@Springstone Springstone added the Area: Policy 📝 Issues / PR's related to Policy label Jan 16, 2025
@Springstone Springstone added this to the policy-refresh-fy25-q3 milestone Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Policy 📝 Issues / PR's related to Policy bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants