XProtect Express 1.1; Administrator's Manual - Milestone

Milestone XProtect ® Express 1.1Administrator's ManualLog locationsAll log files are by default placed in the appropriate All Users folder for the operating system you are using. Bydefault, they are stored there for seven days. Note, however, that log file locations as well as the number of daysto store the logs can be changed as part of the logging configuration.Log structuresMost log files generated by XProtect Express use a shared structure complying with the W3C Extended Log FileFormat. Each log file consists of a header and a number of log lines:The header outlines the information contained in the log lines.The log lines consist of two main parts: the log information itself as well as an encrypted part. Theencrypted part makes it possible, through decryption and comparison, to assert that a log file has notbeen tampered with.Log integrity checksAll log files, except Management Application log files, are subjected to an integrity check once every 24 hours.The integrity check is performed by the XProtect Express Log Check service.The result of the integrity check is automatically written to a file named according to the structureLogCheck_YYYYMMDD.log, for example LogCheck_20091231.log. Like the log files themselves, the log checkfiles are by default placed in the appropriate All Users folder for the operating system you are using.Any inconsistencies will be reported in the form of error messages written in the log check file. Possible errormessages (other, non-error, messages may also appear in the log check file):NameLog integrity information was notfound. Log integrity can't beguaranteed.Log information does not matchintegrity information. Logintegrity can't be guaranteed.[Log file name] not found[Log file name] is emptyLast line changed/removed in [logfile name]Encrypted data missing in [logfile name] near line [#]Inconsistency found in [log filename] near line [#]Inconsistency found in [log filename] at beginning of log fileDescriptionThe log file could not be checked for integrity.The log file exists, but does not contain the expected information. Thus, logintegrity cannot be guaranteed.The log file was not present.The log file was present, but empty.The last line of the log file did not match validation criteria.The encrypted part of the log line in question was not present.The log line does not match the encrypted part.The log file header is not correct. This situation is most likely to occur if auser has attempted to delete the beginning of a log file.Configure system, event and audit loggingXProtect Express can to generate various logs. To configure logging, do the following:www.milestonesys.com 129 Advanced configuration