Loading

Palo Alto Prisma Access

Version 1.6.0 (View all)
Compatible Kibana version(s) 8.13.0 or higher
9.0.0 or higher
Supported Serverless project types
What's this?
Security
Observability
Subscription level
What's this?
Basic
Level of support
What's this?
Elastic

Palo Alto Prisma Access is a Secure Access Service Edge (SASE) platform that enables organizations to provide protected connectivity to their network and applications for branches, retail locations, and remote users. It's designed to ensure secure access to the cloud, SaaS, and internet for users, regardless of their location. Prisma Access uses a cloud-delivered infrastructure to connect users to applications, delivering both network security and a seamless user experience.

Use the Palo Alto Prisma Access integration to collect and parse data from the Syslog server. Then visualize that data in Kibana.

This module has been tested against the latest Palo Alto Prisma Access version 5.0.

The Palo Alto Prisma Access integration collects 16 types of event types:

  • Authentication - Auth logs contain information about authentication events seen by the next-generation firewall.

  • DNS Security - DNS Security logs contain information that the DNS Security service collects, such as server response and request information based on your firewall security policy rules, associated action, and the DNS query details when performing domain lookups.

  • Decryption - By default, decryption logs display entries for unsuccessful TLS handshakes.

  • File - File logs represents a file transfer across the network.

  • GlobalProtect - GlobalProtect logs identify network traffic between a GlobalProtect portal or gateway, and GlobalProtect apps.

  • HIP Match - HIP Match logs capture information about the security status of the endpoints accessing a network (such as whether they have disk encryption enabled).

  • IPtag - IPtag logs display how and when a source IP address is registered or unregistered with the next-generation firewall, and what tag the firewall applied to the address.

  • SCTP - SCTP logs are written at the end of every SCTP network session, as well as optionally at the start of every such session.

  • Threat - Threat logs contain entries for when network traffic matches one of the security profiles attached to a next-generation firewall security rule.

  • Traffic - Traffic logs contain entries for the end of each network session, as well as (optionally) the start of a network session.

  • Tunnel - Tunnel logs are written whenever a next-generation firewall is handling GTP traffic.

  • URL - URL logs are written by next-generation firewalls whenever network traffic matches a URL Filtering Profile attached to one or more security rules.

  • UserID - User-ID logs are generated whenever a user authentication event occurs using a resource to which the firewall has visibility.

  • System - System logs are used to record system events that occur within the writing entity.

  • Configuration - Configuration logs are used to record changes made to the writing entity.

  • GlobalProtect App Troubleshooting - GlobalProtect App troubleshooting logs contain information about the GlobalProtect client and its host to help app users resolve issues.

Note

The Palo Alto Prisma Access integration collects logs for different events, but we have combined all of those in one data stream named event.

Elastic Agent must be installed. For more details, check the Elastic Agent installation instructions.

For step-by-step instructions on how to forward logs to syslog server from your Palo Alto Prisma Access instance, check the Forward Logs to a Syslog Server guide.

  1. In Kibana navigate to Management > Integrations.
  2. In the search top bar, type Palo Alto Prisma Access.
  3. Select the Palo Alto Prisma Access integration and add it.
  4. Add all the required integration configuration parameters.
  5. Save the integration.

This is the Event dataset.