System and method for providing network security to mobile devices

• US 9,497,622 B2
• Filed: 11/27/2013
• Issued: 11/15/2016
• Est. Priority Date: 12/13/2005
• Status: Active Grant

• Current Assignee: CUPP Computing AS
• Original Assignee: CUPP Computing AS
• Inventors: Touboul, Shlomo
• Primary Examiner(s): Okeke, Izunna
• Application Number:
  US14/092,756
• Publication Number:
  US 20140090046A1
• Time in Patent Office: 1,084 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 21/562 Static detection
• CPC Class Codes: H04L 63/02 for separating internal from external traffic, e.g. firewalls
• CPC Class Codes: H04L 63/0263 Rule management
• CPC Class Codes: H04L 63/1416 Event detection, e.g. attack signature detection
• CPC Class Codes: H04L 63/1441 Countermeasures against malicious traffic countermeasures against attacks on cryptographic mechanisms H04L9/002
• CPC Class Codes: H04L 63/145 the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04W 12/00 Security arrangements; Authentication; Protecting privacy or anonymity
• CPC Class Codes: H04W 12/12 Detection or prevention of fraud
• CPC Class Codes: H04W 12/128 Anti-malware arrangements, e.g. protection against SMS fraud or mobile malware

Abstract

A small piece of hardware connects to a mobile device and filters out attacks and malicious code. Using the piece of hardware, a mobile device can be protected by greater security and possibly by the same level of security offered by its associated corporation/enterprise. In one embodiment, a mobile security system includes a connection mechanism for connecting to a data port of a mobile device and for communicating with the mobile device; a network connection module for acting as a gateway to a network; a security policy for determining whether to forward content intended for the mobile device to the mobile device; and a security engine for executing the security policy.

Claims

1. A mobile security system, comprising:

a mobile security system processor;

a mobile security system memory;

a connection mechanism configured to receive network data previously received by a mobile device before being executed by a mobile device processor of the mobile device, the mobile security system processor being different than the mobile device processor;

a network connection module configured to act as a network gateway;

a security policy for determining whether to forward the network data intended for the mobile device to the mobile device, the security policy configured to instruct the mobile security system to allow the network data to be received by the mobile device without scanning by the mobile security system processor of the mobile security system for malicious content if the network connection module is in communication with one or more trusted networks identified by the security policy;

a security engine for executing the security policy in the mobile security system memory; and

a backup module configured to store at least a portion of a boot sector of the mobile device, the stored portion configured to aid recovery of the boot sector of the mobile device should the boot sector of the mobile device become compromised.

2. The mobile security system of claim 1, further comprising a connection mechanism for connecting a data port of the mobile device and for communicating with the mobile device, the connection mechanism including at least one of a USB connector, a PCMCIA connector, an Ethernet connector, and a wireless communication module.

3. The mobile security system of claim 1, wherein the network connection module includes a wireless network interface card.

4. The mobile security system of claim 1, wherein the security engine includes at least one of an antivirus engine, an antispyware engine, a firewall engine, an IPS/IDS engine, a content filtering engine, a multilayered security monitor, a bytecode monitor, and a URL monitor.

5. The mobile security system of claim 1, wherein the security engine performs weighted risk analysis.

6. The mobile security system of claim 5, wherein the weighted risk analysis weighs risk based on content type.

7. The mobile security system of claim 5, wherein the weighted risk analysis weighs risk based on content source.

8. The mobile security system of claim 5, wherein the weighted risk analysis weighs risk based on content source category.

9. The mobile security system of claim 5, wherein the weighted risk analysis weighs risk based on historical actions of a user.

10. The mobile security system of claim 1, further comprising a remote management module capable of receiving security policy updates from a remote trusted source.

11. The mobile security system of claim 1, further comprising a remote management module capable of receiving security engine updates from a remote trusted source.

12. The mobile security system of claim 1, further comprising security data and a remote management module capable of receiving security data updates.

13. The mobile security system of claim 12, wherein the security data includes malicious content signatures.

14. The mobile security system of claim 1, further comprising a distribution module capable of forwarding updates to other mobile security systems.

15. The mobile security system of claim 1, further comprising a remote configuration module capable of communicating with a wizard, the wizard being in communication with a remote enterprise network security system, the wizard being capable of substantially automatic generation of policies and data based on policies and data on the enterprise network security system, the remote configuration module being capable of installing the policies and data generated by the wizard.

16. The mobile security system of claim 1, further comprising a preboot memory that is not accessible during runtime, the preboot memory storing a copy of at least a portion of an operating system of the mobile security system, the mobile security system being configured to load the at least a portion of the operating system every time the mobile security system is rebooted.

17. A method comprising:

executing, by a mobile security system, a security policy by a security engine in a mobile security system memory of the mobile security system using a mobile security system processor of the mobile security system;

detecting, by the mobile security system, if a mobile device connected to the mobile security system is in communication with one or more trusted networks identified by the security policy;

determining, by the mobile security system, not to scan network data received by the mobile device and allow the network data to be executed by a processor of the mobile device if the mobile device is in communication with the one or more trusted networks;

receiving, over a connection mechanism of the mobile security system for connecting to the mobile device, network data received by the mobile device when the mobile device is not in communication with the one or more trusted networks, the network data being intended for the mobile device, the network data being received over the connection mechanism before execution by the processor of the mobile device;

acting, by the mobile security system, as a network gateway on behalf of the mobile device;

determining, by the mobile security system, whether to forward the network data to the mobile device, the determining being based on the security policy in the mobile security system memory; and

storing, by the mobile security system, at least a portion of a boot sector of the mobile device, the stored portion configured to aid recovery of the boot sector of the mobile device should the boot sector of the mobile device become compromised.

18. A system comprising:

an interface for receiving, by a mobile security system, network data previously received by a mobile device before being executed by a mobile device processor of the mobile device;

a processor for executing a security policy in a mobile security system memory of the mobile security system, the security policy for detecting malware in the network data and determining whether to forward the network data intended for the mobile device to the mobile device if malware is not detected in the network data, the security policy configured to instruct the mobile security system to allow the network data to be received by the mobile device without scanning for malicious content if the mobile device is in communication with one or more trusted networks identified by the security policy; and

a data store for storing at least a portion of a boot sector of the mobile device, the stored portion configured to aid recovery of the boot sector of the mobile device should the boot sector of the mobile device become compromised.