Like this:

In most cases, a branch office uses a static outside IP address to connects to a main office by configuring a site-to-site IPsec VPN between two Cisco ASA firewalls with static IP address on both end, But what if one of the remote ASA firewalls has a dynamic IP address?

The Site-to-Site IPsec VPNs were used to connect two distant LANs together over the Internet. Private addresses were used on the LAN that means without tunneling the two LANs would be unable to communicate with each other.

Firewall Logging is Useful to verify if newly added firewall rules are working or not, to identify malicious activity, and to determine if the firewall is dropping packet which causes application failures.

Like this:

Layer 3 is the classical deployment method for the PA firewall, and it is always considered the standard and most powerful deployment method because it has all of the functionalities, while other deployment methods have some limitations (example of the other deployment methods are virtual wire, layer 2, etc …)

PA configuration management has powerful functions to manage configuration, but at the same time it can be very confusing if you are used to other firewalls vendors. So, let me explain the concept of configuration management, and how to set it up in the right way in order to be effective to make a full use of it.

I would like to share my experience with you. Let’s start with configuration management; on a Palo Alto firewall, there is a dedicated Management plane and Data plane.

Forefront Threat Management Gateway (TMG) 2010 is an integrated edge security gateway from Microsoft. It is a Common Criteria certified (EAL4+) enterprise-class application-layer firewall that includes support for proxy services (forward and reverse proxy), content caching, and VPN (both site-to-site and remote access). Forefront TMG is licensed per processor; no client access licenses are required. It can be deployed in all of these roles, or any subset of them.