SECURE INITIALIZATION OF INTRUSION DETECTION SYSTEM

• US 20090126021A1
• Filed: 12/08/2008
• Published: 05/14/2009
• Est. Priority Date: 10/15/2003
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Albornoz, Jordi A.
• Granted Patent: US 7,860,970 B2
• Time in Patent Office: Days
• US Class Current: 726/23
• CPC Class Codes: G06F 21/316 by observing the pattern of computer usage, e.g. typical user behaviour
• CPC Class Codes: G06F 21/552 involving long-term monitoring or reporting
• CPC Class Codes: G06F 21/554 involving event detection and direct action

Abstract

Secure initialization for detecting intrusions is disclosed. The secure initialization includes storing a behavior profile associated with an application, and reading the stored behavior profile that is cryptographically protected. The method further includes monitoring execution of the application during a bootstrapping phase of an intrusion detection system, according to the stored behavior profile. If the behavior of the application does not conform to the behavior profile, a message is issued indicating that the application is not conforming to the behavior profile. The behavior profile can be generated by a developer of the intrusion detection system, a developer of the application, and/or a third party developer. Additionally, the behavior profile is generated by executing the system on a reference computer system or by heuristic determination.

Claims

1. A method in a computer system for detecting intrusions during a bootstrapping phase of an intrusion detection system, the method comprising:

storing a behavior profile associated with an application, wherein the stored behavior profile is cryptographically protected;

reading, with the computer system during a bootstrapping phase of an intrusion detection system, the stored behavior profile associated with the application;

monitoring execution of the application at the computer system during the bootstrapping phase, according to the behavior profile; and

if the behavior of the application does not conform to the behavior profile, issuing a message indicating that the application is not conforming to the behavior profile.

2. The method of claim 1, where the application comprises any one of:

a software program running on a computer system;

a computer network;

a user interfacing with a computer system;

a plurality of computer systems; and

a distributed application.

3. The method of claim 1, wherein the behavior profile is generated by at least one of:

a developer of the method;

a developer of the application; and

a third party developer.

4. The method of claim 1, wherein the behavior profile is generated by any one of:

executing the application on a reference computer system other than the computer system for detecting intrusions during a bootstrapping phase of an intrusion detection system;

heuristic determination; and

a combination of executing the application on the reference computer system and heuristic determination.

5. The method of claim 4, wherein the behavior profile having been generated prior to operation of the application on the computer system that detects intrusions during a bootstrapping phase of an intrusion detection system.

6. The method of claim 1, wherein the behavior profile includes at least one of:

a list of system commands;

a list of file permissions;

a list of directory permissions;

a list of network messages;

a login attempt summary; and

any measurable property of the system or application.

7. The method of claim 1, wherein the stored behavior profile is at least one of:

encrypted; and

digitally signed.

8. The method of claim 1, further comprising:

if the behavior of the application does not conform to the behavior profile, generating a log file describing how the application is not conforming to the behavior profile.

9. The method of claim 1, further comprising:

if the behavior of the application does not conform to the behavior profile, quitting the application that is not conforming to the behavior profile.

10. The method of claim 1, further comprising:

if the behavior of the application does not conform to the behavior profile, prompting the user to determine whether to quit the application that is not conforming to the behavior profile.

11. A computer readable storage medium storing computer instructions for detecting intrusions during a bootstrapping phase of an intrusion detection system, the computer instructions including instructions for:

storing a behavior profile associated with an application, wherein the stored behavior profile is cryptographically protected;

reading, with the computer system during a bootstrapping phase of an intrusion detection system, the stored behavior profile associated with the application;

monitoring execution of the application at the computer system during the bootstrapping phase, according to the behavior profile; and

if the behavior of the application does not conform to the behavior profile, issuing a message indicating that the application is not conforming to the behavior profile.

12. The computer readable medium claim 11, where the application comprises any one of:

a software program running on a computer system;

a computer network;

a user interfacing with a computer system;

a plurality of computer systems; and

a distributed application.

13. The computer readable medium of claim 12, wherein the behavior profile is generated by at least one of:

a developer of the method;

a developer of the application; and

a third party developer.

14. The computer readable medium of claim 11, wherein the behavior profile is generated by any one of:

executing the application on a reference computer system other than the computer system for detecting intrusions during a bootstrapping phase of an intrusion detection system;

heuristic determination; and

a combination of executing the application on the reference computer system and heuristic determination.

15. The method of claim 14, wherein the behavior profile having been generated prior to operation of the application on the computer system that detects intrusions during a bootstrapping phase of an intrusion detection system.

16. The computer readable medium of claim 11, wherein the behavior profile includes at least one of:

a list of system commands;

a list of file permissions;

a list of directory permissions;

a list of network messages;

a login attempt summary; and

any measurable property of the system or application.

17. The computer readable medium of claim 11, wherein the stored behavior profile is at least one of:

encrypted; and

digitally signed.

18. The computer readable medium of claim 11, further comprising:

if the behavior of the application does not conform to the behavior profile, generating a log file describing how the application is not conforming to the behavior profile.

19. A computer system for detecting intrusions during a bootstrapping phase of an intrusion detection system, comprising:

a first memory for storing an application;

a second memory for storing a behavior profile associated with the application, wherein the stored behavior profile is cryptographically protected;

a monitor, communicatively coupled with the first memory and the second memory, for

reading, with the computer system during a bootstrapping phase of an intrusion detection system, the stored behavior profile associated with the application, and

monitoring execution of the application at the computer system during the bootstrapping phase, according to the behavior profile; and

a warning module, communicatively coupled with the monitor, for issuing a message indicating that the application is not conforming to the behavior profile.

20. The computer system of claim 19, wherein the behavior profile having been generated prior to operation of the application on the computer system that detects intrusions during a bootstrapping phase of an intrusion detection system, and wherein the behavior profile is generated by at least one of:

a developer of software for the monitor;

a developer of the application; and

a third party developer.