Security
Built so customer access is harder to lose.
Trilinear exists to reduce risk: fewer clients, fewer stored passwords and fewer paths into a customer network. This page says how, in plain terms, and says plainly what we don't have yet.
- 01 Isolation
- A separate sandbox and network per tunnel
- 02 Credentials
- Encrypted at rest, never on endpoints
- 03 Sign-in
- A second factor on every account
- 04 Audit
- An append-only record of sign-ins and sessions
01 — The boundary
The laptop holds a browser tab. Everything sensitive stays behind the line.
With client software, each laptop carries a VPN client, a route into the customer and often the login too. Trilinear moves all three off the endpoint.
Zone A
Engineer's device
Holds
- A signed-in browser session
Never holds
- A VPN client or agent
- Customer VPN configurations or stored logins
- A route into any customer network
Zone B
Trilinear
Holds
- VPN configurations and shared logins, encrypted
- One sandbox and network per tunnel
- The audit record
Never does
- Route one customer to another
- Route a customer onto your network
- Send VPN configurations or logins to a laptop
Zone C
Customer network
Sees
- One VPN sign-in, under the account you chose
- RDP or SSH to the hosts you open
Never sees
- Your engineers' laptops
- Any other customer
02 — Principles
Seven rules the product keeps.
Each one is enforced in the product today, not written in a policy.
- 01
Isolation is the default
Every VPN connection runs in its own sandbox with its own network. One customer can't see another, even when they use identical address ranges, and nothing is routed onto your own network. In production, sandboxes run behind a hardware-virtualised boundary instead of sharing the host's kernel.
- 02
Credentials stay on the server
Customer VPN configurations and shared logins are encrypted at rest. They never land on an engineer's laptop, and the tunnel process is handed only what it needs for that one connection. A password an engineer types for a connection is used to connect and is not stored.
- 03
Strong sign-in, no exceptions
Every account needs a second factor: a built-in authenticator code, or your identity provider's MFA when you sign in with Microsoft. Passwords are stored as Argon2 hashes. Five failed attempts lock an account for 15 minutes.
- 04
Sessions end
A signed-in session expires after an hour of inactivity and after 16 hours regardless. Disabling a person ends their live session immediately.
- 05
Access follows need
Engineers see and connect only to the customers they've been granted. Administrators decide who has what. Tunnels exist only while someone is using them and shut down on their own.
- 06
A record of everything
Sign-ins, failed attempts, VPN connections and host sessions are logged with who, what and when. Trilinear only adds to that record. It never edits or deletes history.
- 07
Trust on first use, verified after
When a gateway presents a certificate Trilinear can't verify, an administrator checks its fingerprint and pins it. If it ever changes, the connection stops and asks again. An administrator can choose to auto-accept changes for a specific gateway. That is off by default.
03 — Data handling
What Trilinear stores, and how.
The questions a security review asks first, answered up front.
| Data | Stored? | How |
|---|---|---|
| Account passwords | As a hash only | Argon2, salted. The password itself is never stored. |
| Authenticator secrets | Yes, encrypted | Encrypted at rest with authenticated encryption. |
| VPN configurations and shared logins | Yes, encrypted | Encrypted at rest, with support for key rotation. Handed to a tunnel only for that customer's connection. |
| VPN passwords typed per connection | No | Used once to bring the tunnel up, then discarded. |
| Gateway certificates | Fingerprint only | Pinned once an administrator approves it. A change stops the connection, unless an administrator has chosen to auto-accept for that gateway. |
| Audit events | Yes, append-only | Who, what, when and from where. Never edited or deleted by the product. |
| Session content | No | Screens and keystrokes are not recorded. Session recording is on the roadmap. |
04 — Compared with client software
What changes for your risk.
A lost laptop holds no keys. No customer VPN client or login lives on the device, so losing one doesn't open a customer network.
No split-tunnel surprises. Your engineer's machine is never joined to a customer network.
Offboarding is one switch. Disable the account and access ends, instead of chasing credentials across devices.
One place to review access. When a customer asks who connected and when, the answer is already written down.
05 — Assurance
What we can and can't show you yet.
Compliance
Independent audits are planned, not done.
Controls are designed to line up with SOC 2 and ISO 27001. We hold neither today. Reports will be published here when they exist, and not before.
Responsible disclosure
Found something? Tell us.
Email security@trilinear.app. We'll acknowledge your report, keep you updated and credit you if you'd like. Please give us a reasonable chance to fix an issue before sharing it.
Shared responsibility
What stays with you.
Trilinear secures the access path. You still own your customers' VPN accounts and the permissions behind them. We recommend named per-engineer accounts where a customer allows them, and least privilege on the other side.
Running a security review?
Join the waitlist and mention it. We'll answer your questionnaire and share more detail under NDA.