mitre-attack

Map OpenTide object signals to MITRE ATT&CK techniques with a local index.

4|1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/OpenTideHQ/AgentTide --skill mitre-attack-opentidehq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mitre-attack
Source: https://github.com/OpenTideHQ/AgentTide/tree/main/skills/mitre-attack
Command: npx skills add https://github.com/OpenTideHQ/AgentTide --skill mitre-attack-opentidehq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Mapping adversary behavior to ATT&CK and maintaining a locally searchable technique index for OpenTide objects ensures consistency and reduces mapping errors across TVM, DOM, and MDR.

Core Features & Use Cases

  • Local ATT&CK technique index with IDs and tactics from MITRE ATT&CK v19.
  • Tactic, technique, sub-technique mapping guidance for OpenTide objects; version pinning and revocation handling.
  • Use Case: Align threat signals to ATT&CK techniques for threat hunting, detection engineering, and reporting, including multi-technique chaining.

Quick Start

Look up technique IDs for a given OpenTide signal and verify parent/sub-technique mappings against ATT&CK v19.

Frequently Asked Questions about mitre-attack

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

FAQPage Schema
How do I map threat hunting signals to MITRE ATT&CK techniques?

Map threat hunting signals to MITRE ATT&CK techniques by linking OpenTide object signals to specific technique IDs and verifying parent/sub-technique mappings against ATT&CK v19. This ensures consistent tactic assignment and platform data-source alignment.

What is the best way to maintain a local ATT&CK technique index for TVM and MDR objects?

Maintain a local ATT&CK technique index for TVM and MDR objects by storing current ATT&CK data in Enterprise-Techniques.md, enabling precise lookups of technique IDs and tactics without relying on external lookups during detection engineering.

Does this ATT&CK mapping approach support technique versioning and revocation handling?

ATT&CK mapping supports technique versioning using MITRE ATT&CK v19 and handles revocation by guiding technique assignment, ensuring deprecated or revoked techniques are properly managed across OpenTide objects.

Can I chain multiple ATT&CK techniques together for a single threat vector?

Multi-technique chaining is supported for threat-vector mappings across TVM, DOM, and MDR objects, allowing you to link several ATT&CK techniques to model complex adversary behavior and campaign sequences.

Do I need current ATT&CK data files to use this technique mapping process?

Current ATT&CK data in references/Enterprise-Techniques.md is required, along with frontmatter containing name and description, to execute precise technique mappings and ensure the local index reflects the latest v19 techniques.

Why does my ATT&CK mapping fail when assigning tactics to OpenTide objects?

ATT&CK mapping fails when clear mapping rules for tactic assignment and platform data-source alignment are missing, or when the local Enterprise-Techniques.md file lacks current v19 technique data. Verify frontmatter and data-source alignment to resolve errors.