HAProxy must be configured to use TLS for https connections.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-240042	VRAU-HA-000020	SV-240042r879520_rule		Medium

Description
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.

Description

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.

STIG	Date
VMW vRealize Automation 7.x HA Proxy Security Technical Implementation Guide	2023-09-12

Details

Check Text ( C-43275r665293_chk )
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 (F-43234r665294_fix)
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.