ioc-export

Export IOC collections to CSV, STIX 2.1, OpenIOC, and MISP bundles.

15|5|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Liberty91LTD/cti-skills --skill ioc-export
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ioc-export
Source: https://github.com/Liberty91LTD/cti-skills/tree/main/skills/ioc-export
Command: npx skills add https://github.com/Liberty91LTD/cti-skills --skill ioc-export

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

IOC export formats and procedures. CSV, STIX 2.1, OpenIOC, MISP. Handles format conversion and packaging.

Core Features & Use Cases

  • Export formats supported: CSV, STIX 2.1, OpenIOC, MISP.
  • Format conversion and packaging for sharing threat intelligence.
  • Use cases include generating standardized IOC bundles for SIEM imports, threat intel portals, and archival storage.

Quick Start

Invoke the export workflow to generate CSV, STIX 2.1, OpenIOC, or MISP bundles from your IOC collection.

Frequently Asked Questions about ioc-export

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

FAQPage Schema
How do I export IOCs to STIX 2.1 format for threat intelligence sharing?

To export IOCs to STIX 2.1, invoke the export workflow with your IOC collection. The process enforces STIX 2.1 format compliance, applies field mappings, and packages valid STIX artifacts for threat-intelligence sharing and analysis.

What is the best way to convert an IOC collection into a MISP bundle?

The best way to convert an IOC collection into a MISP bundle is using an export workflow that enforces MISP format compliance and packaging rules. This generates valid MISP bundles for threat-intelligence portals and incident response workflows.

Can I generate a CSV file of indicators of compromise for SIEM imports?

Yes, you can generate a CSV file of indicators of compromise for SIEM imports. The export workflow converts IOC collections into CSV format by applying field mappings and packaging rules to produce valid, structured export artifacts.

Does the IOC export process support OpenIOC format for incident response?

Yes, the IOC export process fully supports OpenIOC format for incident response. It applies field mappings and packaging rules to convert your IOC collection into valid OpenIOC artifacts suitable for archival pipelines and threat-intelligence workflows.

What are the limitations of exporting threat intelligence to standardized formats?

Exporting threat intelligence requires strict format compliance, field mappings, and packaging rules for valid artifacts. Limitations depend on the target format constraints, meaning you must ensure your source IOC collection contains the required fields for CSV, STIX, OpenIOC, or MISP conversion.

When do I need to convert IOCs into standardized formats like STIX or OpenIOC?

You need to convert IOCs into standardized formats like STIX or OpenIOC when sharing threat intelligence across platforms, importing indicators into SIEMs, populating threat intel portals, or archiving incident response data in compliant pipelines.