Wavelynx — trust boundaries
Every place a Wavelynx-issued credential's data crosses an organizational trust boundary, and what cryptographic protection wraps each crossing. Internal-to-Wavelynx links (e.g. application tier to Cloud SQL via Unix socket) are not crossings — Wavelynx controls both ends. KMS appears as a distinct zone because Cloud KMS is the only authority that can produce plaintext keysets; Wavelynx delegates that trust to Google.
7 zones10 crossings
- src/wallet-api-data-flow-architecture-v1.0.12.pdf — §2 System context · §7 Security architecture summary