Discord Bot Platform  ·  View 18 of 19  ·  Assurance

Security and Trust Zones

Every crossing is authenticated; every bot-supplied URL is hostile.

Editable source SVG draw.io All views
Internet / bot side Bot Process Bot Endpoint Edge WebSocket Edge WAF, TLS 1.2+ API Edge token auth, buckets Egress Pool SSRF-safe Platform Gateway Shards Interaction Service Token Service Data and trusted chat service Registry Key Vault Chat Service WSS + token authenticated frames entitlements signed payload validated URL only hash keys Discord Bot Platform — Security and Trust Zones External / third party Interface / broker Application we own Security / platform Data store synchronous v 1.0 · owner Integration Platform Architecture · date 2026-10

Decisions

  • Egress is its own zone with no route back inward, so an SSRF bug has nowhere to go (ADR-11).
  • Tokens are validated at the edge and again at the session; interaction tokens are single-use scoped (ADR-12).

Risk

  • A leaked token is the most common compromise; scanning and a 5-minute reset target answer it.
◀  Gateway Session Lifecycle All views Identity — Install and Token Use  ▶
Solution Architecture v1.0 · Microsoft Azure · Integration Platform Architecture · 2026-10 · 19 views · 12 architecture decision records18-security-trust-zones