SECURITY

How MayaUPS protects access and data.

MayaUPS runs on your infrastructure, under your administrator’s control. Every control below is built into the product.

FOR YOUR SECURITY REVIEW

The security guide for your team.

Four pages on the security controls in MayaUPS.

Find answers in the guide

p. 2Access and data paths
The console, network cards, agents and the MayaUPS Cloud portal. Roles, credentials and audit history.
p. 3Availability and recovery
Backups, restore, and signed updates with rollback.
p. 4Deployment
Network, certificates, agent access and commissioning.

The threat model, hardening guide and CycloneDX software bill of materials are available on request.

Roles and sign-in

Viewer, operator and administrator roles separate who watches, who responds and who configures. Passwords are hashed with argon2id. Sign in with local accounts, LDAP and Active Directory or RADIUS, with two-step codes. MayaUPS Cloud contacts have their own portal role.

Scroll across the table to see every role.

Local roles and portal access
TaskLocal viewerLocal operatorLocal administratorPortal contact
Read fleet and device informationYesYesYesPermitted information for their organisation
Acknowledge a local alarmNoYesYesNo
Maintain monitored devices and battery recordsNoYesYesNo
Manage local users and notification settingsNoNoYesNo
Configure and enable a shutdown eventNoNoYesNo

MayaUPS Cloud portal accounts are separate from local accounts and read-only.

Credentials and equipment access

SNMP and platform credentials are encrypted at rest, with Windows DPAPI by default. SNMPv3 with authentication and encryption protects traffic to the network cards.

Agents and shutdown

The Windows and Linux agents authenticate to MayaUPS with mutual TLS. Each shutdown event runs a shutdown test before it is enabled, and an emergency stop disables every action at once.

Console and network

The console is reachable only from its own server until you open it to your network, and then only over TLS. MayaUPS sends no product telemetry.

Audit history

Every change to settings, users and shutdown events is recorded with who made it and when.

Updates and backups

Updates are signed and checked before installation, with automatic rollback. The database is backed up daily and can be restored in one step.

Security documents

A security policy, threat model, hardening checklist and CycloneDX software bill of materials are available for your review.

Report a suspected vulnerability to info@mayaups.com, with the affected product, the steps to reproduce and the expected impact. Leave out passwords and site keys.