VMware vCenter audit and event syslog
VMware vCenter audit and event syslog. vCenter emits management and session activity through service logs and remote syslog.
Source and collection
vCenter service logs / configured remote syslog; ESXi host logs are separate sources.
Configure supported remote logging and time synchronization; retain service/app name and management-plane identity.
Native example and provenance
upstream test fixture. Published example; no independent capture provenance claimed.
Original publisher / pinned upstream fixture — line 3
One complete record selected; values unchanged.
Pinned source commit: 9ae756f00f82786ac3496ce99c2dd288c5a5c031
Download the exact sample · Offline research kit
SHA-256: 67b7b05d871de229ae5a1369f7f00758695528cc8a0546e27e886ff93601827a
<14>1 2021-09-06T14:40:13.263383+00:00 vcenter vpxd 58650 - - Event [575792] [1-1] [2021-09-06T14:40:13.26309Z] [vim.event.UserLoginSessionEvent] [info] [VSPHERE.LOCAL\Administrator] [] [575792] [User VSPHERE.LOCAL\Administrator@10.100.10.190 logged in as Go-http-client/1.1]
Structure and field interpretation
| Field/path | Serialized type |
|---|---|
raw record | syslog |
- APP-NAME
- vpxd identifies the emitting service.
- vim.event.UserLoginSessionEvent
- Native event class.
- Event [id]
- Event identifier inside the message.
Investigation uses
- Review management login/logout sequences and administrative actions.
- Correlate session events with change tickets and hypervisor-side logs.
Validation boundaries
This is a vCenter vpxd event, not an ESXi vmkernel record. Do not use one parser for all VMware services.
This text sample passed byte-integrity and record-framing checks. Its field interpretation follows the cited format; a vendor-specific semantic parser has not been certified.
For a simulation, first parse this fixture offline, then create a separately labelled synthetic variant and test it against the intended collector in an isolated lab. Never replay public example identities or destinations into production.
Related sources
Ecosystem connections
- Telemetry Library — ATT&CK data components
- Detection Rules — candidate detection content
- Threat hunting — from intelligence to validated defense
- Practical security learning paths
- AdversaryGraph — evidence-led investigation
References
Sample provenance is linked above. Field availability and product behavior must be checked against the deployed version.