Palo Alto Networks · Arazzo Workflow

Prisma Cloud Policy Review and Update

Version 1.0.0

Authenticate to Prisma Cloud, list policies, inspect one, then update it.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub Cloud SecurityCybersecurityFirewallNetwork SecuritySASESOARThreat IntelligenceXDRArazzoWorkflows

Provider

palo-alto-networks

Workflows

review-and-update-policy
Review a Prisma Cloud policy and update its severity and enabled state.
Authenticates with Prisma Cloud, lists policies, reads the first policy's detail, and submits an update preserving its core definition while changing severity and enabled state.
4 steps inputs: enabled, newSeverity, password, username outputs: policyId, updatedSeverity
1
authenticate
Authenticate with access-key credentials and capture the JWT for later steps.
2
listPolicies
List all security policies, authorizing with the JWT from the login step.
3
getPolicyDetail
Retrieve the full definition of the first policy so it can be updated in place.
4
updatePolicy
Update the policy, preserving its name, type, description, cloud type, and rule while applying the new severity and enabled state.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Prisma Cloud Policy Review and Update
  summary: Authenticate to Prisma Cloud, list policies, inspect one, then update it.
  description: >-
    A Prisma Cloud CSPM policy-governance flow. The workflow logs in with
    access-key credentials to obtain a short-lived JWT, lists all security
    policies, retrieves the full detail of the first policy, and then updates
    that policy's severity and enabled state. The JWT obtained at login is
    passed inline as the Authorization header on each protected step. Every step
    spells out its request inline so the governance flow can be read and
    executed without opening the underlying OpenAPI description.
  version: 1.0.0
  x-realizes-capability-ids:
  - BC-620.10
  x-capability-derivation:
    method: 'deterministic join: sourceDescriptions -> per-tag OpenAPI -> tag/capability edge. No classification at this step.'
    min_confidence: 0.7
    sources:
    - capability_id: BC-620.10
      capability_name: Security Strategy & Governance Management
      spec: palo-alto-networks-policies-api-openapi.yml
      confidence: 0.7
    model: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
sourceDescriptions:
- name: authenticationApi
  url: ../openapi/palo-alto-networks-authentication-api-openapi.yml
  type: openapi
- name: policiesApi
  url: ../openapi/palo-alto-networks-policies-api-openapi.yml
  type: openapi
workflows:
- workflowId: review-and-update-policy
  summary: Review a Prisma Cloud policy and update its severity and enabled state.
  description: >-
    Authenticates with Prisma Cloud, lists policies, reads the first policy's
    detail, and submits an update preserving its core definition while changing
    severity and enabled state.
  inputs:
    type: object
    required:
    - username
    - password
    - newSeverity
    - enabled
    properties:
      username:
        type: string
        description: Prisma Cloud Access Key ID.
      password:
        type: string
        description: Prisma Cloud Secret Key for the access key.
      newSeverity:
        type: string
        description: Target severity for the policy (e.g. high, medium, low).
      enabled:
        type: boolean
        description: Whether the policy should be enabled after the update.
  steps:
  - stepId: authenticate
    description: Authenticate with access-key credentials and capture the JWT for later steps.
    operationId: login
    requestBody:
      contentType: application/json
      payload:
        username: $inputs.username
        password: $inputs.password
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      token: $response.body#/token
  - stepId: listPolicies
    description: List all security policies, authorizing with the JWT from the login step.
    operationId: listPolicies
    parameters:
    - name: Authorization
      in: header
      value: Bearer $steps.authenticate.outputs.token
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      policyId: $response.body#/0/policyId
  - stepId: getPolicyDetail
    description: Retrieve the full definition of the first policy so it can be updated in place.
    operationId: getPolicy
    parameters:
    - name: Authorization
      in: header
      value: Bearer $steps.authenticate.outputs.token
    - name: policyId
      in: path
      value: $steps.listPolicies.outputs.policyId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      name: $response.body#/name
      policyType: $response.body#/policyType
      description: $response.body#/description
      cloudType: $response.body#/cloudType
      rule: $response.body#/rule
  - stepId: updatePolicy
    description: >-
      Update the policy, preserving its name, type, description, cloud type, and
      rule while applying the new severity and enabled state.
    operationId: updatePolicy
    parameters:
    - name: Authorization
      in: header
      value: Bearer $steps.authenticate.outputs.token
    - name: policyId
      in: path
      value: $steps.listPolicies.outputs.policyId
    requestBody:
      contentType: application/json
      payload:
        name: $steps.getPolicyDetail.outputs.name
        policyType: $steps.getPolicyDetail.outputs.policyType
        severity: $inputs.newSeverity
        description: $steps.getPolicyDetail.outputs.description
        cloudType: $steps.getPolicyDetail.outputs.cloudType
        enabled: $inputs.enabled
        rule: $steps.getPolicyDetail.outputs.rule
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      updatedPolicyId: $response.body#/policyId
      updatedSeverity: $response.body#/severity
  outputs:
    policyId: $steps.listPolicies.outputs.policyId
    updatedSeverity: $steps.updatePolicy.outputs.updatedSeverity

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/palo-alto-networks-prisma-cloud-policy-lifecycle-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.