What your security review will ask, answered
A VPN for AI tools passes through the security team before it reaches developers. This page lists what they will ask about and what Guard Tun does.
Reliable leak protection
If the tunnel drops, traffic to the listed AI domains stops instead of going out directly. This holds on Windows, macOS and Linux. The rest of the machine keeps working, so a dropped tunnel does not take the developer offline, and traffic to the listed domains does not leave from the wrong address.
Encryption and your own egress
One encrypted tunnel runs from the device to your node. The node is a server you own, so the egress is your address and there is no third party between your developers and the AI service.
Everything is signed
Client updates and routing lists are signed. The client checks the signature before it uses either, so a client acts only on what your installation published.
Audit and SIEM
Every action of an administrator is written to the audit log. You can export it to your SIEM, which fits it into the monitoring your security team already runs. The export is off by default and you switch it on.
Administrator access
The console is for administrators only. SSO and MFA for administrators are coming soon.
Where it runs
The console and the nodes run on your servers, under your network rules, your backups and your access control. That puts the installation inside the controls your company already operates, instead of adding an outside service for the security team to assess. The questions a reviewer asks about a hosted VPN, such as who else can see the traffic and where the records are kept, get a short answer: your servers, your people.
Nothing here replaces your own review, and it should not. The aim is to make the review quick, because the answers are concrete and each one can be checked in the product.
A checklist for the reviewer
- If the tunnel drops, traffic to the listed domains stops instead of going out directly.
- Reliable leak protection on Windows, macOS and Linux.
- One encrypted tunnel from the device to your node.
- The egress address is your own server.
- Client updates and routing lists are signed and checked before use.
- Audit log of administrator actions, with SIEM export that you switch on.
- The console is for administrators; SSO and MFA are coming soon.
What this does not claim
Leak protection covers the listed AI domains: that is the traffic the product is there to protect. Other traffic goes direct by design. SSO and MFA are not available yet, and we say so rather than hide it. The product has no named certification, and it does not replace your own controls. What it gives your reviewer is a set of specific, checkable behaviours.
Questions
What happens to AI-tool traffic if the tunnel goes down?
Traffic to the listed AI domains stops instead of going out directly. The rest of the machine keeps working, and the client works to bring the tunnel back.
Can we send the audit log to our SIEM?
Yes. Export to a SIEM is built in. It is off by default, and you switch it on.
Is there SSO and MFA?
For administrators, they are coming soon.
Do you have certifications?
The product runs on your infrastructure, so it falls under your own controls. We answer your security questionnaire on request.
Request a demo or a pilot
Tell us about your team, and we will come back with a time for a call and a plan for a pilot.