The vAMI configuration file must be owned by root.

From VMW vRealize Automation 7.x vAMI Security Technical Implementation Guide

Associated with: CCI-000171

SV-100849r1_rule The vAMI configuration file must be owned by root.

Vulnerability discussion

Log records can be generated from various components within the application server, (e.g., httpd, beans, etc.) From an application perspective, certain specific application functionalities may be logged, as well. The list of logged events is the set of events for which logs are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating log records (e.g., logable events, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked). Application servers utilize role-based access controls in order to specify the individuals who are allowed to configure application component logable events. The application server must be configured to select which personnel are assigned the role of selecting which logable events are to be logged. The personnel or roles that can select logable events are only the ISSM (or individuals or roles appointed by the ISSM).

Check content

At the command prompt, execute the following command: ls -lL /opt/vmware/etc/sfcb/sfcb.cfg If the sfcb.cfg file is not owned by root, this is a finding.

Fix text

At the command prompt, enter the following command: chown root:root /opt/vmware/etc/sfcb/sfcb.cfg

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.