tyler.durden
/
lynis
mirror of https://github.com/CISOfy/lynis.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Lynis - Security auditing tool for Linux, macOS, and UNIX-based systems. Assists with compliance testing (HIPAA/ISO27001/PCI DSS) and system hardening. Agentless, and installation optional.
3,048 Commits 2 Branches 62 Tags 17 MiB
Shell 99.6%
Roff 0.4%
Go to file
Simon Biewald 529bcb2a60
Test for LINUX_VERSION before setting it again 
Before parsing /etc/debian-release and /etc/lsb-release,
it is now checked if the variable LINUX_VERSION is already set.

This fixes cisofy/lynis#1003, but has some side effects.

This will affects Ubuntu and Debian based distributions, like:
 - Pop!_OS (Ubuntu based)
 - Kali (Debian Based)
 - Raspbian
 - ...

Unfortunately this will likely skip/brake a few tests for those
distributions, as they are not considered to be Ubuntu or Debian
anymore. Linux Mint was already detected properly, but at least some
tests already had support for them (will other tests for Ubuntu are
skipped).

Those are tests I identified that will be skipped incorrectly now:
 - BOOT-5180: Check for Linux boot services (Debian style)
     It was already skipped on Linux Mint.
 - KRNL-5622: Check default run level on Linux machines
     This will only be skipped if systemd is not installed. It is
     already skipped on Linux Mint in this case.
 - KRNL-5788: Checking availability new kernel (sic!)
     This was already skipped on Linux Mint.
 - PKGS-7388: Check security repository (...)
     It will now be skipped for all distributions that do use the
     Debian / Ubuntu security repositories but are not detected as such
     anymore (like Pop!_OS). It will now be correctly skipped on
     Raspbian. This test was already aware of Linux Mint.
 - PKGS-7390: Check Ubuntu database consitency
     I am not sure why this test is Ubuntu only, thus it already
     skipped on Debian and Mint.
 - PKGS-7394: Check Ubuntu upgradeable packages
     I am not sure why this is for Ubuntu only, too.
     I think this should be feature tested instead, as
     apt-show-versions can be installed on any Debian based
     distribution as well..
 - PKGS-7366: Checking if debsecan is installed (...)
     While it may be correct to skip, debsecan remains usefull if
     package versions, patches and vulnerability fixes are very close
     on Debian itself.
     It is the correct behaviour to not do this test on Ubuntu and
     Ubuntu based distributions, as Canonical does not provide the
     required databases.
 - PKGS-7420: (Autoupdates)
     Linux Mint was already skipped on this test.

I think this could be solved by introducing a variable like
LINUX_VERSION_PARENT. On Linux Mint it would be set to Ubuntu, on e.g.
Kali Linux the veriable has the value Debian. Tests can use this variable
to check if it is broadly applicable, and then check if the specific
distribution is excluded.
 		2020-08-08 01:39:13 +02:00
