Browse Prior Art Database

Userid Activity Log Procedure Disclosure Number: IPCOM000015446D
Original Publication Date: 2002-Apr-25
Included in the Prior Art Database: 2003-Jun-20

Publishing Venue



At least one privileged userid is set on each computer system in order to do basic tasks: to administer, to install products or to solve critical situations, etc. The log of the activity performed by these userids can be very useful. Let us see, for example, Audit Trackings performed by security teams. On one hand they must now if an especific user was used or not, on the other hand the type of activity he has done. System and Security administrators spend a lot of time in the whole process and much more if we are talking about a descentralized environment with multiple systems and platforms (to retrieve previous information, to perform a correct audit and to take the appropiate corrective actions). The Activity Log Procedure avoid some tasks by gettig an activity commad log in real time process, by showing an initial message at the beginning of a session e.g.: business notice etc.) and storing the user command activity in a log file and sending this information to a single aplication and userid. The following flow chart shows the Activity Log Logic: 1