菜单
Search for existing cases related to specific indicators or entities. Use to find correlation with other investigations before starting new analysis. Takes search terms and returns matching case IDs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Perform exhaustive analysis of a critical IOC. Use when an IOC needs Tier 2+ investigation beyond basic enrichment - includes GTI pivoting, deep SIEM searches, correlation with related entities, and threat attribution. For escalated IOCs requiring comprehensive investigation.
Complete Tier 1 triage workflow. Orchestrates the full alert triage process: check-duplicates, triage-alert, enrich-ioc for each entity, and either close (FP/BTP) or escalate (TP/Suspicious). Use for end-to-end alert processing.
Complete Tier 2 investigation workflow. Orchestrates deep investigation of escalated cases: deep-dive-ioc, correlate-ioc, specialized triage (malware/login), pivot-on-ioc, and generate comprehensive report. Use for escalated cases requiring thorough analysis.
Check for duplicate or similar cases. Use before deep analysis to avoid investigating the same incident twice. Takes a CASE_ID and returns list of similar cases.
Close a case or alert with proper reason and documentation. Use when triage determines an alert is FP/BTP or investigation is complete. Requires artifact ID, type, closure reason, and root cause.
Check for existing SIEM alerts and case management entries related to IOCs. Use to understand if an indicator has triggered previous alerts or is part of ongoing investigations. Takes IOC list and returns related alerts and cases.
| name | find-relevant-case |
| description | Search for existing cases related to specific indicators or entities. Use to find correlation with other investigations before starting new analysis. Takes search terms and returns matching case IDs. |
| required_roles | {"soar":"roles/chronicle.editor"} |
| personas | ["tier1-analyst","tier2-analyst","tier3-analyst","incident-responder"] |
Identify existing cases that may be related to the current investigation based on IOCs, hostnames, usernames, or other entities.
SEARCH_TERMS - List of values to search for (e.g., ["198.51.100.10", "mikeross-pc", "jsmith"])CASE_STATUS_FILTER - Filter by status: "Opened", "Closed" (default: "Opened")TIME_FRAME_HOURS - Lookback period for case creation/updateMAX_RESULTS - Maximum cases to returnBuild a filter for list_cases based on search terms and filters.
Note: The list_cases tool may have limited ability to search within case entities. If direct entity search isn't supported, use broader filters and refine results.
secops-soar.list_cases(
filter=constructed_filter,
limit=MAX_RESULTS
)
Extract case IDs and basic details (DisplayName, Priority) from results.
If too many results, use get_case_full_details on a subset to verify entity presence:
secops-soar.get_case_full_details(case_id=candidate_case_id)
| Output | Description |
|---|---|
RELEVANT_CASE_IDS | List of case IDs that match the search |
RELEVANT_CASE_SUMMARIES | Brief summaries (ID, name, priority) |
FIND_CASE_STATUS | Success/failure status of the search |
The list_cases tool may not support direct entity searching. Alternatives: