Command Post Intel Sharing#

Added in v0.5. The multi-instance Command Post aggregator (see command-post) grew three new endpoints so proxies can share IoCs across the fleet and external red-team peers can subscribe to your scanner observations as a STIX 2.1 feed.

Endpoints#

All three live under any Command Post you spin up (infraguard command-post -c cp.yaml).

POST /api/intel/push#

A proxy node reports an IoC. Called by the alerting or detection plugins on the proxy side; deduplicated on Command Post by (kind, value).

curl -X POST https://cp.example.com/api/intel/push \
  -H "content-type: application/json" \
  -H "authorization: Bearer $CP_TOKEN" \
  -d '{"kind":"ip","value":"198.51.100.7","source_node":"proxy-a",
       "reason":"burst of empty-UA GETs"}'

Accepted kinds: ip, ja3, ua.

GET /api/intel/pull?since=<epoch>&kinds=ip,ja3#

Pull IoCs added after since. Peer proxies call this on a timer to fetch the fleet-wide blocklist.

curl -G https://cp.example.com/api/intel/pull \
  --data-urlencode "since=$(date +%s -d '1 hour ago')" \
  --data-urlencode "kinds=ip"

Response:

{
  "now": 1730073600.12,
  "count": 3,
  "entries": [
    {"kind": "ip", "value": "198.51.100.7", "source_node": "proxy-a",
     "first_seen": 1730073300.11, "reason": "..."},
    ...
  ]
}

GET /taxii2/collections/{collection_id}/objects/#

Serves the IoC set as a STIX 2.1 bundle. Subscribers poll this the same way they would a commercial threat feed. Fixed collection id infraguard-scanners in this initial version.

curl https://cp.example.com/taxii2/collections/infraguard-scanners/objects/ \
  | jq '.objects[] | select(.type == "indicator")'

Proxy-side integration#

The proxy does not push automatically today. Two idiomatic ways to wire it in:

  1. Plugin: write a small on_event hook that POSTs to /api/intel/push when a filter fires above your threshold. See the slack and pagerduty plugins for the pattern.
  2. request_recorder + external processor: let the recorder dump every blocked event to JSONL and post-process into pushes.

JA3 anomaly#

Command Post also tracks which domains have observed each JA3 hash (SharedIntel.push_ja3_seen). SharedIntel.ja3_anomalies(all_domains) returns hashes seen on a strict subset - a strong signal for defender scanner rotation. The UI shows this on the JA3 panel; scripting consumers can call the API directly through a Command Post plugin.

Persistence#

In-memory for this initial version - all state clears on Command Post restart. Peer proxies keep pulling from a fresh cursor after a restart. A SQLite-backed store is a follow-up; see the roadmap.