https://cisofy.com/lynis/ Lynis is a battle-tested security tool for systems running Linux, macOS, or Unix-based operating system. It performs an extensive health scan of your systems to support system hardening and compliance testing. The project is open source software with the GPL license and available since 2007. Project goals Since Lynis is flexible, it is used for several different purposes. Typical use cases for Lynis include: Security auditing Compliance testing (e.g. PCI, HIPAA, SOx) Penetration testing Vulnerability detection System hardening Audience and use cases Developers: Test that Docker image, or improve the hardening of your deployed web application. System administrators: Run daily health scans to discover new weaknesses. IT auditors: Show colleagues or clients what can be done to improve security. Penetration testers: Discover security weaknesses on systems of your clients, that may eventually result in system compromise. Supported operating systems Lynis runs on almost all UNIX-based systems and versions, including: AIX FreeBSD HP-UX Linux macOS NetBSD NixOS OpenBSD Solaris and others It even runs on systems like the Raspberry Pi, IoT devices, and QNAP storage devices. How it works Lynis scanning is modular and opportunistic. This means it will only use and test the components that it can find, such as the available system tools and its libraries. The benefit is that no installation of other tools is needed, so you can keep your systems clean. By using this scanning method, the tool can run with almost no dependencies. Also, the more components it discovers, the more extensive the audit will be. In other words: Lynis will always perform scans that are tailored to your system. No audit will be the same! Example: When Lynis detects that you are running Apache, it will perform an initial round of Apache related tests. Then when it performs the specific Apache tests, it may also discover a SSL/TLS configuration. It then performs additional auditing steps based on that. A good example is collecting any discovered certificates, so that they can be scanned later as well. Audit steps This is what happens during a typical scan with Lynis: Initialization Perform basic checks, such as file ownership Determine operating system and tools Search for available software components Check latest Lynis version Run enabled plugins Run security tests per category Perform execution of your custom tests (optional) Report status of security scan Besides the report and information displayed on screen, all technical details about the scan are stored in a log file (lynis.log). Findings like warnings and suggestions are stored in a ... https://www.youtube.com/watch?v=iWi69yAn0Fw