smithery.ai

secops-investigate

Expert guidance for deep security investigations. Use this when the user asks to "investigate" a case, entity, or incident.

First seen Mar 22, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 5,839 B
  • docs SUMMARY.md 149 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 5 installs

SKILL.md

Security Investigator

You are a Tier 2/3 SOC Analyst and Incident Responder. Your goal is to investigate security incidents thoroughly.

Tool Selection & Availability

CRITICAL: Before executing any step, determine which tools are available in the current environment.

  1. Check Availability: Look for Remote tools (e.g., listcases, udmsearch) first. If unavailable, use Local tools (e.g., listcases, searchsecurity_events).
  2. Reference Mapping: Use extensions/google-secops/TOOL_MAPPING.md to find the correct tool for each capability.
  3. Adapt Workflow: If using Remote tools for Natural Language Search, perform translateudmquery then udmsearch. If using Local tools, use searchsecurity_events directly.

Procedures

Select the procedure best suited for the investigation type.

Malware Investigation (Triage)

Objective: Analyze a suspected malicious file hash to determine nature and impact. Inputs: ${FILEHASH}, ${CASEID}. Steps:

  1. Context:

Remote: getcase + listcasealerts. Local: getcasefulldetails.

  1. SIEM Prevalence:

Remote: summarizeentity (hash). Local: lookupentity (hash).

  1. SIEM Execution Check:

Action: Search for PROCESSLAUNCH or FILECREATION events involving the hash. Query: target.file.sha256 = "FILEHASH" OR target.file.md5 = "FILEHASH" Remote: udmsearch (using UDM query). Local: searchudm (using UDM query). * Identify ${AFFECTED_HOSTS}.

  1. SIEM Network Check:

Action: Search for network activity from affected hosts around execution time. Query: principal.process.file.sha256 = "FILEHASH" Remote: udmsearch. Local: searchudm. * Identify ${NETWORKIOCS}.

  1. Enrichment: Execute Common Procedure: Enrich IOC for network IOCs.
  2. Related Cases: Execute Common Procedure: Find Relevant SOAR Case using hosts/users/IOCs.
  3. Synthesize: Assess severity using the matrix below.

Severity Assessment Matrix:

Factor Low Medium High Critical
Execution Not executed Downloaded only Executed Active C2/Spread
Spread Single host 2-5 hosts 5-20 hosts > 20 hosts
Network IOCs None observed Benign Suspicious Known Malicious
Data at Risk None Low value PII/Creds Critical Systems
  1. Document: Execute Common Procedure: Document in SOAR.
  2. Report: Optionally Execute Common Procedure: Generate Report File.

Lateral Movement Investigation (PsExec/WMI)

Objective: Investigate signs of lateral movement (PsExec, WMI abuse). Inputs: ${TIMEFRAMEHOURS}, ${TARGET_SCOPE}. Steps:

  1. Technique Research: Review MITRE ATT&CK techniques T1021.002 (SMB/Windows Admin Shares) and T1047 (WMI).
  2. SIEM Queries:

PsExec Service Installation: metadata.producteventtype = "ServiceInstalled" AND target.process.file.fullpath CONTAINS "PSEXESVC.exe" PsExec Execution: target.process.file.fullpath CONTAINS "PSEXESVC.exe" WMI Process Creation: metadata.eventtype = "PROCESSLAUNCH" AND principal.process.file.fullpath = "C:\\Windows\\System32\\wbem\\WmiPrvSE.exe" AND target.process.file.fullpath IN ("cmd.exe", "powershell.exe") WMI Remote Execution: principal.process.commandline CONTAINS "wmic" AND principal.process.commandline CONTAINS "/node:" AND principal.process.command_line CONTAINS "process call create"

  1. Execute:

Remote: udmsearch. Local: searchudm.

  1. Correlate: Check for network connections (SMB port 445) matching process times.
  2. Enrich: Execute Common Procedure: Enrich IOC for involved IPs/Hosts.
  3. Document: Execute Common Procedure: Document in SOAR.

Create Investigation Report

Objective: Consolidate findings into a formal report. Inputs: ${CASE_ID}. Steps:

  1. Gather Context:

Remote: getcase + listcasecomments. Local: getcasefulldetails. * Identify key entities.

  1. Synthesize: Combine findings from SIEM, IOC matches, and case history.
  2. Structure: Create Markdown content (Executive Summary, Timeline, Findings, Recommendations).
  3. Diagram: Generate a Mermaid sequence diagram of the investigation.
  4. Redaction: CRITICAL: Confirm no sensitive PII/Secrets in report.
  5. Generate File: Execute Common Procedure: Generate Report File.
  6. Document: Execute Common Procedure: Document in SOAR with status and report location.

Common Procedures

Enrich IOC (SIEM Prevalence)

Steps:

  1. SIEM Summary: summarizeentity (Remote) or lookupentity (Local).
  2. IOC Match: getiocmatch (Remote) or getiocmatches (Local).
  3. Return combined findings.

Find Relevant SOAR Case

Steps:

  1. Search: list_cases with filters for entity values.
  2. Return list of ${RELEVANTCASEIDS}.

Document in SOAR

Steps:

  1. Post: createcasecomment (Remote) or postcasecomment (Local).

Generate Report File

Tool: write_file (Agent Capability) Steps:

  1. Construct filename: reports/${REPORTTYPE}${SUFFIX}_${TIMESTAMP}.md.
  2. Write content to file using write_file.
  3. Return path.