1

Closed

Log Remote Access

description

It should be possible to switch on logging. Logging should perform as follows:
 
When remote access is detected for a user not already "under logging", a remote access event should be logged.
 
No more logging should occur for the same user, until they are detected as "no longer active" i.e. no processes are running for them, at which point a remote access event should be logged and they should no longer be considered "under logging".
 
To facilitate this, the monitor should never "pause" when an alert is issued, but continue to scan. The UI will display the latest "n" log entries and should have the option to "clear" the visible list.
 
There should also be an option to view the log file and to clear out all log files.
 
The UI should note the approximate size of the log files.
 
A remote access event is defined as:
 
Date
Time
User Account
Type (Detected | Finished)
Closed Dec 11, 2009 at 7:22 AM by Sohnee
Included in Beta 2 release

comments

Sohnee wrote Dec 11, 2009 at 7:08 AM

I have added logging within the UI and the monitor continues to scan and logs further events, including where the remote session ends. The remote access event has been created.

I have not written these features to a log file - we will need to decide if that is what we really want to do - the event history is displayed within the UI currently.

I have adjusted the title to reflect this and if anyone thinks it is a useful feature to log to a text file, please add a new feature request for this.

wrote Dec 11, 2009 at 7:22 AM

wrote Feb 13, 2013 at 10:55 PM

wrote May 16, 2013 at 3:33 AM