Communitygithub.com

biblioteca-de-patrones-de-ataque-a-partir-de-informes-cti

Analiza informes de inteligencia de amenazas cibernéticas (Mandiant, CrowdStrike, Talos, Microsoft) con stix2, mitreattack-python y spaCy para extraer comportamientos de adversarios, mapearlos con IDs de técnicas MITRE ATT&CK y construir una biblioteca STIX 2.1 de patrones de ataque con plantillas de detección. Úsalo para catalogar patrones de ataque de informes CTI para ingeniería de detección basada en amenazas, o para generar plantillas Sigma/YARA a partir de comportamientos documentados.

¿Qué es biblioteca-de-patrones-de-ataque-a-partir-de-informes-cti?

Esta habilidad permite a los agentes de IA transformar informes de inteligencia de amenazas cibernéticas (CTI) de fuentes como Mandiant, CrowdStrike, Talos y Microsoft en una biblioteca estructurada de patrones de ataque. El proceso incluye el análisis de informes en formato PDF, HTML o texto para extraer comportamientos de adversarios, el mapeo de esos comportamientos a técnicas de MITRE ATT&CK utilizando las bibliotecas `mitreattack-python` y `stix2`, y la creación de objetos STIX 2.1 Attack Pattern. Además, genera plantillas de reglas de detección (Sigma, YARA) a partir de los patrones documentados, lo que facilita la ingeniería de detección informada por amenazas. La biblioteca resultante es indexable por táctica, técnica y actor de amenaza, y se puede exportar como un bundle STIX 2.1. Es compatible con entornos que ejecutan Python 3.9+ y requiere las bibliotecas mencionadas, así como datos de MITRE ATT&CK obtenidos localmente o a través de TAXII. Esta habilidad es útil para analistas de seguridad que necesitan catalogar rápidamente técnicas adversarias a partir de informes CTI y generar firmas de detección.

Compatible con~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/building-attack-pattern-library-from-cti-reports

Preguntar en tu IA favorita

Abre un nuevo chat con esta habilidad de agente ya precargada.

Documentación

Construyendo una Biblioteca de Patrones de Ataque a partir de Informes CTI

Resumen

Los informes de inteligencia de amenazas cibernéticas (CTI) de proveedores como Mandiant, CrowdStrike, Talos y Microsoft contienen descripciones detalladas de los comportamientos de los adversarios que pueden ser extraídos, normalizados y catalogados en una biblioteca estructurada de patrones de ataque. Esta habilidad cubre el análisis de informes CTI para extraer técnicas de adversarios, el mapeo de comportamientos a IDs de técnicas de MITRE ATT&CK, la creación de objetos STIX 2.1 Attack Pattern, la construcción de una biblioteca indexable por táctica, técnica y actor de amenaza, y la generación de plantillas de reglas de detección a partir de patrones documentados.

Cuándo Usarlo

  • Al implementar o configurar capacidades de construcción de bibliotecas de patrones de ataque a partir de informes CTI en su entorno
  • Al establecer controles de seguridad alineados con requisitos de cumplimiento
  • Al construir o mejorar la arquitectura de seguridad para este dominio
  • Al realizar evaluaciones de seguridad que requieran esta implementación

Prerrequisitos

  • Python 3.9+ con las librerías stix2, mitreattack-python, spacy, requests
  • Colección de informes CTI (formato PDF, HTML o texto)
  • Datos STIX de MITRE ATT&CK (local o a través de TAXII)
  • Comprensión de la estructura de técnicas ATT&CK y convenciones de nomenclatura
  • Familiaridad con conceptos de ingeniería de detección (Sigma, YARA)

Conceptos Clave

Extracción de Patrones de Ataque

Los informes CTI describen comportamientos de adversarios en lenguaje natural. La extracción implica identificar verbos de acción y términos técnicos que se asignan a técnicas ATT&CK, reconocer nombres de herramientas y familias de malware, identificar indicadores de infraestructura y mapear secuencias de comportamientos a cadenas de ataque (fases de la cadena de eliminación).

Objetos STIX 2.1 Attack Pattern

STIX define Attack Pattern como un Objeto de Dominio Estructurado (SDO) que describe las formas en que los adversarios intentan comprometer objetivos. Cada patrón se vincula a ATT&CK a través de referencias externas, incluye fases de la cadena de eliminación (tácticas) y puede relacionarse con objetos Intrusion Set, Malware y Tool.

Generación de Reglas de Detección

Los patrones de ataque extraídos informan la ingeniería de detección al proporcionar: ejemplos de procedimientos específicos para la creación de reglas Sigma, secuencias de comportamiento para reglas de correlación, patrones de IOC para reglas YARA y Snort, y requisitos de fuentes de datos para brechas de telemetría.

Flujo de Trabajo

Paso 1: Analizar Informes CTI y Extraer Comportamientos

import re
import json
from collections import defaultdict

class CTIReportParser:
    """Parse CTI reports to extract adversary behaviors."""

    BEHAVIOR_INDICATORS = [
        "used", "executed", "deployed", "leveraged", "exploited",
        "established", "created", "modified", "downloaded", "uploaded",
        "exfiltrated", "injected", "enumerated", "spawned", "dropped",
        "persisted", "escalated", "moved laterally", "collected",
        "encrypted", "compressed", "encoded", "obfuscated",
    ]

    TOOL_PATTERNS = [
        r'\b(Cobalt Strike|Mimikatz|PsExec|BloodHound|Rubeus|Impacket)\b',
        r'\b(PowerShell|cmd\.exe|WMI|WMIC|certutil|bitsadmin)\b',
        r'\b(Metasploit|Empire|Covenant|Sliver|Brute Ratel)\b',
        r'\b(Lazagne|SharpHound|ADFind|Sharphound|Invoke-Obfuscation)\b',
    ]

    TECHNIQUE_KEYWORDS = {
        "spearphishing": "T1566",
        "phishing attachment": "T1566.001",
        "phishing link": "T1566.002",
        "powershell": "T1059.001",
        "command line": "T1059.003",
        "scheduled task": "T1053.005",
        "registry run key": "T1547.001",
        "process injection": "T1055",
        "dll side-loading": "T1574.002",
        "credential dumping": "T1003",
        "lsass": "T1003.001",
        "kerberoasting": "T1558.003",
        "pass the hash": "T1550.002",
        "remote desktop": "T1021.001",
        "smb": "T1021.002",
        "winrm": "T1021.006",
        "data staging": "T1074",
        "exfiltration over c2": "T1041",
        "dns tunneling": "T1071.004",
        "web shell": "T1505.003",
    }

    def parse_report(self, text, report_metadata=None):
        """Parse a CTI report and extract behaviors."""
        sentences = re.split(r'[.!?]\s+', text)
        behaviors = []

        for sentence in sentences:
            sentence_lower = sentence.lower()
            # Check for behavior indicators
            for indicator in self.BEHAVIOR_INDICATORS:
                if indicator in sentence_lower:
                    behavior = {
                        "sentence": sentence.strip(),
                        "action": indicator,
                        "tools": self._extract_tools(sentence),
                        "technique_hints": self._match_techniques(sentence_lower),
                    }
                    if behavior["technique_hints"]:
                        behaviors.append(behavior)
                    break

        print(f"[+] Extraídos {len(behaviors)} indicadores de comportamiento del informe")
        return behaviors

    def _extract_tools(self, text):
        """Extract tool/malware names from text."""
        tools = set()
        for pattern in self.TOOL_PATTERNS:
            matches = re.findall(pattern, text, re.IGNORECASE)
            tools.update(matches)
        return list(tools)

    def _match_techniques(self, text):
        """Match text to ATT&CK technique hints."""
        matches = []
        for keyword, tech_id in self.TECHNIQUE_KEYWORDS.items():
            if keyword in text:
                matches.append({"keyword": keyword, "technique_id": tech_id})
        return matches

parser = CTIReportParser()
sample_report = """
The threat actor used spearphishing attachments with macro-enabled documents to
gain initial access. Once inside, they executed PowerShell scripts to download
additional tooling. The actor leveraged Mimikatz to dump credentials from LSASS
memory. They then used pass the hash techniques for lateral movement via SMB
to multiple systems. Data was staged in a compressed archive and exfiltrated
over the existing C2 channel. The actor established persistence through
scheduled tasks and registry run keys.
"""
behaviors = parser.parse_report(sample_report)

Paso 2: Mapear Comportamientos a Técnicas ATT&CK

from attackcti import attack_client

class ATTACKMapper:
    def __init__(self):
        self.lift = attack_client()
        self.techniques = {}
        self._load_techniques()

    def _load_techniques(self):
        """Load all ATT&CK techniques for mapping."""
        all_techs = self.lift.get_enterprise_techniques()
        for tech in all_techs:
            tech_id = ""
            for ref in tech.get("external_references", []):
                if ref.get("source_name") == "mitre-attack":
                    tech_id = ref.get("external_id", "")
                    break
            if tech_id:
                self.techniques[tech_id] = {
                    "name": tech.get("name", ""),
                    "description": tech.get("description", "")[:500],
                    "tactics": [p.get("phase_name") for p in tech.get("kill_chain_phases", [])],
                    "platforms": tech.get("x_mitre_platforms", []),
                    "data_sources": tech.get("x_mitre_data_sources", []),
                }
        print(f"[+] Cargadas {len(self.techniques)} técnicas ATT&CK")

    def map_behaviors(self, behaviors):
        """Map extracted behaviors to ATT&CK techniques."""
        mapped = []
        for behavior in behaviors:
            for hint in behavior.get("technique_hints", []):
                tech_id = hint["technique_id"]
                if tech_id in self.techniques:
                    tech_info = self.techniques[tech_id]
                    mapped.append({
                        "technique_id": tech_id,
                        "technique_name": tech_info["name"],
                        "tactics": tech_info["tactics"],
                        "source_sentence": behavior["sentence"],
                        "tools_observed": behavior["tools"],
                        "keyword_matched": hint["keyword"],
                        "data_sources": tech_info["data_sources"],
                    })
        print(f"[+] Mapeados {len(mapped)} comportamientos a técnicas ATT&CK")
        return mapped

mapper = ATTACKMapper()
mapped_behaviors = mapper.map_behaviors(behaviors)

Paso 3: Crear Biblioteca de Patrones de Ataque STIX 2.1

from stix2 import AttackPattern, Relationship, Bundle, TLP_GREEN
from datetime import datetime

class AttackPatternLibrary:
    def __init__(self):
        self.patterns = []
        self.relationships = []

    def add_pattern_from_mapping(self, mapping, report_source="CTI Report"):
        """Create STIX Attack Pattern from mapped behavior."""
        pattern = AttackPattern(
            name=mapping["technique_name"],
            description=f"Observado: {mapping['source_sentence']}\n\n"
                        f"Herramientas: {', '.join(mapping['tools_observed']) or 'Ninguna identificada'}\n"
                        f"Fuente: {report_source}",
            external_references=[{
                "source_name": "mitre-attack",
                "external_id": mapping["technique_id"],
                "url": f"https://attack.mitre.org/techniques/{mapping['technique_id'].replace('.', '/')}/",
            }],
            kill_chain_phases=[{
                "kill_chain_name": "mitre-attack",
                "phase_name": tactic,
            } for tactic in mapping["tactics"]],
            object_marking_refs=[TLP_GREEN],
        )
        self.patterns.append(pattern)
        return pattern

    def build_library(self, mapped_behaviors, report_source="CTI Report"):
        """Build complete attack pattern library from mappings."""
        seen_techniques = set()
        for mapping in mapped_behaviors:
            tech_id = mapping["technique_id"]
            if tech_id not in seen_techniques:
                self.add_pattern_from_mapping(mapping, report_source)
                seen_techniques.add(tech_id)

        bundle = Bundle(objects=self.patterns + self.relationships)
        print(f"[+] Biblioteca: {len(self.patterns)} patrones de ataque")
        return bundle

    def export_library(self, output_file="attack_pattern_library.json"):
        bundle = Bundle(objects=self.patterns + self.relationships)
        with open(output_file, "w") as f:
            f.write(bundle.serialize(pretty=True))
        print(f"[+] Biblioteca exportada a {output_file}")

    def generate_detection_templates(self, mapped_behaviors):
        """Generate Sigma rule templates from attack patterns."""
        templates = []
        for mapping in mapped_behaviors:
            template = {
                "title": f"Detección: {mapping['technique_name']} ({mapping['technique_id']})",
                "status": "experimental",
                "description": f"Detecta {mapping['technique_name']} basado en observación de informe CTI",
                "references": [
                    f"https://attack.mitre.org/techniques/{mapping['technique_id'].replace('.', '/')}/",
                ],
                "tags": [
                    f"attack.{mapping['tactics'][0]}" if mapping['tactics'] else "attack.unknown",
                    f"attack.{mapping['technique_id'].lower()}",
                ],
                "data_sources": mapping.get("data_sources", []),
                "observed_tools": mapping.get("tools_observed", []),
                "source_context": mapping["source_sentence"],
            }
            templates.append(template)

        with open("detection_templates.json", "w") as f:
            json.dump(templates, f, indent=2)
        print(f"[+] Generadas {len(templates)} plantillas de detección")
        return templates

library = AttackPatternLibrary()
bundle = library.build_library(mapped_behaviors, "Informe CTI de Muestra")
library.export_library()
templates = library.generate_detection_templates(mapped_behaviors)

Criterios de Validación

  • Informe CTI analizado e indicadores de comportamiento extraídos
  • Comportamientos mapeados a técnicas ATT&CK con confianza
  • Objetos STIX 2.1 Attack Pattern creados con referencias adecuadas
  • Biblioteca indexable por táctica, técnica y actor de amenaza
  • Plantillas de detección generadas a partir de patrones documentados
  • Biblioteca exportable como bundle STIX para compartir

Referencias

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

abusing-dpapi-for-credential-access

Extract and decrypt Windows DPAPI-protected secrets (Credential Manager, browser logins/cookies, Wi-Fi credentials, KeePass keys) online or offline using SharpDPAPI, SharpChrome, Mimikatz, or Impacket

abusing-shadow-credentials-for-privesc

Take over Active Directory accounts by writing attacker-controlled public keys to msDS-KeyCredentialLink (Shadow Credentials) with pyWhisker, Whisker, or Certipy, then authenticate via PKINIT to recover the target

achieving-cmmc-level-2-compliance

>-

acquiring-disk-image-with-dd-and-dcfldd

Create forensically sound bit-for-bit disk images with dd or dcfldd on a Linux forensic workstation, preserving evidence integrity through hash verification (MD5/SHA) during acquisition. Use when imaging a suspect drive, USB device, or memory card for investigation, preserving volatile disk evidence during incident response, or producing a verified copy for legal or law-enforcement proceedings before any destructive analysis.

analyzing-active-directory-acl-abuse

Detect dangerous ACL misconfigurations in Active Directory using ldap3

analyzing-android-malware-with-apktool

Perform static analysis of Android APK malware using apktool for resource decompilation, jadx for Java source recovery, and androguard for manifest inspection, dangerous permission-combination detection, and identification of obfuscated code, dynamic code loading, and reflection-based API calls. Use to statically triage a suspicious APK without executing it or to build mobile malware detection rules.

analyzing-api-gateway-access-logs

Parses API Gateway access logs (AWS API Gateway, Kong, Nginx) to detect

analyzing-apt-group-with-mitre-navigator

Query ATT&CK data with attackcti, mitreattack-python, and stix2, then build MITRE ATT&CK Navigator layers and multi-layer heatmap overlays mapping one or more APT groups

analyzing-azure-activity-logs-for-threats

Queries Azure Monitor activity logs and sign-in logs via azure-monitor-query

analyzing-bootkit-and-rootkit-samples

Analyzes bootkit and advanced rootkit malware infecting the Master

analyzing-browser-forensics-with-hindsight

Parse Chromium-based browser databases with Hindsight to extract and correlate browsing history, downloads, cookies, cached content, autofill data, saved passwords, and extensions from Chrome, Edge, Brave, Opera, and Vivaldi into a unified timeline (XLSX, JSON, or SQLite output). Use during incident response, insider-threat investigations, or criminal cases when you need to reconstruct a user

analyzing-campaign-attribution-evidence

Systematically evaluate cyber-campaign evidence to attribute an operation to a threat actor, using the Diamond Model and Analysis of Competing Hypotheses (ACH) to weigh infrastructure overlaps, TTP consistency, malware code similarity, and timing/language artifacts into confidence-weighted attribution assessments. Use when an incident investigation needs a defensible attribution confidence level.

analyzing-certificate-transparency-for-phishing

Monitor Certificate Transparency logs using crt.sh and Certstream to

analyzing-cloud-storage-access-patterns

Detect abnormal access in AWS S3, GCS, and Azure Blob Storage by analyzing CloudTrail Data Events, GCS audit logs, and Azure Storage Analytics for after-hours bulk downloads, new-IP access, and API-call spikes (e.g. GetObject) via statistical baselines and time-series anomaly detection. Use when investigating suspected cloud data exfiltration or building related detection rules.

analyzing-cobalt-strike-beacon-configuration

Extract and analyze Cobalt Strike beacon configuration from PE files

analyzing-cobaltstrike-malleable-c2-profiles

Parse and analyze Cobalt Strike Malleable C2 profiles with dissect.cobaltstrike (profiles and beacon-payload configs) and pyMalleableC2 (AST parsing) to extract HTTP/DNS transforms, URIs, headers, sleep/jitter, and injection behavior, then generate network detection signatures. Use when reverse-engineering a captured malleable profile or building detections against Cobalt Strike Beacon traffic.

analyzing-command-and-control-communication

Analyzes malware C2 communication over HTTP, HTTPS, DNS, and custom

analyzing-cyber-kill-chain

Analyzes intrusion activity against the Lockheed Martin Cyber Kill Chain

analyzing-disk-image-with-autopsy

Perform comprehensive forensic analysis of raw (dd), E01, or AFF disk images with Autopsy and The Sleuth Kit, recovering deleted files, examining metadata and embedded artifacts, keyword searching, and building investigation timelines with visual reports. Use for structured analysis of a forensic disk image or when stakeholders need visual reports from evidence.

analyzing-dns-logs-for-exfiltration

Analyzes DNS query logs to detect data exfiltration via DNS tunneling,

Skills relacionados