Back to catalog
Static reviewDevelopment

Skill dossier

modeling-threats-with-opencti

Source declaration

Deploy OpenCTI (Filigran) via Docker Compose and use the pycti Python client to model threat actors, intrusion sets, campaigns, and indicators as a STIX 2.1 knowledge graph with relationships (uses, attributed-to, targets). Use when building a centralized threat-intel knowledge base, correlating IOCs from multiple feeds into one adversary graph, or producing STIX bundles for detection engineering.

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

Deploy OpenCTI (Filigran) via Docker Compose and use the pycti Python client to model threat actors, intrusion sets, campaigns, and indicators as a STIX 2.1 knowledge graph with relationships (uses, attributed-to, targets). Use when building a centralized threat-intel knowledge base, correlating IOCs from multiple feeds into one adversary graph, or producing STIX bundles for detection engineering.

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.

Deploy OpenCTI (Filigran) via Docker Compose and use the pycti Python client to model threat actors, intrusion sets, campaigns, and indicators as a STIX 2.1 knowledge graph with relationships (uses, attributed-to, targets). Use when building a centralized threat-intel knowledge base, correlating IOCs from multiple feeds into one adversary graph, or producing STIX bundles for detection engineering. 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/modeling-threats-with-opencti/SKILL.md:L69]
  • Step 1: Deploy the OpenCTI platform [Source statement; provisional, not tested. Evidence: skills/modeling-threats-with-opencti/SKILL.md:L71]
  • Step 2: Authenticate with pycti [Source statement; provisional, not tested. Evidence: skills/modeling-threats-with-opencti/SKILL.md:L98]
  • Step 3: Create core STIX domain objects [Source statement; provisional, not tested. Evidence: skills/modeling-threats-with-opencti/SKILL.md:L109]
  • Step 4: Build relationships to form the graph [Source statement; provisional, not tested. Evidence: skills/modeling-threats-with-opencti/SKILL.md:L138]
  • Step 5: Add indicators and observables [Source statement; provisional, not tested. Evidence: skills/modeling-threats-with-opencti/SKILL.md:L163]
  • Step 6: Submit a STIX 2.1 bundle directly [Source statement; provisional, not tested. Evidence: skills/modeling-threats-with-opencti/SKILL.md:L185]
  • Step 7: Enable connectors for automated ingestion [Source statement; provisional, not tested. Evidence: skills/modeling-threats-with-opencti/SKILL.md:L199]
  • Step 8: Query the graph and export an actor profile [Source statement; provisional, not tested. Evidence: skills/modeling-threats-with-opencti/SKILL.md:L219]

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/modeling-threats-with-opencti/SKILL.md:L1-L22]

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
5
Markdown files
3
scripts
1
references
2
Size
31.3 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/modeling-threats-with-opencti/LICENSEOther11 KB
skills/modeling-threats-with-opencti/references/api-reference.mdReference3.1 KB
skills/modeling-threats-with-opencti/references/standards.mdReference1.1 KB
skills/modeling-threats-with-opencti/scripts/agent.pyScript5 KB
skills/modeling-threats-with-opencti/SKILL.mdInstruction11.1 KB

SKILL.md frontmatter

{
  "name": "modeling-threats-with-opencti",
  "description": "Deploy OpenCTI (Filigran) via Docker Compose and use the pycti Python client to model threat actors, intrusion sets, campaigns, and indicators as a STIX 2.1 knowledge graph with relationships (uses, attributed-to, targets). Use when building a centralized threat-intel knowledge base, correlating IOCs from multiple feeds into one adversary graph, or producing STIX bundles for detection engineering.",
  "domain": "cybersecurity",
  "subdomain": "threat-intelligence",
  "tags": [
    "opencti",
    "threat-intelligence",
    "stix2",
    "pycti",
    "knowledge-graph",
    "threat-modeling",
    "mitre-attack",
    "cti"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "ID.RA-03"
  ],
  "mitre_attack": [
    "T1589"
  ]
}

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
    Action

    Overview

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

  2. 02
    Decision

    When to Use

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

  3. 03
    Action

    Objectives

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

  4. 04
    Action

    MITRE ATT&CK Mapping

    Source-described action candidate under “MITRE ATT&CK Mapping”; not verified execution.

  5. 05
    Action

    Workflow

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

  6. 06
    Action

    Step 1: Deploy the OpenCTI platform

    Source-described action candidate under “Step 1: Deploy the OpenCTI platform”; not verified execution.

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

    Use the official Docker Compose stack. Generate the required tokens/UUIDs and start the platform, workers, and dependencies.

    Source-described action candidate under “Step 1: Deploy the OpenCTI platform”; not verified execution.

  2. 08
    Action

    Step 2: Authenticate with pycti

    Source-described action candidate under “Step 2: Authenticate with pycti”; not verified execution.

  3. 09
    Action

    Create an `OpenCTIApiClient` instance using your platform URL and API token.

    Source-described action candidate under “Step 2: Authenticate with pycti”; not verified execution.

  4. 10
    Action

    Step 3: Create core STIX domain objects

    Source-described action candidate under “Step 3: Create core STIX domain objects”; not verified execution.

  5. 11
    Action

    Create a Threat Actor, an Intrusion Set, a Campaign, and an Attack Pattern. pycti `create()` calls act as upserts when `update=True`.

    Source-described action candidate under “Step 3: Create core STIX domain objects”; not verified execution.

  6. 12
    Action

    Step 4: Build relationships to form the graph

    Source-described action candidate under “Step 4: Build relationships to form the graph”; not verified execution.

  7. 13
    Action

    Step 5: Add indicators and observables

    Source-described action candidate under “Step 5: Add indicators and observables”; not verified execution.

  8. 14
    Action

    Create an indicator with a STIX pattern and tie it to the intrusion set via an `indicates` relationship.

    Source-described action candidate under “Step 5: Add indicators and observables”; not verified execution.

  9. 15
    Action

    Step 6: Submit a STIX 2.1 bundle directly

    Source-described action candidate under “Step 6: Submit a STIX 2.1 bundle directly”; not verified execution.

  10. 16
    Action

    Step 7: Enable connectors for automated ingestion

    Source-described action candidate under “Step 7: Enable connectors for automated ingestion”; not verified execution.

  11. 17
    Output

    Step 8: Query the graph and export an actor profile

    Source-described output candidate under “Step 8: Query the graph and export an actor profile”; not verified execution.

  12. 18
    Input

    Read back the adversary's full picture for reporting and detection engineering.

    Source-described input candidate under “Step 8: Query the graph and export an actor profile”; not verified execution.

  13. 19
    Action

    Tools and Resources

    Source-described action candidate under “Tools and Resources”; not verified execution.

  14. 20
    Action

    STIX Object Cheat Sheet (pycti entities)

    Source-described action candidate under “STIX Object Cheat Sheet (pycti entities)”; not verified execution.

  15. 21
    Action

    Validation Criteria

    Source-described action candidate under “Validation Criteria”; 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.

Attention recommended

31 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 useObserved
Medium

Network access is mentioned

21 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 21 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

6 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 6 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

3 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 3 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Elevated privileges are referenced

Privilege-elevation syntax is present. Confirm whether elevation is necessary and inspect every operation performed under it; static analysis cannot prove that elevation succeeded. This rule matched 1 location(s) in the collected text; 1 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/modeling-threats-with-opencti/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 5 collected file(s), 3 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/modeling-threats-with-opencti/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/modeling-threats-with-opencti
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.