From ae1effafcd2cf5eb415c5ca3eabd6c15fa2fbec4 Mon Sep 17 00:00:00 2001 From: Guillaume BOURGEOIS Date: Mon, 12 Oct 2026 07:27:36 +0000 Subject: [PATCH] rapid7-insightidr 1.14.6: narrow a log result by field, no query syntax MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit query_log_set takes only="field=value[, …]", applied to the events' fields after the search (case ignored), and says how many matched before it. Static runs a second summary of the same query restricted to what the alert is about — for a "new assets" alert, the new authentications — and names their destination assets: the first real run summarized 978 events but left the 64 new ones mixed in. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_015RhL2gy6Sx6Y3FEsyBE3mZ --- .../rapid7-insightidr/agents/operator.yaml | 5 ++++ integrations/rapid7-insightidr/manifest.yaml | 3 +- .../scripts/query_log_set.py | 28 +++++++++++++++++++ 3 files changed, 35 insertions(+), 1 deletion(-) diff --git a/integrations/rapid7-insightidr/agents/operator.yaml b/integrations/rapid7-insightidr/agents/operator.yaml index d2b52e2..ccadfbf 100644 --- a/integrations/rapid7-insightidr/agents/operator.yaml +++ b/integrations/rapid7-insightidr/agents/operator.yaml @@ -62,6 +62,11 @@ instructions: | hours_before 24, minutes_after 30 (the defaults). Other alerts: hours_before 0.5. Report the "window" field of the answer word for word, never your own reading of it. + - Then isolate what the alert is about with a second summary of the SAME + query and window, adding only "=" with a field name and + value exactly as the first summary printed them. A "new assets" alert: + only the new authentications (e.g. authentication_type= + new_authentication) — its destination assets are the answer. Name them. - "Invalid Query Syntax": report the exact query and error, no variants. - Keep at most 6 calls for logs. 5. ALWAYS call search_investigation(actor_user_name=) once, whatever diff --git a/integrations/rapid7-insightidr/manifest.yaml b/integrations/rapid7-insightidr/manifest.yaml index 8d1e764..3e60851 100644 --- a/integrations/rapid7-insightidr/manifest.yaml +++ b/integrations/rapid7-insightidr/manifest.yaml @@ -1,6 +1,6 @@ id: rapid7_insightidr name: Rapid7 InsightIDR -version: 1.14.5 +version: 1.14.6 description: "Rapid7 InsightIDR (REST API) — investigation ingestion and full lifecycle (list/get/search/create/update/assign/set-status/bulk-close), investigation alerts and Rapid7 product alerts, investigation comments (add/list), custom threat indicators (add/replace), log management and LEQL log/log-set queries with downloads, and user directory search." changelog: "1.13.2 — query_log and query_log_set: trim the quotes and spaces a pasted log or log set ID drags along, and explain the 404. A trailing quote was URL-encoded into the path and the API answered a bare \"HTTP 404 Not Found\" that named nothing. Also send both time bounds on every run: a scheduled run passes only the watermark, and the first run nothing — the window now ends now and, without a start, opens 24 hours back. | 1.13.1 — test_connection: accept an InsightIDR Essential key. Essential answers the Investigations API with a 403 that names the package, so a valid key failed its test; the test now falls back to Log Search and says which commands that package leaves out — the LEQL feeds (query_log, query_log_set) are its way to ingest detections. | 1.13.0 — Add add_comment and list_comments: the investigation comment thread is where an analyst’s reasoning lives, and a playbook had no way to write into it or read it back. The Comments API is v1-only and addresses its target by RRN — the short investigation ID the other v1 endpoints accept is rejected with a 400 that names nothing, so both commands refuse it up front. | 1.12.0 — Make the LEQL queries ingestible: query_log and query_log_set gain an ingest block, a stable event_id for dedup, a bounded page walk and a detection_name stamp, and they now read start_time as ISO-8601, UNIX seconds or milliseconds alike. A tenant whose basic detection rules only notify (email, Slack) creates no investigation and no alert an API can read, so replaying the rule's own query on a schedule is the only way its detections reach a SOAR. | 1.11.1 — Strip the whitespace out of the comma-separated filter params (statuses, priorities, sources, tags) before the URL. \"HIGH, CRITICAL\" as typed sent \" CRITICAL\" to the API, which rejects the whole call — so a priority filter written naturally fetched nothing. | 1.11.0 —Build one evidence row per alert evidence into custom:rapid7_evidence, for the table field: sortable and filterable where the Markdown summary only reads. | 1.10.0 — Render every detection key as Markdown into custom:rapid7_summary, so a layout can show what the OCSF catalogue has no field for. Map both ends of an account action, read source_json top-level scalars, drop placeholder values, and force evidences to stay an array. | 1.9.2 — Read the evidence data in both of its shapes. A parsed source states its event flat, with no source_data/custom_data wrapper, and the parser returned {} for all of them. | 1.9.1 — get_alert_process_trees: explain the 404, which the API returns with an empty body for three different situations. | 1.9.0 — Fetch each alert process tree and flatten it into ctx.process_tree, the shape the layout Process Tree block reads. Gated on the event type by default, since an authentication alert never has one. | 1.8.0 — Fetch each alert evidence at ingestion and parse it: the log line behind the alert lives in a JSON-encoded string no mapper can reach, and it is where the source and destination addresses, the account and the device actually are. | 1.7.0 — Map source/destination assets and accounts to src_endpoint, dst_endpoint, actor.user and user. A connection rule names both ends and neither is \"the host\", so an RDP-to-DC alert produced no entity at all and nothing a layout could show. | 1.6.0 — Surface region_failures: the Alert Triage API answers HTTP 200 with a partial result when it cannot reach a region, and that list was being dropped. Also report the regions seen in the RRNs against the configured one. | 1.5.0 — Flatten the whole of rule_keys_of_interest into the context. It is an open vocabulary — a process rule and an authentication rule share no keys — so the hardcoded list only covered rules already seen and left every other alert empty. | 1.4.1 — Read the alert RRN from `rrn` before `id` and drop anything not RRN-shaped: the investigation alert list also returns bare UUIDs, and one of those rejects the entire /alerts/ops/rrns batch (HTTP 400), losing every alert in the run. | 1.4.0 — Add get_investigations_full: the investigation with its alerts inlined, so it stays the unit that becomes an incident. Drop-in for list_investigations (results_path data, dedup rrn). | 1.3.0 — Add search_investigation_alerts: ingest only the alerts that belong to an investigation, with their full detection content, in 1+N+1 calls. Filtering search_alerts on investigation_rrn does not work — the term is accepted and silently matches nothing. | 1.2.1 — search_alerts: report a malformed terms_json with the input named and echoed, instead of json's bare \"Expecting value: line 1 column 1\". | 1.2.0 — Add the search_alerts OCSF mapper: rule_keys_of_interest carries the host, the process, its command line, its parent and the file hashes, so an alert-based feed indexes entities where the investigation feed indexed none. Validated against a live ABA alert. | 1.1.1 — list_alert_fields: default path_depth to 1 and expose the search filter. The V2 fields endpoint refuses an unbounded walk of the tree (\"root path with path depth greater than 1 is not supported for V2 without a search filter\"), so the bare call returned HTTP 400. | 1.1.0 — Add the Alert Triage API (/idr/at): search alerts, get an alert, its evidence, its actors and its process trees, plus the tenant's alert field catalogue. These carry the detection content the investigation endpoints do not — MITRE T-codes, matched rule keys, assets and accounts, command lines. MDR-gated. | 1.0.0 — Initial release: investigation ingestion (list_investigations) with an exhaustive OCSF mapper, 18 commands across investigations, alerts, custom threats, logs/LEQL search and users. API v1/v2 selectable per instance and per command." category: siem @@ -309,6 +309,7 @@ commands: hours_before: { type: number, description: "With anchor_time: how many hours before it the window starts (default 24)." } minutes_after: { type: number, description: "With anchor_time: how many minutes after it the window ends (default 30)." } summarize: { type: string, description: "true: return per-field counts (each field's most frequent values over every matching event, the first and last event time, and 5 sample events) instead of the raw events — what an agent should ask for. Raw events fill a model's context after a few dozen." } + only: { type: string, description: "Keep only the events whose fields match, applied after the search: \"field=value\" or \"f1=v1, f2=v2\" (all must hold, case ignored). Use a field name exactly as a previous summary printed it, e.g. authentication_type=new_authentication. No query syntax needed." } query: { type: string, description: "Valid LEQL query (no calculations: groupby/calculate are rejected by this endpoint)" } time_range: { type: string, description: "Relative time range (e.g. 1 week, 1 day). When set, start_time/end_time are not needed." } start_time: { type: string, description: "Lower bound: UNIX milliseconds, UNIX seconds or ISO-8601 — all three are accepted. Incremental fetch watermark." } diff --git a/integrations/rapid7-insightidr/scripts/query_log_set.py b/integrations/rapid7-insightidr/scripts/query_log_set.py index c9c3583..77a6cf0 100644 --- a/integrations/rapid7-insightidr/scripts/query_log_set.py +++ b/integrations/rapid7-insightidr/scripts/query_log_set.py @@ -172,6 +172,26 @@ def _fields(e): return flat +def _parse_only(v): + """"field=value, field2=value2" -> {field: value}. Applied to the events' + fields after the search, so narrowing a result needs no query syntax.""" + out = {} + for part in str(v or "").split(","): + if "=" in part: + k, val = part.split("=", 1) + if k.strip(): + out[k.strip()] = val.strip().strip("\"'") + return out + + +def _matches(fields, only): + """Every condition holds, comparing as text and ignoring case.""" + for k, want in only.items(): + if str(fields.get(k, "")).lower() != want.lower(): + return False + return True + + def _summarize(events, limit): """Counts instead of lines: per field, its most frequent values. @@ -283,9 +303,17 @@ def run(): # No fallback log id: a log set spans several logs and every event names its own. events = _identify(_collect(first, limit), "", inp.get("detection_name")) window = "%s to %s" % (_iso(start_time), _iso(end_time)) + only = _parse_only(inp.get("only")) + matched_before_filter = len(events) + if only: + events = [e for e in events if _matches(_fields(e), only)] if str(inp.get("summarize") or "").strip().lower() in ("1", "true", "yes"): out = _summarize(events, limit) + out["truncated"] = matched_before_filter >= limit out.update({"from": start_time, "to": end_time, "window": window}) + if only: + out["only"] = only + out["matched_before_only"] = matched_before_filter print(json.dumps(out)) return print(json.dumps({"events": events, "count": len(events), "from": start_time, "to": end_time,