TMA-YUGABYTEDB-2.1
Ensure the file permissions mask is correct
Description
Files are always created using a default set of permissions. File permissions can be restricted by applying a permissions mask called the umask. The yugabyte user account should use a umask of 077 to deny file access to all user accounts except the owner.
How it is checked
Audit method: Manual review
This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.
As root run su - yugabyte -c umask. The umask of the yugabyte user must be 0077 or more restrictive; anything less restrictive (e.g. the default 0022) is a finding. Check .bash_profile, .profile and .bashrc of the yugabyte user.
How it is fixed
Fix method: Guidance or infrastructure patch
Depending upon the yugabyte user's environment, the umask is typically set in the initialization file .bash_profile, but may also be set in .profile or .bashrc. To set the umask, add the following to the appropriate profile file: # whoami yugabyte # cd ~ # ls -ld .{bash_profile,profile,bashrc} ls: cannot access '.bash_profile': No such file or directory ls: cannot access '.profile': No such file or directory ls: cannot access '.bashrc': No such ...
Properties
- Operating systems
- Any
- Tags
- yugabytedbpermissions
- Reference
- CIS YugabyteDB Benchmark v2.0.0 - 2.1 Ensure the file permissions mask is correct