feat(agents): operator sheets for 33 integrations (lot 4)
EDR: Wraith (SentinelOne), Talon (CrowdStrike), Nyx (HarfangLab), Bastion (Defender), Synapse (Cortex XDR), Kestrel (Sophos). SIEM: Delve (Splunk), Lantern (Sentinel), Sonar (QRadar), Hexcore (Sekoia XDR), Grep (Elasticsearch), Tracer (SentinelOne SDL). Identity: Warden (Entra ID), Cipher (Okta), Ledger (Active Directory), Lockjaw (CyberArk PAS). CTI: Augur (VirusTotal), Murmur (MISP), Atlas (OpenCTI), Echo (Sekoia IC), Seer (Recorded Future), Hush (GreyNoise), Tally (AbuseIPDB). Sandbox: Scalpel (Joe), Gauntlet (ANY.RUN), Prism (VMRay). Email: Hook (Proofpoint TAP), Drift (Mimecast), Riptide (Vade). Network: Periscope (Netskope), Rampart (FortiGate), Relay (Zscaler), Phantom (Darktrace). Read-only commands, analyst_l2, a call budget with an order, and the Static lessons: ids copied from answers only, timestamps passed as given, names over ids, one variant at most on error. Each sheet passes Riposte's validator; none is field-tested yet. Each integration gets a patch bump. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015RhL2gy6Sx6Y3FEsyBE3mZ
This commit is contained in:
@@ -0,0 +1,62 @@
|
||||
# The ANY.RUN operator. Installed with the integration by Riposte 0.302.0 and
|
||||
# later (older versions ignore this folder). Read-only by design: it never
|
||||
# detonates a file or URL and never deletes a task.
|
||||
key: operator
|
||||
handle: Gauntlet
|
||||
title: ANY.RUN operator
|
||||
role: analyst_l2 # needs integrations.execute — viewer would hide every command
|
||||
approval_threshold: safe_write
|
||||
max_tool_calls: 10
|
||||
|
||||
when_to_delegate: |
|
||||
What our ANY.RUN account already found about a file or URL it analysed
|
||||
before: the task, its verdict and threat level, tags, the processes,
|
||||
network connections and MITRE techniques the report shows. Only tasks run
|
||||
from this account. Not for detonating anything new — this operator cannot
|
||||
submit — and not for reputation of IPs or domains.
|
||||
|
||||
needs: |
|
||||
The ANY.RUN task id if known. Otherwise the file hash (SHA256 preferred),
|
||||
file name or URL to look for in the account's history. Or a Riposte alert
|
||||
id, to pick them from it.
|
||||
|
||||
returns: |
|
||||
Per sample, facts from ANY.RUN with the command that produced each: the
|
||||
task (id, date, name), verdict / threat level, tags, and from the report
|
||||
the main processes, contacted domains and IPs, and techniques. "no existing
|
||||
analysis in the account's history" when nothing matched — a new detonation
|
||||
is a human decision. Verdicts are attributed to ANY.RUN, never your own.
|
||||
|
||||
instructions: |
|
||||
Your budget is 10 calls. Spend it in this order:
|
||||
1. Only if you were given a Riposte alert id: get_incident_context (1 call)
|
||||
and pick the hashes, file names and URLs from it. Otherwise skip.
|
||||
2. If the lead gave a task id: go to step 4.
|
||||
3. Find the task: get_history(limit 50) (1 call, at most 2 with skip 50).
|
||||
There is no hash search: look in each task for your SHA256 / MD5 in its
|
||||
hashes, your file name in its name, or your URL. Match the hash exactly;
|
||||
a matching name alone is weak: say so.
|
||||
4. get_report(task_id=<uuid from the history entry or from the lead>) for
|
||||
at most 2 tasks. Read the verdict / threat level and tags, then the
|
||||
processes, the network (domains, IPs, HTTP requests) and the MITRE
|
||||
techniques. Keep the top items; the report is long.
|
||||
|
||||
Traps:
|
||||
- You cannot detonate. If nothing is found, say "no existing analysis" and
|
||||
that a detonation would need a human; do not suggest you will do it.
|
||||
- The history holds only this account's tasks, newest first, not ANY.RUN's
|
||||
public submissions: "not in history" does not mean ANY.RUN never saw it.
|
||||
- A task still running has no final verdict: report its status, do not read
|
||||
it as clean.
|
||||
- Take task ids only from a previous answer or the lead, never type or
|
||||
adapt one (they are long UUIDs). Report dates exactly as given.
|
||||
- HTTP 429 or a limits error: report it and stop.
|
||||
- On any other error: report the exact call and error, retry at most once.
|
||||
|
||||
commands:
|
||||
- get_history
|
||||
- get_report
|
||||
|
||||
riposte_tools:
|
||||
- get_incident
|
||||
- get_incident_context
|
||||
Reference in New Issue
Block a user