Mobile application security system and method

• US 20030037099A1
• Filed: 01/10/2001
• Published: 02/20/2003
• Est. Priority Date: 06/09/2000
• Status: Active Grant

• Current Assignee: Aramira Corporation
• Original Assignee: Aramira Corporation
• Inventors: Rygaard, Christopher A.
• Granted Patent: US 6,931,550 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 21/12 Protecting executable software
• CPC Class Codes: G06F 21/64 Protecting data integrity, e.g. using checksums, certificates or signatures
• CPC Class Codes: G06F 9/4862 the task being a mobile agent, i.e. specifically designed to migrate
• CPC Class Codes: H04L 63/12 Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227

Abstract

The mobile application security system and method in accordance with the invention increases the overall level of security in using a mobile application. In a preferred embodiment, the system may use a client/server architecture wherein each host of a mobile application is treated as a client and a central computer is treated as the server. In operation, any time that a mobile application is going to jump between hosts, it must first pass through the central computer so that the central computer may perform various security checks. The security checks ensure that the security of the mobile application is not compromised and overcomes the above problems with typical mobile application systems.

Claims

1. A mobile application security system, comprising:

a central computer for controlling the security of a mobile application;

one or more host computers connected to the server computer, each host computer executing the mobile application that jumps between the hosts during execution;

the central computer further comprising means for monitoring the security of the mobile application as it jumps between the host computers wherein when the mobile application is communicated from a first host to a second host, it passes through the central computer;

wherein the security monitoring means further comprises means detecting code of the mobile application marked as immutable and means for replacing the immutable code with code known to be safe by the central computer.

2. A mobile application security system, comprising:

a central computer for controlling the security of a mobile application;

one or more host computers connected to the server computer, each host computer executing the mobile application that jumps between the hosts during execution;

the central computer further comprising means for monitoring the security of the mobile application as it jumps between the host computers wherein when the mobile application is communicated from a first host to a second host, it passes through the central computer; and

wherein the security monitoring means further comprises means for detecting state data marked as immutable and means for replacing the immutable state data with state data known to be safe by the central computer.

3. A mobile application security system, comprising:

a central computer for controlling the security of a mobile application;

one or more host computers connected to the server computer, each host computer executing the mobile application that jumps between the hosts during execution;

the central computer further comprising means for monitoring the security of the mobile application as it jumps between the host computers wherein when the mobile application is communicated from a first host to a second host, it passes through the central computer; and

wherein the security monitoring means further comprises means for detecting an itinerary of the mobile application that is marked as immutable and means for replacing the immutable itinerary with an itinerary known to be safe by the central computer.

4. The system of claim 3, wherein the itinerary comprises past historical itinerary data.

5. A mobile application security method, comprising:

receiving a mobile application at a central computer each time the mobile application is jumping between a first host and a second host; and

monitoring the security of the mobile application as it jumps between the host computers, wherein the security monitoring further comprises detecting code of the mobile application that is marked as immutable and replacing the immutable code with code known to be safe by the central computer.

6. A mobile application security method, comprising:

receiving a mobile application at a central computer each time the mobile application is jumping between a first host and a second host; and

monitoring the security of the mobile application as it jumps between the host computers,

wherein the security monitoring further comprises detecting a state of the mobile application that is marked as immutable and replacing the immutable state with state data that is known to be safe by the central computer.

7. A mobile application security method, comprising:

receiving a mobile application at a central computer each time the mobile application is jumping between a first host and a second host; and

monitoring the security of the mobile application as it jumps between the host computers, wherein the security monitoring further comprises detecting an itinerary of the mobile application that is marked as immutable and replacing the immutable itinerary with itinerary data known to be safe by the central computer.

8. The method of claim 7, wherein the itinerary comprises past historical itinerary data.