Write a security report for a chosen audience - technical report, executive summary, or one-page board brief with RED/YELLOW/GREEN risk posture, key metrics, top 3 actions and 30/60/90 day trend. Use when asked for a report, summary, board brief, board report or risk posture report over cases and findings.
Enrich the indicators of compromise (IPs, domains, hashes, URLs) in a finding. Read this before looking up any IOC so the enrichment checks memory first, uses every intel source you hold in parallel, and states provenance and confidence per source.
Grade a periodic outbound flow as c2, suspicious, or benign-periodic. Read this when rawdata shows a repeating connection and you must separate a beacon from NTP, an update check, a monitoring agent, or telemetry.
Give a reported email a verdict, the lure, and the first action. Read this for a user-reported message, suspicious mail, or any finding that is an email.
Judge whether one internal RDP (Remote Desktop) session is lateral movement or an administrator doing their job. Read this for a finding on port 3389 or technique T1021.001 before deciding lateral-movement, suspicious, or expected-admin.
Check or add ATT&CK technique ids on a finding by grounding each id in an observable. Read this when a triage, investigation, or correlation agent is checking or adding technique ids on a finding.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: