docs(webhook): roadmap tick + threat-model component
- DEVELOPMENT.md: tick the "Real-time alerting" roadmap item with a note that Slack/Telegram-specific senders remain per-destination follow-ups (they accept generic webhook payloads already). - THREAT_MODEL.md: new Component 2 — DECNET↔External webhook destination. DFD, full STRIDE table, WH-01 (secret at rest) and WH-02 (half-dead-receiver retry waste) registered as accepted risks pointing at DEBT-037 for post-MVP hardening. Checklist lists two open items: OpenAPI schema omits `secret`, and http:// URL rejection at admin time.
This commit is contained in:
@@ -55,7 +55,7 @@
|
||||
|
||||
## Detection & Intelligence
|
||||
|
||||
- [ ] **Real-time alerting** — Webhook/Slack/Telegram notifications for first-hits.
|
||||
- [x] **Real-time alerting via webhooks** — Admin-configurable outbound webhooks (SIEM/SOAR integration: Wazuh/Shuffle/TheHive/n8n) with HMAC-SHA256 signing, topic-pattern filtering, and bounded retry. Slack/Telegram-specific senders remain as per-destination work (they accept generic webhook payloads already).
|
||||
- [ ] **Threat intel enrichment** — Auto-lookup IPs against AbuseIPDB, Shodan, and GreyNoise.
|
||||
- [ ] **Attack campaign clustering** — Group sessions by signatures and timing patterns.
|
||||
- [ ] **GeoIP mapping** — Visualize attacker origin and ASN data on a map.
|
||||
|
||||
Reference in New Issue
Block a user