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

Feature Request: Enable Defender for APIs #1214

Open
w3b3rf opened this issue Dec 12, 2024 · 0 comments
Open

Feature Request: Enable Defender for APIs #1214

w3b3rf opened this issue Dec 12, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@w3b3rf
Copy link

w3b3rf commented Dec 12, 2024

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Is your feature request related to a problem?

The default policy Deploy-MDFC-Config_20240319 seems to enable Defender for Cloud for every resource type except APIs. Some of the example docs mention a specific configuration parameter to enable / disable Defender for APIs (see https://github.com/Azure/terraform-azurerm-caf-enterprise-scale/wiki/%5BExamples%5D-Deploy-ZT-Network#:~:text=enable_defender_for_apis) but even if I specify this to be true manually (I think the other defender-related parameters are true by default) no changes will be deployed meaning this parameter is simply ignored.

Describe the solution you'd like

Defender for APIs should be enabled by default (like the rest of the defenders) and it should be possible to control it via aforementioned configuration parameter.

Is there a workaround / policy to enable Defender for APIs in the mean time?

Additional context

@matt-FFFFFF matt-FFFFFF added the enhancement New feature or request label Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants