Firewall Rule Task

[Jason_DaSilva]

We are starting to implement auditing and reporting on of firewall activity.  In the past we have used a custom request to manage requests to make changes to our firewall rules.  Trying to move more to the OOB Request, it has been asked if it is possible to prevent a Firewall Rule Task (FWTASK) from being closed if a Security policy has not be selected to associate it with.

I am new with record producers, and am not sure how the flow for closing this type of task is managed.  Any assistance with this would be greatly appriciated.

Thanks.

[Community Alums · Accepted solution]

Hey @Jason_DaSilva 

Love to see the move toward OOB. The simplest way to achieve this would be in your flow, you can configure the flow to wait for the task to complete. Once the task is marked as complete, in your flow, you could have the next activity be a script where you can check your condition. If the security policy hasn't been created, you could have the next activity be to re-open the task OR duplicate the task entirely. I would probably recommend that you re-create the task, because then you could measure how many times very easily a task had to be re-done. Do this all in a loop and you have enforced your business logic such that a step in the process cannot be skipped.

Hope this helps!

~Nick

[Jason_DaSilva]

Thanks for the insight into this.  The ability to track 'incorrect processing' would probably be a need for management, especially as we transition.  Thanks!