IP Library Granted Patent US 8,332,872
Granted Patent B2
US 8,332,872 · App. 12/814,995 · Granted Dec 11, 2012

System and method for handling an event in a computer system

Assignee: Wontok, Inc.
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,332,872
App. No.
12/814,995
Granted
Dec 11, 2012
Kind
B2
Abstract

Systems for handling an event in a computer system which has a kernel-mode and a user-mode. The systems comprise at least one computing device. The computing device is configured to suspend an occurrence of the event in the kernel-mode of an operating system running thereon. The computing device is also configured to cause the event to occur in the user-mode of the operating system. The computing device is further configured to determine if an occurrence of the event in the kernel-mode will compromise the computer system by analyzing the occurrence of the event in the user-mode. If it is determined that the occurrence of the event in the kernel-mode will compromise the computer system, then the computing device executes at least one security measure.

Claims (26)

1. A system for handling an event in a computer system comprising:

at least one computing device having software executing thereon that is configured to

(a) suspend an occurrence of an event in a kernel-mode of an operating system running on said computing device;

(b) cause the event to occur in a user-mode of the operating system;

(c) determine if an occurrence of the event in the kernel-mode will compromise the computer system by analyzing the occurrence of the event in the user-mode; and

(d) execute at least one security measure if it is determined that the occurrence of the event in the kernel-mode will compromise the computer system;

wherein the security measure comprises denying an ability to write data to or read data from a file stored in a memory device of the computer system.

2. The system as claimed in claim 1 , wherein the security measure includes influencing an operation of the computer system based on the occurrence of the event in the user-mode.

3. The system as claimed in claim 2 , wherein the operation of the computer system is influenced by preventing the event from occurring in the kernel-mode.

4. The system as claimed in claim 1 , wherein the computing device is further configured to

run a user-mode software application operative to issue a request for the suspension of the occurrence of the event in the kernel-mode, and

run a first kernel-mode software module operable to use the request in order to activate a second kernel-mode software module operable to effect suspension of a class of events that comprises the event.

5. The system as claimed in claim 4 , wherein the second kernel-mode software module is further operable to interact with the operating system of the computer system in order to effect the suspension.

6. The system as claimed in claim 1 , wherein the event is selected from the group comprising a file system input/output based event, a network input/output based event, a memory management input/output based event, and a process management based event.

7. A method of handling an event in a computer system which has a kernel-mode and a user-mode, the method comprising the following steps performed by at least one computing device:

effecting a suspension of the occurrence of the event in the kernel-mode of an operating system running on said computer system;

effecting an occurrence of the event in the user-mode of the operating system;

determining if an occurrence of the event in the kernel-mode will compromise the computer system by analyzing the occurrence of the event in the user-mode; and

executing at least one security measure if it is determined that the occurrence of the event in the kernel-mode will compromise the computer system;

wherein the security measure comprises denying an ability to write data to or read data from a file stored in a memory device of the computer system.

8. The method as claimed in claim 7 , wherein the step of executing at least one security measure further comprises influencing an operation of the computer system based on the occurrence of the event in the user-mode.

9. The method as claimed in claim 8 , wherein the operation of the computer system is influenced by preventing the event from occurring in the kernel-mode.

10. The method as claimed in claim 9 , further comprising the steps of:

issuing a request for the suspension of the occurrence of the event in the kernel-mode; and

using the request in order to activate a kernel-mode software module that is operable to effect suspension of a class of events that comprises the event.

11. The method as claimed in claim 10 , further comprising the step of using the kernel-mode software module to interact with the operating system of the computer system in order to effect the suspension.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 21, 2011
From: SAFECENTRAL, INC.
To: WONTOK, INC.
Reel/Frame 027424/0250 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 16, 2011
From: KOUZNETSOV, OLEG; KARLSSON, GUSTAV; FREERICKS, HELMUTH
To: SAFECENTRAL, INC.
Reel/Frame 026919/0547 →
Priority Claims (1)
AU 2004903759 · Jul 8, 2004 · national
Continuity (3)
Continuation 11175006 · Jul 5, 2005
Provisional Application 60585520 · Jul 6, 2004
Related Publication 20100251368A1 · Sep 30, 2010