PSE-Strata Professional PSE-Strata Passing Score

When deploying User-ID, it's crucial to specify included and excluded networks to ensure that only relevant traffic is monitored, reducing unnecessary load and potential privacy concerns. Enabling User-ID only on trusted zones minimizes the risk of exposing sensitive user information. Using a dedicated service account with minimal permissions necessary for User-ID services enhances security by limiting the potential damage if the account is compromised.

References:

Palo Alto Networks' User-ID Best Practices

NIST Special Publication 800-53 on Access Control

Prisma SaaS and VM-300 firewalls can send logs to the Cortex Data Lake (now called Strata Logging Service). Prisma SaaS logs user activity and data access within SaaS applications and forwards these logs to the Strata Logging Service for centralized analysis and monitoring. Similarly, VM-300 firewalls deployed in AWS can send various types of logs, including traffic and threat logs, to the Strata Logging Service through Panorama or directly​ (Palo Alto Networks)​​ (Palo Alto Networks)​.

To enable Credential Phishing Prevention on a Palo Alto Networks firewall, three key settings must be configured:

Define an SSL Decryption Rulebase: SSL decryption is necessary to inspect encrypted traffic for credential submission attempts. Without decryption, the firewall cannot see the contents of SSL/TLS encrypted traffic.

Enable User-ID: User-ID is needed to associate traffic with specific users, which is crucial for applying user-specific security policies, including credential phishing prevention.

Define URL Filtering Profile: A URL filtering profile is used to identify and block access to phishing websites. This profile can be configured to enforce strict controls over websites that users are allowed to access, thus preventing credential submission to malicious sites.

These configurations ensure that the firewall can effectively monitor and prevent phishing attempts by inspecting traffic, associating it with users, and controlling access to potentially harmful websites.

When a packet associated with an existing session arrives at the firewall, it is processed through the fast path because the session establishment has already occurred, so the session lookup can be quickly determined. If the packet is subject to content inspection, it will then be processed through a single stream-based content inspection engine before it is allowed to egress. This approach ensures efficient packet handling and minimizes latency while maintaining necessary security inspections.