Configure Policies for Log Forwarding
Table of Contents
Expand all | Collapse all
-
- Firewall and PAN-OS Support of IoT Security
- IoT Security Prerequisites
- Onboard IoT Security
- Onboard IoT Security on VM-Series with Software NGFW Credits
-
- DHCP Data Collection by Traffic Type
- Firewall Deployment Options for IoT Security
- Configure a Pre-PAN-OS 10.0 Firewall with a DHCP Server
- Configure a Pre-PAN-OS 10.0 Firewall for a Local DHCP Server
- Use a Tap Interface for DHCP Visibility
- Use a Virtual Wire Interface for DHCP Visibility
- Use SNMP Network Discovery to Learn about Devices from Switches
- Use Network Discovery Polling to Discover Devices
- Use ERSPAN to Send Mirrored Traffic through GRE Tunnels
- Use DHCP Server Logs to Increase Device Visibility
- Plan for Scaling when Your Firewall Serves DHCP
- Prepare Your Firewall for IoT Security
- Configure Policies for Log Forwarding
- Control Allowed Traffic for Onboarding Devices
- Support Isolated Network Segments
- IoT Security Integration with Prisma Access
- IoT Security Licenses
- Offboard IoT Security Subscriptions
-
- Introduction to IoT Security
- IoT Security Integration with Next-generation Firewalls
- IoT Security Portal
- Vertical-themed Portals
- Device-to-Site Mapping
- Sites and Site Groups
- Networks
- Network Segments Configuration
- Reports
- IoT Security Integration Status with Firewalls
- IoT Security Integration Status with Prisma Access
- Data Quality Diagnostics
- Authorize On-demand PCAP
- IoT Security Integrations with Third-party Products
- IoT Security and FedRAMP
Configure Policies for Log Forwarding
Enable log forwarding so that the firewall sends Enhanced
Application logs (EALs) to the logging service.
Enable log forwarding so that the firewall
sends Enhanced Application logs (EALs) to the Palo Alto Networks
cloud-based logging service. IoT Security then fetches metadata
from there for analysis.
Configure an Interzone Policy
If
the VLAN interfaces are set in different L3 security zones from
the Ethernet interfaces with which they’re paired, Security policy
rules must be configured for the solution to work. The figure below
shows example rules when multiple VLAN interfaces have been configured
to support multiple Ethernet interfaces.
Policy
rule 1: This policy rule allows relayed unicast DHCP messages from
the zones assigned to interfaces ethernet1/1 - ethernet1/3 to the
DHCP zone. In addition, enable log forwarding and choose the log-forwarding
profile you previously created to send EALs for this traffic to
the logging service.
If you name the log
forwarding profile “default” (all lowercase), the firewall will
automatically apply it to new Security policy rules when they’re created—or
when they’re imported from IoT
Security. Doing this will save you time and effort when importing
Security policy rule recommendations from IoT Security. Because
imported rule recommendations don’t include a log forwarding profile,
you have to add one manually to each rule after you import it. However, by
naming the profile “default”, you can avoid this step. (Note that
the “default” log forwarding profile will be applied when adding
new Security policy rules, but it won’t be retroactively applied
to existing rules.)
Policy rule 2: This rule allows
ping (ICMP echo requests) from the VLAN interfaces in the DHCP zone
to networks configured on ethernet1/1 - ethernet1/3.
Policy
rule 3: This rule allows ping from the IP addresses assigned to
ethernet1/1 - ethernet1/3 to VLAN interfaces configured in the DHCP
zone.
Configure an Intrazone Policy
You must
override the logging and log forwarding settings in the default
intrazone policy rule so that the firewall will forward logs to
the logging service.
If the interface hosting the DHCP server
is in the same zone as the interface your clients are on, the default
intrazone policy rule applies to this traffic, which, by default,
allows all traffic within this zone but does not have logging and
log forwarding enabled. Therefore, you must override this by enabling
log forwarding on your default intrazone policy rule.
Even
for cases where the DHCP server is in a different zone from the
DHCP clients and an interzone policy is applied to their DHCP traffic,
we still recommend that you enable log forwarding on the default
intrazone policy rule to capture the enhanced application logs for
traffic within that zone.
- Click PoliciesSecurity, select intrazone-default, and then click Override.The Security Policy Rule configuration window appears.Click Actions, select Log at Session End, choose the log forwarding profile you just configured from the Log Forwarding drop-down list, and then click OK.