Study guide

10.2 Logging Architecture: Strata Logging Service, Log Forwarding, and Collectors

Palo Alto Networks Certified Next-Generation Firewall Engineer Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Device Deployment & Architecture

1.1 Platform Selection & Sizing: Hardware, VM-Series, and Cloud NGFW Form Factors 1.2 Base PAN-OS 11.x System Settings, Management Interfaces, and Service Routes 1.3 Interface Types, Zone Topologies, and Virtual Wire Configurations 1.4 Site-to-Site VPN Tunnels: IPSec, GRE, and Quantum-Resistant Cryptography

2 Chapter 2: Routing, VRFs, and Virtual Routers

2.1 Virtual Routers and VRF Architecture in PAN-OS 11.x 2.2 Static Routing, BGP, and OSPF Configuration & Failover 2.3 Policy-Based Forwarding (PBF) and Path Monitoring

3 Chapter 3: NAT and High Availability Designs

3.1 Source, Destination, and Twice-NAT Policy Configurations 3.2 High Availability Active/Passive Architecture and State Synchronization 3.3 High Availability Active/Active Architecture and HA Clustering

4 Chapter 4: Panorama Management & Policy Hierarchy

4.1 Panorama Architecture: Collector Groups, Log Collectors, and Device Registration 4.2 Templates and Template Stacks Configuration 4.3 Device Groups, Shared Rulestacks, and Policy Hierarchy

5 Chapter 5: Strata Cloud Manager and AIOps

5.1 Strata Cloud Manager (SCM) Architecture and Cloud-Delivered Management 5.2 SCM Rulestacks, Folder Hierarchies, and Unified Policy Management 5.3 AIOps for NGFW: Telemetry, Proactive Best-Practice Audits, and Operational Insights

6 Chapter 6: Security Profiles and Content Inspection

6.1 Antivirus, Anti-Spyware, and DNS Security Profiles 6.2 Vulnerability Protection, Custom Signatures, and Threat Exceptions 6.3 URL Filtering, Advanced WildFire Analysis, and Inline Deep Learning

7 Chapter 7: Decryption Inspection & Policy

7.1 SSL Forward Proxy Architecture and Internal Certificate Authority Trust 7.2 SSL Inbound Inspection for Internal Web Servers 7.3 Decryption Exclusions, HSM Integration, and Troubleshooting Decryption Failures

8 Chapter 8: User Identity and GlobalProtect Remote Access

8.1 User-ID Architecture, Agentless/Agent Deployment, and Cloud Identity Engine (CIE) 8.2 GlobalProtect Portals, Gateways, and Authentication Methods (SAML, MFA) 8.3 Host Information Profile (HIP) Checks and Endpoint Security Enforcement

9 Chapter 9: Cloud NGFW, Automation, and API Integration

9.1 Cloud NGFW for AWS and Azure Architectures (GWLB and VWAN) 9.2 XML and REST API Automation with Palo Alto Networks Firewalls 9.3 Infrastructure as Code: Terraform and Ansible Automation for PAN-OS 9.4 CN-Series, AI Runtime Security, and Edge Deployment Options

10 Chapter 10: Virtual Systems, Logging, and Operational Monitoring

10.1 Virtual Systems (VSYS), Logical Routers, and Inter-VSYS Routing 10.2 Logging Architecture: Strata Logging Service, Log Forwarding, and Collectors 10.3 Application Command Center (ACC), Dashboards, and Custom Reporting 10.4 Explicit and Transparent Web Proxy on PAN-OS

10.2 Logging Architecture: Strata Logging Service, Log Forwarding, and Collectors

Key Takeaways Explain This Topic AI

PAN-OS generates traffic, threat, URL filtering, data, WildFire, system, configuration, and other log types, each written to a log database on the firewall.

Strata Logging Service (SLS, formerly Cortex Data Lake) is Palo Alto Networks' cloud-delivered logging platform that ingests and stores firewall logs at scale without on-premises storage capacity limits.

Log Forwarding Profiles determine which logs are forwarded and to which destinations, including Strata Logging Service, syslog, HTTP servers, email, and SNMP traps.

Panorama Log Collectors and Log Collector Groups aggregate logs from many firewalls into an on-premises repository when cloud logging is not permitted.

Log quotas and retention settings control on-device log storage rotation, while filter-based forwarding lets engineers forward only relevant log streams to conserve SIEM ingestion.

Last updated: July 2026

10.2 Logging Architecture: Strata Logging Service, Log Forwarding, and Collectors

