Over the coming month, we will share with you some of the best practices which we have developed over the last six years working with Palo Alto Networks. In this first video, we will talk about how to migrate an existing legacy firewall to a Palo Alto Networks Next-Generation FireWall. The first part covers the migration strategy and explains the best approach. The second part provides an overview of the Palo Alto Networks Migration Tool which is essential for every migration.
If you would like to learn more about Palo Alto Networks Next-Generation FireWall then join one of our training. In order to prepare yourself for a migration, we particularly recommend the EDU-201 – Firewall: Install, Configure, and Manage as it covers all the fundamentals starting for Interface Configuration to Routing and Network Address Translation (NAT) as well as all the Next-Generation FireWall features like App-ID, Content-ID, User-ID and SSL Decryption.
Follow us on LinkedIn to hear when we publish the next best practice video or sign up to our FireWall Best Practices mailing list.
Contact us or give us a call +353 (1) 5241014 / +1 (650) 407-1995 – We are a Palo Alto Networks Certified Professional Service Provider (CPSP) and the Next-Generation Security Platform is what we do all day every day. Let us share our experience with you to make your Next-Generation Security project a smooth experience but most importantly a peace of mind by truly securing your valuable IT assets.
This document is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. You are free to share and adapt this document as long as you give appropriate credit to the author Lars Meyer. If you remix, transform or build upon the material, you must distribute your contributions under the same license as the original.
Disclaimer: Consigas Limited accepts no liability for the content of this blog post, or for the consequences of any actions taken on the basis of the information provided. Any views or opinions presented in this document are solely those of the author and do not necessarily represent those of Palo Alto Networks.