DashboardcliEnforce fail-closed credential and host…

Enforce fail-closed credential and host-scoping boundaries

Category: preference
Confidence: 0.80
ID: 01a08c3f-5370-734f-aaaa-6f6870d6f6a5
Project ID: c760f4f9-42b0-4ce0-b36d-6b8c38d770b2
Cross-project: No
Recalled in other projects: 0
Source session: 0cvCFbbhdaJ4R16pu
Created: 2026-09-10 16:55:55
Updated: 2026-09-10 16:55:55

Content

Treat credential routing as a strict security boundary. Resolve the active token and trusted host using the documented precedence, snapshot environment-derived trust before weaker configuration can mutate it, and scope regional caches to the control-silo origin that discovered them. Require exact normalized-origin matching, allowing only explicitly defined SaaS and registered-region exceptions. Validate every request and redirect before attaching authorization or custom headers so rejected destinations never receive credentials. Treat legitimate sntrys_ token URL claims as authoritative within the stated threat model, without allowing rc files or URL arguments to redirect them. Never expose sensitive flag values to telemetry. Add regression tests that explicitly verify credentials and headers never hit the wire on mismatches or untrusted redirects.

Move to: