#Xeoma entry point not found password

The main log gives the administrator the other machine’s public IP – it does not coincide with any of the known external supervisors.Īt this point, the administrator is certain that this particular guard’s password has been compromised, willingly or on accident – this is not yet known.

One of them is local (the guard), the other is external – a possible indication that unauthorized personnel gained remote access to the surveillance server. Now the administrator looks up this specific connection (by its time) in the main log to see if both connections were made from inside the local network or not. Session IDs (ColumnA) show that the same user viewed different sources at the same time using different machines. The administrator studies the activity log around the time of the connection. This is reason enough to suspect a possible security breach. The facility’s network indicates that one external connection has been made during the day. The log’s help in this matter is twofold: an innocent man avoided being blamed for a crime he never committed the administrators for this facility found a security breach in their system that can be mended by rearranging the timing for “virtual rounds” for every guard station, so that at any given time every single camera is observed by at least one guard. Apparently, the perpetrator either knew the exact time the entrance won’t be under direct surveillance or had a stroke of good luck.

The log could not have possibly been tempered with, since it is stored on the main server, the guard simply has no direct access to it. The log also shows that this procedure was not unique: he made these “virtual rounds” every hour, following the protocol. The log indicates that at the time of the accident the guard was viewing several other cameras, one-by-one. The administrator examines the activity log, checking the entries relating to the time of the emergency. There are reasons to suspect that he was in cahoots with the perpetrator – this would explain why he neglected to sound the alarm in time. The guard on duty, tasked with controlling this particular entrance, is instantly brought under scrutiny. The alarm was not set off upon the offender’s entry. Its practical applications are plentiful and we shall look at a couple of them.Īn emergency occurred: someone managed to bypass the security using one of the entrances and made off with something valuable.

#Xeoma entry point not found software

Statistics gathering software can use this data for e.g. Now the seemingly confusing mess becomes a logical statement of facts, a data pack, that can be interpreted and analyzed, line-by-line.

#Xeoma entry point not found full

ColumnH: this is the difference between ColumnE and ColumnG in milliseconds it shows you exactly how much time the user spent checking that specific camera’s image in full screen.Įxample: judging by Line7 and Line8, operatorA viewed the camera “Entrance2” for 9173ms (~ 9 sec.).

ColumnF: the date that user minimized that camera’s window back (returned to multiple cameras view mode or exited in a different manner).

ColumnC: this is the name of the camera the user had maximized for the full screen (single camera view mode) the name is assigned in the “Universal camera” module, Source name parameter.

ColumnB: username in Xeoma assigned upon their creation to this user.

log) will give you the IP addresses of the machines for both these people.

Cross-referencing that with Xeoma’s main log ( …/Xeoma/Logs/. ColumnA: this is a unique identifier for the session, its purpose is to let you easily distinguish between connections made from different machines under the same user.Įxample: Line2 and Line3 show the same user (operatorA), but the IDs are different (66836424 vs 66836584) – these are two different people employing the same user credentials on two different machines.On the surface – doesn’t look particularly informative. CSV is basically a spreadsheet or a table that can be viewed both by humans (via spreadsheet programs or simple notepad) and by software. From now on, the directory you specified will contain the file log.csv. One of them – activity log – keeps track of all users currently connected to the server and can be enabled via Main menu → Remote access → Users → Use the csv-file to record users’ actions. Read also: Event log embedded into Xeoma interfaceĮnter Xeoma’s logs.