What each access does, and who authorised it.
This page describes the mechanisms in place and their limits, for a factual assessment by your security team.
The mechanisms
Connections
Agents open an encrypted (TLS) connection to the hub: no inbound port to open on site. The hub is the control point: it sees the traffic in order to enforce permissions and keep the log. There is therefore no end-to-end encryption between the operator and the agent.
Permissions
A new access key starts with no permission at all. Each action and each tool is enabled machine by machine; new tools arrive disabled.
Approval
Depending on the configured policy, some equipment write operations require approval in the console, with a one-time code (TOTP). System commands, files and on-screen actions are governed by separate permissions, enabled machine by machine.
Audit log
The hub keeps an append-only log: accounts, successful and failed logins, permissions, approvals. Every call leaves a line stating its type and target, without arguments or results.
Command log
Optional: who, which tool, which machine, status and fingerprint, and in full mode the masked arguments and output. CSV or NDJSON export from the console; the export itself is logged.
Secrets
The connector engine resolves equipment passwords on the agent; their values are replaced with *** in its results and log.
Accounts
Administrators, operators, client accounts limited to their site, read-only observers.
Updates
Agent releases are signed and verified before installation.
What does not exist yet.
- No single sign-on (SSO) or hardware keys (WebAuthn) for the console yet.
- No turnkey high availability for the hub.
- The audit log is a transactional history in the database; it is not cryptographic proof that would hold against a database administrator.
- Audit log retention is decided with the operator: there is no automatic purge.
These points are described in the technical documentation and in every architecture review we carry out with a client.
A technical review with your team?
We walk through the architecture, the flows and the log on a demo instance.