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 VAMI Security Technical Implementation Guide

V-256667

CAT II (Medium)

VAMI must be protected from being stopped by a nonprivileged user.

Rule ID

SV-256667r888523_rule

STIG

VMware vSphere 7.0 VAMI Security Technical Implementation Guide

Version

V1R2

CCIs

CCI-002385

Discussion

An attacker has at least two reasons to stop a web server. The first is to cause a denial of service, and the second is to put in place changes the attacker made to the web server configuration. Therefore, only administrators should ever be able to stop VAMI. The VAMI process is configured out of the box to be owned by root. This configuration must be verified and maintained.

Check Content

At the command prompt, run the following command:

# ps -f -U root | awk '$0 ~ /vami-lighttpd/ && $0 !~ /awk/ {print $1}'

Expected result:

root

If the output does not match the expected result, this is a finding.

Fix Text

Navigate to and open:

/usr/lib/systemd/system/vami-lighttp.service

Under the "[Service]" section, remove the line that beings with "User=".

Restart the service with the following command:

# vmon-cli --restart applmgmt