Skip to main content

Connected TIPs And CTI Feeds

This framework now has a feed-intake layer for open-source/free CTI updates. The connectors create review candidates, not finished intelligence records.

Connected Without API Keys

FeedTypeWhat It AddsHow To Use
MITRE ATT&CK Enterprise STIXSTIX bundleActor taxonomy, aliases, ATT&CK group modified dates, and drift signals.Review actor alias and technique changes before updating data/actors.csv or data/ttps.csv.
CISA Known Exploited VulnerabilitiesJSON catalogExposure-prioritization leads for edge, identity, remote-access, and OT products.Route to the Surface And Capability Matrix; do not infer actor attribution from KEV alone.
CISA Cybersecurity Advisories RSSRSSNew government advisory leads for ICS, edge, cloud, and critical-infrastructure surfaces.Add a normal source/evidence record before promoting an advisory into actor, hunt, or detection content.

Optional TIP Connectors

PlatformStatusRequired SecretNotes
AlienVault OTXImplemented for subscribed pulsesOTX_API_KEYPulls matching subscribed pulses when configured. Commit reviewed summaries only, not raw private pulse dumps.
VirusTotalImplemented for hash enrichment candidatesVT_API_KEYEnriches reviewed hash seeds in data/virustotal-hash-seeds.csv. Commit only summary rows in data/virustotal-enrichment-candidates.csv; never commit API keys, raw JSON, private telemetry, downloaded samples, or VT-only attribution.
MISPConnector target documentedMISP_API_KEY plus trusted instance URLRequires a trusted MISP instance and local policy for event tags, distribution, and confidence handling.
OpenCTIConnector target documentedOPENCTI_TOKEN plus trusted instance URLRequires a trusted OpenCTI instance and local policy for marking definitions and source reliability.

Commands

Run a local feed pull:

npm run intel:update

Run a local VirusTotal enrichment pass:

VT_API_KEY=... npm run intel:vt

The command updates:

  • data/intel-update-candidates.csv
  • docs/intelligence-updates.md

The VirusTotal command updates:

GitHub Actions

The Intel Update Check workflow runs on a weekday schedule and can be started manually. It uploads the generated update queue as an artifact. It does not auto-commit or auto-promote feed data.

Promotion Workflow

  1. Review the candidate in Intelligence Update Queue.
  2. Open the source URL and verify the claim.
  3. Decide whether the item is actor-specific, surface-specific, or only context.
  4. Add or update data/sources.csv if the source should become a repository source.
  5. Add or update examples/registers/evidence-register.csv for claim-backed content.
  6. Update actor pages, TTP mappings, hunts, detections, or surface routes only after source/evidence review.
  7. Regenerate navigation with npm run validate.

Guardrails

  • Feed hits are leads, not confirmed incidents.
  • KEV entries prove known exploitation in the wild, not use by a specific actor.
  • OTX/MISP/OpenCTI enrichment can be noisy and must be source-rated.
  • VirusTotal verdicts are enrichment only. They do not prove actor attribution, and a not-found result is not a benign verdict.
  • Do not commit API keys, private feeds, restricted reports, raw malware, leaked data, or victim telemetry.
  • Keep the repo boundary: public-source, defensive, TLP:CLEAR.