Skip to content

Linux Server Security Audit

Find what’s open. Fix it with your approval.

CtrlOps runs 25 read-only security audits on your Linux server over SSH, across SSH and access, firewall, databases, web servers and Docker. You get a hardening score, a PDF report you can hand a client, and fix commands that wait for you to press Run.

Download for MacDownload for Windows

14-day free trial, no credit card required.

Read-only checks over the SSH you already use. Nothing installed on your server, and findings stay on your computer.

Show me

Example: A score, every finding and what to do about it, in a PDF you can send.

A score, every finding and what to do about it, in a PDF you can send. Example server. Audits are read-only and run as your SSH user.

What it checks

25 audits. 157 checks. From SSH to Docker.

Pick the audits that match what the server runs. Every check only reads configuration, and one that needs sudo says so.

SSH & Access

Root login, password auth, port, idle timeout, authorized keys and sudo privileges.

11 checks~14s2 need sudoread-only

  • SSH Root Login, high severity
  • SSH Password Auth, medium severity
  • SSH Port, low severity
  • SSH Idle Timeout, low severity
  • SSH Authorized Keys, high severity
  • Extra Root Accounts, high severity
  • Sudo Group Members, medium severity
  • Passwordless Sudo Rules, medium severity
  • SSH Login Restrictions, high severity
  • SSH Crypto Algorithms, medium severity
  • Password Ageing, low severity

Why switch

Still checking servers by hand? Do it in one tab.

Pick how you check a server today, and see what changes in CtrlOps.

Today · By hand

6commands per server, then the write-up

  • Know which questions to ask, and how each distro answers
  • Read every output and decide yourself whether it’s bad
  • Write the findings up by hand, then repeat on the next server

In Sophos’s study, one cloud server was attacked within 52 seconds of going live, and each was hit 13 times a minute. Sophos, 2019 (opens in a new tab)

With CtrlOps

157checks, each with a verdict

  • Every check returns a status and a severity
  • A score, the coverage and a PDF, without the write-up
  • The same audit on the next server, or on several at once

Inside the report

What’s in the audit report? Score, findings and a PDF.

The parts of an audit run that make it worth acting on, and worth sending.

Scope

Only the checks that fit this server

Coverage

A check it can’t read says why

Severity

Worst first, one click

Many servers

The same audit on every server, one report each

Reports

Every run saved, ready to send again

Distros

Ten Linux families, detected for you

Reviews

What people say about the security audit.

Public reviews from people who run servers: finding problems early, and approving every fix.

Nasty surprises

The security audit feature alone would save so many teams from a nasty surprise later.
Vidushee GeetamOn Product HuntProduct Hunt logo

Fixes you approve

…What stands out from an engineering perspective is the approval gate on the AI terminal. Most AI tooling here either runs blind or needs too much manual intervention to be useful. This sits in the right place: the AI does the thinking, the engineer makes the call.
Drijesh P.Engineering Manager at IBMLinkedIn logo

Nothing runs blind

The approve before execute thing is what sold me. Every other AI tool just runs stuff, and you find out what happened after.
Bhautik KapadiyaOn Product HuntProduct Hunt logo

Keys stay local

…Knowing our SSH keys and credentials stay entirely on my local machine, never touching a third-party cloud, gave me the confidence to adopt it.
Chintan P.Co-founder & CEO of BytezTechG2 logo

Context to approve

The approval boundary feels like the real product here. Once AI is suggesting server actions, the useful question is not just whether a command was generated, but whether the operator has enough context to approve it safely.
KeesanOn Product HuntProduct Hunt logo

FAQ

Questions about the security audit.

Can't find your answer? Join Discord

  • Connect the server in CtrlOps and open Audit in the left sidebar. Pick an audit from the catalog, click Generate, tick the checks you want, and click Continue. The checks run over the SSH session you already have, the log streams live, and you get a report with a hardening score and a PDF.

  • 25 audits with 157 checks in four groups: the server itself (SSH and access, firewall, services, file system, updates, logging), databases (MySQL and MariaDB, PostgreSQL, MongoDB, Redis), web servers (Nginx and Apache) and Docker. Every check is listed in the security checklist.

  • Yes. Every check only reads configuration, permissions and process state, and nothing on the server changes. Nothing is installed, and a run that stops partway leaves nothing behind. Only a fix command you approve in the AI terminal changes anything.

  • No. Audits run as the SSH user you connected with. A check that needs to read a root-only file is marked SKIPPED with the reason, and the score card shows the coverage, so a partial run is never mistaken for a clean one. Connect with sudo or as root for full coverage.

  • Yes. Download any run as a PDF with the hardening score, the severity split and every finding with its status and message. The header names the server, its address, the date and the audit version, and past runs stay under Reports.

  • No. Fix selected findings copies a prompt to your clipboard. You paste it into the AI terminal, the assistant writes the command and explains why, and nothing runs until you press Run. Then run the audit again to measure the change.

  • Yes. Open Audit Reports from the Home screen, pick the audit, tick the servers, and click Run on N servers. Each server is audited separately and gets its own report.

  • Either the software isn’t on that server, such as a database audit on a web-only box, or the check needs root to read a file. Run only the audits that match what the server runs, or reconnect with sudo to raise the coverage.

  • No. It’s a configuration audit: it reads how the server is set up, with no CVE feed and no exploit testing. For CVE scanning, use a dedicated scanner such as Trivy, Grype or Nessus alongside it.

  • No. Every audit is a run you start, with no agent and nothing watching between runs. For continuous detection, a host intrusion detection system such as Wazuh or Falco is the right tool.

  • Not as attested evidence. The checks aren’t mapped to CIS Benchmark or STIG control IDs. The report is a hardening record you can act on and hand to a client.

  • Yes. The free VPS security scanner looks at open ports, TLS and HTTP headers from the public internet, with nothing to install. The audit reads the configuration from the inside; the two answer different questions.

  • The Free plan shows your score and summary. Every finding, fix and PDF comes with Personal, $9 a month or $349 once for Lifetime, with unlimited servers and a 14-day free trial, no card needed. See pricing. The Security Audit docs walk through each step.

Find what’s open on your server.

PuTTY
Termius
MobaXterm
WinSCP
SecureCRT
Royal TS
Warp
CtrlOps14 tools left
Webmin
aaPanel
RunCloud
Dokploy
IP spreadsheet
bash (2)
sticky notes

Run your first audit in about 14 seconds: read-only, over the SSH you already use.

Start instantly · No credit card · Cancel anytime

Your privacy preferences. We use product analytics to improve CtrlOps. Google measurement runs without analytics cookies. Live chat stays off until you allow it. Cookie policy