Files
riposte-marketplace/integrations/zscaler/manifest.yaml
T
f3nris 45e9cbd269 feat: declare a risk tier on every command in the catalog
467 of the 1592 commands carried no `risk:`. An unset risk is read as
destructive by the agent approval gate, so half the catalog's write side sat
behind the same prompt — and, in HarfangLab's case, 39 pure lookups did too.
A gate that stops everything stops being read as a signal, which is the
argument already made for the toolkit and for sentinelone (df27876).

The catalog is now 1027 read, 261 safe_write, 304 destructive, with nothing
defaulted. The line follows the one sentinelone drew: impact on the estate,
not reversibility — isolate-agent is reversible and is the canonical
destructive example.

  read        only queries; changes nothing outside Riposte
  safe_write  additive or reversible inside the tool's own case/enrichment
              plane: comments, tickets, tags, alert statuses, threat-intel
              records, sandbox submissions, collection jobs, outbound messages
  destructive changes the estate or weakens a control: containment, blocklists
              and allowlists, exclusions and detection rules, every delete,
              identity and credential operations, code on a host, generic
              API escape hatches

Three calls that were not obvious, and are now applied throughout:

- Undoing a containment is tiered like the containment it lifts. Un-isolating
  a host or un-banning an IP mid-incident is its own decision, not a return to
  a neutral state. The catalog contradicted itself here — crowdstrike's
  lift_containment was destructive while harfanglab's deisolate_from_threat
  was safe_write — so deisolate_from_threat and unquarantine_file are
  re-tiered to destructive, the only two existing tiers this pass changes.
- Retrieving a live secret is destructive: cyberark get_password, delinea
  get_secret, vault read_secret, beyondtrust get_credential. It is a GET, but
  the tier describes the stake, not the HTTP verb.
- Sending outward to humans stays safe_write — slack, teams, twilio, telegram,
  mail. Irreversible, but it is the collaboration plane, not the estate.

An object created but not yet referenced by a rule is safe_write; editing one
a rule already reads is destructive. That is why fortigate create_address and
panos create_custom_url_category are safe_write while update_address_group and
edit_custom_url_category are not.

The template and README never documented the field, which is how 467 commands
came to omit it. Both now carry the tier table and these rules, so the next
integration declares a tier instead of inheriting one.

111 packages get a MINOR bump and a changelog entry: an instance compares
versions to offer an update, so an unbumped manifest would leave the tiers
sitting in the catalog and never reaching the estates that need them.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-08 12:55:20 +02:00

145 lines
5.4 KiB
YAML

id: zscaler
name: Zscaler Internet Access
version: 1.1.0
description: "Zscaler Internet Access (ZIA REST API) — web-layer containment: block/unblock URLs and IPs (advanced block list), manage the allow list, add URLs to custom categories, read Sandbox reports, and activate configuration changes. Session-based API-key authentication; stdlib-only, no extra Python dependencies."
changelog: "1.1.0 — Declare the risk tier on the 7 commands that carried none, all of them destructive. An unset risk was already gated as destructive, so the approval prompt does not move; what changes is that the tier is a stated decision rather than a default, and a command added later cannot inherit it by omission. | 1.0.0 — Initial release: URL/IP block list add/remove, block-list and allow-list read, allow-list add, category URL add, Sandbox report, activate changes."
category: network
# Per-instance configuration. Authentication is session-based: each command logs
# in with the obfuscated API key + username/password, then reuses the session
# cookie for the request.
config_schema:
properties:
cloud:
type: string
description: "Zscaler cloud base URL (e.g. https://zsapi.zscalertwo.net)"
username:
type: string
description: "ZIA admin username"
password:
type: string
description: "ZIA admin password"
x-soar-sensitive: true
api_key:
type: string
description: "ZIA API key"
x-soar-sensitive: true
insecure:
type: boolean
description: "Trust any TLS certificate (not secure)"
default: false
required:
- cloud
- username
- password
- api_key
commands:
- id: blacklist_url
name: zscaler-blacklist-url
description: "Add one or more URLs to the advanced block list."
risk: destructive
inputs_schema:
properties:
urls: { type: string, description: "Comma-separated URLs to block" }
required: [urls]
outputs_schema: { properties: {} }
- id: undo_blacklist_url
name: zscaler-undo-blacklist-url
description: "Remove one or more URLs from the advanced block list."
risk: destructive
inputs_schema:
properties:
urls: { type: string, description: "Comma-separated URLs to remove" }
required: [urls]
outputs_schema: { properties: {} }
- id: blacklist_ip
name: zscaler-blacklist-ip
description: "Add one or more IP addresses to the advanced block list."
risk: destructive
inputs_schema:
properties:
ips: { type: string, description: "Comma-separated IP addresses to block" }
required: [ips]
outputs_schema: { properties: {} }
- id: undo_blacklist_ip
name: zscaler-undo-blacklist-ip
description: "Remove one or more IP addresses from the advanced block list."
risk: destructive
inputs_schema:
properties:
ips: { type: string, description: "Comma-separated IP addresses to remove" }
required: [ips]
outputs_schema: { properties: {} }
- id: get_blacklist
name: zscaler-get-blacklist
description: "Get the current advanced block list (URLs and IPs)."
risk: read
inputs_schema:
properties: {}
required: []
outputs_schema: { properties: {} }
- id: whitelist_url
name: zscaler-whitelist-url
description: "Add one or more URLs to the allow list."
risk: destructive
inputs_schema:
properties:
urls: { type: string, description: "Comma-separated URLs to allow" }
required: [urls]
outputs_schema: { properties: {} }
- id: get_whitelist
name: zscaler-get-whitelist
description: "Get the current allow list."
risk: read
inputs_schema:
properties: {}
required: []
outputs_schema: { properties: {} }
- id: category_add_url
name: zscaler-category-add-url
description: "Add one or more URLs to a custom URL category."
risk: destructive
inputs_schema:
properties:
category_id: { type: string, description: "URL category id (from zscaler-get-categories)" }
urls: { type: string, description: "Comma-separated URLs to add to the category" }
required: [category_id, urls]
outputs_schema: { properties: {} }
- id: get_categories
name: zscaler-get-categories
description: "List URL categories (id and name)."
risk: read
inputs_schema:
properties:
custom_only: { type: boolean, description: "Return only custom categories (default false)" }
required: []
outputs_schema: { properties: {} }
- id: sandbox_report
name: zscaler-sandbox-report
description: "Get the Zscaler Sandbox report for a file by MD5 hash."
risk: read
inputs_schema:
properties:
md5: { type: string, description: "MD5 hash of the file" }
details: { type: string, description: "Report detail level: 'full' or 'summary' (default full)" }
required: [md5]
outputs_schema: { properties: {} }
- id: activate_changes
name: zscaler-activate-changes
description: "Activate pending configuration changes in the Zscaler session."
risk: destructive
inputs_schema:
properties: {}
required: []
outputs_schema: { properties: {} }
- id: test_connection
name: zscaler-test-connection
description: "Verify connectivity and credentials by opening a session (used by the Test button)."
risk: read
inputs_schema:
properties: {}
required: []
outputs_schema: { properties: {} }