System and method for monitoring and controlling software usage in a computer

• US 7,979,898 B2
• Filed: 11/10/2005
• Issued: 07/12/2011
• Est. Priority Date: 11/10/2004
• Status: Active Grant

• Current Assignee: Barclays Capital Incorporated (Barclays PLC)
• Original Assignee: Barclays Capital Incorporated (Barclays PLC)
• Inventors: Zarenin, Alex, Belugin, Anatoliy, Bernadskii, Iouri
• Primary Examiner(s): To, Jennifer N
• Application Number:
  US11/272,161
• Publication Number:
  US 20060107256A1
• Time in Patent Office: 2,070 Days
• Field of Search: 717168-178, 709/201, 709223-226, 726/22, 726/26, 726/7, 726/17
• US Class Current: 726/7
• CPC Class Codes: G06F 21/105 Arrangements for software license management or administration, e.g. for managing licenses at corporate level
• CPC Class Codes: G06F 21/121 Restricting unauthorised execution of programs
• CPC Class Codes: G06F 21/50 Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
• CPC Class Codes: G06F 2221/2135 Metering

Abstract

Methods and systems for providing real-time reporting of software usage includes an agent running on a local computer. The agent identifies new processes started on the computer and checks the new process against a restricted list. If the new process is on the restricted list, the agent automatically performs one or more restriction actions associated with the executable name of the process. The restricted list is contained in a configuration file stored on the local computer. A master configuration file for the local computer is stored on a server and replaces the configuration file when the configuration file is outdated. An authorized administrator may edit the master configuration file by adding or removing executable and DLL names from the restricted list and by adding or removing restriction actions associated with the executable and DLL names on the restricted list.

Claims

1. A method comprising:

running an agent program on a computer;

identifying a new process executing on the computer;

comparing a configuration file to a master configuration file for the computer to determine if the configuration file is updated;

comparing the new process to a restricted list stored in the configuration file on the computer, each entry in the restricted list comprising a name of an executable and a restriction action, the restriction action being a termination of the execution of the new process; and

performing the restriction action on the new process if the new process is on the restricted list and not on an ignore list,

the step of comparing the configuration file to the master configuration file further including the steps of;

calculating a checksum for the configuration file,

transmitting the checksum to a server,

receiving a copy of the master configuration file from the server if the transmitted checksum does not equal a checksum for the master configuration file, and

replacing the configuration file with the copy of the master configuration file.

2. The method of claim 1 further comprising transmitting a report to a central repository in communication with the computer after performing the restriction action thereby providing real-time computer usage to the central repository.

3. The method of claim 2 wherein the report includes a process ID.

4. The method of claim 2 wherein the report includes a start time.

5. The method of claim 2 wherein the report includes an executable name.

6. The method of claim 1, wherein the master configuration file is stored on the server in communication with the computer.

7. The method of claim 6 wherein communication between the computer and the server is via HTTP protocol on Port 80.

8. The method of claim 1 further comprising comparing the new process to the ignore list stored in the configuration file, the agent ignoring the new process if it is listed on the ignore list.

9. A system comprising:

a computer in communication with a server;

a configuration file stored on the computer, the configuration file including a restricted list, each entry in the restricted list comprising an executable name and a restriction action; and

an agent program executing on the computer, the agent configured to identify a new process executing on the computer by comparing the new process to the restricted list stored in the configuration file and perform the restriction action when the new process matches the executable name on the restricted list and is not on an ignore list, the restriction action being a termination of the execution of the new process,

the agent program further configured to compare the configuration file to a master configuration file for the computer to determine if the configuration file is updated, wherein said compare the configuration file to the master configuration file further includes calculating a checksum for the configuration file, transmitting the checksum to the server, receiving a copy of the master configuration file from the server if the transmitted checksum does not equal a checksum for the master configuration file, and replacing the configuration file with the copy of the master configuration file.

10. The system of claim 9 wherein the master configuration file is stored on the server, the server configured to push the master configuration file to the computer when the configuration file stored on the computer is invalid.

11. The system of claim 9 further comprising a central repository, the central repository in communication with the computer and configured to receive a report from the computer, the reporting including information about the new process.

12. A computer program product stored on a non-transitory computer readable medium having thereon computer executable instructions that, when executed on a computer, configure the computer to perform a method comprising the steps of:

running an agent program;

identifying a new process executing;

comparing a configuration file to a master configuration file for the computer to determine if the configuration file is updated;

comparing the new process to a restricted list stored in the configuration file, each entry in the restricted list comprising a name of an executable and a restriction action, the restriction action being a termination of the execution of the new process; and

performing a restriction action on the new process if the new process is on the restricted list and not on an ignore list,

the step of comparing the configuration file to the master configuration file further including the steps of;

calculating a checksum for the configuration file, transmitting the checksum to a server,

receiving a copy of the master configuration file from the server if the transmitted checksum does not equal a checksum for the master configuration file, and

replacing the configuration file with the copy of the master configuration file.