Federated Threat Intelligence: Sharing IOCs Without Sharing Content

Description and use

A federated threat‑intel system shares hashed IOCs via gossip, corroborates detections, and adjusts responses based on peer reputation, cutting latency from hours to minutes.

Problem

AI attacks spread quickly; traditional threat‑intel sharing is slow, shares raw content that contains PII, and relies on binary trust. Organizations need a way for the first detection to benefit all without exposing content or a central authority.

Outcome

The federated system enables near‑real‑time sharing of threat indicators without exposing raw prompts, reduces latency from hours to minutes, and introduces a reputation‑based trust mesh that scales without a central authority.

Workflow

• Detect novel prompt injection and generate IOC
• Compute SHA‑256 fingerprint of canonicalized detection struct
• Publish signed IOC bundle to /manifest endpoint
• Peers pull manifests, verify ECDSA P‑256 signatures
• Compare fingerprints to detect corroboration
• Update peer reputation using EWMA
• Escalate response (alert→block) if corroborated or aggressive mode enabled
• Optionally ingest external TAXII 2.1 feeds with configurable reputation weight

Evidence

When AegisGate detects a threat, it creates an Indicator of Compromise (IOC). But we don't share the raw attack payload. We compute a SHA‑256 fingerprint over the canonicalized detection struct — capturing the technique, pattern match, and confidence without any original content.

Source

Instances communicate via HTTP gossip. Every instance exposes a /manifest endpoint listing its signed IOC bundles. Peers periodically pull manifests, verify signatures, and ingest new IOCs.

Source

We track reputation using an Exponentially Weighted Moving Average (EWMA) with a 7‑day half‑life: A peer that shares IOCs you later corroborate → reputation increases; a peer that shares noise or never‑corroborated IOCs → reputation decays.

Source