Back to catalog
Static reviewDevelopment

Skill dossier

evaluating-threat-intelligence-platforms

Source declaration

Evaluates and selects Threat Intelligence Platform (TIP) products based on organizational requirements including feed integration capability, STIX/TAXII support, workflow automation, analyst interface, and total cost of ownership. Use when conducting a TIP procurement, migrating between TIP solutions, or assessing whether the current TIP meets program maturity requirements. Activates for requests involving ThreatConnect, MISP, OpenCTI, Anomali, EclecticIQ, or TIP procurement decisions.

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

Evaluates and selects Threat Intelligence Platform (TIP) products based on organizational requirements including feed integration capability, STIX/TAXII support, workflow automation, analyst interface, and total cost of ownership. Use when conducting a TIP procurement, migrating between TIP solutions, or assessing whether the current TIP meets program maturity requirements. Activates for requests involving ThreatConnect, MISP, OpenCTI, Anomali, EclecticIQ, or TIP procurement decisions.

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.

Evaluates and selects Threat Intelligence Platform (TIP) products based on organizational requirements including feed integration capability, STIX/TAXII support, workflow automation, analyst interface, and total cost of ownership. Use when conducting a TIP procurement, migrating between TIP solutions, or assessing whether the current TIP meets program maturity requirements. Activates for requests involving ThreatConnect, MISP, OpenCTI, Anomali, EclecticIQ, or TIP procurement decisions. 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/evaluating-threat-intelligence-platforms/SKILL.md:L56]
  • Step 1: Define Evaluation Criteria [Source statement; provisional, not tested. Evidence: skills/evaluating-threat-intelligence-platforms/SKILL.md:L58]
  • Step 2: Evaluate Major TIP Options [Source statement; provisional, not tested. Evidence: skills/evaluating-threat-intelligence-platforms/SKILL.md:L82]
  • Step 3: Conduct Proof of Concept [Source statement; provisional, not tested. Evidence: skills/evaluating-threat-intelligence-platforms/SKILL.md:L114]
  • Step 4: Score and Select [Source statement; provisional, not tested. Evidence: skills/evaluating-threat-intelligence-platforms/SKILL.md:L123]
  • Step 5: Implementation and Onboarding Planning [Source statement; provisional, not tested. Evidence: skills/evaluating-threat-intelligence-platforms/SKILL.md:L137]

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/evaluating-threat-intelligence-platforms/SKILL.md:L1-L37]

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.2 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/evaluating-threat-intelligence-platforms/LICENSEOther11 KB
skills/evaluating-threat-intelligence-platforms/references/api-reference.mdReference2.7 KB
skills/evaluating-threat-intelligence-platforms/scripts/agent.pyScript9.3 KB
skills/evaluating-threat-intelligence-platforms/SKILL.mdInstruction7.3 KB

SKILL.md frontmatter

