Milestone XProtect Go 2014 - Manual (Page 142)

Milestone XProtect ® Go 2014 Administrator's Manual
www.milestonesys.com 142 Advanced configuration
Log structures
Most log files generated by your system use a shared structure complying with the W3C Extended Log
File Format. 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.
The encrypted part makes it possible, through decryption and comparison, to assert that a log
file has not been tampered with.
Log integrity checks
All log files, except Management Application log files, are subjected to an integrity check once every
24 hours. The integrity check is performed by your system's Log Check service. The result of the
integrity check is automatically written to a file named according to the structure
LogCheck_YYYYMMDD.log, for example LogCheck_20091231.log. Like the log files themselves, the
log check files are by default placed in the appropriate All Users folder for the operating system you
are using.
Any inconsistencies are reported in the form of error messages written in the log check file.
Possible error messages:
Name Description
Log integrity information was
not found. Log integrity can't
be guaranteed.
The log file could not be checked for integrity.
Log information does not
match integrity information.
Log integrity can't be
guaranteed.
The log file exists, but does not contain the expected information.
Log integrity cannot be guaranteed.
[Log file name] not found The log file was not present.
[Log file name] is empty The log file was present, but empty.
Last line changed/removed in
[log file name]
The last line of the log file did not match the validation criteria.
Encrypted data missing in [log
file name] near line [#]
The encrypted part of the relevant log line was not present.
Inconsistency found in [log
file name] near line [#]
The log line does not match the encrypted part.
Inconsistency found in [log
file name] at beginning of log
file
The log file header is not correct. This situation is most likely to
occur if a user has attempted to delete the beginning of a log file.
Note: Other messages that are not error-related may also appear in the log check file.