Task 2.3 of the NGFW Engineer blueprint covers logging configuration, including the Strata Logging Service, log forwarding, and log collectors and log collector groups. Logging is how the firewall records every connection, threat, URL, and system event so that engineers can investigate incidents and demonstrate compliance.

Log Types Generated by PAN-OS

  • Log Type What It Records
  • Traffic Session start/end, source/destination, application (App-ID), user (User-ID), bytes
  • Threat Matches against IPS, Antivirus, Anti-Spyware, WildFire, DNS Security, and DLP profiles
  • URL Filtering URL category matches and blocked/allowed URL decisions
  • Data Data filtering and file blocking events
  • WildFire Verdicts for files submitted to WildFire analysis
  • System Firewall system events, HA failovers, software updates, hardware health
  • Configuration Configuration commits and changes

All logs are first written to the firewall's local log database, whose size is bounded by the platform's log quota settings.

Strata Logging Service (SLS)

Strata Logging Service (SLS) is Palo Alto Networks' cloud-delivered logging platform. It was previously known as Cortex Data Lake (and earlier as the Logging Service). SLS ingests firewall logs over the cloud, stores them at scale, and exposes them through the Strata Cloud Manager and Cortex applications for querying and reporting.

When to Use SLS

Environments that want log storage without managing on-premises disk capacity.

Cloud and hybrid NGFW fleets (including Cloud NGFW and Prisma Access) that already use cloud-delivered services.

Organizations that need long retention and centralized queries across many firewalls.

SLS is licensed as part of the Strata Cloud Manager / Cortex bundle; the firewall authenticates and forwards logs to the regional SLS tenant.

Log Forwarding Profiles

A Log Forwarding Profile is the device-side object that decides what is forwarded and where. The blueprint item 2.3.2 (log forwarding) centers on this object.

How a Profile Works

The profile is created at the device level and references one or more destination servers (Strata Logging Service, syslog server, HTTP server, email, SNMP trap).

For each log type, the profile enables forwarding and can attach a match filter so only matching logs (for example, only severity high threats, or only traffic from a specific zone) are forwarded.

The profile is attached to a security policy rule, a decryption rule, or the device-wide log settings so that logs produced by that rule are forwarded.

Common Destinations

Strata Logging Service: cloud storage and query.

Syslog (UDP/TCP/TLS): traditional SIEM ingestion over standard syslog.

HTTP/HTTPS server: custom endpoints or cloud SIEM APIs.

Email and SNMP trap: alerting on specific high-severity events.

Filter-based forwarding is a key exam skill: rather than forwarding every traffic log to an expensive SIEM, engineers forward only threat logs or only high-severity events while sending the full stream to the cheaper Strata Logging Service.

Log Collectors and Log Collector Groups (Panorama)

When cloud logging is not permitted (regulated or air-gapped environments), Panorama provides on-premises log aggregation.

Panorama Log Collector: a dedicated logging function, available on dedicated M-Series appliances (for example the M-600, M-700) or as the Panorama virtual log collector. It receives logs from connected firewalls and stores them on local disk.

Log Collector Group: a group of log collectors that together serve a set of firewalls. Collector groups provide redundancy and capacity growth: adding collectors to a group increases aggregate storage and allows logs to survive a single collector failure.

Architecture Placement

Managed firewalls are assigned to a Log Collector Group (configured in Panorama under the device or device-group level). Each firewall forwards its logs to the assigned group, which stores them and makes them queryable through Panorama. This separates the management plane (Panorama config push) from the logging plane (collectors), so log volume does not consume Panorama's management performance.

On-Device Log Quotas and Retention

The firewall's local log database is finite. Log quotas set the maximum disk space each log type may consume; when a quota is reached, the oldest logs of that type are rotated out. Best practice is to reserve generous quotas for threat and WildFire logs (which drive investigations) and smaller quotas for routine traffic logs that are also forwarded off-device. Quota planning prevents a flood of low-value traffic logs from evicting high-value threat evidence.

Choosing Between SLS and On-Premises Collectors

  • Factor Strata Logging Service Panorama Log Collectors
  • Storage location Palo Alto Networks cloud On-premises appliances/virtual collectors
  • Capacity management Elastic, managed by PAN Engineer-sized disk; add collectors to grow
  • Best fit Cloud/hybrid fleets, long retention Regulated/air-gapped environments
  • Query surface Strata Cloud Manager / Cortex Panorama log viewer

Both options can coexist: a single firewall can forward some log streams to Strata Logging Service and others to an on-premises collector or SIEM simultaneously through different Log Forwarding Profile destinations.