Understanding the Problem:

The issue is that Advanced Threat Prevention (ATP) logs are visible on the firewall but are not being ingested into the company’s SIEM.

This implies that the ATP subscription is working and generating logs on the firewall but the logs are not being forwarded properly to the SIEM.

Action to Resolve:

Log Forwarding Configuration:

Verify that the Security policy rules configured to inspect traffic using Advanced Threat Prevention are set to forward logs to the SIEM instance.

This is a common oversight. Even if the logs are generated locally, they will not be forwarded unless explicitly configured.

Configuration steps to verify in the Palo Alto Networks firewall:

Go to Policies > Security Policies and check the " Log Forwarding " profile applied.

Ensure the " Log Forwarding " profile includes the correct settings to forward Threat Logs to the SIEM.

Go to Device > Log Settings and ensure the firewall is set to forward Threat logs to the desired Syslog or SIEM destination.

Why Not the Other Options?

A (Enable the Threat Prevention license):

The problem does not relate to the license; the administrator already confirmed the license is active.

B (Check with the SIEM vendor):

While verifying SIEM functionality is important, the first step is to ensure the logs are being forwarded correctly from the firewall to the SIEM. This is under the systems administrator’s control.

C (Have the SIEM vendor troubleshoot):

This step should only be taken after confirming the logs are forwarded properly from the firewall.

References from Palo Alto Networks Documentation:

Log Forwarding and Security Policy Configuration

Advanced Threat Prevention Configuration Guide

When adopting additional security features over time, remaining aligned with Zero Trust principles requires a focus on constant visibility, control, and adherence to best practices. The following actions are the most relevant:

Why " Apply decryption where possible to inspect and log all new and existing traffic flows " (Correct Answer B)? Zero Trust principles emphasize visibility into all traffic, whether encrypted or unencrypted. Without decryption, encrypted traffic becomes a blind spot, which attackers can exploit. By applying decryption wherever feasible, organizations ensure they can inspect, log, and enforce policies on encrypted traffic, thus adhering to Zero Trust principles.

Why " Use the Best Practice Assessment (BPA) tool to measure progress toward Zero Trust principles " (Correct Answer C)? The BPA tool provides detailed insights into the customer’s security configuration, helping measure alignment with Palo Alto Networks’ Zero Trust best practices. It identifies gaps in security posture and recommends actionable steps to strengthen adherence to Zero Trust principles over time.

Why not " Turn on all licensed Cloud-Delivered Security Services (CDSS) subscriptions in blocking mode for all policies " (Option A)? While enabling CDSS subscriptions (like Threat Prevention, URL Filtering, Advanced Threat Prevention) in blocking mode can enhance security, it is not an action specifically tied to maintaining alignment with Zero Trust principles. A more holistic approach, such as decryption and BPA analysis, is critical to achieving Zero Trust.

Why not " Use the Policy Optimizer tool to understand security rules allowing users to bypass decryption " (Option D)? Policy Optimizer is used to optimize existing security rules by identifying unused or overly permissive policies. While useful, it does not directly address alignment with Zero Trust principles or help enforce decryption.

Create a New Threat Profile (Answer B):

Performance tuning in Intrusion Prevention System (IPS) involves ensuring that only the most relevant and necessary signatures are enabled for the specific environment.

Palo Alto Networks allows you to create custom threat profiles to selectively enable signatures that match the threats most likely to affect the environment. This reduces unnecessary resource usage and ensures optimal performance.

By tailoring the signature set, organizations can focus on real threats without impacting overall throughput and latency.

Why Not A:

Leaving all signatures turned on is not a best practice because it may consume excessive resources, increasing processing time and degrading firewall performance, especially in high-throughput environments.

Why Not C:

While working with TAC for debugging may help identify specific performance bottlenecks, it is not a recommended approach for routine performance tuning. Instead, proactive configuration changes, such as creating tailored threat profiles, should be made.

Why Not D:

Disabling irrelevant threat signatures can improve performance, but this task is effectively accomplished by creating a new threat profile . Manually disabling signatures one by one is not scalable or efficient.

References from Palo Alto Networks Documentation:

Threat Prevention Best Practices

Custom Threat Profile Configuration