Tool and Usage
- Year of inception
- Programming language
- shell script
- Michael Boelen
- Latest release
- Latest release date
Lynis is an open-source security auditing tool that is available since 2007 and created by Michael Boelen. Its primary goal is to evaluate the security defenses of systems running Linux or other flavors of Unix. It provides suggestions to install, configure, or correct any security measures.
Why this tool?
Lynis can detect vulnerabilities and configuration flaws. Where a typical vulnerability scanner will just point out vulnerabilities, Lynis aims for an in-depth audit and continuous improvement. For this reason, it needs to be executed on the host system itself. By seeing the system from the inside out, it can provide more specific details than the average vulnerability scanner.
How it works
Lynis starts with an initialization phase in where it detects the operating system. After that part is finished, the discovery of binaries and tools is done. This collecting of tools is the base for the scanning engine, that performs hundreds of individual tests. Every system will have a different set of performed tests. After completing the scan, a report with findings and suggestions is displayed.
The tool is typically used by system administrators, security professionals, and auditors. Occasionally a pentester will also use it during a security assignment to discover vulnerabilities or find possible flaws in the system to exploit.
The tests performed by Lynis are a combination of advice found in hardening guides, tips by Linux distributions and vendors, and other best practices within the field.
Lynis was originally written by Michael to automate security scans of systems he managed for his employer at the time. He devoted his spare time to replace printed hardening guides at his desk with the tool. In 2013, Michael went to full-time development on Lynis and the commercial Lynis Enterprise version.
Usage and audience
Lynis is commonly used for IT audit, penetration testing, security assessment, system hardening, or vulnerability scanning. Target users for this tool are auditors, pentesters, security professionals, and system administrators.
- Command line interface
- Customization and additions are possible
- Extendable with custom tests and plugins
- Installation of tool is optional
- Tool is modular
Example usage and output
Tool review and remarks
The review and analysis of this project resulted in the following remarks for this security tool:
- + The source code is easy to read and understand
- + More than 100 contributors
- + More than 8000 GitHub stars
- + Tool is easy to use
- + Available as package (simplified installation)
- + Commercial support available
- + Used language is shell script
- + Very low number of dependencies
- + Project is mature (10+ years)
- + The source code of this software is available
History and highlights
- Demo at Black Hat Europe 2014 Arsenal
- Demo at Black Hat Europe 2015 Arsenal
- Demo at Black Hat Europe 2016 Arsenal
- Demo at Black Hat USA 2015 Arsenal
- First Lynis release in 2007 (November)
Supported operating systems
Lynis is known to work on AIX, FreeBSD, Linux, NetBSD, OpenBSD, Solaris, and macOS.
- No installation required (just extract/run)
- Git clone
- Tarball (extract)
|Run only Lynis tests from one group|
lynis audit system --tests-from-group "firewalls"
Similar tools to Lynis:
YASAT describes itself as another simple stupid audit tool to test Linux systems. It has many tests for checking the security configuration of the system.
Tools to assist administrators and auditors with assessment, measurement and enforcement of security baselines
Zeus is a security tool to provide security audits on AWS environments. It is written in shell script and can be used for security audits.
This tool page was updated at . Found an improvement? Help the community by submitting an update.
Related tool information
- Technical audit
- A technical audit is the process of information gathering and analysis of company assets. Typical areas that are checked are compliance with security policies.