Security
The AI gets one way into your systems: the gateway.
Suveren checks every action the AI takes through the gateway. It cannot check what the AI does another way. This page shows your IT how to close the other ways, and how to check that they are closed.
What has to hold
Four things have to be true
Setup
Choose a setup
Copies a guide for your own AI: the four things, the setups, the locks for your AI app, and how to read the result.
Setup
How to give the AI its own place
An AI with a terminal runs in a container with one door. Through the door it reaches the gateway and its AI provider. It reaches nothing else: no other website, no other program on the computer, none of your files.
You need Docker and two small files from the gateway's documentation. One builds the AI's place, the other is the door. Tested with Claude Code: it connects to the gateway and reaches its provider, and every other address is refused.
The steps and the two files →Locks
Lock the AI app
These four AI apps can be locked by your IT. ChatGPT in the browser and Microsoft 365 Copilot cannot reach a gateway inside your company, so they are not covered here. The settings for Claude Code and Codex are tested on Windows 11. The others come from each vendor's documentation; try them on one computer first.
| AI app | What your IT sets | Where |
|---|---|---|
| Claude Code | A fixed connector list with only the gateway. Terminal and web access forbidden, or confined to a sandbox on the AI's own machine. Connectors from the Claude account switched off. | Managed settings in a system folder only administrators can write |
| Claude desktop app | The gateway as managed connector. Extensions, built-in browser, Cowork and the Code area switched off. Chrome extension off and blocked in the browser. | Device management, plus the Claude admin console |
| ChatGPT desktop app and Codex | A connector list with only the gateway. Browser use, computer use, plugins and web search switched off. | A requirements file in a system folder, plus OpenAI's admin console |
| GitHub Copilot in VS Code | A connector list with only the gateway. Browser tools and automatic approval off. The terminal cannot be removed, so this app belongs on its own machine. | Copilot's managed settings and VS Code's policies |
Locks
Lock the gateway
The AI app is one side. The gateway is the other. Your IT fixes the address of the Authority Server in a settings file that only an administrator can change. Without it, a person could point the gateway at another server, one that signs anything. Your IT also installs the gateway itself, so the person cannot change the program.
Tested on Windows 11: a normal user can neither change nor delete this file.
Setup check Coming soon
Check it
The Setup check is in development. This is what it will do.
Your IT runs the Setup check that comes with the gateway. It reads, changes nothing and sends nothing. Each line ends in closed, open or cannot tell. Any AI can explain the result to your IT, but never the AI that is being checked. Run it at installation, after every update, and every month.
# Example of a result $ suveren-gateway check Suveren Setup check — 12 November 2026 AI apps found: Claude desktop app, Claude Code No other route closed Claude desktop app: the gateway is the only connector open Claude Code: 2 other connectors (github, postgres) open Claude Code: terminal is allowed cannot tell Connectors in the Claude account: confirm in the admin console No passwords within reach closed No key files for connected systems outside the vault No hand on the gateway closed Gateway answers only on this computer open AI app and gateway run under the same user account Result: 3 open, 1 to confirm by hand
Copies a guide for your own AI: the four things, the setups, the locks for your AI app, and how to read the result.
By hand
Confirm by hand
Three things the Setup check cannot see:
- Connectors switched on in your AI provider's account.
- The service accounts your systems accept.
- Whether the AI can operate the browser your people approve in.
The AI itself
What no setup closes
Even when every way around the gateway is closed, the AI can still do this:
- Everything the mandate allows. Start with narrow mandates. Widen them when the tickets show it works.
- Be wrong inside the limits. The gateway checks to whom, how much and how often. It does not check whether a text is right. Let a person approve what leaves your company until you trust the results.
- Be steered by what it reads. An incoming email can contain instructions for the AI. The limits hold even then, so keep recipients and amounts narrow.
- Pass on what it reads to your AI provider. Decide by contract which data the AI may read.
- Ask for more. A person who approves without reading is the weakest point.
In general
General advice for AI that acts
- Give the AI its own place. An AI with a terminal runs in a sandbox, a container or a virtual machine, never in a person's everyday account.
- Let it reach only what it needs. From that place, the AI reaches the gateway and its AI provider, and nothing else.
- Keep passwords out of that place. No keys in files, in the environment or in the AI app. They belong in the gateway's vault.
- Treat everything the AI reads as untrusted. Emails, web pages and documents can contain instructions for the AI.
- Approve on a screen the AI cannot touch. The AI does not control the browser or the screen in which a person approves.
- Give every system its own narrow key, and replace keys regularly.
- Keep the AI app and the gateway up to date.
- Decide which data the AI may read, and settle with your AI provider what happens to it.
Limits
What is still open
- An administrator can undo every lock. The person using the AI must not be an administrator on that computer.
- On one shared computer, the gateway is protected only because the AI has no terminal.
- An AI that can operate the person's browser or screen can approve for them. Both must be off.
- The Setup check sees the computer, not the AI provider's account.
- An AI app the Setup check does not know is reported as "cannot tell".
- The check shows one moment. A setup can open again the next day.
- The gateway limits what the AI may ask for, not the service account itself. If an account allows more than the mandates need, narrow it in the system.