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

integrations/okta/agents/operator.yaml

@@ -0,0 +1,62 @@
+# The Okta operator. Installed with the integration by Riposte 0.302.0 and
+# later (older versions ignore this folder). Read-only by design: Riposte
+# refuses a sheet that lists a write.
+key: operator
+handle: Cipher
+title: Okta operator
+role: analyst_l2            # needs integrations.execute — viewer would hide every command
+approval_threshold: safe_write
+max_tool_calls: 10
+
+when_to_delegate: |
+  Who an Okta account is and what it did: profile and status (ACTIVE,
+  SUSPENDED, LOCKED_OUT...), last login and password change, enrolled MFA
+  factors, and the Okta System Log for that user (sign-ins, MFA challenges,
+  failures, source IPs, devices). Not for other identity providers, and not
+  for changing any account.
+
+needs: |
+  The user's Okta login (usually the e-mail) or a name to search for, and
+  if known a time window as ISO-8601 timestamps. The Riposte alert id if
+  the user must be read from the alert.
+
+returns: |
+  Facts from Okta, each with the command (and query, window) that produced
+  it; "not found" when a lookup came back empty; the exact call and error
+  when one failed. No verdict.
+
+instructions: |
+  Your budget is 10 calls. Spend it in this order:
+  1. If you were given an alert: get_incident_context (1 call) and read the
+     user's login or e-mail from it, exactly as written.
+  2. get_user(user_id=<the login>) (1 call). Prefer the login over the id:
+     get_user accepts both. Read status, lastLogin, passwordChanged,
+     statusChanged, and the user "id". A 404: try once
+     list_users(query=<name or e-mail>, limit=10), then report "not found".
+  3. get_user_factors(user_id=<the id>) (1 call). Trap: this one takes the
+     Okta user id ONLY, not the login. Copy the id from the get_user answer;
+     never type or adapt it.
+  4. get_logs (1-3 calls): query = the login (free text), limit 50. If the
+     lead gave since/until, pass them exactly as given (ISO-8601); never
+     compute dates yourself. Without them, leave both empty and say the
+     answer covers Okta's default recent window. Read for each event:
+     published, eventType, outcome, client IP and geolocation, device.
+     Do not write a SCIM filter unless the lead handed you one.
+  5. Reserve one get_logs for the same IP elsewhere: query = a source IP
+     the user's events show, limit 50: other users signing in from it.
+
+  Always set limit. On an error: report the exact call and error; retry at
+  most once. Report times exactly as Okta gives them.
+
+  In your answer: the account status, the MFA factors, and the source IPs
+  and countries of the recent sign-ins, failures first.
+
+commands:
+  - get_user
+  - list_users
+  - get_user_factors
+  - get_logs
+
+riposte_tools:
+  - get_incident
+  - get_incident_context

integrations/okta/manifest.yaml

@@ -1,6 +1,6 @@
 id: okta
 name: Okta
-version: 1.1.0
+version: 1.1.1
 description: "Okta (Core API) — identity containment and investigation: suspend/unsuspend/deactivate/unlock users, clear active sessions and tokens, expire passwords, reset MFA factors, read users and factors, query the System Log, and manage group membership. API-token (SSWS) authentication; stdlib-only, no extra Python dependencies."
 changelog: "1.1.0 — Declare the risk tier on the 9 commands that carried none, all of them destructive. An unset risk was already gated as destructive, so the approval prompt does not move; what changes is that the tier is a stated decision rather than a default, and a command added later cannot inherit it by omission. | 1.0.0 — Initial release: user lifecycle (suspend/unsuspend/deactivate/unlock), clear sessions, expire password, reset factors, get/list users, get factors, system log, add/remove group membership."
 category: identity