Aeion Bridge Security & Network Architecture
Traditional remote-hardware solutions (VPN, ngrok, reverse SSH, port forwarding) create security disasters — open inbound ports, perpetually-active VPN tunnels, shared credentials, no per-operation authorization. Aeion Bridge inverts the model. The Bridge client initiates an outbound WebSocket (port 443) to cloud Aeion — same direction your browser uses for HTTPS. No inbound ports. No firewall changes. Per-tenant scoped credentials. Per-MCP-tool authorization. Per-operation audit trail. Compromise containment by construction.
Why Outbound-Only Matters
`
Per-Tenant Credential Model
```json
MCP Authorization Per-Tool
`
Defense-in-Depth Scenarios
`
Compliance + Audit Posture
`
FAQ
No. Bridge has no inbound listening port. Only outbound WebSocket. Attacker must compromise the Bridge host machine itself (different attack vector).
TLS 1.3 + optional cert pinning. Per-tenant signed envelope. Provider-grade encryption.
Encrypted at rest. Per-OS keychain integration (macOS Keychain / Windows Credential Manager / Linux Secret Service).
Per-sensitive-tool MFA enforced. Per-user TOTP / WebAuthn. Per-MFA session timeout configurable.
Per-Bridge unique device-id (TPM-backed where available). Per-Bridge fingerprint validation.
Per-tenant data + credentials stored in tenant DB. Cross-tenant compromise prevented by per-tenant isolation.
Per-Bridge OS-level sandboxing (where supported). Per-MCP-tool scope enforcement on cloud side.
Outbound 443 only. Standard HTTPS port. Works through corporate proxies (where allowed).
Per-tenant policy. Per-update signed channel. Per-update staged rollout.
Per-tenant configurable. Per-tool restricted-or-allowed list. Per-global deprecated list.
Per-tenant approval. Per-session time-limited. Per-session activity audited.
Per-Bridge SOC 2 + ISO 27001 + HIPAA BAA evidence. Per-Bridge subprocessor disclosure.