Security
Security is built into Null Autos at every layer: identity, network, storage, and authorization. This page summarizes the protections that matter to customers. For sign-in and permissions specifically, see Identity & Access.
Encryption in transit
- TLS on every public endpoint. Public traffic terminates at a managed gateway with certificates issued and renewed automatically. The portal, the API, identity, and every other public hostname are HTTPS only.
- Encrypted database connections. The control plane connects to its database with TLS required.
Identity & single sign-on
- Single sign-on (SSO) over OIDC, including federation to your existing identity provider so users sign in with corporate credentials.
- Per-tenant identity boundaries keep each organization's identities separate.
- PKCE is used for browser-based sign-in flows.
Authorization
- Relationship-based access control (ReBAC) gates every API request. Authorization is a hard dependency: the control plane refuses to serve traffic without it, so there is no fail-open mode.
- Permissions are inherited through the resource hierarchy and can be granted to groups, making least-privilege access practical to manage at scale.
Tenant isolation
- Resources are scoped and tagged by tenant, so one tenant can never list or reach another tenant's emulators, snapshots, or data.
- Optional dedicated isolated environments provide a separate platform boundary for organizations that need one. See Multi-Tenancy.
Workload & infrastructure security
- No long-lived cloud keys. Platform services use cloud workload identity rather than static credentials.
- Short-lived access. Operational access uses certificates with a short lifetime rather than shared keys.
- Managed secrets. Sensitive configuration is held in a managed secrets service.
- Network segmentation. Databases and shared storage run on private networks, and emulator and build workloads are isolated onto dedicated compute pools.
- Restricted administrative access. Infrastructure administration is limited to named principals and itself gated by SSO.
Auditing
The platform records security-relevant events using a standard, structured event schema, capturing the actor, action, outcome, and tenant for each event so activity can be reviewed and exported to your observability pipeline.
Device & emulator isolation
- Emulators run as isolated workloads on dedicated, virtualization-capable nodes.
- Browser access to a device goes through the control plane and an authenticated, relayed WebRTC connection. Devices are not directly exposed to the public internet for media.
- ADB access is brokered through an authenticated proxy, not an open port.
Shared-responsibility summary
| Null Autos provides | You manage |
|---|---|
| TLS, SSO, authorization, tenant isolation, hardened infrastructure | Your users and group membership |
| Audit event capture | Reviewing access and least-privilege grants within your tenant |
| Secret storage for platform services | Your own VCS tokens and credentials |
note
Security features described here reflect the platform's implemented controls. Specific compliance certifications, data-residency options, and contractual SLAs depend on your deployment and agreement. Contact your Null Autos representative for details.