How to solve
Files and directories are created with a default set of permissions. These depend on the parent directory and the umask value. This umask value contains three or four numbers and gives the system a hint on how to create new objects on the file system. For example using the umask 027 will be translated into 750 for directories or 640 for files. This means that the owner can read and write, with additional execution rights for directories. This latter part means that you are allowed to traverse the directory. The group will get read permissions for files, and again execution rights for directories. The other won't get any access to the file.
Using the right umask helps with limiting who can access created files. This is especially important for systems with multiple users. This is also the case when loose file permissions can result in unauthorized information disclosure, like a web server.
- Umask (Wikipedia)
Need more details?
Consider the upgrade to Lynis Enterprise to receive additional details and guidance. The Enterprise version helps to you with daily health checks of your environment, learn in-depth system hardening, and resources to protect your systems better.See demo
Lynis is a technical security auditing tool for Unix flavors like Linux, macOS, AIX, Solaris, and *BSD. It is open source software and free to use. Typical usage include system hardening, compliance testing, and vulnerability scanning. The project has an active community, including development via GitHub.
Do you need to collect data from multiple systems or compliance reporting? Lynis Enterprise uses Lynis to collect the data and make your work easier.
Benefits: automate security audits, detailed reporting, compliance testing.
- Centralized management
- Improvement plan with priorities
- Predefined policies
- Integration (API)
- Improvement snippets for tools like Ansible, Chef, Cfengine, Puppet, and SaltStack