Prisma Access egress IP
You can register a limited number of individual IP addresses rather than large ranges. Shared egress addresses used by many organizations, such as a security cloud’s default pool or a cloud provider’s ephemeral IPs, cannot be added to your allowlist.
Prisma Access gives each location you onboard its own egress IP addresses, and those addresses belong to your tenant. To work with the Chainalysis allowlist you register the egress IPs for the locations your users connect through, and keep that set of locations as small as practical.
How it works
Before you begin
To follow this guide, you’ll need:
- Admin access to Strata Cloud Manager or Panorama for Prisma Access.
- GlobalProtect deployed to users, and any branch sites connected as remote networks.
- Your Chainalysis CSM contact in order to register your IPs.
Chainalysis domains to route
Wherever your platform lets you target destinations, use these domains.
Caution: Ensure that you route by domain, not by IP address. Chainalysis IP addresses change, so rules built on them will break.
Configuration steps
Review your Prisma Access locations
Prisma Access allocates egress IPs per location: at least two for each mobile user location (one active, one backup for autoscaling), and more during large scaling events.
List the locations your Chainalysis users actually need. Fewer locations means fewer IPs to register.
Turn on egress IP allow listing
- Strata Cloud Manager: Go to Configuration > NGFW and Prisma Access > Configuration Scope > Prisma Access > GlobalProtect > Infrastructure and edit the Prisma Access Locations settings. Turn on egress IP allow listing.
- Panorama: Go to Cloud Services > Configuration > Mobile Users - GlobalProtect, select your hostname and set Using IP Allow List in SaaS Apps to Yes. Commit and push.
Collect the egress IPs
Open the egress IP allow list table to see the addresses for each location. You can also retrieve them with the Prisma Access IP address API, which is useful for keeping your records current.
For remote networks (branch sites), collect their Prisma Access egress IPs the same way.
Register your IPs with Chainalysis
Send the following to your Chainalysis CSM or Chainalysis Support, using the IP submission template:
- Your dedicated egress IP addresses: IPv4 addresses and, if your network uses IPv6, your IPv6
/64range. - Your organization name and, if you have more than one, the Chainalysis account or organization each IP should apply to.
- Any other fixed addresses that call Chainalysis outside this platform, such as servers or integrations that use the API.
- The egress IPs for every location your users connect through, including backup addresses.
Your allowlist can contain up to 50 IP addresses. If your number of IPs exceeds 50, you can request an exception through your CSM or Chainalysis Support.
The following table details the types of IPs we support.
At this time, we do not accept private addresses (10.x, 172.16-31.x, 192.168.x, 100.64.x), home internet connections, shared or commercial VPN services, shared security-cloud egress pools, or broad ISP ranges.
Your CSM will tell you when the allowlist is live. Do not switch traffic over until they have confirmed.
Confirm the IPs and push
After Chainalysis confirms your IPs are registered, mark each address as added to your allow list (in Strata Cloud Manager select Migrate; in Panorama mark them Added to My Allow List). Commit and push again.
Prisma Access can add new egress IPs when it scales. Check the allow list table regularly and send any new addresses to your CSM before you confirm them.
Allow Chainalysis in your security policy
Make sure your Prisma Access security policy allows the Chainalysis domains, and that GlobalProtect split tunneling does not exclude chainalysis.com.
Confirm your connection
- On a GlobalProtect-connected device, sign in to KYT.
- Check your Prisma Access traffic logs for requests to
chainalysis.comand confirm the location matches one you registered. - Run a test API call from every system that uses the Chainalysis API.
- Repeat the sign-in test with a remote user who is off your corporate network.
When you confirm your connection, we recommend resetting your password (if your organization uses SSO, you can skip this). To reset your password, log out and go to app.chainalysis.com. Enter your email address, click Continue, select Reset password, and follow the on-screen instructions.
We also recommend rotating your API key by following the steps on this page.
If you have issues, please contact support@chainalysis.com.
Common issues
Receiving the following message: “Access Restricted. Your IP address is not on the Chainalysis Allowed IPs List.”
- Likely cause: Your IPs are not on the Chainalysis allowlist yet, or a different IP was registered.
- How to resolve: Check with your CSM that the exact egress IPs are registered and active.
The KYT user interface works but API calls return a 403 error.
- Likely cause:
- API calls come from servers that don’t route through this platform.
- The API key doesn’t have the right permissions or the API key must be rotated, even though the IP is allowed.
- How to resolve:
- Route those servers through it, or register their fixed egress IPs as well (see the Cloud NAT guide).
- Check the API key’s permissions in your Chainalysis account, or create a new key.
- API keys created before November 2, 2026 no longer work. To replace one, follow the key rotation steps.
Blocked even though your IPv4 address is registered.
- Likely cause: Your network is dual-stack and the browser or client is connecting over IPv6.
- How to resolve: Send your IPv6
/64range to your CSM or Chainalysis Support. As a quick test, disable IPv6 on the device and retry.
Users are sometimes blocked, sometimes not.
- Likely cause: Prisma Access scaled out and added a new egress IP.
- How to resolve: Check the egress IP allow list table for new addresses and send them to your CSM.
Too many IPs to register.
- Likely cause: Many locations are onboarded.
- How to resolve: Limit Chainalysis users to fewer locations, or ask your CSM about your limit.
Remote users bypass Prisma Access.
- Likely cause: Split tunneling excludes Chainalysis.
- How to resolve: Remove
chainalysis.comfrom GlobalProtect split tunnel exclusions.
Additional support
We’re here to help. For questions, contact your Chainalysis CSM or Chainalysis Support.