The vAMI sfcb must have HTTP disabled.

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

Associated with: CCI-002422

SV-100909r1_rule The vAMI sfcb must have HTTP disabled.

Vulnerability discussion

Information can be either unintentionally or maliciously disclosed or modified during reception, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. Protecting the confidentiality and integrity of received information requires that application servers take measures to employ approved cryptography in order to protect the information during transmission over the network. This is usually achieved through the use of Transport Layer Security (TLS), SSL VPN, or IPsec tunnel. The application server must utilize approved encryption when receiving transmitted data.

Check content

At the command prompt, execute the following command: grep 'enableHttp:' /opt/vmware/etc/sfcb/sfcb.cfg | grep -v '^#' If the value of "enableHttp" is set to "true", this is a finding.

Fix text

Navigate to and open /opt/vmware/etc/sfcb/sfcb.cfg. Configure the sfcb.cfg file with the following value: 'enableHttp: false'

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.