Clone Rule as Disabled

[Nathan_Evans]

Feature Request.

Add an option to automatically disable a rule when it is cloned on the NGFW. This eliminates the need for manual disabling—a step that can be easily missed—and streamlines the workflow.

Cloning is the fastest and most efficient way to create new rules, but it also introduces risk: incomplete or unreviewed rules can be unintentionally committed to policy. A “Clone as Disabled” option provides a built-in safety guard, ensuring that only rules explicitly reviewed and enabled by an engineer are deployed.

The existing Clone (Active) behavior should remain unchanged for teams that do not require this additional control, giving engineers flexibility while improving overall policy safety and confidence.

[JayGolf · Accepted solution]

Hi @Nathan_Evans ,

Thanks for sharing! 

I would recommend submitting a FR for this. You can contact your PAN rep (Solutions Consultant/ AE) and they should point you to the right person to get it logged for you. 

You will basically share the details of the requested feature with them like you've done here, including the use case and business justification, and they will open a Feature Request ID (FRID) on your behalf. Once submitted, the request can be reviewed and prioritized internally, and other customers may also vote on the same FRID which can help increase its visibility.

If you’re unsure who your PANW representative is, your account team should be able to point you in the right direction.

Once you get that created, feel free to include the FRID here so we can let others be aware of it and vote as well!