Getting Started With Palo Alto Firewalls v8
Getting Started With Palo Alto Firewalls v8
Overtime the attackers and sophistication of attacks has become more and more advanced more time.
We must have equivalent counter measures ideally to help prevent being compromised.
- NAT
- Layer 3 and layer 4 based ACL.
- Stateful filtering: Traffic going out is remember by firewall, when reply comes back from firewall refers to stateful
table (matches the IP address and headers) and allows that reply traffic to reach the user.
NGFW
- URL Filtering.
- Threat prevention and identify malicious content.
- Dynamic updates (learn new threats)
- uploads the suspicious files on the cloud to analyze.
- Deep packet inspection (looking higher than layer 4 in application layer).
- User-id (policies based on groups and users).
- Application layer inspection (Two end TCP connection between user and FW, FW and internet).
Operational— Use operational mode to view information about the firewall and the traffic running through it or to view information about Panorama or
a Log Collector. Additionally, use operational mode commands to perform operations such as restarting, loading a configuration, or shutting down.
When you log in, the CLI opens in operational mode.
If we want Palo Alto to use different interface, We can do it in Service Route Configuration.
8.0.x version may need certain minimum dynamic update version (Anti-virus, Threat Intelligence) in place.
First we will update the dynamic update software and then PAN OS.
In a network in which we have all types of traffic going through it might make a lot of sense also to
deploy a firewall but instead of deploying it inline initially we can set it on the network to just see what's
happening so we can do reconnaissance and learn about that network traffic, what kind of attacks are
there before we put policies in place, to control and allow traffic.
Interface configured in TAP mode gets copies of data (network traffic) so it can look at the data and we
can use reporting on the firewall to tell us what it sees what kind of malicious traffic.
We use port mirroring(SPAN) to send copy of traffic to TAP interface connected on switch the traffic can
configured to send for VLAN or router interface.
Keep in mind, however, because the traffic is not running through the firewall when in tap mode it
cannot take any action on the traffic, such as blocking traffic with threats or applying QoS traffic control.
Eg: Source port: Router interface connected on switch, Destination port: TAP interface connected on
switch.
There is quite a bit of hassle when changing network topologies and changing addresses, it will be awesome if there is option for
deploying Palo Alto firewall including all the rules and control it can bring without re ip addressing the portion of our network.
It is possible, One of the option is using network interface on Palo Alto configured as VIRTUAL WIRE.
Firewall will pass all traffic if the security policies on firewall allows it. Its like a bump in the wire.
Firewall is not doing Layer 2 switching or layer 3 forwarding, It allows to pass traffic if security policy allows.
In a virtual wire deployment, you install a firewall transparently on a network segment by binding two firewall ports (interfaces) together.
The virtual wire logically connects the two interfaces; hence, the virtual wire is internal to the firewall.
By using Virtual wire mode will we still get most of the feature of Palo Alto firewall?
VLAN-Tagged Traffic
Preview changes can used to check the candidate config. Pop-up may be blocked on browser if preview changes does not come.
There are some additional configuration that needs to be done including adding interface to security zone.
Another option available to us besides Virtual wire to implement policy and control through the network using Palo alto without having to
readdress our network is use option of layer 2 type interfaces.
If configure Palo Alto interface as Layer 2 they are in same broadcast domain but benefit is if we assign security zones,
we control flow of traffic between security zones.
If we want to use Palo Alto as Layer 2 switch for multiple VLANs we can do that as well with sub interface and VLAN object.
We are limited to just two interfaces with virtual wire with Layer 2 we can have multiple interfaces.
Each interface has IP address and packets are actually routed through the interfaces on Palo Alto.
Not every Palo Alto firewall has same interface options. Eg: Cloud solution with virtual firewall we
should what options are available to us.
If firewall rules are interface based we have add and tweak rules based on individual interface.
Suppose we add new inside interface we have to add and tweak rules for that interface.
Benefit of security zones is when we are creating security policies on our firewall we can create those
policies if we want to include details regarding zones.
We can say if traffic is coming in on an interface associated with inside zone and going to internet from
interface associated with outside zone allow it.
An interface can only be member of one security zone, but there can be many interfaces associated to a
security zone.
Suppose we have deployed our Palo alto firewall using layer 3 interfaces, Hence each interface will have
IP address and is also responsible for routing based on IP.
If we want a set of interface to share separate routing table than other set of interface on Palo Alto
firewall we will create two virtual routers and assign those interface to VR accordingly.
(We may have a default route on management interface but that is not related to default VR.)
Configuring Zones:
What is NAT
What is PAT
Cool thing about security zones are that we can build NAT policies based on Zones.
If packet is sourced from inside and is going to outside then translate the source ip address.
We can translate the source ip address to specific ip address, interface ip address or from pool of ip addresses.
Firewall remembers the translation in NAT table and when the reply comes back, firewall will untranslate it and
put the original ip address.
Address type: we can the interface ip address or specific ip address or ip address from Pool.
Hence we have to create a new rule and place it above the existing rules for the traffic from user in inside zone to be
allowed internet access.
We can add color to zones, security and NAT policies for better visibility in Palo Alto by using tags
We can create tags for lot of different elements in Palo Alto, We can create tags for subnet, or all internal network.
We can add additional search functionality based on this tags.
Destination NAT.
Security policy.
Configuring NAT
=============