HAProxy must be configured to use TLS for https connections.

From VMW vRealize Automation 7.x HA Proxy Security Technical Implementation Guide

Associated with: CCI-001453

SV-100953r1_rule HAProxy must be configured to use TLS for https connections.

Vulnerability discussion

Data exchanged between the user and the web server can range from static display data to credentials used to log into the hosted application. Even when data appears to be static, the non-displayed logic in a web page may expose business logic or trusted system relationships. The integrity of all the data being exchanged between the user and web server must always be trusted. To protect the integrity and trust, encryption methods should be used to protect the complete communication session.In order to protect the integrity and confidentiality of the remote sessions, HAProxy uses SSL/TLS.

Check content

Navigate to and open the following files: /etc/haproxy/conf.d/20-vcac.cfg /etc/haproxy/conf.d/30-vro-config.cfg Verify that each frontend is configured with the following: bind : ssl crt ciphers FIPS:+3DES:!aNULL no-sslv3 Note: and will be different for each frontend. If "ssl" is not set for the bind option for each frontend, this is a finding.

Fix text

Navigate to and open the following files: /etc/haproxy/conf.d/20-vcac.cfg /etc/haproxy/conf.d/30-vro-config.cfg Configure the bind option for each frontend with the "ssl" parameter.

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.