The vAMI configuration file must be protected from unauthorized access.

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

Associated with: CCI-001813

SV-100897r1_rule The vAMI configuration file must be protected from unauthorized access.

Vulnerability discussion

When dealing with access restrictions pertaining to change control, it should be noted that any changes to the software and/or application server configuration can potentially have significant effects on the overall security of the system. Access restrictions for changes also include application software libraries. If the application server provides automatic code deployment capability, (where updates to applications hosted on the application server are automatically performed, usually by the developers' IDE tool), it must also provide a capability to restrict the use of automatic application deployment. Automatic code deployments are allowable in a development environment, but not in production.

Check content

At the command prompt, execute the following command: ls -lL /opt/vmware/etc/sfcb/sfcb.cfg If the permissions on the sfcb.cfg file are greater than 640, this is a finding.

Fix text

At the command prompt, enter the following command: chmod 640 /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.