Security & Architecture

Documented controls for tenant access, connected credentials, production transport, and administrative sessions.

Access & Authorization

Tenant-Scoped Access: Fleet-data API lookups are scoped to the authenticated tenant and protected by permission checks.
Role-Based Permissions: Application access is governed by precise role permissions mapped to organizational duties.

Credential Protection: Verizon Connect Reveal credentials are encrypted at rest and omitted from integration status responses.
Provider-Client Boundary: Integration credentials are decrypted only when constructing the provider client used for synchronization.
Webhook Verification: Stripe signature verification is required when live Stripe is configured.

Transport Security: Production environments enforce strict HTTP Strict Transport Security (HSTS).
Content Policies: Application responses apply a Content Security Policy alongside restrictive Referrer and Permissions policies.
Session Protection: Cross-Site Request Forgery (CSRF) protection is enforced on all unsafe DZ Command cookie-session requests.

1. Authenticate

The user and active tenant are established before protected fleet routes run.

2. Authorize

Role permissions determine whether the requested fleet or integration action is allowed.

3. Connect

Encrypted Verizon credentials are opened only to construct the synchronization client.

4. Respond

Integration status responses report configuration state without returning raw credentials.

Request a focused walkthrough of tenant boundaries, Verizon Connect handling, migration planning, and the controls relevant to your fleet.