Anton Logging Tip of the Day #16: Virtually There - Journey Into VMWare ESX Log Analysis

Following the new "tradition" of posting tips of the week, I decided to follow along and join the initiative. So, after a long delay, Anton Logging Tip of the Day #16: Virtually There - Journey Into VMWare ESX Log Analysis CISecurity guide for VMWare (here) and DISA STIG for virtual machines (here) both mandate collection and analysis of VM platform logs; none goes into enough details on what to look for in logs. Let's try to shed some light on security-focused log analysis of VMWare ESX v. 3.x logs. First, at least until ESXi becomes the default choice, one needs to keep in mind that ESX has "Linux-inside" and thus diving into /var/log will not reveal any "alien technology" (well, not much of it :-)). However, one of the most useful logs is /var/log/hostd.N which is not a descendant of Linux standard logs. Extensive VM event records are written into this file. Let's focus on various types of logins to the ESX platform and identify logs that indicate a successful and failed attempts to log in. Here are a few useful examples to analyze: Successful logins:
- May 30 09:20:42 esx2 su(pam_unix)[9405]: session opened for user root by jhonny(uid=1626)
This is a classic Linux root login message; you can watch for these by searching VMWare ESX logs for "session AND opened AND user AND root." Notice the user name of the user who switched to root.
- May 30 09:20:34 esx2 sshd(pam_unix)[9364]: session opened for user jhonny by (uid=0)
This is also a classic Linux message for a normal (non-root) user login.
- [2008-05-25 06:57:48.774 'ha-eventmgr' 111639472 info] Event 40645 : User logged in
This is a VMWare -specific application login to ESX. You can track such events by username, by event ID or by keywords "event AND logged AND user" (if you are using search) Failed logins:
- May 30 09:20:31 esx2 sshd[9356]: Failed password for jhonny from 1.1.1.1 port 54773 ssh2
Another classic Linux message from the ESX system; a failure to login due to incorrect password.
- May 27 12:06:59 esx2 sshd[4756]: Failed password for illegal user jonny from 1.1.1.1 port 30594 ssh2
A message indicating a failure to login due to incorrect username (note a typo).
- May 25 07:03:48 esx1 sudo: jhonny : 3 incorrect password attempts ; TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/bin/bash
This ESX Linux platform message should also be familiar to Linux/Unix admins: it indicates multiple sudo password failures; look for such messages in the logs. BTW, do you need to be reminded to track NOT only failed, but also successful login events?! This applies to virtual as well as physical environments. Overall, you must prepare for the future by learning to analyze VMWare logs, just like you handled "legacy OS", such as Linux/Unix and Windows. As I said before, I am tagging all the tips on my del.icio.us feed; here is the link: All Security Tips of the Day. Technorati tags: security, tips, logging, log management
- christophe.briguet's blog
- Login or register to post comments
- Feed: LogBlog
- Original article
User login
Current Poll
Developer Resources
Active Forum Topics
- Restrictions on the Virtual Appliance
- Sample the LogLogic API Realtime dashboard
- Random Tech Preview performance data
- Great tool for testing the tech preview
- Download Instructions for Tech Preview
- Getting Started With .NET
- wrong log type format error
- Lasso 4.0.5 doesnt work.
- Simple Installation
- Simple Installation
Recent Comments
- answered
44 weeks 1 day ago - fail to update web service. can not connect to server
44 weeks 3 days ago - Challenges of Enterprise Cloud Computing
51 weeks 17 hours ago - is this an authentication
1 year 3 weeks ago - Answered
1 year 8 weeks ago - How to add Web References
1 year 9 weeks ago - 6/12
edge case crash fix
1 year 11 weeks ago - sure, email me at
1 year 13 weeks ago - Is Source Code Available?
1 year 14 weeks ago - Slight Problem with the .NET DevKit
1 year 15 weeks ago

Most of our web hosting is being done on shared servers some with vmware.