Tool profilesBased on official documentation, not tested by us

Lynis: a free audit that checks a Linux server's security settings and tells you what to fix

Lynis is an open source auditing tool that runs on the system itself, runs hundreds of tests and lists warnings and suggestions to harden it. Based on the official README and documentation, not tested by us: what it does, what it needs, its limits and what we could not confirm.

Type

Security audit and hardening tool (runs on the host)

License and cost

GPLv3 and free to run, with no functional limits per its FAQ. CISOfy also sells Lynis Enterprise (web interface, dashboards, hardening snippets, support), which we did not read about in detail

Reviewed

9 Nov 2026

Version

Not shown on the pages we read

Best for

Anyone who runs their own Linux server and wants a checklist of settings to tighten, without a network scan.

Watch out for

A full audit needs root, and the log is overwritten at every run. Run it only on systems you own or are allowed to audit, and read each suggestion before changing anything.

← All tool profilesNo. 10 / 11

In one sentence

Lynis is a security auditing tool: you run it on a server and it checks the system's own settings (kernel, accounts, services, file permissions and more), then lists warnings and suggestions to harden it. It looks inside the machine, not at your network from the outside.

Who it is for

People who run their own Linux, BSD or macOS machines: a small VPS, a home lab, a company server. It is not for a founder whose whole product sits on a hosted service, where the provider handles the servers. We cover it as analysis only.

What the documentation says

Everything below comes from the README, the product page and the documentation, read on 9 November 2026.

  • What it is: the README calls it a security auditing tool for UNIX-like systems such as Linux, macOS and BSD. It runs on the system itself and does what the README calls an in-depth security scan. The listed goals are automated security auditing, compliance testing (ISO 27001, PCI DSS, HIPAA) and vulnerabilityVulnerability A weakness in software, a setting or a process that an attacker could use to get in or do harm. Tap again to open the glossary detection.
  • How it works: the product page says scanning is modular and opportunistic: it only uses what it finds on the system. It runs hundreds of tests, mostly shell scripts, each with an identifier such as KRNL-6000.
  • Licence: GPLv3. The project says it has existed since 2007.
  • Ways to get it: a distribution or CISOfy package, Homebrew, a tarball or a git clone. The README and product page say installation is not required: you can extract it and run it from the folder.
  • The documented command: lynis audit system (written ./lynis audit system when run from a folder). Other options include --quick and --pentest, a non-privileged scan for when you do not have root.
  • Requirements: write access to /tmp. For a full audit the documentation says it must run as root.
  • Output: details go to a log file, by default /var/log/lynis.log, which is purged at every scan. Warnings and suggestions go to a separate report file, lynis-report.dat.
  • Warnings and suggestions: warnings are usually events that need action; suggestions point to room for improvement. The documentation says there are normally many more suggestions than warnings, that a warning is not always bad, and that an "OK" does not always mean the target is correctly configured.
  • Free and paid: the FAQ says Lynis is open source and free to use, with no limits on functionality. Lynis Enterprise is a separate paid product with central management and reporting.

The good

  • Free, open source and old enough to be well known.
  • No installation needed: it can run from a folder.
  • It inspects the real settings of the machine, which an outside scan cannot see.
  • Every finding has an identifier you can look up in the log.

The limits it admits

  • "Lynis needs to be executed as root for a full audit." Without root only a reduced scan is possible.
  • No auto-updating yet, according to the documentation.
  • It is tested on the most common operating systems, not all of them.
  • The log is overwritten each time, so copy it if you want to compare runs.
  • If the files are unpacked by a non-root user, it warns about ownership and permissions.

When not to use it

  • On a system you do not own or have no permission to audit.
  • If you think a clean report means you are secure. It means the checks it knows about passed.
  • If you want to scan from outside, as an attacker would see you. It is a different kind of tool.
  • If you apply every suggestion without reading it. Some may not suit your setup.

What it costs you

A server you can log in to as an administrator, and time to read the results and decide what to change. We found no figures for how long an audit takes. It is not a one-off: settings drift as you install things.

Typical setup mistakes

  • Running it as a normal user and trusting the result. The full audit needs root, and --pentest is a reduced scan.
  • Treating every suggestion as an order. The documentation says a warning is not always bad. Judge each one. This is our advice.
  • Losing the previous report. The log is purged at every scan; keep copies if you want to see progress.
  • Downloading it from an unofficial place. Use the official repository or package source and check what you get. This is our advice.
  • Doing it once. Repeat after big changes.

How to check that it works

Official documentation and our approach, not something we ran: in a throwaway virtual machine you own, with nothing real on it, run the audit command, then deliberately weaken one setting (for example, leave a test account without a password) and run it again to see whether a finding appears or changes.

Where to start

We did not test the tool, so we offer no tutorial for now. Start with the documentation: httpsHTTPS The secure version of the web address protocol: it encrypts what travels between a visitor and your site and checks that the site is the real one. Tap again to open the glossary://cisofy.com/documentation/lynis/

What we could not confirm

We did not install or run Lynis. We read the README, the product page and the documentation, not the Get Started guide, the list of tests or Lynis Enterprise. No page we read showed a version number or release date, and we could not find a definition of the hardening score the tool is known for. We do not know how many false alarms it gives or how it compares with other auditing tools.

Glossary: hardening, vulnerability, root, exposure scanner. Runbook 01, security check.

More free tools

Other profiles in this section.

Sources

Follow us

New profiles and security news: YouTube (@safet2ship) and Instagram (@safet2ship).

YouTube channel · Instagram

Get the free runbooks

One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

Send me the runbooks