{
  "name": "evaluating-threat-intelligence-platforms",
  "description": "Evaluates and selects Threat Intelligence Platform (TIP) products based on organizational requirements including feed integration capability, STIX/TAXII support, workflow automation, analyst interface, and total cost of ownership. Use when conducting a TIP procurement, migrating between TIP solutions, or assessing whether the current TIP meets program maturity requirements. Activates for requests involving ThreatConnect, MISP, OpenCTI, Anomali, EclecticIQ, or TIP procurement decisions.\n",
  "domain": "cybersecurity",
  "subdomain": "threat-intelligence",
  "tags": [
    "TIP",
    "ThreatConnect",
    "MISP",
    "OpenCTI",
    "Anomali",
    "EclecticIQ",
    "STIX-TAXII",
    "CTI-program",
    "procurement"
  ],
  "version": "1.0.0",
  "author": "team-cybersecurity",
  "license": "Apache-2.0",
  "nist_csf": [
    "ID.RA-01",
    "ID.RA-05",
    "DE.CM-01",
    "DE.AE-02"
  ],
  "mitre_attack": [
    "T1591",
    "T1592",
    "T1593",
    "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
    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: Define Evaluation Criteria

    Source-described action candidate under “Step 1: Define Evaluation Criteria”; not verified execution.

  4. 04
    Input

    M: STIX 2.1 import/export with TAXII 2.1 server

    Source-described input candidate under “Step 1: Define Evaluation Criteria”; not verified execution.

  5. 05
    Output

    M: REST API for automated IOC ingestion and export

    Source-described output candidate under “Step 1: Define Evaluation Criteria”; not verified execution.

  6. 06
    Action

    M: Indicator deduplication and TTL management

    Source-described action candidate under “Step 1: Define Evaluation Criteria”; not verified execution.

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

    M: TLP classification enforcement

    Source-described action candidate under “Step 1: Define Evaluation Criteria”; not verified execution.

  2. 08
    Action

    D: Built-in MITRE ATT&CK integration and technique tagging

    Source-described action candidate under “Step 1: Define Evaluation Criteria”; not verified execution.

  3. 09
    Action

    D: Graph visualization of indicator relationships

    Source-described action candidate under “Step 1: Define Evaluation Criteria”; not verified execution.

  4. 10
    Action

    D: Workflow automation for analyst triage

    Source-described action candidate under “Step 1: Define Evaluation Criteria”; not verified execution.

  5. 11
    Action

    M: SIEM integration (Splunk, Sentinel, QRadar) via syslog, API, or native connector

    Source-described action candidate under “Step 1: Define Evaluation Criteria”; not verified execution.

  6. 12
    Action

    M: EDR integration for IOC push (CrowdStrike, Defender, SentinelOne)

    Source-described action candidate under “Step 1: Define Evaluation Criteria”; not verified execution.

  7. 13
    Action

    D: SOAR integration (XSOAR, Splunk SOAR) for playbook triggers

    Source-described action candidate under “Step 1: Define Evaluation Criteria”; not verified execution.

  8. 14
    Action

    D: Ticketing system (ServiceNow, Jira) for intelligence task tracking

    Source-described action candidate under “Step 1: Define Evaluation Criteria”; not verified execution.

  9. 15
    Action

    M: Role-based access control with TLP-aware data segregation

    Source-described action candidate under “Step 1: Define Evaluation Criteria”; not verified execution.

  10. 16
    Action

    M: Audit logging for all analyst actions

    Source-described action candidate under “Step 1: Define Evaluation Criteria”; not verified execution.

  11. 17
    Action

    D: Multi-tenancy for MSSP use cases

    Source-described action candidate under “Step 1: Define Evaluation Criteria”; not verified execution.

  12. 18
    Action

    Step 2: Evaluate Major TIP Options

    Source-described action candidate under “Step 2: Evaluate Major TIP Options”; not verified execution.

  13. 19
    Action

    Cost: Free (self-hosted infrastructure cost only)

    Source-described action candidate under “Step 2: Evaluate Major TIP Options”; not verified execution.

  14. 20
    Action

    Strengths: Largest community, 250+ modules, extensive ISAC usage, STIX 2.0 native

    Source-described action candidate under “Step 2: Evaluate Major TIP Options”; not verified execution.

  15. 21
    Action

    Weaknesses: Requires dedicated admin, limited visualization, UI dated

    Source-described action candidate under “Step 2: Evaluate Major TIP Options”; not verified execution.

  16. 22
    Action

    Best for: Budget-constrained teams with technical staff; government/ISAC sharing programs

    Source-described action candidate under “Step 2: Evaluate Major TIP Options”; not verified execution.

  17. 23
    Action

    Cost: Free (self-hosted); paid SaaS at $3,000–$15,000/year

    Source-described action candidate under “Step 2: Evaluate Major TIP Options”; not verified execution.

  18. 24
    Action

    Strengths: Native STIX 2.1, graph visualization, ATT&CK integration, modern API

    Source-described action candidate under “Step 2: Evaluate Major TIP Options”; not verified execution.

  19. 25
    Action

    Weaknesses: Resource-intensive deployment (Elasticsearch, MinIO required)

    Source-described action candidate under “Step 2: Evaluate Major TIP Options”; not verified execution.

  20. 26
    Input

    Best for: Teams wanting open source with modern UX; SOC/CTI integration focus

    Source-described input candidate under “Step 2: Evaluate Major TIP Options”; not verified execution.

  21. 27
    Action

    Cost: $50,000–$500,000/year depending on scale

    Source-described action candidate under “Step 2: Evaluate Major TIP Options”; not verified execution.

  22. 28
    Action

    Strengths: End-to-end CTI lifecycle, playbook automation, TC Exchange marketplace, analyst workflow

    Source-described action candidate under “Step 2: Evaluate Major TIP Options”; not verified execution.

  23. 29
    Action

    Weaknesses: High cost; complex implementation; best value at larger scale

    Source-described action candidate under “Step 2: Evaluate Major TIP Options”; not verified execution.

  24. 30
    Action

    Best for: Mature enterprise CTI programs; MSSPs; red team/blue team integration

    Source-described action candidate under “Step 2: Evaluate Major TIP Options”; not verified execution.

  25. 31
    Action

    Cost: $30,000–$200,000/year

    Source-described action candidate under “Step 2: Evaluate Major TIP Options”; not verified execution.

  26. 32
    Action

    Strengths: Strong feed aggregation, Splunk-native integration, extensive pre-built connectors

    Source-described action candidate under “Step 2: Evaluate Major TIP Options”; not verified execution.

  27. 33
    Action

    Weaknesses: Graph visualization weaker than OpenCTI; UI refresh lagging

    Source-described action candidate under “Step 2: Evaluate Major TIP Options”; not verified execution.

  28. 34
    Action

    Best for: Splunk-heavy environments; teams prioritizing feed volume over analysis workflows

    Source-described action candidate under “Step 2: Evaluate Major TIP Options”; not verified execution.

  29. 35
    Action

    Cost: $40,000–$300,000/year

    Source-described action candidate under “Step 2: Evaluate Major TIP Options”; not verified execution.

  30. 36
    Action

    Strengths: STIX 2.1 native, collaborative intelligence workbench, strong European customer base

    Source-described action candidate under “Step 2: Evaluate Major TIP Options”; not verified execution.

  31. 37
    Action

    Weaknesses: Smaller partner ecosystem than ThreatConnect

    Source-described action candidate under “Step 2: Evaluate Major TIP Options”; not verified execution.

  32. 38
    Action

    Best for: Teams with MITRE ATT&CK-centric workflows; EMEA-focused organizations

    Source-described action candidate under “Step 2: Evaluate Major TIP Options”; not verified execution.

  33. 39
    Action

    Step 3: Conduct Proof of Concept

    Source-described action candidate under “Step 3: Conduct Proof of Concept”; not verified execution.

  34. 40
    Action

    Feed onboarding: Can your top 5 feeds be ingested within 4 hours?

    Source-described action candidate under “Step 3: Conduct Proof of Concept”; not verified execution.

  35. 41
    Action

    SIEM integration: Can enriched IOCs push to your SIEM in <5 minutes?

    Source-described action candidate under “Step 3: Conduct Proof of Concept”; not verified execution.

  36. 42
    Action

    ATT&CK mapping: Can analysts tag indicators with ATT&CK techniques efficiently?

    Source-described action candidate under “Step 3: Conduct Proof of Concept”; not verified execution.

  37. 43
    Output

    Report generation: Can the platform produce a tactical IOC bulletin with one click?

    Source-described output candidate under “Step 3: Conduct Proof of Concept”; not verified execution.

  38. 44
    Action

    API performance: Can the REST API handle 10,000 indicator queries per day?

    Source-described action candidate under “Step 3: Conduct Proof of Concept”; not verified execution.

  39. 45
    Action

    Step 4: Score and Select

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

  40. 46
    Action

    Use weighted scoring matrix (weight each criterion by organizational priority):

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

  41. 47
    Action

    Step 5: Implementation and Onboarding Planning

    Source-described action candidate under “Step 5: Implementation and Onboarding Planning”; not verified execution.

  42. 48
    Action

    Week 1–2: Infrastructure deployment (cloud or on-prem)

    Source-described action candidate under “Step 5: Implementation and Onboarding Planning”; not verified execution.

  43. 49
    Action

    Week 3–4: Feed onboarding and deduplication tuning

    Source-described action candidate under “Step 5: Implementation and Onboarding Planning”; not verified execution.

  44. 50
    Action

    Week 5–6: SIEM/SOAR integration and testing

    Source-described action candidate under “Step 5: Implementation and Onboarding Planning”; not verified execution.

  45. 51
    Action

    Week 7–8: Analyst workflow configuration and training

    Source-described action candidate under “Step 5: Implementation and Onboarding Planning”; not verified execution.

  46. 52
    Action

    Week 9–12: Operational validation and go-live

    Source-described action candidate under “Step 5: Implementation and Onboarding Planning”; not verified execution.

  47. 53
    Action

    Key Concepts

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

  48. 54
    Action

    Tools & Systems

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

  49. 55
    Action

    Common Pitfalls

    Source-described action candidate under “Common Pitfalls”; 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

28 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

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

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

2 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 2 location(s) in the collected text; 2 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/evaluating-threat-intelligence-platforms/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/evaluating-threat-intelligence-platforms/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/evaluating-threat-intelligence-platforms
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.