IP Library Granted Patent US 9,609,460
Granted Patent B2
US 9,609,460 · App. 14/797,227 · Granted Mar 28, 2017

Cloud based mobile device security and policy enforcement

Inventor: Amit Sinha (San Jose, CA)
Assignee: Zscaler, Inc.
H04W4/003H04L63/145H04L63/1425H04L63/1441H04L63/20H04L67/306H04W12/08H04W12/10H04W12/12H04L63/104
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 9,609,460
App. No.
14/797,227
Granted
Mar 28, 2017
Kind
B2
Abstract

Cloud based mobile device security and policy systems and methods use the “cloud” to pervasively enforce security and policy on mobile devices. The cloud based mobile device security and policy systems and methods provide uniformity in securing mobile devices for small to large organizations. The cloud based mobile device security and policy systems and methods may enforce one or more policies for users wherever and whenever the users are connected across a plurality of different devices including mobile devices. This solution ensures protection across different types, brands, operating systems, etc. for smartphones, tablets, netbooks, mobile computers, and the like.

Claims (43)

1. A mobile device security and policy enforcement method implemented by a processing node in a cloud based system, comprising:

subsequent to communicatively coupling a mobile device to the processing node based on configuring the mobile device with a mobile configuration profile which natively supports updating configuration settings in a mobile operating system to cause communication of the mobile device through the cloud based system, monitoring data between the mobile device and an external network;

enforcing policy relative to the data, wherein the policy is associated with a user of the mobile device, and inspecting the data for malicious content therein, wherein an authority node provides threat data for the malicious content and updates to the processing node;

allowing the data responsive to the data complying with the policy and/or containing no malicious content such that the data is provided through the cloud based system to either the mobile device or the external network; and

blocking the data in the processing node responsive to the data not complying with the policy and/or containing malicious content such that the data is not provided to either the mobile device or the external network, wherein the enforcing, the inspecting, the allowing, and the blocking is performed in the processing node independent of the mobile device.

2. The mobile device security and policy enforcement method of claim 1 , wherein the monitoring, the enforcing, the inspecting, the allowing, and the blocking are performed by the node without a platform-specific app on the mobile device.

3. The mobile device security and policy enforcement method of claim 1 , wherein the malicious content comprises one or more of viruses, spyware, malware, Trojans, botnets, spam email, phishing content, and blacklisted content.

4. The mobile device security and policy enforcement method of claim 1 , wherein the policy comprises one or more of inappropriate content, data leakage, data usage limits, time-of-day usage limits, location, operation of a particular application, and black lists of websites.

5. The mobile device security and policy enforcement method of claim 1 , wherein the policy comprises preventing installation of a particular application on the mobile device.

6. The mobile device security and policy enforcement method of claim 5 , wherein the particular application is blocked for one or more of failing to meet a minimum threshold for security and/or privacy and interfering with an enterprise network associated with the user.

7. The mobile device security and policy enforcement method of claim 1 , further comprising:

receiving an update to the policy for the user or for a group of users comprising the users; and

performing the enforcing with the updated policy.

8. The mobile device security and policy enforcement method of claim 1 , further comprising:

receiving an update related to the malicious content from another node in the cloud based system; and

performing the inspecting the data with the update.

9. The mobile device security and policy enforcement method of claim 1 , wherein the node forms an association with the mobile device.

10. A mobile device security and policy enforcement system comprising a processing node in a cloud based system, comprising:

a network interface communicatively coupled to a processor; and

memory storing instructions that, when executed, cause the processor to:

subsequent to communicatively coupling to a mobile device based on configuring the mobile device with a mobile configuration profile which natively supports updating configuration settings in a mobile operating system to cause communication of the mobile device through the cloud based system, monitor data between the mobile device and an external network;

enforce policy relative to the data, wherein the policy is associated with a user of the mobile device, and inspect the data for malicious content therein, wherein an authority node provides threat data for the malicious content and updates to the processing node;

allow the data responsive to the data complying with the policy and/or containing no malicious content such that the data is provided through the system to either the mobile device or the external network; and

block the data in the processing node responsive to the data not complying with the policy and/or containing malicious content such that the data is not provided to either the mobile device or the external network, wherein the policy is enforced, the data is inspected, and the data is allowed or blocked in the system independent of the mobile device.

11. The mobile device security and policy enforcement system of claim 10 , wherein the mobile device does not utilize a platform-specific app for mobile device security and policy enforcement.

12. The mobile device security and policy enforcement system of claim 10 , wherein the malicious content comprises one or more of viruses, spyware, malware, Trojans, botnets, spam email, phishing content, and blacklisted content.

13. The mobile device security and policy enforcement system of claim 10 , wherein the policy comprises one or more of inappropriate content, data leakage, data usage limits, time-of-day usage limits, location, operation of a particular application, and black lists of websites.

14. The mobile device security and policy enforcement system of claim 10 , wherein the policy comprises preventing installation of a particular application on the mobile device.

15. The mobile device security and policy enforcement system of claim 14 , wherein the particular application is blocked for one or more of failing to meet a minimum threshold for security and/or privacy and interfering with an enterprise network associated with the user.

16. The mobile device security and policy enforcement system of claim 10 , wherein the memory storing instructions that, when executed, further cause the processor to:

receive an update to the policy for the user or for a group of users comprising the users; and

enforce the policy with the updated policy.

17. The mobile device security and policy enforcement system of claim 10 , wherein the memory storing instructions that, when executed, further cause the processor to:

receive an update related to the malicious content from another node in the cloud based system; and

inspect the data with the update.

18. The mobile device security and policy enforcement system of claim 10 , wherein the node forms an association with the mobile device.

19. A mobile device, comprising:

a network interface communicatively coupled to a processor; and

memory storing instructions that, when executed, cause the processor to:

subsequent to communicatively coupling to a processing node in a mobile device security and policy enforcement system based on configuring the mobile device with a mobile configuration profile which natively supports updating configuration settings in a mobile operating system to cause communication of the mobile device through the cloud based system, transmit data to an external network through the processing node, wherein responsive to the data (i) complying with policy associated with a user of the mobile device based on enforcement by the processing node and (ii) containing no malicious data therein based on inspection of the data for the policy and for the malicious data by the processing node independent of the mobile device, the processing node is configured to allow the data;

responsive to responsive data from the external network (i) complying with the policy based on enforcement by the processing node and (ii) containing no malicious content therein based on inspection by the processing node for the policy and the malicious content independent of the mobile device, receive the responsive data, from the processing node, wherein an authority node provides threat data for the malicious content and updates to the processing node; and

responsive to any of the data not complying with the policy, responsive to the data containing malicious data therein, responsive to the responsive data from the external network not complying with the policy, or responsive to the responsive data containing malicious content therein, receive a notification from the processing node and the data is blocked by the processing node independent of the mobile device such that the data is not provided to either the mobile device or the external network.

20. The mobile device of claim 19 , wherein the mobile device does not execute a platform-specific application related to policy enforcement and data inspection by the node.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 13, 2015
From: SINHA, AMIT
To: ZSCALER, INC.
Reel/Frame 036065/0192 →
Continuity (5)
Continuation 13243807 · Sep 23, 2011
Continuation In Part 13206337 · Aug 9, 2011
Continuation In Part 14797227
Continuation In Part 13051519 · Mar 18, 2011
Related Publication 20150326615A1 · Nov 12, 2015