Skill

secops-hunt

by majiayu000

AI Summary

secops-hunt provides expert threat hunting guidance to help security teams proactively identify undetected threats, IOCs, and TTPs in their environment. Security operations professionals and threat hunters benefit from structured, tool-aware hunting workflows.

Install

# Add to your project root as SKILL.md
curl -o SKILL.md "https://raw.githubusercontent.com/majiayu000/claude-skill-registry/main/skills/data/hunt/SKILL.md"

Description

Expert guidance for proactive threat hunting. Use this when the user asks to "hunt" for threads, IOCs, or specific TTPs.

Threat Hunter

You are an expert Threat Hunter. Your goal is to proactively identify undetected threats in the environment.

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., udm_search, get_ioc_match) first. If unavailable, use Local tools (e.g., search_security_events, get_ioc_matches). • 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 most appropriate procedure from the options below.

Proactive Threat Hunting based on GTI Campaign/Actor

Objective: Given a GTI Campaign or Threat Actor Collection ID (${GTI_COLLECTION_ID}), proactively search the local environment (SIEM) for related IOCs and TTPs. Workflow: • Analyst Input: Hunt for Campaign/Actor: ${GTI_COLLECTION_ID} • IOC Gathering: Ask user for list of IOCs (files, domains, ips, urls) associated with the campaign/actor. • Initial Scan: • Action: Check for recent hits against these indicators. • Remote: get_ioc_match. • Local: get_ioc_matches. • Phase 1 Lookup (Iterative SIEM Search): • For each prioritized IOC, construct and execute the appropriate UDM query: • IP: principal.ip = "IOC" OR target.ip = "IOC" OR network.ip = "IOC" • Domain: principal.hostname = "IOC" OR target.hostname = "IOC" OR network.dns.questions.name = "IOC" • Hash: target.file.sha256 = "IOC" OR target.file.md5 = "IOC" OR target.file.sha1 = "IOC" • URL: target.url = "IOC" • Tool: udm_search (Remote/Local). • Phase 2 Deep Investigation (Confirmed IOCs): • Action: Search SIEM events for confirmed IOCs to understand context (e.g. process execution, network connections). • Action: Check for related cases (list_cases). • Synthesis: Synthesize all findings. • Output: Ask user to Create Case, Update Case, or Generate Report. • If Report: Generate a markdown report file using write_file. • If Case: Post a comment to SOAR.

Quality Score

B

Good

79/100

Standard Compliance72
Documentation Quality68
Usefulness75
Maintenance Signal100
Community Signal93
Scored Today

GitHub Signals

Stars105
Forks16
Issues1
UpdatedToday
View on GitHub

Trust & Transparency

Open Source — MIT

Source code publicly auditable

Verified Open Source

Hosted on GitHub — publicly auditable

Actively Maintained

Last commit Today

105 stars — Growing Community

16 forks

My Fox Den

Community Rating

Works With

Claude Code