Enforcing security policies on mobile devices in a hybrid architecture
Systems and methods include intercepting traffic on a mobile device based on a set of rules; determining whether a connection associated with the traffic is allowed based on a local map associated with an application; responsive to the connection being allowed or blocked based on the local map, one of forwarding the traffic associated with the connection when allowed and generating a block of the connection at the mobile device when blocked; and, responsive to the connection not having an entry in the local map, forwarding a request for the connection to a cloud-based system for processing therein. The cloud-based system is configured to allow or block the connection based on the connection not having an entry in the local map.
1. A non-transitory computer-readable medium storing computer-executable instructions, and in response to execution by a mobile device, the computer-executable instructions cause the mobile device to perform the steps of:
intercepting traffic on the mobile device based on a set of rules;
consulting a plurality of local maps associated with an application including a firewall map, a domain map, and a Hypertext Transfer Protocol (HTTP) request map, wherein (1) the firewall map is consulted for rules based on destination Internet Protocol (IP) address, (2) the domain map is consulted for HTTP and HTTPS connections, and (3) the HTTP request map is consulted for HTTP requests;
determining whether a connection associated with the traffic is allowed based on the local maps associated with the application;
responsive to the connection being allowed or blocked based on the local maps, one of forwarding the traffic associated with the connection when allowed and generating a block of the connection at the mobile device when blocked; and
responsive to the connection not having an entry in the local maps, forwarding a request for the connection to a cloud-based system for processing therein.
2. The non-transitory computer-readable medium of claim 1 , wherein the cloud-based system is configured to allow or block the connection based on the connection not having an entry in the local maps.
3. The non-transitory computer-readable medium of claim 1 , wherein the steps further include
receiving an update from the cloud-based system based on the forwarding the request to the cloud-based system; and
updating the local maps based on the update.
4. The non-transitory computer-readable medium of claim 1 , wherein the steps further include
receiving periodic updates from the cloud-based system; and
updating the local maps based on the periodic updates.
5. The non-transitory computer-readable medium of claim 4 , wherein the periodic updates are based on monitoring in the cloud-based system and based on policy of a tenant associated with a user of the mobile device.
6. The non-transitory computer-readable medium of claim 1 , wherein the steps further include
timing out entries in the local maps and removing timed out entries.
7. The non-transitory computer-readable medium of claim 1 , wherein the traffic includes any of Hypertext Transfer Protocol (HTTP) and HTTP Secure (HTTPS) requests and traffic based on a plurality of destination Internet Protocol (IP) address, protocol, and port.
8. A mobile device configured to execute an application for service discovery and connectivity, the mobile device comprising:
a network interface, a data store, and a processor communicatively coupled to one another; and
memory storing computer-executable instructions, and in response to execution by the processor, the computer-executable instructions cause the processor to
intercept traffic on the mobile device based on a set of rules,
consult a plurality of local maps associated with an application including a firewall map, a domain map, and a Hypertext Transfer Protocol (HTTP) request map, wherein (1) the firewall map is consulted for rules based on destination Internet Protocol (IP) address, (2) the domain map is consulted for HTTP and HTTPS connections, and (3) the HTTP request map is consulted for HTTP requests;
determine whether a connection associated with the traffic is allowed based on the local maps associated with the application,
responsive to the connection being allowed or blocked based on the local maps, one of forward the traffic associated with the connection when allowed and generate a block of the connection at the mobile device when blocked, and
responsive to the connection not having an entry in the local maps, forward a request for the connection to a cloud-based system for processing therein.
9. The mobile device of claim 8 , wherein the cloud-based system is configured to allow or block the connection based on the connection not having an entry in the local maps.
10. The mobile device of claim 8 , wherein the computer-executable instructions further cause the processor to
receive an update from the cloud-based system based on the forwarding the request to the cloud-based system; and
update the local maps based on the received update.
11. The mobile device of claim 8 , wherein the computer-executable instructions further cause the processor to
receive periodic updates from the cloud-based system; and
update the local maps based on the periodic updates.
12. The mobile device of claim 11 , wherein the periodic updates are based on monitoring in the cloud-based system and based on policy of a tenant associated with a user of the mobile device.
13. The mobile device of claim 8 , wherein the computer-executable instructions further cause the processor to
timing out entries in the local maps and removing timed out entries.
14. The mobile device of claim 8 , wherein the traffic includes any of Hypertext Transfer Protocol (HTTP) and HTTP Secure (HTTPS) requests and traffic based on a plurality of destination Internet Protocol (IP) address, protocol, and port.
15. A method implemented by a mobile device, the method comprising:
intercepting traffic on the mobile device based on a set of rules;
consulting a plurality of local maps associated with an application including a firewall map, a domain map, and a Hypertext Transfer Protocol (HTTP) request map, wherein (1) the firewall map is consulted for rules based on destination Internet Protocol (IP) address, (2) the domain map is consulted for HTTP and HTTPS connections, and (3) the HTTP request map is consulted for HTTP requests;
determining whether a connection associated with the traffic is allowed based on the local maps associated with the application;
responsive to the connection being allowed or blocked based on the local maps, one of forwarding the traffic associated with the connection when allowed and generating a block of the connection at the mobile device when blocked; and
responsive to the connection not having an entry in the local maps, forwarding a request for the connection to a cloud-based system for processing therein.
16. The method of claim 15 , wherein the cloud-based system is configured to allow or block the connection based on the connection not having an entry in the local maps.
17. The method of claim 15 , further comprising
receiving an update from the cloud-based system based on the forwarding the request to the cloud-based system; and
updating the local maps based on the update.
18. The method of claim 15 , further comprising
receiving periodic updates from the cloud-based system; and
updating the local maps based on the periodic updates.
19. The method of claim 18 , wherein the periodic updates are based on monitoring in the cloud-based system and based on policy of a tenant associated with a user of the mobile device.
20. The method of claim 15 , further comprising
timing out entries in the local maps and removing timed out entries.