STIGhubSTIGhub
STIGsRMF ControlsCompare

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
  • RMF Controls
  • 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 vRealize Automation 7.x Lighttpd Security Technical Implementation Guide

V-240249

CAT II (Medium)

Lighttpd must have private key access restricted.

Rule ID

SV-240249r879613_rule

STIG

VMware vRealize Automation 7.x Lighttpd Security Technical Implementation Guide

Version

V1R2

CCIs

CCI-000186

Discussion

Lighttpd'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. Only authenticated system administrators or the designated PKI Sponsor for the web server must have access to the web servers private key. By gaining access to the private key, an attacker can pretend to be an authorized server and decrypt the encrypted traffic between a client and the web server.

Check Content

At the command prompt, execute the following command:

ls -al /opt/vmware/etc/lighttpd/server.pem

If the "server.pem" file is not owned by "root" or the file permissions are not "400", this is a finding.

Fix Text

At the command prompt, execute the following commands:

chown root:root /opt/vmware/etc/lighttpd/server.pem
chmod 400 /opt/vmware/etc/lighttpd/server.pem