The definition of a keylogger is any device or program that captures and records information from an input device. Input devices include keyboards, mice, touch screens and voice commands. So, yes, a keylogger is what you need to use, but most keyloggers only capture keyboard input.
Recording mouse clicks, however, is fairly meaningless unless you know what the user is clicking on. The main legitimate purpose of keyloggers is to monitor user activity. If, for example, an organization suspects an employee of sending confidential information to a third party, they may want to record his or her actions. This type of keylogger can be either a software program or a hardware dongle that sits between the keyboard and the desktop. With keyloggers, the main aim is capture the data input. Therefore the time between inputs is not critical, and time statistics are not recorded. Even a hacker's keyloggers do not record time-related data.
If you can't find a keylogger that captures all the data that you need, you could very easily write your own simple program to do this. If you're not that familiar with coding such a program, you could start by looking at the code for Keymail. Keymail is a keylogger that emails keystrokes to a chosen email address, but this program could easily be adapted to capture and store the information that your boss needs. If you need to capture data from users running different operating systems, then a hardware keylogger is the way to go; these are usually OS independent and do not require any software to be installed. They also have the advantage of not being affected by hardware crashes or system formats.
Whatever route you choose, you should be aware of the personal privacy rules that need to be adhered to. Also, you need to ensure that the logged data does not fall into the wrong hands, captured keystrokes may well include network passwords and other sensitive data. This is why hackers use keyloggers so frequently. They install keyloggers on users' machines in order to gather useful information for further attacks.
This was first published in April 2007