| Where Can I Use This? | What Do I Need? |
|---|
- Prisma Access (Managed by Strata Cloud Manager)
- Prisma Access (Managed by Panorama)
- NGFW (Managed by Panorama)
|
- Check the prerequisites for the deployment you're
using
- Prisma Access Agent 25.6 or earlier versions
- macOS 14 and later desktop devices
- Contact your Palo Alto Networks account representative to
activate the Prisma Access Agent feature
|
To set up the Prisma Access Agent on macOS devices, you will need to deploy an
installation package to the target endpoint. During the installation process, macOS
will prompt for various system permissions including system extension approval,
notification permissions, and Full Disk Access permissions for Prisma Access Agent processes.
For a streamlined deployment that eliminates the need for end-user interaction or
manual configuration by you, Palo Alto Networks offers a unified configuration
profile (V2_1 version). You can use this profile with Jamf Pro to deploy the Prisma Access Agent to your managed macOS endpoints. The V2_1 configuration
profiles are compatible with Prisma Access Agents 25.6 or earlier versions.
The Prisma Access Agent configuration profile includes the following
payloads:
- Content Filter
Payload type:
com.apple.webcontent-filter
- Notifications
Payload type:
com.apple.notificationsettings
- Privacy Preferences Policy Control
Payload type:
com.apple.TCC.configuration-profile-policy
- System Extensions
Payload type:
com.apple.system-extension-policy
- VPN
Payload type: com.apple.vpn.managed
The unified configuration profile also contains specifications for enabling
Prisma Access Agent with
Endpoint DLP.
The macOS System Settings window does not show Full Disk
Access permissions granted to the Prisma Access Agent by the configuration
profile.
The following procedure shows how to deploy Prisma Access Agent on macOS
endpoints using the unified configuration profile file from Palo Alto Networks.
Ensure that you perform the steps consecutively as described below. If you change
the order, the configuration profiles might not be available at the time the agent
requires them, which could cause unexpected behavior.
