Security & privacy
Security built into the platform
How StellarSecure isolates tenants, authenticates devices, authorizes privileged operations and handles your data.
Tenant isolation and access control
Every workspace-owned resource is scoped to its workspace. A user in one workspace cannot access another’s devices, data or billing — enforced in the application and verified by negative authorization tests.
Staff roles and permissions
Role-based permissions govern what each staff member can do, including privileged operations such as remote access and deployments.
Per-device authentication
Each device authenticates with its own credentials. The enrollment reference alone never authorizes management; enrollment uses a scoped, expiring mechanism, and credentials are revocable and rotatable.
Authorized remote support
Remote-support access is bound to the session, workspace, device, participant role and expiry — not to a guessable link. Ending or revoking a session stops further access.
Auditing of privileged operations
Privileged device operations are recorded with who did what and when.
Agent and package integrity
Agent releases and packages are verified by checksum and signature before installation where implemented.
Data access, retention and deletion
Telemetry and logs follow retention policies; data access, export and deletion practices are defined and enforced.
Platform permissions and prerequisites
Native management and remote support respect each platform’s permission and enrollment model.
We describe only controls we can describe accurately, and we don’t claim certifications or audits we haven’t earned. The implementation and operational status of each item is verified before publication.
Reporting a security concern? Email [email protected].