mcpbeat

Secops Investigate

google/secops-investigate

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

1k tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
515
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/google/mcp-security --skill secops-investigate

The instruction itself

11 sections, as written by the author

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.

  • Check Availability: Look for Remote tools (e.g., list_cases, udm_search) first. If unavailable, use Local tools (e.g., list_cases, search_security_events).
  • Reference Mapping: Use extensions/google-secops/TOOL_MAPPING.md to find the correct tool for each capability.
  • Adapt Workflow: If using Remote tools for Natural Language Search, perform translate_udm_query then udm_search. If using Local tools, use search_security_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: ${FILE_HASH}, ${CASE_ID}.

Steps:

  • Context:
  • Remote: get_case + list_case_alerts.
  • Local: get_case_full_details.
  • SIEM Prevalence:
  • Remote: summarize_entity (hash).
  • Local: lookup_entity (hash).
  • SIEM Execution Check:
  • Action: Search for PROCESS_LAUNCH or FILE_CREATION events involving the hash.
  • Query: target.file.sha256 = "FILE_HASH" OR target.file.md5 = "FILE_HASH"
  • Remote: udm_search (using UDM query).
  • Local: search_udm (using UDM query).
  • Identify ${AFFECTED_HOSTS}.
  • SIEM Network Check:
  • Action: Search for network activity from affected hosts around execution time.
  • Query: principal.process.file.sha256 = "FILE_HASH"
  • Remote: udm_search.
  • Local: search_udm.
  • Identify ${NETWORK_IOCS}.
  • Enrichment: Execute Common Procedure: Enrich IOC for network IOCs.
  • Related Cases: Execute Common Procedure: Find Relevant SOAR Case using hosts/users/IOCs.
  • 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 |

  • Document: Execute Common Procedure: Document in SOAR.
  • Report: Optionally Execute Common Procedure: Generate Report File.

Lateral Movement Investigation (PsExec/WMI)

Objective: Investigate signs of lateral movement (PsExec, WMI abuse).

Inputs: ${TIME_FRAME_HOURS}, ${TARGET_SCOPE}.

Steps:

  • Technique Research: Review MITRE ATT&CK techniques T1021.002 (SMB/Windows Admin Shares) and T1047 (WMI).
  • SIEM Queries:
  • PsExec Service Installation:
  • metadata.product_event_type = "ServiceInstalled" AND target.process.file.full_path CONTAINS "PSEXESVC.exe"
  • PsExec Execution:
  • target.process.file.full_path CONTAINS "PSEXESVC.exe"
  • WMI Process Creation:
  • metadata.event_type = "PROCESS_LAUNCH" AND principal.process.file.full_path = "C:\\Windows\\System32\\wbem\\WmiPrvSE.exe" AND target.process.file.full_path IN ("cmd.exe", "powershell.exe")
  • WMI Remote Execution:
  • principal.process.command_line CONTAINS "wmic" AND principal.process.command_line CONTAINS "/node:" AND principal.process.command_line CONTAINS "process call create"
  • Execute:
  • Remote: udm_search.
  • Local: search_udm.
  • Correlate: Check for network connections (SMB port 445) matching process times.
  • Enrich: Execute Common Procedure: Enrich IOC for involved IPs/Hosts.
  • Document: Execute Common Procedure: Document in SOAR.

Create Investigation Report

Objective: Consolidate findings into a formal report.

Inputs: ${CASE_ID}.

Steps:

  • Gather Context:
  • Remote: get_case + list_case_comments.
  • Local: get_case_full_details.
  • Identify key entities.
  • Synthesize: Combine findings from SIEM, IOC matches, and case history.
  • Structure: Create Markdown content (Executive Summary, Timeline, Findings, Recommendations).
  • Diagram: Generate a Mermaid sequence diagram of the investigation.
  • Redaction: CRITICAL: Confirm no sensitive PII/Secrets in report.
  • Generate File: Execute Common Procedure: Generate Report File.
  • Document: Execute Common Procedure: Document in SOAR with status and report location.

Common Procedures

Enrich IOC (SIEM Prevalence)

Steps:

  • SIEM Summary: summarize_entity (Remote) or lookup_entity (Local).
  • IOC Match: get_ioc_match (Remote) or get_ioc_matches (Local).
  • Return combined findings.

Find Relevant SOAR Case

Steps:

  • Search: list_cases with filters for entity values.
  • Return list of ${RELEVANT_CASE_IDS}.

Document in SOAR

Steps:

  • Post: create_case_comment (Remote) or post_case_comment (Local).

Generate Report File

Tool: write_file (Agent Capability)

Steps:

  • Construct filename: reports/${REPORT_TYPE}_${SUFFIX}_${TIMESTAMP}.md.
  • Write content to file using write_file.
  • Return path.

How to use it

Copy the folder

Take google/secops-investigate from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.