Azure Workflow Automation - Block BruteForce - NSG rule name and Priority are static which blocks the creation of new nsg rule for the same vm about microsoft-defender-for-cloud HOT 3 CLOSED

Adding @safeenab786 as the owner of this automation.

from microsoft-defender-for-cloud.

Hey @darkweb-123
Thanks for raising this issue. We're currently working on an updated version of this automation which we're planning to release during February 2021.

from microsoft-defender-for-cloud.

We've updated the BlockBruteForceAttack automation to V2 with the following improvements:

1. The Logic App will take all IP Addresses from the alert and add them to the Deny Rule in the VM's NSG.
2. The rule name is unique to make sure it does not overwrite an existing BlockBruteForce rule.
3. The rule priority is dynamically assigned. The Logic App will use the lowest free priority number to create the rule.

Please find the newest release at https://github.com/Azure/Azure-Security-Center/tree/master/Workflow%20automation/BlockBruteforceAttack

Closing this issue since a solution was provided.

from microsoft-defender-for-cloud.