.github Set more conservative values 2019-12-26 14:48:48 +01:00
db add new test to test database 2020-07-09 18:27:02 +02:00
extras Command line option for slow test threshold 2020-07-02 23:42:28 +02:00
include Test for LINUX_VERSION before setting it again 2020-08-08 01:39:13 +02:00
plugins Removed restriction for using the plugin and code style improvements 2020-03-23 11:30:10 +01:00
.gitignore Ignore swap files 2016-07-30 14:12:27 +02:00
.travis.yml Added notifications 2016-05-12 08:23:32 +02:00
CHANGELOG.md Updated log 2020-08-07 11:56:19 +02:00
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md 2017-08-17 20:37:37 +02:00
CONTRIBUTING.md Update CONTRIBUTING.md 2020-05-15 23:59:59 -05:00
CONTRIBUTORS.md Add myself as contributor 2020-03-20 19:03:21 +02:00
FAQ Updated date/year 2020-03-20 14:50:25 +01:00
HAPPY_USERS.md Update HAPPY_USERS.md 2020-07-07 15:05:50 +12:00
INSTALL Updated date/year 2020-03-20 14:50:25 +01:00
LICENSE Update of LICENSE file, which has version control texts in it 2014-10-06 14:00:47 +02:00
README Fix links CONTRIBUTIONS -> CONTRIBUTING (#472) 2017-10-19 09:56:37 +02:00
README.md Update README.md 2020-05-15 23:56:43 -05:00
SECURITY.md Create SECURITY.md file 2019-07-11 10:55:54 +02:00
default.prf Merge pull request #913 from topimiettinen/check-der-certs 2020-08-07 11:54:39 +02:00
developer.prf Run non-interactive by default, use --wait to enforce waiting after finishing a group of tests 2019-07-12 14:38:52 +02:00
lynis Merge pull request #974 from igloonet/feature/warn-slow-settting 2020-08-07 11:39:39 +02:00
lynis.8 Fix quote syntax error in manpage 2020-03-17 12:01:21 +09:00

README.md

Linux Security Expert badge Build Status CII Best Practices Documentation

Do you like this software? Star the project and become a stargazer.

lynis

Lynis - Security auditing and hardening tool, for UNIX-based systems.

Lynis is a security auditing tool for systems based on UNIX like Linux, macOS, BSD, and others. It performs an in-depth security scan and runs on the system itself. The primary goal is to test security defenses and provide tips for further system hardening. It will also scan for general system information, vulnerable software packages, and possible configuration issues. Lynis was commonly used by system administrators and auditors to assess the security defenses of their systems. Besides the "blue team," nowadays penetration testers also have Lynis in their toolkit.

We believe software should be simple, updated on a regular basis, and open. You should be able to trust, understand, and have the option to change the software. Many agree with us, as the software is being used by thousands every day to protect their systems.

Goals

The main goals are:

  • Automated security auditing
  • Compliance testing (e.g. ISO27001, PCI-DSS, HIPAA)
  • Vulnerability detection

The software (also) assists with:

  • Configuration and asset management
  • Software patch management
  • System hardening
  • Penetration testing (privilege escalation)
  • Intrusion detection

Audience

Typical users of the software:

  • System administrators
  • Auditors
  • Security officers
  • Penetration testers
  • Security professionals

Installation

Git

  1. Clone or download the project files (no compilation nor installation is required) ;

     git clone https://github.com/CISOfy/lynis

  2. Execute:

     cd lynis; ./lynis audit system

If you want to run the software as root, we suggest changing the ownership of the files. Use chown -R 0:0 to recursively alter the owner and group and set it to user ID 0 (root).

Software Package

For Linux, BSD, and macOS, there is typically a package available. The Lynis project also provides packages in RPM or DEB format. The CISOfy software repository can be used to install Lynis on systems running: CentOS, Debian, Fedora, OEL, openSUSE, RHEL, Ubuntu, and others.

Some distributions may also have Lynis in their software repository: Repology If they don't provide an up-to-date version, consider the CISOfy repository, tarball (website), or GitHub release.

Enterprise Version

This software component is also part of an enterprise solution. Same quality, yet with more functionality.

Focus areas include compliance (PCI DSS, HIPAA, ISO27001, and others). The Enterprise version comes with:

  • a web interface and features a dashboard;
  • hardening snippets;
  • and an improvement plan.

Documentation

Full documentation: https://cisofy.com/documentation/lynis/.

Customization

If you want to create your own tests, have a look at the Lynis software development kit.

Security

We participate in the CII best practices badge program of the Linux Foundation.

Media and Awards

Lynis is collecting some awards and we are proud of that.

Contribute

We love contributors.

Do you have something to share? Want to help out with translating Lynis into your own language? Create an issue or pull request on GitHub, or send us an e-mail: lynis-dev@cisofy.com.

More details can be found in the Contributors Guide.

You can also simply contribute to the project by starring the project and show your appreciation that way.

Thanks!

License

GPLv3