VMware vSphere 7.0 ESXi Security Technical Implementation Guide

Description

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: [email protected].

Details

Version / Release: V1R1

Published: 2023-02-21

Updated At: 2023-05-04 00:38:34

Actions

Download

Filter

Findings
Severity Open Not Reviewed Not Applicable Not a Finding
Overall 0 0 0 0
Low 0 0 0 0
Medium 0 0 0 0
High 0 0 0 0
Drop CKL or SCAP (XCCDF) results here.

    Vuln Rule Version CCI Severity Title Description Status Finding Details Comments
    SV-256375r885906_rule ESXI-70-000001 CCI-000054 MEDIUM Access to the ESXi host must be limited by enabling lockdown mode. Enabling lockdown mode disables direct access to an ESXi host, requiring the host to be managed remotely from vCenter Server. This is done to ensure the roles and access controls implemented in vCenter are always enforced and users cannot bypass them by l
    SV-256376r885909_rule ESXI-70-000002 CCI-000366 MEDIUM The ESXi host must verify the DCUI.Access list. Lockdown mode disables direct host access, requiring that administrators manage hosts from vCenter Server. However, if a host becomes isolated from vCenter, the administrator is locked out and can no longer manage the host. The "DCUI.Access" advanced se
    SV-256377r885912_rule ESXI-70-000003 CCI-000366 MEDIUM The ESXi host must verify the exception users list for lockdown mode. While a host is in lockdown mode (strict or normal), only users on the "Exception Users" list are allowed access. These users do not lose their permissions when the host enters lockdown mode. The organization may want to add service accounts such as a b
    SV-256378r885915_rule ESXI-70-000004 CCI-000067 MEDIUM Remote logging for ESXi hosts must be configured. Remote logging to a central log host provides a secure, centralized store for ESXi logs. By gathering host log files onto a central host, it can more easily monitor all hosts with a single tool. It can also do aggregate analysis and searching to look for
    SV-256379r885918_rule ESXI-70-000005 CCI-000044 MEDIUM The ESXi host must enforce the limit of three consecutive invalid logon attempts by a user. By limiting the number of failed logon attempts, the risk of unauthorized access via user password guessing, otherwise known as brute forcing, is reduced. Once the configured number of attempts is reached, the account is locked by the ESXi host.
    SV-256380r885921_rule ESXI-70-000006 CCI-002238 MEDIUM The ESXi host must enforce an unlock timeout of 15 minutes after a user account is locked out. By enforcing a reasonable unlock timeout after multiple failed logon attempts, the risk of unauthorized access via user password guessing, otherwise known as brute forcing, is reduced. Users must wait for the timeout period to elapse before subsequent log
    SV-256381r885924_rule ESXI-70-000007 CCI-000048 MEDIUM The ESXi host must display the Standard Mandatory DOD Notice and Consent Banner before granting access to the system via the Direct Console User Interface (DCUI). Failure to display the DOD logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources. Satisfies: SRG-OS-000023-VMM-000060, SRG-OS-000024-VMM-000070
    SV-256382r885927_rule ESXI-70-000008 CCI-000048 MEDIUM The ESXi host must display the Standard Mandatory DOD Notice and Consent Banner before granting access to the system via Secure Shell (SSH). Failure to display the DOD logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources.
    SV-256383r885930_rule ESXI-70-000009 CCI-000048 MEDIUM The ESXi host SSH daemon must be configured with the DOD logon banner. The warning message reinforces policy awareness during the logon process and facilitates possible legal action against attackers. Alternatively, systems whose ownership should not be obvious should ensure use of a banner that does not provide easy attribu
    SV-256384r885933_rule ESXI-70-000010 CCI-000068 MEDIUM The ESXi host Secure Shell (SSH) daemon must use FIPS 140-2 validated cryptographic modules to protect the confidentiality of remote access sessions. OpenSSH on the ESXi host ships with a FIPS 140-2 validated cryptographic module that is enabled by default. For backward compatibility reasons, this can be disabled so this setting can be audited and corrected if necessary.
    SV-256385r885936_rule ESXI-70-000012 CCI-000767 MEDIUM The ESXi host Secure Shell (SSH) daemon must ignore ".rhosts" files. SSH trust relationships mean a compromise on one host can allow an attacker to move trivially to other hosts. SSH can emulate the behavior of the obsolete "rsh" command in allowing users to enable insecure access to their accounts via ".rhosts" files.
    SV-256386r885939_rule ESXI-70-000013 CCI-000366 MEDIUM The ESXi host Secure Shell (SSH) daemon must not allow host-based authentication. SSH trust relationships mean a compromise on one host can allow an attacker to move trivially to other hosts. SSH's cryptographic host-based authentication is more secure than ".rhosts" authentication because hosts are cryptographically authenticated. How
    SV-256387r885942_rule ESXI-70-000015 CCI-000366 LOW The ESXi host Secure Shell (SSH) daemon must not allow authentication using an empty password. Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misconfiguration elsewhere.
    SV-256388r885945_rule ESXI-70-000016 CCI-000366 MEDIUM The ESXi host Secure Shell (SSH) daemon must not permit user environment settings. SSH environment options potentially allow users to bypass access restriction in some configurations. Users must not be able to present environment options to the SSH daemon.
    SV-256389r885948_rule ESXI-70-000020 CCI-000366 MEDIUM The ESXi host Secure Shell (SSH) daemon must perform strict mode checking of home directory configuration files. If other users have access to modify user-specific SSH configuration files, they may be able to log on the system as another user.
    SV-256390r885951_rule ESXI-70-000021 CCI-000366 MEDIUM The ESXi host Secure Shell (SSH) daemon must not allow compression or must only allow compression after successful authentication. If compression is allowed in an SSH connection prior to authentication, vulnerabilities in the compression software could result in compromise of the system from an unauthenticated connection, potentially with root privileges.
    SV-256391r885954_rule ESXI-70-000022 CCI-000366 LOW The ESXi host Secure Shell (SSH) daemon must be configured to not allow gateway ports. SSH Transmission Control Protocol (TCP) connection forwarding provides a mechanism to establish TCP connections proxied by the SSH server. This function can provide convenience similar to a virtual private network (VPN) with the similar risk of providing
    SV-256392r885957_rule ESXI-70-000023 CCI-000366 MEDIUM The ESXi host Secure Shell (SSH) daemon must be configured to not allow X11 forwarding. X11 forwarding over SSH allows for the secure remote execution of X11-based applications. This feature can increase the attack surface of an SSH connection.
    SV-256393r885960_rule ESXI-70-000025 CCI-000366 MEDIUM The ESXi host Secure Shell (SSH) daemon must not permit tunnels. OpenSSH has the ability to create network tunnels (layer 2 and layer 3) over an SSH connection. This function can provide similar convenience to a virtual private network (VPN) with the similar risk of providing a path to circumvent firewalls and network
    SV-256394r885963_rule ESXI-70-000026 CCI-000366 LOW The ESXi host Secure Shell (SSH) daemon must set a timeout count on idle sessions. Setting a timeout ensures that a user login will be terminated as soon as the "ClientAliveCountMax" is reached.
    SV-256395r885966_rule ESXI-70-000027 CCI-000366 LOW The ESXi host Secure Shell (SSH) daemon must set a timeout interval on idle sessions. Automatically logging out idle users guards against compromises via hijacked administrative sessions.
    SV-256396r885969_rule ESXI-70-000030 CCI-000130 MEDIUM The ESXi host must produce audit records containing information to establish what type of events occurred. Without establishing what types of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. Satisfies: SRG-OS-000037-VMM-000150, SRG-OS-000063-VMM-000310
    SV-256397r885972_rule ESXI-70-000031 CCI-000192 MEDIUM The ESXi host must be configured with a sufficiently complex password policy. To enforce the use of complex passwords, minimum numbers of characters of different classes are mandated. The use of complex passwords reduces the ability of attackers to successfully obtain valid passwords using guessing or exhaustive search techniques
    SV-256398r885975_rule ESXI-70-000032 CCI-000200 MEDIUM The ESXi host must prohibit the reuse of passwords within five iterations. If a user or root used the same password continuously or was allowed to change it back shortly after being forced to change it to something else, it would provide a potential intruder with the opportunity to keep guessing at one user's password until it w
    SV-256399r885978_rule ESXI-70-000034 CCI-000381 MEDIUM The ESXi host must disable the Managed Object Browser (MOB). The MOB provides a way to explore the object model used by the VMkernel to manage the host and enables configurations to be changed. This interface is meant to be used primarily for debugging the vSphere Software Development Kit (SDK), but because there a
    SV-256400r885981_rule ESXI-70-000035 CCI-000381 MEDIUM The ESXi host must be configured to disable nonessential capabilities by disabling Secure Shell (SSH). The ESXi Shell is an interactive command line interface (CLI) available at the ESXi server console. The ESXi shell provides temporary access to commands essential for server maintenance. Intended primarily for use in break-fix scenarios, the ESXi shell is
    SV-256401r885984_rule ESXI-70-000036 CCI-000381 MEDIUM The ESXi host must disable ESXi Shell unless needed for diagnostics or troubleshooting. The ESXi Shell is an interactive command line environment available locally from the Direct Console User Interface (DCUI) or remotely via SSH. Activities performed from the ESXi Shell bypass vCenter role-based access control (RBAC) and audit controls. Th
    SV-256402r885987_rule ESXI-70-000037 CCI-000764 LOW The ESXi host must use Active Directory for local user authentication. Join ESXi hosts to an Active Directory domain to eliminate the need to create and maintain multiple local user accounts. Using Active Directory for user authentication simplifies the ESXi host configuration, ensures password complexity and reuse policies
    SV-256403r885990_rule ESXI-70-000038 CCI-000764 MEDIUM ESXi hosts using Host Profiles and/or Auto Deploy must use the vSphere Authentication Proxy to protect passwords when adding themselves to Active Directory. If a host is configured to join an Active Directory domain using Host Profiles and/or Auto Deploy, the Active Directory credentials are saved in the profile and are transmitted over the network. To avoid having to save Active Directory credentials in th
    SV-256404r885993_rule ESXI-70-000039 CCI-000764 MEDIUM Active Directory ESX Admin group membership must not be used when adding ESXi hosts to Active Directory. When adding ESXi hosts to Active Directory, all user/group accounts assigned to the Active Directory group \"ESX Admins\" will have full administrative access to the host. If this group is not controlled or known to the system administrators, it may be
    SV-256405r885996_rule ESXI-70-000041 CCI-001133 MEDIUM The ESXi host must set a timeout to automatically disable idle shell sessions after two minutes. If a user forgets to log out of their local or remote ESXi Shell session, the idle connection will remain open indefinitely and increase the likelihood of inappropriate host access via session hijacking. The "ESXiShellInteractiveTimeOut" allows the automa
    SV-256406r885999_rule ESXI-70-000042 CCI-001133 MEDIUM The ESXi host must terminate shell services after 10 minutes. When the ESXi Shell or Secure Shell (SSH) services are enabled on a host, they will run indefinitely. To avoid having these services left running, set the "ESXiShellTimeOut". The "ESXiShellTimeOut" defines a window of time after which the ESXi Shell and S
    SV-256407r886002_rule ESXI-70-000043 CCI-001133 MEDIUM The ESXi host must log out of the console UI after two minutes. When the Direct Console User Interface (DCUI) is enabled and logged in, it should be automatically logged out if left logged on to avoid access by unauthorized persons. The "DcuiTimeOut" setting defines a window of time after which the DCUI will be logged
    SV-256408r886005_rule ESXI-70-000045 CCI-001849 MEDIUM The ESXi host must enable a persistent log location for all locally stored logs. ESXi can be configured to store log files on an in-memory file system. This occurs when the host's "/scratch" directory is linked to "/tmp/scratch". When this is done, only a single day's worth of logs are stored at any time. In addition, log files will b
    SV-256409r886008_rule ESXI-70-000046 CCI-001891 MEDIUM The ESXi host must configure NTP time synchronization. To ensure the accuracy of the system clock, it must be synchronized with an authoritative time source within DOD. Many system functions, including time-based logon and activity restrictions, automated reports, system logs, and audit records, depend on an
    SV-256410r886011_rule ESXI-70-000047 CCI-001749 HIGH The ESXi Image Profile and vSphere Installation Bundle (VIB) acceptance levels must be verified. Verify the ESXi Image Profile to only allow signed VIBs. An unsigned VIB represents untested code installed on an ESXi host. The ESXi Image profile supports four acceptance levels: 1. VMwareCertified - VIBs created, tested, and signed by VMware. 2. VMwa
    SV-256411r886014_rule ESXI-70-000048 CCI-002418 MEDIUM The ESXi host must protect the confidentiality and integrity of transmitted information by isolating vMotion traffic. While encrypted vMotion is available, vMotion traffic should still be sequestered from other traffic to further protect it from attack. This network must only be accessible to other ESXi hosts, preventing outside access to the network. The vMotion VMkern
    SV-256412r886017_rule ESXI-70-000049 CCI-002418 MEDIUM The ESXi host must protect the confidentiality and integrity of transmitted information by protecting ESXi management traffic. The vSphere management network provides access to the vSphere management interface on each component. Services running on the management interface provide an opportunity for an attacker to gain privileged access to the systems. Any remote attack most like
    SV-256413r886020_rule ESXI-70-000050 CCI-002418 MEDIUM The ESXi host must protect the confidentiality and integrity of transmitted information by isolating IP-based storage traffic. Virtual machines (VMs) might share virtual switches and VLANs with the IP-based storage configurations. IP-based storage includes vSAN, iSCSI, and NFS. This configuration might expose IP-based storage traffic to unauthorized VM users. IP-based storage fre
    SV-256414r886023_rule ESXI-70-000053 CCI-000366 MEDIUM Simple Network Management Protocol (SNMP) must be configured properly on the ESXi host. If SNMP is not being used, it must remain disabled. If it is being used, the proper trap destination must be configured. If SNMP is not properly configured, monitoring information can be sent to a malicious host that can use this information to plan an at
    SV-256415r886026_rule ESXI-70-000054 CCI-000366 MEDIUM The ESXi host must enable bidirectional Challenge-Handshake Authentication Protocol (CHAP) authentication for Internet Small Computer Systems Interface (iSCSI) traffic. When enabled, vSphere performs bidirectional authentication of both the iSCSI target and host. When not authenticating both the iSCSI target and host, there is potential for a man-in-the-middle attack, in which an attacker might impersonate either side of
    SV-256416r886029_rule ESXI-70-000055 CCI-000366 LOW The ESXi host must disable Inter-Virtual Machine (VM) Transparent Page Sharing. Published academic papers have demonstrated that by forcing a flush and reload of cache memory, it is possible to measure memory timings to try to determine an Advanced Encryption Standard (AES) encryption key in use on another virtual machine running on
    SV-256417r886032_rule ESXI-70-000056 CCI-000366 MEDIUM The ESXi host must configure the firewall to restrict access to services running on the host. Unrestricted access to services running on an ESXi host can expose a host to outside attacks and unauthorized access. Reduce the risk by configuring the ESXi firewall to only allow access from authorized networks.
    SV-256418r886035_rule ESXI-70-000057 CCI-000366 MEDIUM The ESXi host must configure the firewall to block network traffic by default. In addition to service-specific firewall rules, ESXi has a default firewall rule policy to allow or deny incoming and outgoing traffic. Reduce the risk of attack by ensuring this is set to deny incoming and outgoing traffic.
    SV-256419r886038_rule ESXI-70-000058 CCI-000366 MEDIUM The ESXi host must enable Bridge Protocol Data Units (BPDU) filter on the host to prevent being locked out of physical switch ports with Portfast and BPDU Guard enabled. BPDU Guard and Portfast are commonly enabled on the physical switch to which the ESXi host is directly connected to reduce the Spanning Tree Protocol (STP) convergence delay. If a BPDU packet is sent from a virtual machine (VM) on the ESXi host to the ph
    SV-256420r886041_rule ESXI-70-000059 CCI-000366 MEDIUM All port groups on standard switches must be configured to reject forged transmits. If the virtual machine (VM) operating system changes the Media Access Control (MAC) address, the operating system can send frames with an impersonated source MAC address at any time. This allows an operating system to stage malicious attacks on the device
    SV-256421r886044_rule ESXI-70-000060 CCI-000366 HIGH All port groups on standard switches must be configured to reject guest Media Access Control (MAC) address changes. If the virtual machine (VM) operating system changes the MAC address, it can send frames with an impersonated source MAC address at any time. This allows it to stage malicious attacks on the devices in a network by impersonating a network adaptor authoriz
    SV-256422r886047_rule ESXI-70-000061 CCI-000366 MEDIUM All port groups on standard switches must be configured to reject guest promiscuous mode requests. When promiscuous mode is enabled for a virtual switch, all virtual machines (VMs) connected to the Portgroup have the potential to read all packets across that network (only the virtual machines connected to that Portgroup). Promiscuous mode is disabled
    SV-256423r886050_rule ESXI-70-000062 CCI-000366 MEDIUM Use of the dvFilter network application programming interfaces (APIs) must be restricted. If the organization is not using products that use the dvfilter network API, the host should not be configured to send network information to a virtual machine (VM). If the API is enabled, an attacker might attempt to connect a virtual machine to it, pot
    SV-256424r886053_rule ESXI-70-000063 CCI-000366 MEDIUM All port groups on standard switches must be configured to a value other than that of the native virtual local area network (VLAN). ESXi does not use the concept of native VLAN. Frames with a VLAN specified in the port group will have a tag, but frames with VLAN not specified in the port group are not tagged and therefore will belong to the native VLAN of the physical switch. For exa
    SV-256425r886056_rule ESXI-70-000064 CCI-000366 MEDIUM All port groups on standard switches must not be configured to virtual local area network (VLAN) 4095 unless Virtual Guest Tagging (VGT) is required. When a port group is set to VLAN 4095, the vSwitch passes all network frames to the attached virtual machines (VMs) without modifying the VLAN tags. In vSphere, this is referred to as VGT. The VM must process the VLAN information itself via an 802.1Q driv
    SV-256426r886059_rule ESXI-70-000065 CCI-000366 MEDIUM All port groups on standard switches must not be configured to virtual local area network (VLAN) values reserved by upstream physical switches. Certain physical switches reserve certain VLAN IDs for internal purposes and often disallow traffic configured to these values. For example, Cisco Catalyst switches typically reserve VLANs 1001 to 1024 and 4094, while Nexus switches typically reserve 3968
    SV-256427r886062_rule ESXI-70-000070 CCI-000366 MEDIUM The ESXi host must not provide root/administrator-level access to Common Information Model (CIM)-based hardware monitoring tools or other third-party applications. The CIM system provides an interface that enables hardware-level management from remote applications via a set of standard application programming interfaces (APIs). In environments that implement CIM hardware monitoring, create a limited-privilege, rea
    SV-256428r886065_rule ESXI-70-000072 CCI-000366 HIGH The ESXi host must have all security patches and updates installed. Installing software updates is a fundamental mitigation against the exploitation of publicly known vulnerabilities.
    SV-256429r886068_rule ESXI-70-000074 CCI-002420 HIGH The ESXi host must exclusively enable Transport Layer Security (TLS) 1.2 for all endpoints. TLS 1.0 and 1.1 are deprecated protocols with well-published shortcomings and vulnerabilities. TLS 1.2 should be enabled on all interfaces and SSLv3, TL 1.1, and 1.0 disabled, where supported. Mandating TLS 1.2 may break third-party integrations and add-
    SV-256430r886071_rule ESXI-70-000076 CCI-000366 MEDIUM The ESXi host must enable Secure Boot. Secure Boot is part of the Unified Extensible Firmware Interface (UEFI) firmware standard. With UEFI Secure Boot enabled, a host refuses to load any UEFI driver or app unless the operating system bootloader has a valid digital signature. Secure Boot for E
    SV-256431r886074_rule ESXI-70-000078 CCI-000366 MEDIUM The ESXi host must use DOD-approved certificates. The default self-signed host certificate issued by the VMware Certificate Authority (VMCA) must be replaced with a DOD-approved certificate when the host will be accessed directly, such as during a virtual machine (VM) console connection. The use of a DO
    SV-256432r886077_rule ESXI-70-000079 CCI-000366 MEDIUM The ESXi host must not suppress warnings that the local or remote shell sessions are enabled. Warnings that local or remote shell sessions are enabled alert administrators to activity they may not be aware of and need to investigate.
    SV-256433r886080_rule ESXI-70-000081 CCI-000366 MEDIUM The ESXi host must not suppress warnings about unmitigated hyperthreading vulnerabilities. The L1 Terminal Fault (L1TF) CPU vulnerabilities published in 2018 have patches and mitigations available in vSphere. However, there are performance impacts to these mitigations that require careful thought and planning from the system administrator befor
    SV-256434r886083_rule ESXI-70-000082 CCI-000366 MEDIUM The ESXi host Secure Shell (SSH) daemon must disable port forwarding. While enabling Transmission Control Protocol (TCP) tunnels is a valuable function of sshd, this feature is not appropriate for use on the ESXi hypervisor.
    SV-256435r886086_rule ESXI-70-000083 CCI-000366 MEDIUM The ESXi host OpenSLP service must be disabled. OpenSLP implements the Service Location Protocol to help CIM clients discover CIM servers over TCP 427. This service is not widely needed and has had vulnerabilities exposed in the past. To reduce attack surface area and following the minimum functionalit
    SV-256436r886089_rule ESXI-70-000084 CCI-000366 MEDIUM The ESXi host must enable audit logging. ESXi offers both local and remote audit recordkeeping to meet the requirements of the NIAP Virtualization Protection Profile and Server Virtualization Extended Package. Local records are stored on any accessible local or VMFS path. Remote records are sent
    SV-256437r886092_rule ESXI-70-000085 CCI-000366 MEDIUM The ESXi host must enable strict x509 verification for SSL syslog endpoints. When sending syslog data to a remote host via SSL, the ESXi host is presented with the endpoint's SSL server certificate. In addition to trust verification, configured elsewhere, this "x509-strict" option performs additional validity checks on CA root cer
    SV-256438r886095_rule ESXI-70-000086 CCI-000366 MEDIUM The ESXi host must verify certificates for SSL syslog endpoints. When sending syslog data to a remote host, ESXi can be configured to use any combination of TCP, UDP and SSL transports. When using SSL, the server certificate must be validated to ensure that the host is connecting to a valid syslog server.
    SV-256439r886098_rule ESXI-70-000087 CCI-000366 MEDIUM The ESXi host must enable volatile key destruction. By default, pages allocated for virtual machines (VMs), userspace applications, and kernel threads are zeroed out at allocation time. ESXi will always ensure that no nonzero pages are exposed to VMs or userspace applications. While this prevents exposing
    SV-256440r886101_rule ESXI-70-000088 CCI-000366 MEDIUM The ESXi host must configure a session timeout for the vSphere API. The vSphere API (VIM) allows for remote, programmatic administration of the ESXi host. Authenticated API sessions are no different from a risk perspective than authenticated UI sessions and they need similar protections. One of these protections is a bas
    SV-256441r886104_rule ESXI-70-000089 CCI-000366 MEDIUM The ESXi Host Client must be configured with a session timeout. The ESXi Host Client is the UI served up by the host itself, outside of vCenter. It is accessed by browsing to "https:///ui". ESXi is not usually administered via this interface for long periods, and all users will be highly privileged. Implementing a man
    SV-256442r886107_rule ESXI-70-000090 CCI-000068 MEDIUM The ESXi host rhttpproxy daemon must use FIPS 140-2 validated cryptographic modules to protect the confidentiality of remote access sessions. ESXi runs a reverse proxy service called rhttpproxy that front ends internal services and application programming interfaces (APIs) over one HTTPS port by redirecting virtual paths to localhost ports. This proxy implements a FIPS 140-2 validated OpenSSL
    SV-256443r886110_rule ESXI-70-000091 CCI-000366 MEDIUM The ESXi host must be configured with an appropriate maximum password age. The older an ESXi local account password is, the larger the opportunity window is for attackers to guess, crack or reuse a previously cracked password. Rotating passwords on a regular basis is a fundamental security practice and one that ESXi supports.
    SV-256444r886113_rule ESXI-70-000092 CCI-000366 MEDIUM The ESXi host must not be configured to override virtual machine (VM) configurations. Each VM on an ESXi host runs in its own "vmx" process. Upon creation, a vmx process will look in two locations for configuration items, the ESXi host itself and the per-vm *.vmx file in the VM storage path on the datastore. The settings on the ESXi host a
    SV-256445r886116_rule ESXI-70-000093 CCI-000366 MEDIUM The ESXi host must not be configured to override virtual machine (VM) logger settings. Each VM on an ESXi host runs in its own "vmx" process. Upon creation, a vmx process will look in two locations for configuration items, the ESXi host itself and the per-vm *.vmx file in the VM storage path on the datastore. The settings on the ESXi host a
    SV-256446r886119_rule ESXI-70-000094 CCI-000366 MEDIUM The ESXi host must require TPM-based configuration encryption. An ESXi host's configuration consists of configuration files for each service that runs on the host. The configuration files typically reside in the /etc/ directory, but they can also reside in other namespaces. The configuration files contain run-time in
    SV-256447r886122_rule ESXI-70-000095 CCI-001494 MEDIUM The ESXi host must implement Secure Boot enforcement. Secure Boot is part of the UEFI firmware standard. With UEFI Secure Boot enabled, a host refuses to load any UEFI driver or app unless the operating system bootloader has a valid digital signature. Secure Boot for ESXi requires support from the firmware a
    SV-256448r886125_rule ESXI-70-000097 CCI-000366 MEDIUM The ESXi Common Information Model (CIM) service must be disabled. The CIM system provides an interface that enables hardware-level management from remote applications via a set of standard application programming interfaces (APIs). These APIs are consumed by external applications such as HP SIM or Dell OpenManage for ag
    SV-256449r886128_rule ESXI-70-000274 CCI-002450 MEDIUM The ESXi host SSH daemon must be configured to only use FIPS 140-2 validated ciphers. Use of weak or untested encryption algorithms undermines the purposes of using encryption to protect data. ESXi must implement cryptographic modules adhering to the higher standards approved by the federal government because this provides assurance they h