https://live.paloaltonetworks.com/t5/expedition-discussions/management-port-asa-migration/m-p/582065#M4985 <P>I am looking for a collective answer best practice when using expedition to migrate from a Cisco ASA to a Palo Alto Pan-OS. Expedition typically maps the ASA Management interface to an ethernet interface and management zone on the Pan-OS and then sometimes attaches that zone to firewall policies that do not define an ACL as well.&nbsp;</P> <P>&nbsp;</P> <P>In regards to best practice, what do you do with the Management Interface migration from an ASA?</P> <UL> <LI>Delete it all together since the Palo Alto Management takes it's place and isn't easily converted?</LI> <LI>Merge the management interface and zone with "inside" zone traffic?&nbsp;</LI> <LI>Other practices I am unfamiliar with?</LI> </UL> <P>Thank you in advance!</P> Thu, 28 Mar 2024 20:46:25 GMT robert.kremnitzer 2024-03-28T20:46:25Z https://live.paloaltonetworks.com/t5/expedition-discussions/management-port-asa-migration/m-p/582065#M4985 <P>I am looking for a collective answer best practice when using expedition to migrate from a Cisco ASA to a Palo Alto Pan-OS. Expedition typically maps the ASA Management interface to an ethernet interface and management zone on the Pan-OS and then sometimes attaches that zone to firewall policies that do not define an ACL as well.&nbsp;</P> <P>&nbsp;</P> <P>In regards to best practice, what do you do with the Management Interface migration from an ASA?</P> <UL> <LI>Delete it all together since the Palo Alto Management takes it's place and isn't easily converted?</LI> <LI>Merge the management interface and zone with "inside" zone traffic?&nbsp;</LI> <LI>Other practices I am unfamiliar with?</LI> </UL> <P>Thank you in advance!</P> Thu, 28 Mar 2024 20:46:25 GMT https://live.paloaltonetworks.com/t5/expedition-discussions/management-port-asa-migration/m-p/582065#M4985 robert.kremnitzer 2024-03-28T20:46:25Z