f3nris
45e9cbd269
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>
90 lines
3.3 KiB
YAML
90 lines
3.3 KiB
YAML
id: datadog
|
|
name: Datadog
|
|
version: 1.1.0
|
|
description: "Datadog (API v1/v2) — observability and monitoring: search logs, list and read monitors, submit and list events. API-key + Application-key authentication; stdlib-only, no extra Python dependencies."
|
|
changelog: "1.1.0 — Declare the risk tier on the 1 command that carried none: 1 safe_write. 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: search logs, list/get monitors, submit event, list events."
|
|
category: siem
|
|
|
|
# Per-instance configuration. Auth uses the 'DD-API-KEY' and 'DD-APPLICATION-KEY'
|
|
# headers. site selects the API host (e.g. datadoghq.com, datadoghq.eu, us5.datadoghq.com).
|
|
config_schema:
|
|
properties:
|
|
api_key:
|
|
type: string
|
|
description: "Datadog API key"
|
|
x-soar-sensitive: true
|
|
app_key:
|
|
type: string
|
|
description: "Datadog Application key"
|
|
x-soar-sensitive: true
|
|
site:
|
|
type: string
|
|
description: "Datadog site (default datadoghq.com)"
|
|
default: "datadoghq.com"
|
|
required:
|
|
- api_key
|
|
- app_key
|
|
|
|
commands:
|
|
- id: search_logs
|
|
name: datadog-search-logs
|
|
description: "Search logs."
|
|
risk: read
|
|
inputs_schema:
|
|
properties:
|
|
query: { type: string, description: "Log search query (e.g. 'service:web status:error')" }
|
|
from_time: { type: string, description: "From time (e.g. now-1h)" }
|
|
to_time: { type: string, description: "To time (e.g. now)" }
|
|
limit: { type: number, description: "Max logs (default 50)" }
|
|
required: [query]
|
|
outputs_schema: { properties: {} }
|
|
- id: list_monitors
|
|
name: datadog-list-monitors
|
|
description: "List monitors."
|
|
risk: read
|
|
inputs_schema:
|
|
properties:
|
|
tag: { type: string, description: "Optional monitor tag filter" }
|
|
required: []
|
|
outputs_schema: { properties: {} }
|
|
- id: get_monitor
|
|
name: datadog-get-monitor
|
|
description: "Get a single monitor by ID."
|
|
risk: read
|
|
inputs_schema:
|
|
properties:
|
|
monitor_id: { type: string, description: "Monitor ID" }
|
|
required: [monitor_id]
|
|
outputs_schema: { properties: {} }
|
|
- id: submit_event
|
|
name: datadog-submit-event
|
|
description: "Post an event to the Datadog event stream."
|
|
risk: safe_write
|
|
inputs_schema:
|
|
properties:
|
|
title: { type: string, description: "Event title" }
|
|
text: { type: string, description: "Event body" }
|
|
tags: { type: string, description: "Comma-separated tags" }
|
|
alert_type: { type: string, description: "info, warning, error, or success (default info)" }
|
|
required: [title, text]
|
|
outputs_schema: { properties: {} }
|
|
- id: list_events
|
|
name: datadog-list-events
|
|
description: "List events in a time window."
|
|
risk: read
|
|
inputs_schema:
|
|
properties:
|
|
start: { type: number, description: "Start POSIX timestamp (seconds)" }
|
|
end: { type: number, description: "End POSIX timestamp (seconds)" }
|
|
required: [start, end]
|
|
outputs_schema: { properties: {} }
|
|
|
|
- id: test_connection
|
|
name: datadog-test-connection
|
|
description: "Verify the API/app keys (used by the Test button)."
|
|
risk: read
|
|
inputs_schema:
|
|
properties: {}
|
|
required: []
|
|
outputs_schema: { properties: {} }
|