Is it possible to outsmart the Visulox Recording System by writing in a window, which is not in focus and/or hidden behind another, or writing in a window with a font, that has been sized too small to read the text?
Visulox Service is not preventing it is controlling.
In the VideoLog you will see, that the user is shuffling windows and the focus is at an underlaying context. The question is, why is it doing this? In a standard professional context, there is never a need for that and if the user is doing this, he makes himself suspicious. But we can solve this. Basically the possibility of shuffling windows is a feature of the Windows Manager (MWM,TWM, DTWM). We provide a window manager configuration within Visulox Service where the shuffling is disabled (!). And shuffling would be more hardened as with standard key strokes.
The font-issue has the same argumentation as shuffling windows. Why should he use a small font. But this can also be prevented by removing the small fonts from the font manager (just an idea). If you think about “Scale to fit to window”, this will not effect the Videolog. In SGD the dimension of a XPE is fixed and this is what we are taping. The “Scale to fit to window” is a presentation feature and behind our taping scope.
VideoLog assists in controlling and is not a tool preventing users from doing things they should not do.
It is the same as at a petrol station: You are controlled and you can do what you want, and you are still responsible for what you are doing. VideoLog is collecting the evidence.
If IT people know that what they are doing is being recorded, they work with more obedience and “prevent” themselves from doing things they should not do.
How big are the recorded films?
In one hour, one recorded film needs approximately 5 MByte.
Sizing example:
For 20 recorders running, the maximum per hour would be 100 MByte.
If 20 recorders are running in an average 12 hours, 1,2 GByte is needed each day.
The films have a life time in days.
After the lifetime has run out, the film is removed from the storage.
If the lifetime is set to 30 days, a storage of approximately 36 GByte is needed.