Hello Pasi,
The catch here is that lsdata and lsmaint are command line utilities outside the envision product itself. The simple act of running a command line executable does not generate a windows event log (or any log for that matter).
The best way I can think of handling this is to turn on file/object auditing for both of those executable files and then read in the enVision appliance's own Windows logs. This should generate a Security_592_Security event whenever one of those files is executed.
