How to Configure Make SSH Data Masking
To set up make ssh data masking, you pair remote shell steps with output filters. This setup rewrites sensitive fields before the automation tool stores the command output. Teams often use Make to run remote scripts on Linux hosts over SSH. They store private SSH keys inside the automation tool to log in. This broad role lets the automation runner read any file that the Linux user owns. If a script prints customer records, those raw values land in the build logs. How to set up make ssh data ma
Data Masking (Static) + SSH Access Management: the complete guide
Architecture patterns, implementation strategies, and security best practices. Delivered to your inbox.
To set up make ssh data masking, you pair remote shell steps with output filters. This setup rewrites sensitive fields before the automation tool stores the command output. Teams often use Make to run remote scripts on Linux hosts over SSH. They store private SSH keys inside the automation tool to log in. This broad role lets the automation runner read any file that the Linux user owns. If a script prints customer records, those raw values land in the build logs.
How to set up make ssh data masking with native tools
In a standard setup, Make connects to a remote server using an SSH key. Or, teams use an OpenSSH certificate signed by a Certification Authority key. An OpenSSH certificate holds a public key, identity info, principal names, and signed options. Certificate login for users and hosts arrived in OpenSSH 5.4. It uses a much simpler format than X.509 certificates. When the automation scenario runs, it opens an SSH tunnel to the target host. Then it runs a shell command and reads back the standard output stream.
Native OpenSSH does not inspect or alter command output on its own. To build a basic filter, engineers pipe the remote command through text tools. They write regular expressions in the shell script to find patterns like emails. The script replaces matched patterns with placeholder text before sending data back to Make. Teams also try to limit risk by restricting which scripts the SSH key can run. They bind the public key or certificate to a single wrapper script on the host. That wrapper script runs the job and applies text replacement rules to the output.
What native SSH setup solves and what it misses
OpenSSH keys and certificates do a great job of proving who can log in. Signing a public key with a CA key lets you set user principals and options. You can also set a validity time window so the certificate expires on schedule. Without a validity window, an OpenSSH certificate stays valid forever by default. These native controls stop unknown users from opening a shell on your Linux hosts. They also help you map a specific automation job to a specific host user.
Still, login checks only decide who gets into the server at the start. They do not watch what individual commands do once the session is active. Relying on shell scripts for data masking creates major gaps for operations teams. If an engineer edits the Make scenario and forgets the pipe filter, raw data leaks. Output containing phone numbers, card numbers, or national IDs goes straight into Make logs. Maintaining regex filters across dozens of remote servers takes a lot of manual work. When a pattern changes, you must update every wrapper script on every Linux host. Also, standard SSH logs do not show which specific commands ran inside the automation session.
Data Masking (Static) + SSH Access Management: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Inspect one-shot SSH commands and file tasks
SSH certificates and host rules decide who is allowed on a machine. Setup alone does not check single commands or block sftp reads on sensitive paths. By design, hoop.dev runs an open-source SSH listener on the host where people and agents keep their normal ssh, sftp, and scp tools.
First, hoop.dev guardrails check one-shot commands and file paths before they run. Next, hoop.dev data masking masks matched values in file downloads. The audit trail logs the certificate principal, requested action, and verdict without storing session content. Interactive shells carry no guardrails and can be turned off when every action must be checked. Explore the code on GitHub.
Frequently asked questions
Can OpenSSH mask sensitive data in command output by itself?
No, OpenSSH only handles encrypted transport and user or host login checks. It does not parse command output or rewrite fields like emails or card numbers.
How do teams usually hide secrets in Make SSH outputs?
Teams often pipe remote command output through text tools on the Linux host. This manual method breaks if someone changes the command in the Make scenario.
Why are static SSH keys risky in automation tools like Make?
Static keys do not expire on their own and often grant full shell permissions. If a key leaks, anyone can run commands and read raw data on the host.
Related guides
In this post