The SLES for vRealize must define default permissions for all authenticated users in such a way that the user can only read and modify their own files.

From VMware vRealize Automation 7.x SLES Security Technical Implementation Guide

Part of SRG-OS-000480-GPOS-00228

Associated with: CCI-000366

SV-100529r1_rule The SLES for vRealize must define default permissions for all authenticated users in such a way that the user can only read and modify their own files.

Vulnerability discussion

Setting the most restrictive default permissions ensures that when new accounts are created they do not have unnecessary access.

Check content

Check for the configured "umask" value in "login.defs" with the following command: # grep UMASK /etc/login.defs If the default "umask" is not "077", this a finding. Note: If the default umask is "000" or allows for the creation of world-writable files this becomes a Severity Code I finding.

Fix text

To configure the correct UMASK setting run the following command: # sed -i "/^[^#]*UMASK/ c\UMASK 077" /etc/login.defs

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.

Powered by sagemincer