Systems and methods for securely managing browser plugins via embedded browser
Embodiments described include systems and methods for securely managing browser plugins via embedded browser. The solution enables a client application or embedded browser to dynamically load the browser components into the embedded browser based on a risk or security profile and one or more policies. The policies can be centrally managed to enable only allowed browser components to be loaded within the embedded browser for a given risk profile. Based on the risk profile, a session established by the embedded browser can be transferred from the client application to a hosted browser at a secure server. When the session is transferred to the hosted browser, the present system can also redirect the browser component configurations to the hosted browser such that the same browser components are enabled, disabled, or modified at the hosted browser.
1. A method comprising
identifying, by a computing device, an application hosted by a remote computing device of another entity different than that of the computing device;
generating, by a security engine, a risk profile associated with the computing device;
determining, by the computing device based on identification of the application, executable code configured to change a function of the client application to access the application;
changing, by the computing device, the function of the client application based on the risk profile; and
providing, by the computing device, the client application including the executable code.
2. The method of claim 1 , further comprising identifying, by the computing device, the executable code stored on one of the computing device or a second computing device of an entity different from the another entity.
3. The method of claim 1 , wherein the executable code comprises one of a plug-in, an extension or an add-on to the client application.
4. The method of claim 1 , further comprising identifying, by the computing device based at least on identification of the application, one or more executable codes to exclude from the client application.
5. The method of claim 4 , further comprising removing, by the computing device, the one or more executable codes from the client application.
6. The method of claim 1 , further comprising including, by the computing device, the executable code in an embedded browser of the client application.
7. The method of claim 1 , further comprising executing, by the client application, the function of the executable code in accessing the application on the remote computing device.
8. A system comprising
a computing device configured to:
identify an application hosted by a remote computing device of another entity different than that of the computing device;
generating, by a security engine, a risk profile associated with the computing device;
determine, based on the risk profile, executable code configured to change a function of the client application to access the application; and
provide the client application including the executable code.
9. The system of claim 8 , wherein the computing device is further configured to identify the executable code stored on one of the computing device or a second computing device of an entity different from the another entity.
10. The system of claim 8 , wherein the executable code comprises one of a plug-in, an extension or an add-on to the client application.
11. The system of claim 8 , wherein the computing device is further configured to identify, based at least on identification of the application, one or more executable codes to exclude from the client application.
12. The system of claim 11 , wherein the computing device is further configured to remove the one or more executable codes from the client application.
13. The system of claim 8 , wherein the computing device is further configured to include the executable code in an embedded browser of the client application.
14. The system of claim 8 , wherein the client application is further configured to execute the function of the executable code in accessing the application on the remote computing device.
15. A client device comprising
one or more processors, coupled to memory and configured to:
determine, based on identification of an application hosted by a remote computing device of, an executable code configured to change a function of the browser to access the application;
generating a risk profile associated with accessing the remote computing device;
based on the risk profile, modify the browser to include the executable code; and
cause execution of the function of the executable code in accessing the application on the remote computing device.
16. The client device of claim 15 , wherein the executable code is stored on one of the computing device or a second computing device of an entity different from the another entity.
17. The client device of claim 15 , wherein the executable code comprises one of a plug-in, an extension or an add-on to the browser.
18. The client device of claim 15 , wherein the computing device is further configured to identify, based at least on identification of the application, one or more executable codes to exclude from the browser.
19. The client device of claim 18 , wherein the one or more processors are further configured to remove the one or more executable codes from the client application.
20. The client device of claim 15 , wherein the browser is an embedded browser of a client application on the client device.