Back to catalog
Static reviewDevelopment

Skill dossier

collecting-indicators-of-compromise

Source declaration

Systematically collects, categorizes, and distributes indicators of compromise (IOCs) during and after security incidents to enable detection, blocking, and threat intelligence sharing. Covers network, host, email, and behavioral indicators using STIX/TAXII formats and threat intelligence platforms. Activates for requests involving IOC collection, indicator extraction, threat indicator sharing, compromise indicators, STIX export, or IOC enrichment.

The author's original description, preserved in English. It describes intent, not verified performance.

Systematically collects, categorizes, and distributes indicators of compromise (IOCs) during and after security incidents to enable detection, blocking, and threat intelligence sharing. Covers network, host, email, and behavioral indicators using STIX/TAXII formats and threat intelligence platforms. Activates for requests involving IOC collection, indicator extraction, threat indicator sharing, compromise indicators, STIX export, or IOC enrichment.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Systematically collects, categorizes, and distributes indicators of compromise (IOCs) during and after security incidents to enable detection, blocking, and threat intelligence sharing. Covers network, host, email, and behavioral indicators using STIX/TAXII formats and threat intelligence platforms. Activates for requests involving IOC collection, indicator extraction, threat indicator sharing, compromise indicators, STIX export, or IOC enrichment. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/collecting-indicators-of-compromise/SKILL.md:L56]
  • Step 1: Identify IOC Categories [Source statement; provisional, not tested. Evidence: skills/collecting-indicators-of-compromise/SKILL.md:L58]
  • Step 2: Extract IOCs from Evidence Sources [Source statement; provisional, not tested. Evidence: skills/collecting-indicators-of-compromise/SKILL.md:L85]
  • Step 3: Enrich IOCs with Context [Source statement; provisional, not tested. Evidence: skills/collecting-indicators-of-compromise/SKILL.md:L122]
  • Step 4: Score and Prioritize IOCs [Source statement; provisional, not tested. Evidence: skills/collecting-indicators-of-compromise/SKILL.md:L148]
  • Step 5: Distribute IOCs for Detection and Blocking [Source statement; provisional, not tested. Evidence: skills/collecting-indicators-of-compromise/SKILL.md:L160]
  • Step 6: Share IOCs with Partners [Source statement; provisional, not tested. Evidence: skills/collecting-indicators-of-compromise/SKILL.md:L171]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/collecting-indicators-of-compromise/SKILL.md:L1-L34]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
30.9 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/collecting-indicators-of-compromise/LICENSEOther11 KB
skills/collecting-indicators-of-compromise/references/api-reference.mdReference2.2 KB
skills/collecting-indicators-of-compromise/scripts/agent.pyScript7.3 KB
skills/collecting-indicators-of-compromise/SKILL.mdInstruction10.5 KB

SKILL.md frontmatter

{
  "name": "collecting-indicators-of-compromise",
  "description": "Systematically collects, categorizes, and distributes indicators of compromise (IOCs) during and after security incidents to enable detection, blocking, and threat intelligence sharing. Covers network, host, email, and behavioral indicators using STIX/TAXII formats and threat intelligence platforms. Activates for requests involving IOC collection, indicator extraction, threat indicator sharing, compromise indicators, STIX export, or IOC enrichment.\n",
  "domain": "cybersecurity",
  "subdomain": "incident-response",
  "tags": [
    "IOC-collection",
    "threat-indicators",
    "STIX-TAXII",
    "MISP",
    "threat-intelligence-sharing"
  ],
  "mitre_attack": [
    "T1071.001",
    "T1071.004",
    "T1053.005",
    "T1547.001",
    "T1059.001",
    "T1041"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "RS.MA-01",
    "RS.MA-02",
    "RS.AN-03",
    "RC.RP-01"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: Identify IOC Categories

    Source-described action candidate under “Step 1: Identify IOC Categories”; not verified execution.

  4. 04
    Action

    IP addresses (C2 servers, staging servers, exfiltration destinations)

    Source-described action candidate under “Step 1: Identify IOC Categories”; not verified execution.

  5. 05
    Action

    Domain names (C2 domains, phishing domains, DGA domains)

    Source-described action candidate under “Step 1: Identify IOC Categories”; not verified execution.

  6. 06
    Action

    URLs (malware download, C2 check-in, exfiltration endpoints)

    Source-described action candidate under “Step 1: Identify IOC Categories”; not verified execution.

Inspect all extracted workflow candidates (41 candidate steps)
  1. 07
    Action

    JA3/JA3S hashes (TLS client/server fingerprints)

    Source-described action candidate under “Step 1: Identify IOC Categories”; not verified execution.

  2. 08
    Action

    User-Agent strings (custom or unusual HTTP headers)

    Source-described action candidate under “Step 1: Identify IOC Categories”; not verified execution.

  3. 09
    Action

    DNS query patterns (tunneling signatures, DGA patterns)

    Source-described action candidate under “Step 1: Identify IOC Categories”; not verified execution.

  4. 10
    Action

    File hashes (MD5, SHA-1, SHA-256 of malware, tools, scripts)

    Source-described action candidate under “Step 1: Identify IOC Categories”; not verified execution.

  5. 11
    Action

    File paths (known malware installation directories)

    Source-described action candidate under “Step 1: Identify IOC Categories”; not verified execution.

  6. 12
    Action

    Registry keys (persistence mechanisms, configuration storage)

    Source-described action candidate under “Step 1: Identify IOC Categories”; not verified execution.

  7. 13
    Action

    Scheduled tasks and service names (persistence)

    Source-described action candidate under “Step 1: Identify IOC Categories”; not verified execution.

  8. 14
    Action

    Mutex/event names (malware instance synchronization)

    Source-described action candidate under “Step 1: Identify IOC Categories”; not verified execution.

  9. 15
    Action

    Named pipes (C2 communication channels, e.g., Cobalt Strike)

    Source-described action candidate under “Step 1: Identify IOC Categories”; not verified execution.

  10. 16
    Action

    Sender addresses and domains (spoofed or attacker-controlled)

    Source-described action candidate under “Step 1: Identify IOC Categories”; not verified execution.

  11. 17
    Action

    Subject lines and body content patterns

    Source-described action candidate under “Step 1: Identify IOC Categories”; not verified execution.

  12. 18
    Action

    Attachment names and hashes

    Source-described action candidate under “Step 1: Identify IOC Categories”; not verified execution.

  13. 19
    Action

    Embedded URLs

    Source-described action candidate under “Step 1: Identify IOC Categories”; not verified execution.

  14. 20
    Action

    Email header anomalies (SPF/DKIM/DMARC failures)

    Source-described action candidate under “Step 1: Identify IOC Categories”; not verified execution.

  15. 21
    Action

    Step 2: Extract IOCs from Evidence Sources

    Source-described action candidate under “Step 2: Extract IOCs from Evidence Sources”; not verified execution.

  16. 22
    Action

    Step 3: Enrich IOCs with Context

    Source-described action candidate under “Step 3: Enrich IOCs with Context”; not verified execution.

  17. 23
    Action

    Step 4: Score and Prioritize IOCs

    Source-described action candidate under “Step 4: Score and Prioritize IOCs”; not verified execution.

  18. 24
    Action

    Step 5: Distribute IOCs for Detection and Blocking

    Source-described action candidate under “Step 5: Distribute IOCs for Detection and Blocking”; not verified execution.

  19. 25
    Action

    Firewall/IPS: Block C2 IPs and domains

    Source-described action candidate under “Step 5: Distribute IOCs for Detection and Blocking”; not verified execution.

  20. 26
    Action

    DNS: Sinkhole malicious domains

    Source-described action candidate under “Step 5: Distribute IOCs for Detection and Blocking”; not verified execution.

  21. 27
    Action

    EDR: Add file hashes to blocklist, create custom IOC watchlists

    Source-described action candidate under “Step 5: Distribute IOCs for Detection and Blocking”; not verified execution.

  22. 28
    Action

    Email Gateway: Block sender domains, attachment hashes, malicious URLs

    Source-described action candidate under “Step 5: Distribute IOCs for Detection and Blocking”; not verified execution.

  23. 29
    Action

    SIEM: Create correlation searches for IOC matches

    Source-described action candidate under “Step 5: Distribute IOCs for Detection and Blocking”; not verified execution.

  24. 30
    Action

    Web Proxy: Block URLs and domains in web filtering policy

    Source-described action candidate under “Step 5: Distribute IOCs for Detection and Blocking”; not verified execution.

  25. 31
    Action

    Step 6: Share IOCs with Partners

    Source-described action candidate under “Step 6: Share IOCs with Partners”; not verified execution.

  26. 32
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  27. 33
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  28. 34
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  29. 35
    Action

    Compile all network, host, and email indicators from the investigation

    Source-described action candidate under “Scenario: Post-Incident IOC Package for ISAC Sharing”; not verified execution.

  30. 36
    Action

    Enrich each IOC with VirusTotal and MISP correlation data

    Source-described action candidate under “Scenario: Post-Incident IOC Package for ISAC Sharing”; not verified execution.

  31. 37
    Action

    Assign confidence scores based on direct observation vs. secondary correlation

    Source-described action candidate under “Scenario: Post-Incident IOC Package for ISAC Sharing”; not verified execution.

  32. 38
    Action

    Mark all IOCs with TLP:AMBER for partner sharing

    Source-described action candidate under “Scenario: Post-Incident IOC Package for ISAC Sharing”; not verified execution.

  33. 39
    Output

    Export as STIX 2.1 bundle and submit to FS-ISAC TAXII feed

    Source-described output candidate under “Scenario: Post-Incident IOC Package for ISAC Sharing”; not verified execution.

  34. 40
    Output

    Create a human-readable IOC summary report for email distribution

    Source-described output candidate under “Scenario: Post-Incident IOC Package for ISAC Sharing”; not verified execution.

  35. 41
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

20 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

10 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 10 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

10 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 10 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/collecting-indicators-of-compromise/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/collecting-indicators-of-compromise/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/collecting-indicators-of-compromise
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.