Encrypted in Transit
Connections between gateways, servers, browsers and brokers use TLS. MQTT runs over TLS with client certificates or a username and password.
Most industrial protocols predate today's threats. IoTServa adds the controls they lack and tells you where the gaps are.

Connections between gateways, servers, browsers and brokers use TLS. MQTT runs over TLS with client certificates or a username and password.
Owner, Admin, Operator and Viewer roles are scoped per Client, Organization or Site, with per-user access control on top. API keys belong to one Organization and carry read or control scopes.
Each Organization and Site is read-only by default. Writes are enabled per Node within min and max limits, and every command is signed, re-checked by the gateway and logged.
Changes to configuration and every write to a device are recorded with who, what and when, in a tamper-evident chain.
Gateway configuration, telemetry and software updates are signed, and an update that fails its checks rolls back automatically.
Broker passwords, API keys and certificates are stored as secrets, not inside project exports or shared profiles.
A gateway initiates its connection outward, so you do not have to open inbound ports to the equipment network.
Every user can protect sign-in with an authenticator app or an SMS code, and Owners can require two-factor sign-in for the whole company.
Sign in with Microsoft Entra ID or Google Workspace through SAML or OpenID Connect, so access follows your own staff directory.
Limit sign-in to your office or VPN addresses, and set session timeouts and forced sign-out for shared control-room screens.
Databases, backups and stored files are encrypted at rest, and secrets are sealed with keys kept apart from the data.
Personal data is handled in line with the Malaysian Personal Data Protection Act, with data kept in the region you choose and exported on request.
These are properties of the protocols, not of IoTServa. Plan the network around them.
Modbus. Classic Modbus RTU and TCP have no built-in authentication or encryption, so anyone on the network segment can read or write registers. A separate Modbus/TCP Security specification exists, but few devices implement it.
BACnet/IP. Classic BACnet/IP is unauthenticated in practice. BACnet/SC adds secure connections where devices support it.
KNX IP. Unsecured by default. KNX Secure adds encryption and authentication where the installation supports it.
LoRaWAN. Encrypts application payloads end to end and protects network messages with integrity checks, using session keys. Keys must be provisioned and stored carefully.
IoTServa Private Edition runs on a server for your company alone, for stronger data privacy, security and governance.
Yes. VYROX INTERNATIONAL SDN BHD, the company behind IoTServa, is certified to ISO 9001:2015 for quality management and ISO/IEC 27001:2022 for information security. These certifications cover the company's management systems, not the IoTServa product itself. Ask about the controls you require and we will answer against your checklist.
No. Keep equipment networks segmented, and let a gateway connect outward to IoTServa instead of exposing devices.
Yes. Users can sign in with an authenticator app or an SMS code, Owners can require it for everyone, and companies can sign in through Microsoft Entra ID or Google Workspace.
We will answer each control honestly, including the ones that depend on your network design.