2 APIs across 1 product group.
| I want to... | Use | Why |
|---|---|---|
| Detect cloud misconfigurations and compliance drift | Prisma Cloud CSPM API | Prisma Cloud CSPM queries alerts, compliance posture, and asset inventory across AWS, Azure, and GCP. |
| Orchestrate incident response and playbooks | Cortex XSOAR API | Cortex XSOAR manages incidents, indicators, war rooms, and playbook execution for SOAR workflows. |
| Track security work in incidents and war rooms | Cortex XSOAR API | Cortex XSOAR owns incident records, evidence, and analyst collaboration; Prisma Cloud only produces the findings. |
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Palo Alto Networks APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpaloaltonetworks.com" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpaloaltonetworks.com" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Once connected, ask your agent something like: .
What agents get from Jentic-routed access to this vendor.
Setup
Wiring these APIs by hand means handling two different auth models, Prisma Cloud's bearer token with regional host selection and Cortex XSOAR's Authorization-header key against your own host, plus your own retry and error handling. With Jentic you install once, add each Palo Alto Networks API from the Jentic directory, store each credential once, and your agent calls both.
Permission scoping
Your own rules decide which operations each API exposes to the agent. You can let it read Prisma Cloud alerts and compliance posture while withholding cloud-account onboarding, and let it create Cortex XSOAR incidents while withholding playbook execution, so higher-impact actions are added only when you choose.
Credential isolation
Specific to using Palo Alto Networks APIs through Jentic.
What can an agent do across the Palo Alto Networks APIs on Jentic?
An agent can detect cloud security issues with Prisma Cloud CSPM, covering alerts, compliance posture, and multi-cloud asset inventory, and then orchestrate the response with Cortex XSOAR, covering incidents, indicators, war rooms, and playbooks. The two APIs let one agent go from finding a cloud risk to running an automated response.
Do the two APIs share one set of credentials?
No. Prisma Cloud CSPM authenticates with a bearer token derived from an access key and secret, while Cortex XSOAR uses an API key in the Authorization header pointed at your own XSOAR host. Each API is added and credentialed separately in your Jentic One instance.
When should I use Prisma Cloud CSPM versus Cortex XSOAR?
Use Prisma Cloud CSPM to find and assess cloud misconfigurations, compliance drift, and asset risk across AWS, Azure, and GCP. Use Cortex XSOAR when you need to open incidents, enrich indicators, collaborate in war rooms, or run playbooks in response to those findings.
Can I connect a cloud finding to an automated response?
Yes. An agent can read a high-severity alert or compliance failure from Prisma Cloud, then create a Cortex XSOAR incident and execute a playbook to remediate it. This is the main cross-API pattern for the Palo Alto Networks portfolio on Jentic.
BOOK A DEMO
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
For Agents
An agent can query cloud security alerts, check compliance posture against frameworks like CIS and PCI-DSS, and inventory multi-cloud assets through Prisma Cloud, then create incidents, enrich indicators, and execute response playbooks through Cortex XSOAR. This lets one agent move from detecting a cloud risk to orchestrating its remediation.
Palo Alto Networks pairs cloud security posture management with a full security orchestration and response platform, so detection and remediation live under one vendor. Prisma Cloud finds misconfigurations and compliance drift across three clouds, and Cortex XSOAR turns those findings into automated, auditable response workflows.
Use for: Monitoring multi-cloud security posture and compliance with Prisma Cloud and orchestrating incident response and playbooks with Cortex XSOAR
Not supported: endpoint detection, network firewall management, vulnerability scanning, threat intelligence generation, application-layer security
Credentials: No. Prisma Cloud CSPM uses bearer token authentication from an access key and secret, while Cortex XSOAR uses an API key in the Authorization header against your own XSOAR host, so each API needs its own credential.
Across 2 Palo Alto Networks APIs: 1 vendor-official, 1 Jentic-generated, all indexed by Jentic and kept validated and agent-ready.
Palo Alto Networks provides cloud and security operations platforms accessible through two APIs on Jentic. The Prisma Cloud CSPM API monitors cloud security posture, compliance, and asset inventory across AWS, Azure, and GCP, while the Cortex XSOAR API drives security orchestration, incident management, and playbook automation. Together they let agents detect cloud misconfigurations and orchestrate the response.
Each workflow spans multiple Palo Alto Networks APIs. Jentic routes each operation to the right API automatically.
Cloud finding to orchestrated response
An agent pulls a high-severity misconfiguration or compliance failure from Prisma Cloud, then opens a Cortex XSOAR incident and runs a remediation playbook. This connects cloud detection to an auditable response workflow without an analyst copying alert details by hand.
List open high-severity alerts via Prisma Cloud GET /alert, then create a Cortex XSOAR incident with POST /incident and trigger a playbook with POST /playbook/execute.
Prisma Cloud CSPM API + Cortex XSOAR API
Compliance drift into SOC tracking
An agent checks compliance posture against a framework like CIS or PCI-DSS in Prisma Cloud, and for each failing standard creates a tracked Cortex XSOAR incident with the failing resources attached as evidence. This gives compliance findings a documented owner and timeline.
Retrieve posture via Prisma Cloud GET /compliance/posture, then for failing standards create incidents with POST /incident and attach findings via POST /entry.
Prisma Cloud CSPM API + Cortex XSOAR API
Enrich cloud alerts with indicators
An agent triages Prisma Cloud alerts tied to anomalous activity, then records the associated IPs, domains, and hashes as indicators of compromise in Cortex XSOAR for playbook-driven enrichment. This links cloud posture data to the threat intel used across investigations.
Fetch alert detail via Prisma Cloud GET /alert/{id}, then create matching indicators in Cortex XSOAR with POST /indicators/create.
Prisma Cloud CSPM API + Cortex XSOAR API
Your Prisma Cloud access key and your Cortex XSOAR API key are each stored once, encrypted, by your own Jentic One instance and injected at execution time. Neither credential enters the agent's prompt, logs, or context.
Intent-based discovery
An agent searches Jentic by intent such as 'check cloud compliance posture' or 'create an xsoar incident', and Jentic returns the matching Prisma Cloud or Cortex XSOAR operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Are these APIs free to use?
Both Prisma Cloud and Cortex XSOAR are commercial Palo Alto Networks products with licensing tiers, and the APIs are included with those licenses. Contact Palo Alto Networks for pricing. Jentic provides the integration layer, not the underlying subscriptions.
What kinds of security work fall outside these two APIs?
These APIs cover cloud posture and orchestration, not endpoint detection, network firewall management, vulnerability scanning, or application-layer security. Security data feeding XSOAR often comes from separate integrated tools like SIEM, EDR, and threat intel feeds.
All 3 are in the Jentic catalogue with the same one-credential, intent-search pattern.