OpenControls Logo

STIG Viewer

STIGViewer Support

VAMI must be configured to hide the server type and version in client responses.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-256671VCLD-70-000027SV-256671r888535_ruleCCI-001312medium
Description
Web servers will often display error messages to client users, displaying enough information to aid in the debugging of the error. The information given back in error messages may display the web server type, version, patches installed, plug-ins and modules installed, type of code being used by the hosted application, and any backends being used for data storage. This information could be used by an attacker to blueprint what type of attacks might be successful. Therefore, VAMI must be configured to hide the server version at all times.
STIGDate
VMware vSphere 7.0 VAMI Security Technical Implementation Guide2023-06-15

Related Frameworks

1 mapping across 3 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.

TDA-19Error Handling
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (19) 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-17(1)Monitoring and 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-3Content of Audit Records
1.00
AU-3(1)Additional Audit Information
1.00
AU-9Protection of Audit Information
1.00
CM-3(5)Automated Security Response
1.00
CM-5(1)Automated Access Enforcement and Audit Records
1.00

+9 more (top 10 by confidence shown)

CCI1 mapping
CCI-001312
1.00

Details

Check Text (C-256671r888535_chk)

At the command prompt, run the following command: # /opt/vmware/sbin/vami-lighttpd -p -f /opt/vmware/etc/lighttpd/lighttpd.conf 2>/dev/null|grep "server.tag"|sed 's: ::g' Expected result: server.tag="vami" If the output does not match the expected result, 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-60289r888534_fix)

Navigate to and open: /etc/applmgmt/appliance/lighttpd.conf Add or reconfigure the following value: server.tag = "vami" Restart the service with the following command: # vmon-cli --restart applmgmt