Is LRO suitable for compliance and audit requirements?

LRO is built around the things an auditor asks about: who can reach what, who did what, and can anyone in the middle read the data. Here is how each is handled.

An append-only audit log

Actions taken in the panel are recorded to an audit log that is append-only — entries are added, never edited or deleted in place. What gets recorded includes:

Each entry records the acting user and their IP address — or the system itself for automatic events such as a subscription renewal — and is written in the same database transaction as the change it describes, so the record and the action are committed together, not as a best-effort afterthought. The log captures who did what in the panel; it is not a session or keystroke recorder, and the financial ledger of amounts and balances lives in the separate billing history.

Operators cannot read your traffic

Tunnel traffic is end-to-end encrypted between the agents. The server relays opaque ciphertext and holds no key to decrypt it, so “the provider can read our sessions” is simply not a risk in the model.

Least-privilege access

Access is granular: organizations group machines, and permissions are assigned per user and per endpoint, so a person sees and reaches only what they have been granted. That maps directly onto least-privilege and separation-of-duties expectations.

Together — append-only audit trail with actor and IP, end-to-end encryption, and per-endpoint access control — LRO supports the access-control and accountability controls common to SOC 2 and ISO 27001 programmes. For specific framework or contractual requirements, talk to us.

Grant least-privilege access and keep an audit trail of every action.

Create an account →