The vAMI sfcb must have HTTPS enabled.

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

Associated with: CCI-002421

SV-100907r1_rule The vAMI sfcb must have HTTPS enabled.

Vulnerability discussion

Preventing the disclosure or modification of transmitted 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. If data in transit is unencrypted, it is vulnerable to disclosure and modification. If approved cryptographic algorithms are not used, encryption strength cannot be assured. FIPS 140-2 approved TLS versions include TLS V1.0 or greater. TLS must be enabled and non-FIPS-approved SSL versions must be disabled. NIST SP 800-52 specifies the preferred configurations for Government systems.

Check content

At the command prompt, execute the following command: grep 'enableHttps:' /opt/vmware/etc/sfcb/sfcb.cfg | grep -v '^#' If the value of "enableHttps" is missing or is not 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: 'enableHttps: true'

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.