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

138 lines
5.8 KiB
YAML

id: misp
name: MISP
version: 1.1.0
description: "MISP (threat-intelligence platform, REST API) — search events and attributes, read and create events, add attributes, tag events, add sightings, publish and delete events. API-key authentication; stdlib-only, no extra Python dependencies. Works with any MISP instance."
changelog: "1.1.0 — Declare the risk tier on the 6 commands that carried none: 4 safe_write, 2 destructive. An unset risk is read as destructive by the agent approval gate, so the 4 that only annotate sat behind the same prompt as the ones that change the estate. | 1.0.0 — Initial release: event/attribute search, event read/create/publish/delete, attribute add, event tagging and sightings."
category: enrichment
# Per-instance configuration. The API key (auth key) is sent in the
# 'Authorization' header. Set insecure for MISP instances with a self-signed cert.
config_schema:
properties:
server_url:
type: string
description: "MISP instance URL (e.g. https://misp.example.com)"
api_key:
type: string
description: "MISP API authentication key"
x-soar-sensitive: true
insecure:
type: boolean
description: "Trust any TLS certificate (not secure)"
default: false
required:
- server_url
- api_key
commands:
- id: search_events
name: misp-search-events
description: "Search events with MISP REST-search filters (returns matching events)."
risk: read
inputs_schema:
properties:
value: { type: string, description: "Attribute value to match" }
type: { type: string, description: "Attribute type filter (e.g. ip-dst, domain, sha256)" }
tags: { type: string, description: "Comma-separated tags" }
limit: { type: number, description: "Maximum events (default 25)" }
filter_json: { type: string, description: "Raw restSearch filter as a JSON object (advanced; merged last)" }
required: []
outputs_schema: { properties: {} }
- id: search_attributes
name: misp-search-attributes
description: "Search attributes with MISP REST-search filters."
risk: read
inputs_schema:
properties:
value: { type: string, description: "Attribute value to match" }
type: { type: string, description: "Attribute type filter" }
category: { type: string, description: "Attribute category filter" }
tags: { type: string, description: "Comma-separated tags" }
limit: { type: number, description: "Maximum attributes (default 25)" }
filter_json: { type: string, description: "Raw restSearch filter as a JSON object (advanced; merged last)" }
required: []
outputs_schema: { properties: {} }
- id: get_event
name: misp-get-event
description: "Get a full event by ID or UUID."
risk: read
inputs_schema:
properties:
event_id: { type: string, description: "Event ID or UUID" }
required: [event_id]
outputs_schema: { properties: {} }
- id: create_event
name: misp-create-event
description: "Create a new event."
risk: safe_write
inputs_schema:
properties:
info: { type: string, description: "Event description/info" }
distribution: { type: number, description: "Distribution level 0-4 (default 0 = your org only)" }
threat_level_id: { type: number, description: "Threat level 1 (high) - 4 (undefined), default 4" }
analysis: { type: number, description: "Analysis state 0 (initial) - 2 (completed), default 0" }
published: { type: boolean, description: "Publish immediately (default false)" }
required: [info]
outputs_schema: { properties: {} }
- id: add_attribute
name: misp-add-attribute
description: "Add an attribute (indicator) to an event."
risk: safe_write
inputs_schema:
properties:
event_id: { type: string, description: "Event ID" }
type: { type: string, description: "Attribute type (e.g. ip-dst, domain, url, sha256)" }
value: { type: string, description: "Attribute value" }
category: { type: string, description: "Attribute category (e.g. Network activity)" }
to_ids: { type: boolean, description: "Mark the attribute for IDS export (default true)" }
comment: { type: string, description: "Comment" }
required: [event_id, type, value]
outputs_schema: { properties: {} }
- id: add_tag_to_event
name: misp-add-tag-to-event
description: "Attach a tag to an event."
risk: safe_write
inputs_schema:
properties:
event_id: { type: string, description: "Event ID or UUID" }
tag: { type: string, description: "Tag name (e.g. tlp:amber)" }
required: [event_id, tag]
outputs_schema: { properties: {} }
- id: add_sighting
name: misp-add-sighting
description: "Add a sighting for an attribute value."
risk: safe_write
inputs_schema:
properties:
value: { type: string, description: "Attribute value that was sighted" }
sighting_type: { type: number, description: "0 = sighting, 1 = false positive, 2 = expiration (default 0)" }
required: [value]
outputs_schema: { properties: {} }
- id: publish_event
name: misp-publish-event
description: "Publish an event."
risk: destructive
inputs_schema:
properties:
event_id: { type: string, description: "Event ID" }
required: [event_id]
outputs_schema: { properties: {} }
- id: delete_event
name: misp-delete-event
description: "Delete an event."
risk: destructive
inputs_schema:
properties:
event_id: { type: string, description: "Event ID" }
required: [event_id]
outputs_schema: { properties: {} }
- id: test_connection
name: misp-test-connection
description: "Verify connectivity and the API key (used by the Test button)."
risk: read
inputs_schema:
properties: {}
required: []
outputs_schema: { properties: {} }