Paloalto Networks PCNSE - Palo Alto Networks Certified Security Engineer (PCNSE) PAN-OS 11.0

To apply tags automatically based on User-ID logs, the engineer must configure a Log Forwarding profile that specifies the criteria for matching the logs and the tags to apply. The Log Forwarding profile can be attached to a security policy rule or a decryption policy rule to enable auto-tagging for the traffic that matches the rule. The tags can then be used for dynamic address groups, policy enforcement, or reporting1. References: Use Auto-Tagging to Automate Security Actions, PCNSE Study Guide (page 49)

https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/high-availability/set-up-activeactive-ha/prerequisites-for-activeactive-ha

These are the two links that can be used to configure an active/active high availability pair. An active/active high availability pair consists of two firewalls that are both active and share the traffic load between them1. To configure an active/active high availability pair, the following links are required2:

HA1: This is the control link that is used for exchanging heartbeat messages and configuration synchronization between the firewalls. It can be a dedicated interface or a subinterface. It can also have a backup link for redundancy.

HA2: This is the data link that is used for forwarding sessions from one firewall to another in case of failover or load balancing. It can be a dedicated interface or a subinterface. It can also have a backup link for redundancy.

HA3: This is the session owner synchronization link that is used for synchronizing session information between the firewalls in different virtual systems. It can be a dedicated interface or a subinterface. It is only required for active/active high availability pairs, not for active/passive pairs.

In PAN-OS, the Log Forwarding object under Objects configures forwarding for Authentication (Option B) and User-ID (Option C) logs, among others, to external systems (e.g., syslog servers).

Option A (GlobalProtect) and Option D (WildFire) logs are managed differently (e.g., via profiles or Panorama). Documentation lists supported log types in Log Forwarding.

When managing firewalls with Panorama, configurations can be pushed from Panorama templates to managed firewalls. However, there are scenarios where specific settings need to be overridden on the local firewall level due to unique requirements or exceptions.

B. The modification will not be visible in Panorama:

When an override is made directly on the firewall, this change is not automatically reflected back in Panorama's templates or device groups. The local configuration on the firewall will take precedence over the Panorama pushed configuration for the overridden settings, but these local changes will not be visible in the Panorama interface. This means that while Panorama maintains central control and visibility over the bulk of the configuration, it does not have visibility into local overrides made directly on the firewalls.

This distinction is crucial for auditors and administrators to understand, as it impacts how configurations are managed and synchronized between Panorama and the individual firewalls. Local overrides provide flexibility but require careful management to ensure consistency and compliance with security policies.