OpenControls Logo

STIG Viewer

STIGViewer Support

The vCenter VAMI service must generate information to monitor remote access.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-259139VCLD-80-000005SV-259139r1003691_ruleCCI-000067medium
Description
Remote access can be exploited by an attacker to compromise the server. By recording all remote access activities, it will be possible to determine the attacker's location, intent, and degree of success. VAMI uses the "mod_accesslog" module to log information relating to remote requests. These logs can then be piped to external monitoring systems.
STIGDate
VMware vSphere 8.0 vCenter Appliance Management Interface (VAMI) Security Technical Implementation Guide2026-05-23

Related Frameworks

1 mapping across 4 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

NET-14.1Automated Monitoring & Control
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (22) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-16Security and Privacy Attributes
1.00
AC-17(1)Monitoring and Control
1.00
AC-2(4)Automated Audit Actions
1.00
AC-3(3)Mandatory Access Control
1.00
AC-6(9)Log Use of Privileged Functions
1.00
AU-10Non-repudiation
1.00
AU-12Audit Record Generation
1.00
AU-14(1)System Start-up
1.00
AU-14(2)Capture and Record Content
1.00
AU-3Content of Audit Records
1.00

+12 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.1.12
1.00
CCI1 mapping
CCI-000067
1.00

Details

Check Text (C-259139r1003691_chk)

At the command prompt, run the following command: # /opt/vmware/cap_lighttpd/sbin/lighttpd -p -f /var/lib/vmware/cap-lighttpd/lighttpd.conf 2>/dev/null|awk '/server\.modules/,/\)/'|grep mod_accesslog Example result: "mod_accesslog", If the "mod_accesslog" is not present, this is a finding. Note: The command must be run from a bash shell and not from a shell generated by the "appliance shell". Use the "chsh" command to change the shell for the account to "/bin/bash". Refer to KB Article 2100508 for more details: https://kb.vmware.com/s/article/2100508

Fix Text (F-62788r1003690_fix)

Navigate to and open: /opt/vmware/etc/lighttpd/applmgmt-lighttpd.conf Add the following value in the "server.modules" section: mod_accesslog The result should be similar to the following: server.modules += ("mod_accesslog", "mod_cgi", "mod_magnet", "mod_rewrite") Restart the service with the following command: # systemctl restart cap-lighttpd