STIGhubSTIGhub
STIGsSearchCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to VMware vSphere 7.0 vCenter Appliance RhttpProxy Security Technical Implementation Guide

V-256741

CAT II (Medium)

The Envoy private key file must be protected from unauthorized access.

Rule ID

SV-256741r889161_rule

STIG

VMware vSphere 7.0 vCenter Appliance RhttpProxy Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-000186

Discussion

Envoy's private key is used to prove the identity of the server to clients and securely exchange the shared secret key used to encrypt communications between the web server and clients. By gaining access to the private key, an attacker can pretend to be an authorized server and decrypt the Transport Layer Security (TLS) traffic between a client and the web server.

Check Content

At  the command prompt, run the following command: 
 
# stat -c "%n permissions are %a, is owned by %U and group owned by %G" /etc/vmware-rhttpproxy/ssl/rui.key 
 
Expected result: 
 
/etc/vmware-rhttpproxy/ssl/rui.key permissions are 600, is owned by root and group owned by root 
 
If the output does not match the expected result, this is a finding.

Fix Text

At the command prompt, run the following commands: 
 
# chmod 600 /etc/vmware-rhttpproxy/ssl/rui.key 
# chown root:root /etc/vmware-rhttpproxy/ssl/rui.key