ESXi Audit Tampering
The following analytic identifies the use of the esxcli system auditrecords commands, which can be used to tamper with logging on an ESXi host. This action may indicate an attempt to evade detection or hinder…
Description
The following analytic identifies the use of the esxcli system auditrecords commands, which can be used to tamper with logging on an ESXi host. This action may indicate an attempt to evade detection or hinder forensic analysis by preventing the recording of system-level audit events.
Detection logic
Detection requirements
- Platform
- ContainersESXiLinuxmacOSNetwork DevicesOffice SuiteWindows
The rule states no platform. This is derived from the 2 ATT&CK techniques it maps to.
- Log source category
- vmware_esxi_syslog
Known benign triggers
- No false positives have been identified at this time.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| detect.fyi/detecting-and-responding-to-esxi-compromise-with-splunk-f33998ce7823 | 4 |
From the source
- At source
- Open at source
- Upstream identifier
- c48a155b-2861-417a-813c-220f5272cf01
- Tagged by the source as
- Black Basta RansomwareESXi Post CompromiseInfrastructureapplicationSplunk CloudSplunk EnterpriseSplunk Enterprise Securityendpoint
Licence
- Published under
- Apache License 2.0Read the licence
- Attribution
- Required
- Obtained under
- Apache-2.0Read the origin licence
Authorship
- Written by
- Published
- Sep 22, 2026
- Version
- 2