A Security Readiness Review (SRR) script was run against our servers operating system and several STIG violations related to Oracle directories were found.
These files are listed below:
-rwsr-s--- 1 oracle dba 2986436 Mar 31 14:12 dbsnmp
-r-sr-s--- 1 oracle dba 11784 Oct 14 2004 oradism
-rwsr-s--x 1 oracle dba 65422428 Mar 31 16:53 oracle
-rwsr-s--x 1 oracle dba 65357392 Mar 31 14:13 oracleO
-rwSr----- 1 oracle dba 1536 Apr 12 01:06 orapwriacurw
-rwSr----- 1 oracle dba 1536 Apr 12 01:20 orapwriacutm
I am not familiar with how SUID and SGID works. Do these files have a sticky
bit set on them? The security team says that the permissions are a sticky bit violation and that they need to be changed (i.e. remove the s). My concern is whether or not changing these permission to satisfy them will cause certain processes not to run or break anything in Oracle. If these permission settings must remain this way then I have to supply a written justification. Can someone provide and explanation, guidance, and/or recommendation for this issue?