I can confirm this. Usually when I do this I will use the "inside" interface as the default gateway. This makes updating easy because you don't have to create a profile allowing the "internet" facing interface to pull updates/activation/etc. You can even attach a network cable from the management interface directly to another port on the firewall to do this. It's a little goofy, but it works.
As a recommendation, I would say put it onto another vlan and zone. Then have the PAN hold the vlan gateway IP so that any traffic going to the management port requires security policies. You can even use AD groups so that not everyone on the inside can hit it.
I'm a fan of the zero trust model so the more you can restrict, the better.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!