How to Configure Devin SSH Read Only Access
You set up devin ssh read only access by making a restricted Linux user. Then you pair that account with a limited shell and signed OpenSSH keys. Many teams start by giving an AI agent a broad admin key to debug hosts. That wide key lets the agent change files, restart apps, or read secrets by mistake. How devin ssh read only access works on Linux hosts OpenSSH does not have a single switch for a read only login. Instead, the host operating system controls what a user can read or write. You f
Auditor Read-Only Access + SSH Access Management: the complete guide
Architecture patterns, implementation strategies, and security best practices. Delivered to your inbox.
You set up devin ssh read only access by making a restricted Linux user. Then you pair that account with a limited shell and signed OpenSSH keys. Many teams start by giving an AI agent a broad admin key to debug hosts. That wide key lets the agent change files, restart apps, or read secrets by mistake.
How devin ssh read only access works on Linux hosts
OpenSSH does not have a single switch for a read only login. Instead, the host operating system controls what a user can read or write. You first create a dedicated user role on the target server for Devin. This user should belong only to groups that can read log files.
Next, you lock down the login shell for that user account. Standard shells let users write to temporary folders and run local scripts. A restricted shell stops the user from changing directories or setting new path variables. You also point the user to a small folder of safe, read-only tools.
To handle login keys, teams use OpenSSH certificates instead of static public keys. A certificate Authority key signs the agent public key to make a user certificate. The certificate holds the public key, an identity string, and valid user principal names. It also holds a set of options signed by the authority key.
OpenSSH certificates use a much simpler format than standard TLS certificates. When you sign a user certificate, you should always set a short validity window. Without a set window, an OpenSSH certificate stays valid forever by default. Short windows make sure old agent keys stop working after a task ends.
How to restrict commands in an SSH setup
File permissions alone do not stop an agent from running heavy commands. A read-only user can still run a command that uses up all server memory. To fix this, admins use OpenSSH certificate options or authorized keys rules. These rules can force a single command or block port forwarding during the login.
You can attach a wrapper script to the agent key or certificate. When Devin logs in over SSH, the server runs this wrapper script first. The script checks the command string that the agent wants to run. If the command is on an approved list, the script runs it.
Auditor Read-Only Access + SSH Access Management: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
If the command tries to edit a file, the script blocks the run. Teams often route these agent logins through a central bastion or jump host. The jump host holds the wrapper scripts and checks every login in one place. This keeps you from copying custom scripts to hundreds of backend servers.
What native SSH limits solve and what they miss
Native OS permissions and OpenSSH certificates solve the basic login problem well. They make sure the AI agent logs in as a known, low-privilege user. Certificate expiry windows also stop lost keys from working weeks later. Wrapper scripts block obvious write commands before they touch the disk.
Still, native SSH setup only checks who logs in and which binary starts. It does not inspect what happens inside an active shell session in flight. An agent can still read a config file that holds live database passwords. It can also read customer emails, phone numbers, card numbers, or national IDs in logs.
Standard SSH logs only record that a user logged in at a certain time. They do not show the exact commands the agent ran or the output returned. Maintaining custom regex wrapper scripts across many servers also breaks down over time. One small mistake in a shell script can let an unsafe command slip through.
Check SSH commands and file transfers on the host
OpenSSH keys and certificates decide who can log into a Linux host. They do not check what a one-shot command or file transfer does once the session starts. With hoop.dev, you run an open-source SSH server with guardrails on the host. It checks callers with OpenSSH certificates and works with ssh, sftp, scp, and rsync clients.
When a caller runs a one-shot command or moves a file, hoop.dev guardrails check the command or path before it runs. Then hoop.dev data masking masks matched sensitive patterns in downloads and output. Interactive shells carry no guardrails because keystrokes have no statement boundary. Teams can turn interactive shells off and allow only commands and file tasks. The audit trail logs who connected and what was allowed or refused, without storing keystrokes or file bytes. See the source on GitHub.
Frequently asked questions
Can OpenSSH make a session read only by itself?
No, OpenSSH only handles the login and starts the user shell. You must use Linux file permissions, restricted shells, or command rules to block writes.
Why use OpenSSH certificates for Devin instead of static keys?
Static SSH keys never expire unless someone removes them from the server by hand. OpenSSH certificates let you set a time limit and tie identity data to the key.
How do you stop Devin from reading secrets in log files over SSH?
OS permissions can block whole files, but they cannot hide single lines inside a log. To hide emails or card numbers inside output, you need in-flight data masking.
Related guides
In this post