As a security best practice, ensure that the application resources are protected.

Follow the steps to ensure that the application resources are protected.

Procedure

  1. Run the find / -path /proc -prune -o -type f -perm /6000 -ls command to verify that the files have a well-defined SUID and GUID bits set.
    The following list appears:
    584208     44 -rwsr-xr-x   1  root     root        44696 Feb  4  2019 /usr/bin/su
       584210     60 -rwsr-xr-x   1  root     root        54112 Feb  4  2019 /usr/bin/chfn
       584646     56 -rwsr-x---   1  root     root        51872 Feb  4  2019 /usr/bin/crontab
       584216     40 -rwsr-xr-x   1  root     root        37128 Feb  4  2019 /usr/bin/newgidmap
       584206     68 -rwsr-xr-x   1  root     root        63736 Feb  4  2019 /usr/bin/passwd
       584211     44 -rwsr-xr-x   1  root     root        44544 Feb  4  2019 /usr/bin/chsh
       584218     40 -rwsr-xr-x   1  root     root        37128 Feb  4  2019 /usr/bin/newuidmap
       587446    144 -rwsr-xr-x   1  root     root       140856 Feb  4  2019 /usr/bin/sudo
       585233     36 -rwsr-xr-x   1  root     root        36144 Feb  4  2019 /usr/bin/umount
       584212     32 -rwsr-xr-x   1  root     root        31048 Feb  4  2019 /usr/bin/expiry
       584209     76 -rwsr-xr-x   1  root     root        71848 Feb  4  2019 /usr/bin/chage
       585231     56 -rwsr-xr-x   1  root     root        52968 Feb  4  2019 /usr/bin/mount
       583901     36 -rwsr-xr-x   1  root     root        34944 Feb  4  2019 /usr/bin/fusermount
       586675     36 -rwsr-xr-x   1  root     root        34952 Feb  4  2019 /usr/bin/fusermount3
       584217     44 -rwsr-xr-x   1  root     root        44472 Feb  4  2019 /usr/bin/newgrp
       584214     80 -rwsr-xr-x   1  root     root        75776 Feb  4  2019 /usr/bin/gpasswd
       582975    428 -rwsr-xr-x   1  root     root       432512 Mar  6  2019 /usr/libexec/ssh-keysign
       587407     80 -rwsr-x---   1  root     root        76224 Feb  4  2019 /usr/libexec/dbus-daemon-launch-helper
       587109     16 -rwsr-xr-x   1  root     root        14408 Feb  4  2019 /usr/sbin/usernetctl
       587105     16 -rwxr-sr-x   1  root     root        14384 Feb  4  2019 /usr/sbin/netreport
       582750     40 -rwsr-xr-x   1  root     root        38960 Feb  4  2019 /usr/sbin/unix_chkpw
    
  2. Run the find / -path */proc -prune -o -nouser -o -nogroup command to verify that all the files in the vApp have an owner.
    All the files have an owner if there are no results.
  3. Run the find / -name "*.*" -type f -perm -a+w | xargs ls -ldb command to verify that none of the files are world writable files by reviewing permissions of all the files on the vApp.
    Others should not have write permission. The permissions on these files should be ##4 or ##5, where # equals the default given set of permissions for the Owner and Group, such as 6 or 7.
  4. Run the find / -path */proc -prune -o ! -user root -o -user admin -print command to verify that the files are owned by the correct user.
    All the files belong to either root or admin if there are no results.
  5. Run the find /usr/lib/vmware-casa/ -type f -perm -o=w command to ensure that files in the /usr/lib/vmware-casa/ directory are not world writable.
    There must be no results.
  6. Run the find /usr/lib/vmware-vcops/ -type f -perm -o=w command to ensure that files in the /usr/lib/vmware-vcops/ directory are not world writable.
    There must be no results.
  7. Run the find /usr/lib/vmware-vcopssuite/ -type f -perm -o=w command to ensure that files in the /usr/lib/vmware-vcopssuite/ directory are not world writable.
    There must be no results.