ioc-development

Extract and validate atomic, computed, and behavioral indicators from incident data.

6|Updated May 30, 2026
One-click install
npx skills add https://github.com/jassics/awesome-claude-security --skill ioc-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ioc-development
Source: https://github.com/jassics/awesome-claude-security/tree/main/plugins/dfir/skills/ioc-development
Command: npx skills add https://github.com/jassics/awesome-claude-security --skill ioc-development

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users extract and operationalize indicators (IOCs) and behaviors (IOAs) from incidents or samples, preparing them for detection, blocking, and intel sharing.

Core Features & Use Cases

  • IOC Extraction: Extract atomic, computed, and behavioral indicators from incident findings or samples.
  • Validation: Filter out benign indicators to avoid false positives.
  • Prioritization: Emphasize behavioral indicators for durable defense.
  • Operationalization: Prepare indicators for detection, blocking, and intel sharing, with support for STIX-friendly output.
  • Use Case: After an investigation, use this Skill to turn findings into defensive value by generating a structured indicator set.

Quick Start

Extract indicators from the sample 'malware-analysis-report.txt' and prepare them for intel sharing.

Frequently Asked Questions about ioc-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract IOCs and IOAs from incident data for threat intelligence sharing?

IOC and IOA extraction from incident data involves analyzing forensic findings to identify atomic, computed, and behavioral indicators. This Skill automates that extraction, validates indicators to filter false positives, and prepares them for detection, blocking, and intel sharing using STIX-friendly output formats.

What is the difference between atomic, computed, and behavioral indicators in incident response?

Atomic, computed, and behavioral indicators represent different layers of threat evidence. Atomic indicators are simple artifacts like IP addresses, computed indicators involve hashed values, and behavioral indicators capture malicious patterns, prioritizing durable defense over easily changed atomic artifacts.

How do I prepare STIX-friendly indicator sets after a malware investigation?

Preparing STIX-friendly indicator sets requires structuring extracted IOCs and IOAs for operationalization. This Skill processes your forensic analysis reports, filters benign indicators, and formats the validated behavioral and atomic indicators into structured outputs for threat intelligence sharing.

Can I validate extracted IOCs to filter out benign indicators and reduce false positives?

Validating extracted IOCs to filter benign indicators is a core feature of this Skill. It automatically processes incident findings to remove false positives, ensuring that only actionable atomic, computed, and behavioral indicators are prioritized for detection and blocking workflows.

Do I need forensic findings or malware samples to start extracting IOAs and IOCs?

Forensic findings or malware samples are required as input to start extracting IOAs and IOCs. The Skill requires analysis of these incident data sources to accurately identify and operationalize atomic, computed, and behavioral indicators for your threat intelligence workflows.

Why prioritize behavioral indicators over atomic IOCs for durable threat defense?

Prioritizing behavioral indicators over atomic IOCs provides durable threat defense because behaviors are harder for attackers to modify than simple artifacts. This Skill emphasizes behavioral IOAs during extraction to ensure your detection mechanisms remain effective against evolving threats.