Files
riposte-marketplace/integrations/fortigate/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

143 lines
6.1 KiB
YAML

id: fortigate
name: FortiGate
version: 1.1.0
description: "Fortinet FortiGate (FortiOS REST API v2) — network containment: ban/unban IP addresses (quarantine), manage firewall address objects and address groups, and read firewall policies and services. API-token authentication; stdlib-only, no extra Python dependencies. Supports multi-VDOM."
changelog: "1.1.0 — Declare the risk tier on the 5 commands that carried none: 1 safe_write, 4 destructive. An unset risk is read as destructive by the agent approval gate, so the 1 that only annotate sat behind the same prompt as the ones that change the estate. | 1.0.0 — Initial release: ban/unban/list banned IPs, address object create/delete/list, address-group update/list, firewall policy and service listing."
category: network
# Per-instance configuration. The API token is sent as 'Authorization: Bearer <token>'.
# vdom is an optional default applied to every request (overridable per command).
config_schema:
properties:
server:
type: string
description: "FortiGate URL (e.g. https://192.168.0.1)"
api_key:
type: string
description: "FortiOS REST API token"
x-soar-sensitive: true
vdom:
type: string
description: "Default VDOM (leave empty for the management VDOM)"
insecure:
type: boolean
description: "Trust any TLS certificate (not secure)"
default: false
required:
- server
- api_key
commands:
- id: ban_ip
name: fortigate-ban-ip
description: "Quarantine one or more source IP addresses (adds them to the FortiGate banned-IP list)."
risk: destructive
inputs_schema:
properties:
ip_addresses: { type: string, description: "Comma-separated IPv4/IPv6 addresses to ban" }
expiry_seconds: { type: number, description: "Ban duration in seconds (0 or empty = indefinite)" }
vdom: { type: string, description: "VDOM override" }
required: [ip_addresses]
outputs_schema: { properties: {} }
- id: unban_ip
name: fortigate-unban-ip
description: "Remove one or more IP addresses from the FortiGate banned-IP list."
risk: destructive
inputs_schema:
properties:
ip_addresses: { type: string, description: "Comma-separated addresses to unban (empty = clear all)" }
vdom: { type: string, description: "VDOM override" }
required: []
outputs_schema: { properties: {} }
- id: list_banned_ips
name: fortigate-list-banned-ips
description: "List the currently banned (quarantined) IP addresses."
risk: read
inputs_schema:
properties:
vdom: { type: string, description: "VDOM override" }
required: []
outputs_schema: { properties: {} }
- id: create_address
name: fortigate-create-firewall-address
description: "Create a firewall address object (subnet type)."
risk: safe_write
inputs_schema:
properties:
name: { type: string, description: "Address object name" }
subnet: { type: string, description: "Subnet as 'IP netmask' or CIDR (e.g. '10.0.0.5 255.255.255.255' or '10.0.0.5/32')" }
comment: { type: string, description: "Optional comment" }
vdom: { type: string, description: "VDOM override" }
required: [name, subnet]
outputs_schema: { properties: {} }
- id: delete_address
name: fortigate-delete-firewall-address
description: "Delete a firewall address object by name."
risk: destructive
inputs_schema:
properties:
name: { type: string, description: "Address object name" }
vdom: { type: string, description: "VDOM override" }
required: [name]
outputs_schema: { properties: {} }
- id: list_addresses
name: fortigate-list-firewall-addresses
description: "List firewall address objects (optionally a single one by name)."
risk: read
inputs_schema:
properties:
name: { type: string, description: "Optional address object name to fetch a single entry" }
vdom: { type: string, description: "VDOM override" }
required: []
outputs_schema: { properties: {} }
- id: update_address_group
name: fortigate-update-firewall-address-group
description: "Replace the members of a firewall address group (e.g. a blocked-hosts group referenced by a deny policy)."
risk: destructive
inputs_schema:
properties:
name: { type: string, description: "Address group name" }
members: { type: string, description: "Comma-separated address object names that become the group's members" }
vdom: { type: string, description: "VDOM override" }
required: [name, members]
outputs_schema: { properties: {} }
- id: list_address_groups
name: fortigate-list-firewall-address-groups
description: "List firewall address groups (optionally a single one by name)."
risk: read
inputs_schema:
properties:
name: { type: string, description: "Optional address group name to fetch a single entry" }
vdom: { type: string, description: "VDOM override" }
required: []
outputs_schema: { properties: {} }
- id: list_policies
name: fortigate-list-firewall-policies
description: "List IPv4 firewall policies (optionally a single one by policy id)."
risk: read
inputs_schema:
properties:
policy_id: { type: string, description: "Optional policy id to fetch a single entry" }
vdom: { type: string, description: "VDOM override" }
required: []
outputs_schema: { properties: {} }
- id: list_services
name: fortigate-list-firewall-services
description: "List custom firewall services (optionally a single one by name)."
risk: read
inputs_schema:
properties:
name: { type: string, description: "Optional service name to fetch a single entry" }
vdom: { type: string, description: "VDOM override" }
required: []
outputs_schema: { properties: {} }
- id: test_connection
name: fortigate-test-connection
description: "Verify connectivity and the API token (used by the Test button)."
risk: read
inputs_schema:
properties: {}
required: []
outputs_schema: { properties: {} }