Carefully considered controls.
Every simulated vehicle command runs on the server. The browser never receives Fleet secrets or signing keys.
Intent before action
Sensitive commands require explicit confirmation. Routines list every action and stop when a critical step fails. Real high-risk controls will require recent account authentication before they can be enabled.
Request protection
Commands use validated input, same-origin CSRF checks, session cookies, rate limits, and request IDs that prevent duplicates. Production cookies are Secure, HTTP-only, and SameSite Strict. A nonce-based Content Security Policy and security headers protect the interface.
Demo boundary
Sessions, rate limits, audit records, and request IDs are stored in memory. This milestone is designed for one Node.js process. Persistent, shared storage and security review are required before a multi-instance or live vehicle deployment.
Reporting a concern
For a locally hosted demo, report concerns directly to the person who provided this installation. A public security contact and coordinated disclosure policy must be established before public launch. Do not include credentials, vehicle identifiers, or sensitive addresses in a report.