I spent the last two days researching how this should be done and since I dont' want to build another box just to monitor file integrity, i'm going to implement a script that will create a listing of the file name, byte size and date modified for each of the config and other files listed in the hardening guide, then create a secondary file of the same information on a schedule. I find it irritating that VMware best practices specify something that you should do but have no easy way of achieving it. ![]() Thanks for the reply, i'm not actively using the vMA, I'm having all logs be sent to a remote logging server for more dissection and control on a customized syslog box. If not, I was thinking about creating a script that will either grab the file size and date modified of the specific files and then run a comparison of the current and previous values at a certain interval.Īnyone do anything remotely like this? I'm trying to get away with not having to build another server (OSSEC) for monitoring. Since there is no service console there are no native md5 or other checksum applications that are apart of or built into ESXI.Īre there any power cli commands that can remotely pull this information down or do a remote file integrity check? I was wondering if anyone is using this or what other methods are there to verify file integrity on an esxi host. There are certain intrusion detection software that can do this, such as OSSEC using the ssh_generic_diff example, which you can specify which files to monitor. ![]() In the April Security Hardening Document, it suggests "establishing and maintaining configuration file integrity". Not sure if this is the right place to put this, but i'm wondering what people are using for file integrity monitoring.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |