US20230048038A1 - Systems and methods for traffic accounting for saas usage - Google Patents

Abstract

A client application installed on a client device may monitor communications flows between embedded browsers of the client application and one or more servers, including enterprise servers and non-enterprise servers, at upper layers of a network stack of the client device including the application layer, session layer, and presentation layer. Communications to different endpoints may be classified as enterprise or non-enterprise, measured, and aggregated to provide disambiguation of enterprise and non-enterprise communications of the device transiting a single communications link (e.g. cellular data connection). Server and network policies may be applied in accordance with the measurements with higher accuracy than policies based on total bandwidth utilized by the device without regard to its classification. These policies may include load balancing, communication pooling, multiplexing, buffering, pre-fetching or edge caching of data, instantiating or halting execution of virtual machines in a cloud environment, or other such functions.

Description

CROSS-REFERENCE TO RELATED APPLICATION
• This application is a continuation of and claims priority to and the benefit of U.S. patent application Ser. No. 16/188,454, titled “SYSTEMS AND METHODS FOR TRAFFIC ACCOUNTING FOR SAAS USUAGE,” and filed on Nov. 13, 2018, the contents of all of which are hereby incorporated herein by reference in its entirety for all purposes.
FIELD OF THE DISCLOSURE
• The present application generally relates to network or software-as-a-service (SaaS) applications.
BACKGROUND
• User devices or client devices may utilize data connections, such as cellular data, for both enterprise-related communications such as network applications or software-as-a-service applications provided by application servers, as well as non-enterprise-related communications, such as social media, general web browsing, voice or video communications, etc. As these communications may utilize the same network interface and, in some implementations, the same lower layer connections, it may be difficult to disambiguate enterprise and non-enterprise communications. This may impair network operations such as load balancing among servers, instantiating virtual machines to meet anticipated need, pre-fetching of data, or other such operations, resulting in network and device inefficiencies, slowdowns, and higher latency for crucial communications.
BRIEF SUMMARY
• A client application installed on a client device may comprise a usage monitor configured to monitor communications flows between embedded browsers of the client application and one or more servers, including enterprise servers and non-enterprise servers, at upper layers of a network stack of the client device including the application layer, session layer, and presentation layer. Communications to different endpoints may be classified as enterprise or non-enterprise, measured, and aggregated to provide disambiguation of enterprise and non-enterprise communications of the device transiting a single communications link (e.g. cellular data connection). Server and network policies may be applied in accordance with the measurements with higher accuracy than policies based on total bandwidth utilized by the device without regard to its classification. These policies may include load balancing, communication pooling, multiplexing, buffering, pre-fetching or edge caching of data, instantiating or halting execution of virtual machines in a cloud environment, or other such functions.
• The present disclosure is directed towards systems and methods of an embedded browser. A client application executing on a client device can allow a user to access network applications. A browser that is embedded or integrated with the client application can render to the user a network application that is accessed or requested via the client application, and can enable interactivity between the user and the network application. The browser is sometimes referred to as an embedded browser, and the client application with embedded browser (CEB) is sometimes referred to as a workspace application. The client application can establish a secure connection to the one or more servers to provide an application session for the user to access the network application using the client device and the embedded browser. The embedded browser can be integrated with the client application to ensure that traffic related to the network application is routed through and/or processed in the client application, which can provide the client application with real-time visibility to the traffic (e.g., when decrypted through the client application), and user interactions and behavior. The embedded browser can provide a seamless experience to a user as the network application is requested via the user interface (shared by the client application and the embedded browser) and rendered through the embedded browser within the same user interface.
• In one aspect, this disclosure is directed to a method for disambiguation between personal and enterprise data transmitted via a network service provider. The method includes establishing, by a client application on a client device, one or more sessions with one or more network applications via an embedded browser of the client application, the one or more network applications provided via a network service provider to the user by an enterprise and accessed by a user of the enterprise, the client device used by the user for both enterprise and non-enterprise communications. The method also includes tracking, by the client application, a first amount of data of the one or more network applications of the enterprise being communicated between the client device and the network service provider over a first time period for use. The method also includes tracking, by the client application, a second amount of data of the client device other than the one or more network applications being communicated between the client device and the network service provider over a second time period for use. The method also includes communicating, by the client application, to a server an identification of the first amount of data and an identification of the second amount of data.
• In some implementations, the first time period for use and the second time period for use are concurrent. In some implementations, communicating the identification of the first amount of data includes communicating an identification of a name or a type of each of the one or more network applications of the enterprise. In a further implementation, communicating the identification of the first amount of data includes communicating, for each network application of the one or more network applications of the enterprise, an identification of an amount of data communicated by the network application. In some implementations, tracking the first amount of data includes tracking an amount of data communicated via the embedded browser. In a further implementation, tracking the second amount of data includes tracking an amount of data communicated via a second client application of the client device different from the client application. In some implementations, the first amount of data and the second amount of data are communicated via a single network layer connection or a single transport layer connection. In some implementations, the network service provider is unable to distinguish between the first amount of data and the second amount of data. In some implementations, the first amount of data and the second amount of data are both communicated to a server of the enterprise, and the second amount of data is redirected by the server to a server not of the enterprise. In some implementations, the enterprise provides a payment to the network service provider for the first amount of data and not for the second amount of data.
• In another aspect, the present disclosure is directed to a system for disambiguation between personal and enterprise data transmitted via a network service provider. The system includes a client device executing a client application comprising an embedded browser and a usage monitor, and a network interface in communication via a network service provider with one or more network applications provided via a network service provider to the user by an enterprise and accessed by a user of the enterprise, the client device used by the user for both enterprise and non-enterprise communications. The usage monitor is configured to: track a first amount of data of the one or more network applications of the enterprise being communicated between the client device and the network service provider over a first time period for use; track a second amount of data of the client device other than the one or more network applications being communicated between the client device and the network service provider over a second time period for use; and communicate, to a server, an identification of the first amount of data and a identification of the second amount of data.
• In some implementations, the first time period for use and the second time period for use are concurrent. In some implementations, the usage monitor is further configured to communicate, to the server, an identification of a name or a type of each of the one or more network applications of the enterprise. In a further implementation, the usage monitor is further configured to communicate, for each network application of the one or more network applications of the enterprise, an identification of an amount of data communicated by the network application. In some implementations, the usage monitor is further configured to track an amount of data communicated via the embedded browser. In a further implementation, the usage monitor is further configured to track an amount of data communicated via a second client application of the client device different from the client application.
• In some implementations, the first amount of data and the second amount of data are communicated via a single network layer connection or a single transport layer connection. In some implementations, the network service provider is unable to distinguish between the first amount of data and the second amount of data. In some implementations, the first amount of data and the second amount of data are both communicated to a server of the enterprise, and the second amount of data is redirected by the server to a server not of the enterprise. In some implementations, the enterprise provides a payment to the network service provider for the first amount of data and not for the second amount of data.
BRIEF DESCRIPTION OF THE FIGURES
• The foregoing and other objects, aspects, features, and advantages of the present solution will become more apparent and better understood by referring to the following description taken in conjunction with the accompanying drawings, in which:
• FIG.1 is a block diagram of embodiments of a computing device;
• FIG.2 is a block diagram of an illustrative embodiment of cloud services for use in accessing resources;
• FIG.3 is a block diagram of an example embodiment of an enterprise mobility management system;
• FIG.4 is a block diagram of asystem400 of an embedded browser;
• FIG.5 is a block diagram of an example embodiment of a system for using a secure browser;
• FIG.6 is an example representation of an implementation for browser redirection using a secure browser plug-in;
• FIG.7 is a block diagram of an example embodiment of a system of using a secure browser;
• FIG.8 is a block diagram of an example embodiment of a system for using local embedded browser(s) and hosted secured browser(s);
• FIG.9 is an example process flow for using local embedded browser(s) and hosted secured browser(s);
• FIG.10 is an example embodiment of a system for managing user access to webpages;
• FIG.11 is a block diagram of an example embodiment of a system for traffic accounting for network applications;
• FIG.12 is a flow chart of an implementation of a method for traffic accounting for network applications.
• The features and advantages of the present solution will become more apparent from the detailed description set forth below when taken in conjunction with the drawings, in which like reference characters identify corresponding elements throughout. In the drawings, like reference numbers generally indicate identical, functionally similar, and/or structurally similar elements.
DETAILED DESCRIPTION
• For purposes of reading the description of the various embodiments below, the following descriptions of the sections of the specification and their respective contents may be helpful:
• Section A describes a computing environment which may be useful for practicing embodiments described herein.
• Section B describes systems and methods for an embedded browser.
• Section C describes systems and methods for traffic accounting for network applications.
A. Computing Environment
• Prior to discussing the specifics of embodiments of the systems and methods detailed herein in Section B, it may be helpful to discuss the computing environments in which such embodiments may be deployed.
• As shown inFIG.1,computer101 may include one ormore processors103, volatile memory122 (e.g., random access memory (RAM)), non-volatile memory128 (e.g., one or more hard disk drives (HDDs) or other magnetic or optical storage media, one or more solid state drives (SSDs) such as a flash drive or other solid state storage media, one or more hybrid magnetic and solid state drives, and/or one or more virtual storage volumes, such as a cloud storage, or a combination of such physical storage volumes and virtual storage volumes or arrays thereof), user interface (UI)123, one ormore communications interfaces118, andcommunication bus150.User interface123 may include graphical user interface (GUI)124 (e.g., a touchscreen, a display, etc.) and one or more input/output (I/O) devices126 (e.g., a mouse, a keyboard, a microphone, one or more speakers, one or more cameras, one or more biometric scanners, one or more environmental sensors, one or more accelerometers, etc.).Non-volatile memory128stores operating system115, one ormore applications116, anddata117 such that, for example, computer instructions ofoperating system115 and/orapplications116 are executed by processor(s)103 out ofvolatile memory122. In some embodiments,volatile memory122 may include one or more types of RAM and/or a cache memory that may offer a faster response time than a main memory. Data may be entered using an input device ofGUI124 or received from I/O device(s)126. Various elements ofcomputer101 may communicate via one or more communication buses, shown ascommunication bus150.
• Computer101 as shown inFIG.1 is shown merely as an example, as clients, servers, intermediary and other networking devices and may be implemented by any computing or processing environment and with any type of machine or set of machines that may have suitable hardware and/or software capable of operating as described herein. Processor(s)103 may be implemented by one or more programmable processors to execute one or more executable instructions, such as a computer program, to perform the functions of the system. As used herein, the term “processor” describes circuitry that performs a function, an operation, or a sequence of operations. The function, operation, or sequence of operations may be hard coded into the circuitry or soft coded by way of instructions held in a memory device and executed by the circuitry. A “processor” may perform the function, operation, or sequence of operations using digital values and/or using analog signals. In some embodiments, the “processor” can be embodied in one or more application specific integrated circuits (ASICs), microprocessors, digital signal processors (DSPs), graphics processing units (GPUs), microcontrollers, field programmable gate arrays (FPGAs), programmable logic arrays (PLAs), multi-core processors, or general-purpose computers with associated memory. The “processor” may be analog, digital or mixed-signal. In some embodiments, the “processor” may be one or more physical processors or one or more “virtual” (e.g., remotely located or “cloud”) processors. A processor including multiple processor cores and/or multiple processors multiple processors may provide functionality for parallel, simultaneous execution of instructions or for parallel, simultaneous execution of one instruction on more than one piece of data.
• Communications interfaces118 may include one or more interfaces to enablecomputer101 to access a computer network such as a Local Area Network (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN), or the Internet through a variety of wired and/or wireless or cellular connections.
• In described embodiments, thecomputing device101 may execute an application on behalf of a user of a client computing device. For example, thecomputing device101 may execute a virtual machine, which provides an execution session within which applications execute on behalf of a user or a client computing device, such as a hosted desktop session. Thecomputing device101 may also execute a terminal services session to provide a hosted desktop environment. Thecomputing device101 may provide access to a computing environment including one or more of: one or more applications, one or more desktop applications, and one or more desktop sessions in which one or more applications may execute.
• Additional details of the implementation and operation of network environment,computer101 and client and server computers may be as described in U.S. Pat. No. 9,538,345, issued Jan. 3, 2017 to Citrix Systems, Inc. of Fort Lauderdale, Fla., the teachings of which are hereby incorporated herein by reference.
B. Systems and Methods for an Embedded Browser
• The present disclosure is directed towards systems and methods of an embedded browser. A client application executing on a client device can allow a user to access applications (apps) that are served from and/or hosted on one or more servers, such as web applications and software-as-a-service (SaaS) applications (hereafter sometimes generally referred to as network applications). A browser that is embedded or integrated with the client application can render to the user a network application that is accessed or requested via the client application, and can enable interactivity between the user and the network application. The browser is sometimes referred to as an embedded browser, and the client application with embedded browser (CEB) is sometimes referred to as a workspace application. The client application can establish a secure connection to the one or more servers to provide an application session for the user to access the network application using the client device and the embedded browser. The embedded browser can be integrated with the client application to ensure that traffic related to the network application is routed through and/or processed in the client application, which can provide the client application with real-time visibility to the traffic (e.g., when decrypted through the client application), and user interactions and behavior. The embedded browser can provide a seamless experience to a user as the network application is requested via the user interface (shared by the client application and the embedded browser) and rendered through the embedded browser within the same user interface.
• The client application can terminate one end of a secured connection established with a server of a network application, such as a secure sockets layer (SSL) virtual private network (VPN) connection. The client application can receive encrypted traffic from the network application, and can decrypt the traffic before further processing (e.g., rendering by the embedded browser). The client application can monitor the received traffic (e.g., in encrypted packet form), and also have full visibility into the decrypted data stream and/or the SSL stack. This visibility can allow the client application to perform or facilitate policy-based management (e.g., including data loss prevention (DLP) capabilities), application control (e.g., to improve performance, service level), and collection and production of analytics. For instance, the local CEB can provide an information technology (IT) administrator with a controlled system for deploying web and SaaS applications through the CEB, and allow the IT administrator to set policies or configurations via the CEB for performing any of the forgoing activities.
• Many web and SaaS delivered applications connect from web servers to generic browsers (e.g., Internet Explorer, Firefox, and so on) of users. Once authenticated, the entire session of such a network application is encrypted. However, in this scenario, an administrator may not have visibility, analytics, or control of the content entering the network application from the user's digital workspace, or the content leaving the network application and entering the user's digital workspace. Moreover, content of a network application viewed in a generic browser can be copied or downloaded (e.g., by a user or program) to potentially any arbitrary application or device, resulting in a possible breach in data security.
• This present systems and methods can ensure that traffic associated with a network application is channeled through a CEB. By way of illustration, when a user accesses a SaaS web service with security assertion markup language (SAML) enabled for instance, the corresponding access request can be forwarded to a designated gateway service that determines, checks or verifies if the CEB was used to make the access request. Responsive to determining that a CEB was used to make the access request, the gateway service can perform or provide authentication and single-sign-on (SSO), and can allow the CEB to connect directly to the SaaS web service. Encryption (e.g., standard encryption) can be used for the application session between the CEB and the SaaS web service. When the content from the web service is unencrypted in the CEB to the viewed via the embedded browser, and/or when input is entered via the CEB, the CEB can provide added services on selective application-related information for control and analytics for instance. For example, an analytics agent or application programming interface (API) can be embedded in the CEB to provide or perform the added services.
• The CEB (sometimes referred to as workspace application or receiver) can interoperate with one or more gateway services, intermediaries and/or network servers (sometimes collectively referred to as cloud services or Citrix Cloud) to provide access to a network application. Features and elements of an environment related to the operation of an embodiment of cloud services are described below.
• FIG.2 illustrates an embodiment of cloud services for use in accessing resources including network applications. The cloud services can include an enterprise mobilitytechnical architecture200, which can include anaccess gateway260 in one illustrative embodiment. The architecture can be used in a bring-your-own-device (BYOD) environment for instance. The architecture can enable a user of a client device202 (e.g., a mobile or other device) to both access enterprise or personal resources from a client device202, and use the client device202 for personal use. The user may accesssuch enterprise resources204 orenterprise services208 via a client application executing on the client device202. The user may accesssuch enterprise resources204 orenterprise services208 using a client device202 that is purchased by the user or a client device202 that is provided by the enterprise to user. The user may utilize the client device202 for business use only or for business and personal use. The client device may run an iOS operating system, and Android operating system, or the like. The enterprise may choose to implement policies to manage the client device202. The policies may be implanted through a firewall or gateway in such a way that the client device may be identified, secured or security verified, and provided selective or full access to the enterprise resources. The policies may be client device management policies, mobile application management policies, mobile data management policies, or some combination of client device, application, and data management policies. A client device202 that is managed through the application of client device management policies may be referred to as an enrolled device. The client device management policies can be applied via the client application for instance.
• In some embodiments, the operating system of the client device may be separated into a managedpartition210 and anunmanaged partition212. The managedpartition210 may have policies applied to it to secure the applications running on and data stored in the managed partition. The applications running on the managed partition may be secure applications. In other embodiments, all applications may execute in accordance with a set of one or more policy files received separate from the application, and which define one or more security parameters, features, resource restrictions, and/or other access controls that are enforced by the client device management system when that application is executing on the device. By operating in accordance with their respective policy file(s), each application may be allowed or restricted from communications with one or more other applications and/or resources, thereby creating a virtual partition. Thus, as used herein, a partition may refer to a physically partitioned portion of memory (physical partition), a logically partitioned portion of memory (logical partition), and/or a virtual partition created as a result of enforcement of one or more policies and/or policy files across multiple apps as described herein (virtual partition). Stated differently, by enforcing policies on managed apps, those apps may be restricted to only be able to communicate with other managed apps and trusted enterprise resources, thereby creating a virtual partition that is not accessible by unmanaged apps and devices.
• The secure applications may be email applications, web browsing applications, software-as-a-service (SaaS) access applications, Windows Application access applications, and the like. The client application can include asecure application launcher218. The secure applications may be securenative applications214, secureremote applications222 executed by thesecure application launcher218,virtualization applications226 executed by thesecure application launcher218, and the like. The securenative applications214 may be wrapped by asecure application wrapper220. Thesecure application wrapper220 may include integrated policies that are executed on the client device202 when the secure native application is executed on the device. Thesecure application wrapper220 may include meta-data that points the securenative application214 running on the client device202 to the resources hosted at the enterprise that the securenative application214 may require to complete the task requested upon execution of the securenative application214. The secureremote applications222 executed by asecure application launcher218 may be executed within the secureapplication launcher application218. Thevirtualization applications226 executed by asecure application launcher218 may utilize resources on the client device202, at theenterprise resources204, and the like. The resources used on the client device202 by thevirtualization applications226 executed by asecure application launcher218 may include user interaction resources, processing resources, and the like. The user interaction resources may be used to collect and transmit keyboard input, mouse input, camera input, tactile input, audio input, visual input, gesture input, and the like. The processing resources may be used to present a user interface, process data received from theenterprise resources204, and the like. The resources used at theenterprise resources204 by thevirtualization applications226 executed by asecure application launcher218 may include user interface generation resources, processing resources, and the like. The user interface generation resources may be used to assemble a user interface, modify a user interface, refresh a user interface, and the like. The processing resources may be used to create information, read information, update information, delete information, and the like. For example, the virtualization application may record user interactions associated with a graphical user interface (GUI) and communicate them to a server application where the server application may use the user interaction data as an input to the application operating on the server. In this arrangement, an enterprise may elect to maintain the application on the server side as well as data, files, etc., associated with the application. While an enterprise may elect to “mobilize” some applications in accordance with the principles herein by securing them for deployment on the client device (e.g., via the client application), this arrangement may also be elected for certain applications. For example, while some applications may be secured for use on the client device, others might not be prepared or appropriate for deployment on the client device so the enterprise may elect to provide the mobile user access to the unprepared applications through virtualization techniques. As another example, the enterprise may have large complex applications with large and complex data sets (e.g., material resource planning applications) where it would be very difficult, or otherwise undesirable, to customize the application for the client device so the enterprise may elect to provide access to the application through virtualization techniques. As yet another example, the enterprise may have an application that maintains highly secured data (e.g., human resources data, customer data, engineering data) that may be deemed by the enterprise as too sensitive for even the secured mobile environment so the enterprise may elect to use virtualization techniques to permit mobile access to such applications and data. An enterprise may elect to provide both fully secured and fully functional applications on the client device. The enterprise can use a client application, which can include a virtualization application, to allow access to applications that are deemed more properly operated on the server side. In an embodiment, the virtualization application may store some data, files, etc., on the mobile phone in one of the secure storage locations. An enterprise, for example, may elect to allow certain information to be stored on the phone while not permitting other information.
• In connection with the virtualization application, as described herein, the client device may have a virtualization application that is designed to present GUIs and then record user interactions with the GUI. The virtualization application may communicate the user interactions to the server side to be used by the server side application as user interactions with the application. In response, the application on the server side may transmit back to the client device a new GUI. For example, the new GUI may be a static page, a dynamic page, an animation, or the like, thereby providing access to remotely located resources.
• The secure applications may access data stored in asecure data container228 in the managedpartition210 of the client device. The data secured in the secure data container may be accessed by the secure wrappedapplications214, applications executed by asecure application launcher222,virtualization applications226 executed by asecure application launcher218, and the like. The data stored in thesecure data container228 may include files, databases, and the like. The data stored in thesecure data container228 may include data restricted to a specificsecure application230, shared amongsecure applications232, and the like. Data restricted to a secure application may include securegeneral data234 and highly secure data238. Secure general data may use a strong form of encryption such as Advanced Encryption Standard (AES) 128-bit encryption or the like, while highly secure data238 may use a very strong form of encryption such as AES 256-bit encryption. Data stored in thesecure data container228 may be deleted from the device upon receipt of a command from thedevice manager224. The secure applications may have a dual-mode option240. Thedual mode option240 may present the user with an option to operate the secured application in an unsecured or unmanaged mode. In an unsecured or unmanaged mode, the secure applications may access data stored in anunsecured data container242 on theunmanaged partition212 of the client device202. The data stored in an unsecured data container may bepersonal data244. The data stored in anunsecured data container242 may also be accessed by unsecured applications248 that are running on theunmanaged partition212 of the client device202. The data stored in anunsecured data container242 may remain on the client device202 when the data stored in thesecure data container228 is deleted from the client device202. An enterprise may want to delete from the client device selected or all data, files, and/or applications owned, licensed or controlled by the enterprise (enterprise data) while leaving or otherwise preserving personal data, files, and/or applications owned, licensed or controlled by the user (personal data). This operation may be referred to as a selective wipe. With the enterprise and personal data arranged in accordance to the aspects described herein, an enterprise may perform a selective wipe.
• The client device202 may connect toenterprise resources204 andenterprise services208 at an enterprise, to the public Internet248, and the like. The client device may connect toenterprise resources204 andenterprise services208 through virtual private network connections. The virtual private network connections, also referred to as microVPN or application-specific VPN, may be specific to particular applications (e.g., as illustrated by microVPNs250), particular devices, particular secured areas on the client device (e.g., as illustrated by0/S VPN252), and the like. For example, each of the wrapped applications in the secured area of the phone may access enterprise resources through an application specific VPN such that access to the VPN would be granted based on attributes associated with the application, possibly in conjunction with user or device attribute information. The virtual private network connections may carry Microsoft Exchange traffic, Microsoft Active Directory traffic, HyperText Transfer Protocol (HTTP) traffic, HyperText Transfer Protocol Secure (HTTPS) traffic, application management traffic, and the like. The virtual private network connections may support and enable single-sign-on authentication processes254. The single-sign-on processes may allow a user to provide a single set of authentication credentials, which are then verified by anauthentication service258. Theauthentication service258 may then grant to the user access tomultiple enterprise resources204, without requiring the user to provide authentication credentials to eachindividual enterprise resource204.
• The virtual private network connections may be established and managed by anaccess gateway260. Theaccess gateway260 may include performance enhancement features that manage, accelerate, and improve the delivery ofenterprise resources204 to the client device202. The access gateway may also re-route traffic from the client device202 to the public Internet248, enabling the client device202 to access publicly available and unsecured applications that run on the public Internet248. The client device may connect to the access gateway via atransport network262. Thetransport network262 may use one or more transport protocols and may be a wired network, wireless network, cloud network, local area network, metropolitan area network, wide area network, public network, private network, and the like.
• Theenterprise resources204 may include email servers, file sharing servers, SaaS/Web applications, Web application servers, Windows application servers, and the like. Email servers may include Exchange servers, Lotus Notes servers, and the like. File sharing servers may include ShareFile servers, and the like. SaaS applications may include Salesforce, and the like. Windows application servers may include any application server that is built to provide applications that are intended to run on a local Windows operating system, and the like. Theenterprise resources204 may be premise-based resources, cloud based resources, and the like. Theenterprise resources204 may be accessed by the client device202 directly or through theaccess gateway260. Theenterprise resources204 may be accessed by the client device202 via atransport network262. Thetransport network262 may be a wired network, wireless network, cloud network, local area network, metropolitan area network, wide area network, public network, private network, and the like.
• Cloud services can include anaccess gateway260 and/orenterprise services208. The enterprise services208 may includeauthentication services258,threat detection services264,device manager services224,file sharing services268,policy manager services270,social integration services272,application controller services274, and the like.Authentication services258 may include user authentication services, device authentication services, application authentication services, data authentication services and the like.Authentication services258 may use certificates. The certificates may be stored on the client device202, by theenterprise resources204, and the like. The certificates stored on the client device202 may be stored in an encrypted location on the client device, the certificate may be temporarily stored on the client device202 for use at the time of authentication, and the like.Threat detection services264 may include intrusion detection services, unauthorized access attempt detection services, and the like. Unauthorized access attempt detection services may include unauthorized attempts to access devices, applications, data, and the like.Device management services224 may include configuration, provisioning, security, support, monitoring, reporting, and decommissioning services.File sharing services268 may include file management services, file storage services, file collaboration services, and the like.Policy manager services270 may include device policy manager services, application policy manager services, data policy manager services, and the like.Social integration services272 may include contact integration services, collaboration services, integration with social networks such as Facebook, Twitter, and LinkedIn, and the like.Application controller services274 may include management services, provisioning services, deployment services, assignment services, revocation services, wrapping services, and the like.
• The enterprise mobilitytechnical architecture200 may include anapplication store278. Theapplication store278 may include unwrapped applications280,pre-wrapped applications282, and the like. Applications may be populated in theapplication store278 from theapplication controller274. Theapplication store278 may be accessed by the client device202 through theaccess gateway260, through the public Internet248, or the like. The application store may be provided with an intuitive and easy to use User Interface.
• Asoftware development kit284 may provide a user the capability to secure applications selected by the user by providing a secure wrapper around the application. An application that has been wrapped using thesoftware development kit284 may then be made available to the client device202 by populating it in theapplication store278 using theapplication controller274.
• The enterprise mobilitytechnical architecture200 may include a management and analytics capability. The management and analytics capability may provide information related to how resources are used, how often resources are used, and the like. Resources may include devices, applications, data, and the like. How resources are used may include which devices download which applications, which applications access which data, and the like. How often resources are used may include how often an application has been downloaded, how many times a specific set of data has been accessed by an application, and the like.
• FIG.3 depicts is an illustrative embodiment of an enterprisemobility management system300. Some of the components of themobility management system200 described above with reference toFIG.2 have been omitted for the sake of simplicity. The architecture of thesystem300 depicted inFIG.3 is similar in many respects to the architecture of thesystem200 described above with reference toFIG.2 and may include additional features not mentioned above.
• In this case, the left hand side represents an enrolledclient device302 with aclient agent304, which interacts withgateway server306 to accessvarious enterprise resources308 andservices309 such as Web or SasS applications, Exchange, Sharepoint, public-key infrastructure (PKI) Resources, Kerberos Resources, Certificate Issuance service, as shown on the right hand side above. Thegateway server306 can include embodiments of features and functionalities of the cloud services, such asaccess gateway260 and application controller functionality. Although not specifically shown, theclient agent304 may be part of, and/or interact with the client application which can operate as an enterprise application store (storefront) for the selection and/or downloading of network applications.
• Theclient agent304 can act as a UI (user interface) intermediary for Windows apps/desktops hosted in an Enterprise data center, which are accessed using the High-Definition User Experience (HDX) or Independent Computing Architecture (ICA) display remoting protocol. Theclient agent304 can also support the installation and management of native applications on theclient device302, such as native iOS or Android applications. For example, the managed applications310 (mail, browser, wrapped application) shown in the figure above are native applications that execute locally on the device.Client agent304 and application management framework of this architecture act to provide policy driven management capabilities and features such as connectivity and SSO (single sign on) to enterprise resources/services308. Theclient agent304 handles primary user authentication to the enterprise, for instance to access gateway (AG) with SSO to other gateway server components. Theclient agent304 obtains policies fromgateway server306 to control the behavior of the managedapplications310 on theclient device302.
• The Secure interprocess communication (IPC) links312 between thenative applications310 andclient agent304 represent a management channel, which allows client agent to supply policies to be enforced by theapplication management framework314 “wrapping” each application. TheIPC channel312 also allowsclient agent304 to supply credential and authentication information that enables connectivity and SSO toenterprise resources308. Finally theIPC channel312 allows theapplication management framework314 to invoke user interface functions implemented byclient agent304, such as online and offline authentication.
• Communications between theclient agent304 andgateway server306 are essentially an extension of the management channel from theapplication management framework314 wrapping each native managedapplication310. Theapplication management framework314 requests policy information fromclient agent304, which in turn requests it fromgateway server306. Theapplication management framework314 requests authentication, andclient agent304 logs into the gateway services part of gateway server306 (also known as NetScaler access gateway).Client agent304 may also call supporting services ongateway server306, which may produce input material to derive encryption keys for the local data vaults316, or provide client certificates which may enable direct authentication to PKI protected resources, as more fully explained below.
• In more detail, theapplication management framework314 “wraps” each managedapplication310. This may be incorporated via an explicit build step, or via a post-build processing step. Theapplication management framework314 may “pair” withclient agent304 on first launch of anapplication310 to initialize the Secure IPC channel and obtain the policy for that application. Theapplication management framework314 may enforce relevant portions of the policy that apply locally, such as the client agent login dependencies and some of the containment policies that restrict how local OS services may be used, or how they may interact with theapplication310.
• Theapplication management framework314 may use services provided byclient agent304 over theSecure IPC channel312 to facilitate authentication and internal network access. Key management for the private and shared data vaults316 (containers) may be also managed by appropriate interactions between the managedapplications310 andclient agent304.Vaults316 may be available only after online authentication, or may be made available after offline authentication if allowed by policy. First use ofvaults316 may require online authentication, and offline access may be limited to at most the policy refresh period before online authentication is again required.
• Network access to internal resources may occur directly from individual managedapplications310 throughaccess gateway306. Theapplication management framework314 is responsible for orchestrating the network access on behalf of eachapplication310.Client agent304 may facilitate these network connections by providing suitable time limited secondary credentials obtained following online authentication. Multiple modes of network connection may be used, such as reverse web proxy connections and end-to-end VPN-style tunnels318.
• The Mail and Browser managedapplications310 can have special status and may make use of facilities that might not be generally available to arbitrary wrapped applications. For example, the Mail application may use a special background network access mechanism that allows it to access Exchange over an extended period of time without requiring a full AG logon. The Browser application may use multiple private data vaults to segregate different kinds of data.
• This architecture can support the incorporation of various other security features. For example, gateway server306 (including its gateway services) in some cases might not need to validate active directory (AD) passwords. It can be left to the discretion of an enterprise whether an AD password is used as an authentication factor for some users in some situations. Different authentication methods may be used if a user is online or offline (i.e., connected or not connected to a network).
• Step up authentication is a feature whereingateway server306 may identify managednative applications310 that are allowed to have access to more sensitive data using strong authentication, and ensure that access to these applications is only permitted after performing appropriate authentication, even if this means a re-authentication is requested from the user after a prior weaker level of login.
• Another security feature of this solution is the encryption of the data vaults316 (containers) on theclient device302. Thevaults316 may be encrypted so that all on-device data including clipboard/cache data, files, databases, and configurations are protected. For on-line vaults, the keys may be stored on the server (gateway server306), and for off-line vaults, a local copy of the keys may be protected by a user password or biometric validation. When data is stored locally on thedevice302 in thesecure container316, it is preferred that a minimum of AES256 encryption algorithm be utilized.
• Other secure container features may also be implemented. For example, a logging feature may be included, wherein all security events happening inside anapplication310 are logged and reported to the backend. Data wiping may be supported, such as if theapplication310 detects tampering, associated encryption keys may be written over with random data, leaving no hint on the file system that user data was destroyed. Screenshot protection is another feature, where an application may prevent any data from being stored in screenshots. For example, the key window's hidden property may be set to YES. This may cause whatever content is currently displayed on the screen to be hidden, resulting in a blank screenshot where any content would normally reside.
• Local data transfer may be prevented, such as by preventing any data from being locally transferred outside the application container, e.g., by copying it or sending it to an external application. A keyboard cache feature may operate to disable the autocorrect functionality for sensitive text fields. SSL certificate validation may be operable so the application specifically validates the server SSL certificate instead of it being stored in the keychain. An encryption key generation feature may be used such that the key used to encrypt data on the device is generated using a passphrase or biometric data supplied by the user (if offline access is required). It may be XORed with another key randomly generated and stored on the server side if offline access is not required. Key Derivation functions may operate such that keys generated from the user password use KDFs (key derivation functions, notably Password-Based Key Derivation Function 2 (PBKDF2)) rather than creating a cryptographic hash of it. The latter makes a key susceptible to brute force or dictionary attacks.
• Further, one or more initialization vectors may be used in encryption methods. An initialization vector might cause multiple copies of the same encrypted data to yield different cipher text output, preventing both replay and cryptanalytic attacks. This may also prevent an attacker from decrypting any data even with a stolen encryption key. Further, authentication then decryption may be used, wherein application data is decrypted only after the user has authenticated within the application. Another feature may relate to sensitive data in memory, which may be kept in memory (and not in disk) only when it's needed. For example, login credentials may be wiped from memory after login, and encryption keys and other data inside objective-C instance variables are not stored, as they may be easily referenced. Instead, memory may be manually allocated for these.
• An inactivity timeout may be implemented via the CEB, wherein after a policy-defined period of inactivity, a user session is terminated.
• Data leakage from theapplication management framework314 may be prevented in other ways. For example, when anapplication310 is put in the background, the memory may be cleared after a predetermined (configurable) time period. When backgrounded, a snapshot may be taken of the last displayed screen of the application to fasten the foregrounding process. The screenshot may contain confidential data and hence should be cleared.
• Another security feature relates to the use of an OTP (one time password)320 without the use of an AD (active directory)322 password for access to one or more applications. In some cases, some users do not know (or are not permitted to know) their AD password, so these users may authenticate using anOTP320 such as by using a hardware OTP system like SecurID (OTPs may be provided by different vendors also, such as Entrust or Gemalto). In some cases, after a user authenticates with a user ID, a text is sent to the user with anOTP320. In some cases, this may be implemented only for online use, with a prompt being a single field.
• An offline password may be implemented for offline authentication for thoseapplications310 for which offline use is permitted via enterprise policy. For example, an enterprise may want storefront to be accessed in this manner. In this case, theclient agent304 may require the user to set a custom offline password and the AD password is not used.Gateway server306 may provide policies to control and enforce password standards with respect to the minimum length, character class composition, and age of passwords, such as described by the standard Windows Server password complexity requirements, although these requirements may be modified.
• Another feature relates to the enablement of a client side certificate forcertain applications310 as secondary credentials (for the purpose of accessing PKI protected web resources via the application management framework micro VPN feature). For example, an application may utilize such a certificate. In this case, certificate-based authentication using ActiveSync protocol may be supported, wherein a certificate from theclient agent304 may be retrieved bygateway server306 and used in a keychain. Each managed application may have one associated client certificate, identified by a label that is defined ingateway server306.
• Gateway server306 may interact with an Enterprise special purpose web service to support the issuance of client certificates to allow relevant managed applications to authenticate to internal PKI protected resources.
• Theclient agent304 and theapplication management framework314 may be enhanced to support obtaining and using client certificates for authentication to internal PKI protected network resources. More than one certificate may be supported, such as to match various levels of security and/or separation requirements. The certificates may be used by the Mail and Browser managed applications, and ultimately by arbitrary wrapped applications (provided those applications use web service style communication patterns where it is reasonable for the application management framework to mediate https requests).
• Application management client certificate support on iOS may rely on importing a public-key cryptography standards (PKCS) 12 BLOB (Binary Large Object) into the iOS keychain in each managed application for each period of use. Application management framework client certificate support may use a HTTPS implementation with private in-memory key storage. The client certificate might never be present in the iOS keychain and might not be persisted except potentially in “online-only” data value that is strongly protected.
• Mutual SSL or TLS may also be implemented to provide additional security by requiring that aclient device302 is authenticated to the enterprise, and vice versa. Virtual smart cards for authentication togateway server306 may also be implemented.
• Both limited and full Kerberos support may be additional features. The full support feature relates to an ability to do full Kerberos login to Active Directory (AD)322, using an AD password or trusted client certificate, and obtain Kerberos service tickets to respond to HTTP Negotiate authentication challenges. The limited support feature relates to constrained delegation in Citrix Access Gateway Enterprise Edition (AGEE), where AGEE supports invoking Kerberos protocol transition so it can obtain and use Kerberos service tickets (subject to constrained delegation) in response to HTTP Negotiate authentication challenges. This mechanism works in reverse web proxy (aka corporate virtual private network (CVPN)) mode, and when http (but not https) connections are proxied in VPN and MicroVPN mode.
• Another feature relates to application container locking and wiping, which may automatically occur upon jail-break or rooting detections, and occur as a pushed command from administration console, and may include a remote wipe functionality even when anapplication310 is not running.
• A multi-site architecture or configuration of enterprise application store and an application controller may be supported that allows users to be service from one of several different locations in case of failure.
• In some cases, managedapplications310 may be allowed to access a certificate and private key via an API (example OpenSSL). Trusted managedapplications310 of an enterprise may be allowed to perform specific Public Key operations with an application's client certificate and private key. Various use cases may be identified and treated accordingly, such as when an application behaves like a browser and no certificate access is used, when an application reads a certificate for “who am I,” when an application uses the certificate to build a secure session token, and when an application uses private keys for digital signing of important data (e.g., transaction log) or for temporary data encryption.
• Referring now toFIG.4, depicted is a block diagram of asystem400 of an embedded browser. In brief overview, thesystem400 may include aclient device402 with a digital workspace for a user, aclient application404,cloud services408 operating on at least onenetwork device432, andnetwork applications406 served from and/or hosted on one ormore servers430. Theclient application404 can for instance include at least one of: an embeddedbrowser410, anetworking agent412, acloud services agent414, aremote session agent416, or asecure container418. Thecloud services408 can for instance include at least one of: secure browser(s)420, an access gateway422 (or CIS, e.g., for registering and/or authenticating the client application and/or user), or analytics services424 (or CAS, e.g., for receiving information from the client application for analytics). Thenetwork applications406 can include sanctionedapplications426 andnon-sanctioned applications428.
• Each of the above-mentioned elements or entities is implemented in hardware, or a combination of hardware and software, in one or more embodiments. Each component of thesystem400 may be implemented using hardware or a combination of hardware or software detailed above in connection withFIG.1. For instance, each of these elements or entities can include any application, program, library, script, task, service, process or any type and form of executable instructions executing on hardware of theclient device402, the at least onenetwork device432 and/or the one ormore servers430. The hardware includes circuitry such as one or more processors in one or more embodiments. For example, the at least onenetwork device432 and/or the one ormore servers430 can include any of the elements of a computing device described above in connection with at leastFIG.1 for instance.
• Theclient device402 can include any embodiment of a computing device described above in connection with at leastFIG.1 for instance. Theclient device402 can include any user device such as a desktop computer, a laptop computer, a tablet device, a smart phone, or any other mobile or personal device. Theclient device402 can include a digital workspace of a user, which can include file system(s), cache or memory (e.g., including electronic clipboard(s)), container(s), application(s) and/or other resources on theclient device402. The digital workspace can include or extend to one or more networks accessible by theclient device402, such as an intranet and the Internet, including file system(s) and/or other resources accessible via the one or more networks. A portion of the digital workspace can be secured via the use of theclient application404 with embedded browser410 (CEB) for instance. The secure portion of the digital workspace can include for instance file system(s), cache or memory (e.g., including electronic clipboard(s)), application(s), container(s) and/or other resources allocated to the CEB, and/or allocated by the CEB to network application(s)406 accessed via the CEB. The secure portion of the digital workspace can also include resources specified by the CEB (via one or more policies) for inclusion in the secure portion of the digital workspace (e.g., a particular local application can be specified via a policy to be allowed to receive data obtained from a network application).
• Theclient application404 can include one or more components, such as an embeddedbrowser410, anetworking agent412, a cloud services agent414 (sometimes referred to as management agent), a remote session agent416 (sometimes referred to as HDX engine), and/or a secure container418 (sometimes referred to as secure cache container). One or more of the components can be installed as part of a software build or release of theclient application404 or CEB, or separately acquired or downloaded and installed/integrated into an existing installation of theclient application404 or CEB for instance. For instance, the client device may download or otherwise receive the client application404 (or any component) from the network device(s)432. In some embodiments, the client device may send a request for theclient application404 to the network device(s)432. For example, a user of the client device can initiate a request, download and/or installation of the client application. The network device(s)432 in turn may send the client application to the client device. In some embodiments, the network device(s)432 may send a setup or installation application for the client application to the client device. Upon receipt, the client device may install the client application onto a hard disk of the client device. In some embodiments, the client device may run the setup application to unpack or decompress a package of the client application. In some embodiments, the client application may be an extension (e.g., an add-on, an add-in, an applet or a plug-in) to another application (e.g., a networking agent412) installed on the client device. The client device may install the client application to interface or inter-operate with the pre-installed application. In some embodiments, the client application may be a standalone application. The client device may install the client application to execute as a separate process.
• The embeddedbrowser410 can include elements and functionalities of a web browser application or engine. The embeddedbrowser410 can locally render network application(s) as a component or extension of the client application. For instance, the embeddedbrowser410 can render a SaaS/Web application inside the CEB which can provide the CEB with full visibility and control of the application session. The embedded browser can be embedded or incorporated into the client application via any means, such as direct integration (e.g., programming language or script insertion) into the executable code of the client application, or via plugin installation. For example, the embedded browser can include a Chromium based browser engine or other type of browser engine, that can be embedded into the client application, using the Chromium embedded framework (CEF) for instance. The embedded browser can include a HTML5-based layout graphical user interface (GUI). The embedded browser can provide HTML rendering and JavaScript support to a client application incorporating various programming languages. For example, elements of the embedded browser can bind to a client application incorporating C, C++, Delphi, Go, Java, .NET/Mono, Visual Basic 6.0, and/or Python.
• In some embodiments, the embedded browser comprises a plug-in installed on the client application. For example, the plug-in can include one or more components. One such components can be an ActiveX control or Java control or any other type and/or form of executable instructions capable of loading into and executing in the client application. For example, the client application can load and run an Active X control of the embedded browser, such as in a memory space or context of the client application. In some embodiments, the embedded browser can be installed as an extension on the client application, and a user can choose to enable or disable the plugin or extension. The embedded browser (e.g., via the plugin or extension) can form or operate as a secured browser for securing, using and/or accessing resources within the secured portion of the digital workspace.
• The embedded browser can incorporate code and functionalities beyond that available or possible in a standard or typical browser. For instance, the embedded browser can bind with or be assigned with asecured container418, to define at least part of the secured portion of a user's digital workspace. The embedded browser can bind with or be assigned with a portion of the client device's cache to form a secured clipboard (e.g., local to the client device, or extendable to other devices), that can be at least part of thesecured container418. The embedded browser can be integrated with the client application to ensure that traffic related to network applications is routed through and/or processed in the client application, which can provide the client application with real-time visibility to the traffic (e.g., when decrypted through the client application). This visibility to the traffic can allow the client application to perform or facilitate policy-based management (e.g., including data loss prevention (DLP) capabilities), application control, and collection and production of analytics.
• In some embodiments, the embedded browser incorporates one or more other components of theclient application404, such as thecloud services agent414,remote session agent416 and/orsecure container418. For instance, a user can use thecloud services agent414 of the embedded browser to interoperate with the access gateway422 (sometimes referred to as CIS) to access a network application. For example, thecloud services agent414 can execute within the embedded browser, and can receive and transmit navigation commands from the embedded browser to a hosted network application. The cloud services agent can use a remote presentation protocol to display the output generated by the network application to the embedded browser. For example, thecloud services agent414 can include a HTML5 web client that allows end users to access remote desktops and/or applications on the embedded browser.
• Theclient application404 and CEB operate on the application layer of the operational (OSI) stack of the client device. Theclient application404 can include and/or execute one or more agents that interoperate with the cloud services408. Theclient application404 can receive, obtain, retrieve or otherwise access various policies (e.g., an enterprise's custom, specified or internal policies or rules) and/or data (e.g., from anaccess gateway422 and/or network device(s) ofcloud services408, or other server(s), that may be managed by the enterprise). The client application can access the policies and/or data to control and/or manage a network application (e.g., a SaaS, web or remote-hosted application). Control and/or management of a network application can include control and/or management of various aspects of the network application, such as access control, session delivery, available features or functions, service level, traffic management and monitoring, and so on. The network application can be from a provider or vendor of the enterprise (e.g., salesforce.com, SAP, Microsoft Office365), from the enterprise itself, or from another entity (e.g., Dropbox or Gmail service).
• For example, thecloud services agent414 can provide policy driven management capabilities and features related to the use and/or access of network applications. For example, thecloud services agent414 can include a policy engine to apply one or more policies (e.g., received from cloud services) to determine access control and/or connectivity to resources such as network applications. When a session is established between the client application and aserver430 providing a SaaS application for instance, thecloud services agent414 can apply one or more policies to control traffic levels and/or traffic types (or other aspects) of the session, for instance to manage a service level of the SaaS application. Additional aspects of the application traffic that can be controlled or managed can include encryption level and/or encryption type applied to the traffic, level of interactivity allowed for a user, limited access to certain features of the network application (e.g., print-screen, save, edit or copy functions), restrictions to use or transfer of data obtained from the network application, limit concurrent access to two or more network applications, limit access to certain file repositories or other resources, and so on.
• Thecloud services agent414 can convey or feed information toanalytics services424 of thecloud services408, such as information about SaaS interaction events visible to the CEB. Such a configuration using the CEB can monitor or capture information for analytics without having an inline device or proxy located between the client device and the server(s)430, or using a SaaS API gateway ‘out-of-band’ approach. In some embodiments, thecloud services agent414 does not execute within the embedded browser. In these embodiments, a user can similarly use thecloud services agent414 to interoperate with the access gateway (or CIS)422 to access a network application. For instance, thecloud services agent414 can register and/or authenticate with the access gateway (or CIS)422, and can obtain a list of the network applications from the access gateway (or CIS)422. Thecloud services agent414 can include and/or operate as an application store (or storefront) for user selection and/or downloading of network applications. Upon logging in to access a network application, thecloud services agent414 can intercept and transmit navigation commands from the embedded browser to the network application. The cloud services agent can use a remote presentation protocol to display the output generated by the network application to the embedded browser. For example, thecloud services agent414 can include a HTML5 web client that allows end users to access remote desktops and/or applications on the embedded browser.
• In some embodiments, thecloud services agent414 provides single sign on (SSO) capability for the user and/or client device to access a plurality of network applications. Thecloud services agent414 can perform user authentication to access network applications as well as other network resources and services, by communicating with theaccess gateway422 for instance. For example, thecloud services agent414 can authenticate or register with theaccess gateway422, to access other components of thecloud services408 and/or thenetwork applications406. Responsive to the authentication or registration, theaccess gateway422 can perform authentication and/or SSO for (or on behalf of) the user and/or client application, with the network applications.
• Theclient application404 can include anetworking agent412. Thenetworking agent412 is sometimes referred to as a software-defined wide area network (SD-WAN) agent, mVPN agent, or microVPN agent. Thenetworking agent412 can establish or facilitate establishment of a network connection between the client application and one or more resources (e.g.,server430 serving a network application). Thenetworking agent412 can perform handshaking for a requested connection from the client application to access a network application, and can establish the requested connection (e.g., secure or encrypted connection). Thenetworking agent412 can connect to enterprise resources (including services) for instance via a virtual private network (VPN). For example, thenetworking agent412 can establish a secure socket layer (SSL) VPN between the client application and aserver430 providing thenetwork application406. The VPN connections, sometimes referred to as microVPN or application-specific VPN, may be specific to particular network applications, particular devices, particular secured areas on the client device, and the like, for instance as discussed above in connection withFIG.3. Such VPN connections can carry Microsoft Exchange traffic, Microsoft Active Directory traffic, HyperText Transfer Protocol (HTTP) traffic, HyperText Transfer Protocol Secure (HTTPS) traffic, as some examples.
• The remote session agent416 (sometimes referred to as HDX engine) can include features of theclient agent304 discussed above in connection withFIG.2 for instance, to support display a remoting protocol (e.g., HDX or ICA). In some embodiments, theremote session agent416 can establish a remote desktop session and/or remote application session in accordance to any variety of protocols, such as the Remote Desktop Protocol (RDP), Appliance Link Protocol (ALP), Remote Frame Buffer (RFB) Protocol, and ICA Protocol. For example, theremote session agent416 can establish a remote application session for a user of the client device to access an enterprise network application. Theremote session agent416 can establish the remote application session within or over a secure connection (e.g., a VPN) established by thenetworking agent412 for instance.
• The client application or CEB can include or be associated with asecure container418. A secure container can include a logical or virtual delineation of one or more types of resources accessible within the client device and/or accessible by the client device. For example, thesecure container418 can refer to the entirety of the secured portion of the digital workspace, or particular aspect(s) of the secured portion. In some embodiments, thesecure container418 corresponds to a secure cache (e.g., electronic or virtual clipboard), and can dynamically incorporate a portion of a local cache of each client device of a user, and/or a cloud-based cache of the user, that is protected or secured (e.g., encrypted). The secure container can define a portion of file system(s), and/or delineate resources allocated to a CEB and/or to network applications accessed via the CEB. The secure container can include elements of thesecure data container228 discussed above in connection withFIG.2 for example. The CEB can be configured (e.g., via policies) to limit, disallow or disable certain actions or activities on resources and/or data identified to be within a secure container. A secured container can be defined to specify that the resources and/or data within the secure container are to be monitored for misuse, abuse and/or exfiltration.
• In certain embodiments, a secure container relates to or involves the use of a secure browser (e.g., embeddedbrowser410 or secure browser420) that implements various enterprise security features. Network applications (or web pages accessed by the secure browser) that are configured to run within the secure browser can effectively inherit the security mechanisms implemented by the secure browser. These network applications can be considered to be contained within the secure container. The use of such a secure browser can enable an enterprise to implement a content filtering policy in which, for example, employees are blocked from accessing certain web sites from their client devices. The secure browser can be used, for example, to enable client device users to access a corporate intranet without the need for a VPN.
• In some embodiments, a secure container can support various types of remedial actions for protecting enterprise resources. One such remedy is to lock the client device, or a secure container on the client device that stores data to be protected, such that the client device or secure container can only be unlocked with a valid code provided by an administrator for instance. In some embodiments, these and other types of remedies can be invoked automatically based on conditions detected on the client device (via the application of policies for instance), or can be remotely initiated by an administrator.
• In some embodiments, a secure container can include a secure document container for documents. A document can comprise any computer-readable file including text, audio, video, and/or other types of information or media. A document can comprise any single one or combination of these media types. As explained herein, the secure container can help prevent the spread of enterprise information to different applications and components of the client device, as well as to other devices. The enterprise system (which can be partially or entirely within a cloud network) can transmit documents to various devices, which can be stored within the secure container. The secure container can prevent unauthorized applications and other components of the client device from accessing information within the secure container. For enterprises that allow users to use their own client devices for accessing, storing, and using enterprise data, providing secure container on the client devices helps to secure the enterprise data. For instance, providing secure containers on the client devices can centralize enterprise data in one location on each client device, and can facilitate selective or complete deletion of enterprise data from each client device when desired.
• The secure container can include an application that implements a file system that stores documents and/or other types of files. The file system can comprise a portion of a computer-readable memory of the client device. The file system can be logically separated from other portions of the computer-readable memory of the client device. In this way, enterprise data can be stored in a secure container and private data can be stored in a separate portion of the computer-readable memory of the client device for instance. The secure container can allow the CEB, network applications accessed via the CEB, locally installed applications and/or other components of the client device to read from, write to, and/or delete information from the file system (if authorized to do so). Deleting data from the secure container can include deleting actual data stored in the secure container, deleting pointers to data stored in the secure container, deleting encryption keys used to decrypt data stored in the secure container, and the like. The secure container can be installed by, e.g., the client application, an administrator, or the client device manufacturer. The secure container can enable some or all of the enterprise data stored in the file system to be deleted without modifying private data stored on the client device outside of the secure container. The file system can facilitate selective or complete deletion of data from the file system. For example, an authorized component of the enterprise's system can delete data from the file system based on, e.g., encoded rules. In some embodiments, the client application can delete the data from the file system, in response to receiving a deletion command from the enterprise's system.
• The secure container can include an access manager that governs access to the file system by applications and other components of the client device. Access to the file system can be governed based on document access policies (e.g., encoded rules) maintained by the client application, in the documents and/or in the file system. A document access policy can limit access to the file system based on (1) which application or other component of the client device is requesting access, (2) which documents are being requested, (3) time or date, (4) geographical position of the client device, (5) whether the requesting application or other component provides a correct certificate or credentials, (6) whether the user of the client device provides correct credentials, (7) other conditions, or any combination thereof. A user's credentials can comprise, for example, a password, one or more answers to security questions (e.g., What is the mascot of your high school?), biometric information (e.g., fingerprint scan, eye-scan), and the like. Hence, by using the access manager, the secure container can be configured to be accessed only by applications that are authorized to access the secure container. As one example, the access manager can enable enterprise applications installed on the client device to access data stored in the secure container and to prevent non-enterprise applications from accessing the data stored in the secure container.
• Temporal and geographic restrictions on document access may be useful. For example, an administrator may deploy a document access policy that restricts the availability of the documents (stored within the secure container) to a specified time window and/or a geographic zone (e.g., as determined by a GPS chip) within which the client device must reside in order to access the documents. Further, the document access policy can instruct the secure container or client application to delete the documents from the secure container or otherwise make them unavailable when the specified time period expires or if the client device is taken outside of the defined geographic zone.
• Some documents can have access policies that forbid the document from being saved within the secure container. In such embodiments, the document can be available for viewing on the client device only when the user is logged in or authenticated via the cloud services for example.
• The access manager can also be configured to enforce certain modes of connectivity between remote devices (e.g., an enterprise resource or other enterprise server) and the secure container. For example, the access manager can require that documents received by the secure container from a remote device and/or sent from the secure container to the remote device be transmitted through secured tunnels/connections, for example. The access manager can require that all documents transmitted to and from the secure container be encrypted. The client application or access manager can be configured to encrypt documents sent from the secure container and decrypt documents sent to the secure container. Documents in the secure container can also be stored in an encrypted form.
• The secure container can be configured to prevent documents or data included within documents or the secure container from being used by unauthorized applications or components of the client device or other devices. For instance, a client device application having authorization to access documents from the secure container can be programmed to prevent a user from copying a document's data and pasting it into another file or application interface, or locally saving the document or document data as a new file outside of the secure container. Similarly, the secure container can include a document viewer and/or editor that do not permit such copy/paste and local save operations. Moreover, the access manager can be configured to prevent such copy/paste and local save operations. Further, the secure container and applications programmed and authorized to access documents from the secure container can be configured to prevent users from attaching such documents to emails or other forms of communication.
• One or more applications (e.g., applications installed on the client device, and/or network applications accessed via the CEB) can be programmed or controlled (e.g., via policy-based enforcement) to write enterprise-related data only into the secure container. For instance, an application's source code can be provided with the resource name of the secure container. Similarly, a remote application (e.g., executing on a device other than the client device) can be configured to send data or documents only to the secure container (as opposed to other components or memory locations of the client device). Storing data to the secure container can occur automatically, for example, under control of the application, the client application, and/or the secure browser. The client application can be programmed to encrypt or decrypt documents stored or to be stored within the secure container. In certain embodiments, the secure container can only be used by applications (on the client device or a remote device) that are programmed to identify and use the secure container, and which have authorization to do so.
• Thenetwork applications406 can include sanctionednetwork applications426 andnon-sanctioned network applications428. By way of a non-limiting example, sanctionednetwork applications426 can include network applications from Workday, Salesforce,Office365, SAP, and so on, whilenon-sanctioned network applications426 can include network applications from Dropbox, Gmail, and so on. For instance,FIG.4 illustrates a case where sanctionedapplications426 are accessed via a CEB. In operation (1), a user instance of aclient application404, that is installed onclient device402, can register or authenticate with theaccess gateway422 ofcloud services408. For example, the user can authenticate the user to the client device and login to theclient device402. The client application can automatically execute, or be activated by the user. In some embodiments, the user can sign in to the client application (e.g., by authenticating the user to the client application). In response to the login or sign-in, the client application can register or authenticate the user and/or the client application with theaccess gateway422.
• In operation (2), in response to the registration or authentication, theaccess gateway422 can identify or retrieve a list of enumerated network applications available or pre-assigned to the user, and can provide the list to the client application. For example, in response to the registration or authentication, the access gateway can identify the user and/or retrieve a user profile of the user. According to the identity and/or user profile, the access gateway can determine the list (e.g., retrieve a stored list of network applications matched with the user profile and/or the identity of the user). The list can correspond to a list of network applications sanctioned for the user. The access gateway can send the list to the client application or embedded browser, which can be presented via the client application or embedded browser to the user (e.g., in a storefront user interface) for selection.
• In operation (3), the user can initiate connection to a sanctioned network application (e.g., a SaaS application), by selecting from the list of network applications presented to the user. For example, the user can click on an icon or other representation of the sanctioned network application, displayed via the client application or embedded browser. This user action can trigger the CEB to transmit a connection or access request to a server that provisions the network application. The request can include a request to the server (e.g., SaaS provider) to communicate with the access gateway to authenticate the user. The server can send a request to the access gateway to authenticate the user for example.
• In operation (4), the access gateway can perform SSO with the server, to authenticate the user. For example, in response to the server's request to authenticate the user, the access gateway can provide credentials of the user to the server(s)430 for SSO, to access the selected network application and/or other sanctioned network applications. In operation (5), the user can log into the selected network application, based on the SSO (e.g., using the credentials). The client application (e.g., thenetworking agent412 and/or the remote session agent416) can establish a secure connection and session with the server(s)430 to access the selected network application. The CEB can decrypt application traffic received via the secure connection. The CEB can monitor traffic sent via the CEB and the secured connection to theservers430.
• In operation (6), the client application can provide information to theanalytics services424 ofcloud services408, for analytics processing. For example, thecloud services agent414 of theclient application404 can monitor for or capture user interaction events with the selected network application. Thecloud services agent414 can convey the user interaction events to theanalytics services424, to be processed to produce analytics.
• FIG.5 depicts an example embodiment of a system for using a secure browser. In brief overview, the system includescloud services408,network applications406 andclient device402. In some embodiments, various elements of the system are similar to that described above forFIG.4, but that the client application (with embedded browser) is not available in theclient device402. A standard or typical browser may be available on the client device, from which a user can initiate a request to access a sanctioned network application for instance. A network application can be specified as being sanctioned or unsanctioned via policies that can be set by an administrator or automatically (e.g., via artificial intelligence).
• For example, in operation (1), the user may log into the network application using the standard browser. For accessing a sanctioned network application, the user may access a predefined URL and/or corresponding webpage of a server that provisions the network application, via the standard browser, to initiate a request to access the network application. In some embodiments, the request can be forwarded to or intercepted by a designated gateway service (e.g., in a data path of the request). For example, the gateway service can reside on the client device (e.g., as an executable program), or can reside on anetwork device432 of thecloud services408 for instance. In some embodiments, the access gateway can correspond to or include the gateway service. The gateway service can determine if the requested network application is a sanctioned network application. The gateway service can determine if a CEB initiated the request. The gateway service can detect or otherwise determine that the request is initiated from a source (e.g., initiated by the standard browser) in the client device other than a CEB. In some embodiments, there is no requirement for a designated gateway service to detect or determine if the request is initiated from a CEB, for example if the requested network application is sanctioned, that user is initiating the request via a standard browser, and/or that the predefined URL and/or corresponding webpage is accessed.
• In operation (2), the server may authenticate the user via the access gateway of the cloud services408. The server may communicate with the access gateway to authenticate the user, in response to the request. For instance, the request can include an indication to the server to communicate with the access gateway to authenticate the user. In some embodiments, the server is pre-configured to communicate with the access gateway to authenticate the user, for requests to access a sanctioned network application. The server may send a request to the access gateway to authenticate the user. In response to the server's request to authenticate the user, the access gateway can provide credentials of the user to theserver430.
• In operation (3), the gateway service and/or the server can direct (or redirect) all traffic to asecure browser420 which provides a secure browsing service. This may be in response to at least one of: a determination that the requested network application is a sanctioned network application, a determination that the request is initiated from a source other than a CEB, a determination that the requested network application is sanctioned, a determination that user is initiating the request via a standard browser, and/or a determination that the predefined URL and/or corresponding webpage is accessed.
• The user's URL session can be redirected to the secure browser. For example, the server, gateway service and/or the access gateway can generate and/or send a URL redirect message to the standard browser, responsive to the determination. The secure browser plug-in of the standard browser can receive the URL redirect message, and can for example send a request to access the non-sanctioned network application, to thesecure browser420. Thesecure browser420 can direct the request to the server of the non-sanctioned network application. The URL redirect message can instruct the standard browser (and/or the secure browser plug-in) to direct traffic (e.g., destined for the network application) from the standard browser to thesecure browser420 hosted on a network device. This can provide clientless access and control via dynamic routing though a secure browser service. In some embodiments, a redirection of all traffic to thesecure browser420 is initiated or configured, prior to performing authentication of the user (e.g., using SSO) with the server.
• In some embodiments, the gateway service can direct or request the server of the requested network application to communicate with thesecure browser420. For example, the gateway service can direct the server and/or the secure browser to establish a secured connection between the server and the secure browser, for establishing an application session for the network application.
• In some embodiments, thesecured browser420 comprises a browser that is hosted on anetwork device432 of the cloud services408. Thesecured browser420 can include one or more features of thesecured browser420 described above in connection with at leastFIG.4 for instance. The hosted browser can include an embedded browser of a CEB that is hosted on thenetwork device432 instead of on the client device. The hosted browser can include an embedded browser of a hosted virtualized version of the CEB that is hosted on thenetwork device432. Similar to the CEB installed on the client device, traffic is routed through the CEB hosted on the network device, which allows an administrator to have visibility of the traffic through the CEB and to remain in control for security policy control, analytics, and/or management of performance.
• FIG.6 illustrates an example implementation for browser redirection using a secure browser plug-in. In brief overview, the implementation includes aweb browser512 with a secure browser plug-in516 operating on a client device, and a hosted web browser (or secure browser)522 residing on a network device. Theweb browser512 can correspond to a standard browser, instead of an embedded browser as discussed above in connection withFIG.4 for example. The secure browser plug-in516 can execute within afirst network510 and access aserver430 in asecond network530. Thefirst network510 and thesecond network530 are for illustration purposes and may be replaced with fewer or additional computer networks. A secure browser plug-in516 can be installed on thestandard browser512. The plug-in can include one or more components. One such component can include an ActiveX control or Java control or any other type and/or form of executable instructions capable of loading into and executing in the standard browser. For example, the standard browser can load and run an Active X control of the secure browser plug-in516, in a memory space or context of the standard browser. In some embodiments, the secure browser plug-in can be installed as an extension on the standard browser, and a user can choose to enable or disable the plugin or extension. The secure browser plug-in can communicate and/or operate with thesecured browser420 for securing, using and/or accessing resources within the secured portion of the digital workspace.
• By using the secure browser plug-in516 operating within thestandard browser512 network applications accessed via thestandard browser512 can be redirected to a hosted secure browser. For instance, the secure browser plug-in516 can be implemented and/or designed to detect that a network application is being accessed via the standard browser, and can direct/redirect traffic from the client device associated with the network application, to the hosted secure browser. The hosted secure browser can direct traffic received from the network application, to the secure browser plug-in516 and/or aclient agent514 for rendering and/or display for example. Theclient agent514 can execute within theweb browser512 and/or the secure browser plug-in, and can include certain elements or features of theclient application404 discussed above in connection with at leastFIG.4 for example. For instance, theclient agent514 can include aremote session agent416 for rendering the network application at theweb browser512. In some embodiments, the network application is rendered at the hosted secure browser, and the rendered data is conveyed or mirrored to the secure browser plug-in516 and/or theclient agent514 for processing and/or display.
• By way of an example, a user may be working remotely and may want to access a network application that is internal to a secure corporate network while the user is working on a computing device connected to an unsecure network. In this case, the user may be utilizing thestandard browser512 executing in thefirst network510, in which thefirst network510 may comprise an unsecure network. Theserver430 that the user wants to access may be on thesecond network530, in which thesecond network530 comprises a secure corporate network for instance. The user might not be able to access theserver430 from the unsecurefirst network510 by clicking on an internal uniform record locator (URL) for the secure website532. That is, the user may need to utilize a different URL (e.g., an external URL) while executing thestandard browser512 from the externalunsecure network510. The external URL may be directed to or may address one or more hostedweb browsers522 configured to access server(s)430 within the second network530 (e.g., secure network). To maintain secure access, the secure browser plug-in516 may redirect an internal URL to an external URL for a hosted secure browser.
• The secure browser plug-in516 may be able to implement network detection in order to identify whether or not to redirect internal URLs to external URLs. Thestandard browser512 may receive a request comprising an internal URL for a website executing within the secure network. For example, thestandard browser512 may receive the request in response to a user entering a web address (e.g., for secure website532) in the standard browser. The secure browser plug-in516 may redirect the userweb browser application512 from the internal URL to an external URL for a hosted web browser application. For example, the secure browser plug-in516 may replace the internal URL with an external URL for the hostedweb browser application522 executing within thesecure network530.
• The secure browser plug-in516 may allow theclient agent514 to be connected to the hostedweb browser application522. Theclient agent514 may comprise a plug-in component, such as an ActiveX control or Java control or any other type and/or form of executable instructions capable of loading into and executing in thestandard browser512. For example, theclient agent514 may comprise an ActiveX control loaded and run by astandard browser512, such as in the memory space or context of the userweb browser application512. Theclient agent514 may be pre-configured to present the content of the hostedweb browser application522 within the userweb browser application512.
• Theclient agent514 may connect to a server or the cloud/hostedweb browser service520 using a thin-client or remote-display protocol to present display output generated by the hostedweb browser application522 executing on theservice520. The thin-client or remote-display protocol can be any one of the following non-exhaustive list of protocols: the Independent Computing Architecture (ICA) protocol developed by Citrix Systems, Inc. of Ft. Lauderdale, Fla.; or the Remote Desktop Protocol (RDP) manufactured by the Microsoft Corporation of Redmond, Wash.
• The hostedweb browser application522 may navigate to the requested network application in full-screen mode, and can render the requested network application. Theclient agent514 may present the content or rendition of the network application on theweb browser application512 in a seamless and transparent manner such that it appears that the content is being displayed by thestandard browser512, e.g., based on the content being displayed in full screen mode. In other words, the user may be given the impression that the web site content is displayed by the userweb browser application512 and not by the hostedweb browser application522. Theclient agent514 may transmit navigation commands generated by the userweb browser application512 to the hostedweb browser application522 using the thin-client or remote-display protocol. Changes to the display output of the hostedweb browser application522, due to the navigation commands, may be reflected in the userweb browser application512 by theclient agent514, giving the impression to the user that the navigation commands were executed by the userweb browser application512.
• Referring again toFIG.5, and in operation (4), a new browser tab can open on the standard browser, to render or display the secure browser session. The new browser tab can be established or opened by the secure browser plug-in for instance. The secure browser plug-in and/or a client agent can receive data from the secure browser session, and can render the network application within the new browser tab as discussed above in connection withFIG.6 for instance.
• In operation (5), the secure browser can feed all user interaction events via the network application, back to analytics service for processing. The secure browser plug-in can monitor for and intercept any user interaction events directed to the rendition of the network application within the browser tab. Hence, a user can use a native (or standard) browser to access a network application while allowing visibility into the network application's traffic, via the interoperation of cloud services and a secure browser (in the absence of the client application).
• FIG.7 depicts another example embodiment of a system of using a secure browser. In brief overview, the system includescloud services408,network applications406 and theclient device402. In some embodiments, various elements of the system are similar to that described above forFIG.5. A client application with embedded browser is not available in theclient device402. A standard or typical (e.g., HTMLS) browser is available on the client device, from which a user can initiate a request to access a non-sanctioned network application. A network application can be specified as being sanctioned or non-sanctioned via policies that can be set by an administrator or automatically (e.g., via artificial intelligence).
• In operation (1), the user may attempt to log into a non-sanctioned network application using the standard browser. The user may attempt to access a webpage of a server that provisions the network application, and to initiate a request to access the network application. In some embodiments, the request can be forwarded to or intercepted by a designated gateway service (e.g., in a data path of the request). For example, the gateway service (sometimes referred to as SWG) can reside on the client device (e.g., as an executable program), or can reside on anetwork device432 of thecloud services408 for instance. The gateway service can detect or otherwise determine if the requested network application is a sanctioned network application. The gateway service can determine if a CEB initiated the request. The gateway service can detect or otherwise determine that the request is initiated from a source (e.g., initiated by the standard browser) in the client device other than a CEB.
• In operation (2), the gateway service detects that the requested network application is a non-sanctioned network application. The gateway service can for instance extract information from the request (e.g., destination address, name of the requested network application), and compare the information against that from a database of sanctioned and/or non-sanctioned network applications. The gateway service can determine, based on the comparison, that the requested network application is a non-sanctioned network application.
• In operation (3), responsive to the determination, the gateway service can block access to the requested network application, e.g., by blocking the request. The gateway service can generate and/or send a URL redirect message to the standard browser, responsive to the determination. The URL redirect message can be similar to a URL redirect message sent from the server to the standard browser inFIG.5 in operation (3). A secure browser plug-in of the standard browser can receive the URL redirect message, and can for example send a request to access the non-sanctioned network application, to thesecure browser420. Thesecure browser420 can direct the request to the server of the non-sanctioned network application.
• The server of the non-sanctioned network application may authenticate the user via the access gateway of thecloud services408, e.g., responsive to receiving the request from the secure browser. The server may communicate with the access gateway to authenticate the user, in response to the request. The server may send a request to the access gateway to authenticate the user. In response to the server's request to authenticate the user, the access gateway can provide credentials of the user to theserver430. Upon authentication, the secure browser (or a corresponding CEB) can establish a secured connection and an application session with the server.
• In operation (4), a new browser tab can open on the standard browser, to render or display the secure browser's application session. The new browser tab can be established or opened by the secure browser plug-in for instance. The secure browser plug-in and/or a client agent can receive data from the secure browser session, and can render the network application within the new browser tab as discussed above in connection withFIGS.5-6 for instance.
• In operation (5), the secure browser can feed all user interaction events via the network application, back to analytics service for processing. The secure browser plug-in can monitor for and intercept any user interaction events directed to the rendition of the network application within the browser tab. Hence, a user can use a native (or standard) browser to access a network application while allowing visibility into the network application's traffic, via the interoperation of cloud services and a secure browser (in the absence of the client application).
• In some embodiments, in the absence or non-availability of a CEB on the client device, browser redirection is performed so that each requested network application is accessed via a corresponding hosted secure browser (or hosted CEB) for handling, instead of having all traffic redirected through a single hosted secure browser (or hosted CEB). Each dedicated secure browser can provide compartmentalization and improved security.
• The use of a CEB, whether hosted or local to the client device, can allow for end-to-end visibility of application traffic for analytics, service level agreement (SLA), resource utilization, audit, and so on. In addition to such visibility, the CEB can be configured with policies for managing and controlling any of these as well as other aspects. For example, DLP features can be supported, to control “copy and paste” activities, download of files, sharing of files, and to implement watermarking for instance. As another example, the CEB can be configured with policies for managing and controlling access to local drives and/or device resources such as peripherals.
• Referring now toFIG.8, an example embodiment of a system for using local embedded browser(s) and hosted secured browser(s) is depicted. An environment is shown where different types ofclient devices402A,402B may be used (e.g., in a BYOD context), such that one may be locally equipped with a suitable CEB, and another client device may not have a suitable local CEB installed. In such an environment, systems described inFIGS.4,5 and7 can be used to support each of the client devices based on the availability of a locally installed and suitable CEB.
• FIG.9 depicts an example process flow for using local embedded browser(s) and hosted secured browser(s). The process flow can be used in the environment described above inFIG.8, to determine whether an embedded browser or a hosted secured browser should be used for each client device to access a network application. For example, inoperation901, a HTTP client can attempt to access a web service (e.g., server of a network application). Inoperation903, the web service can redirect the HTTP client to a gateway service for authentication. Inoperation905, the gateway service can determine if the HTTP client is a CEB. If so, inoperation909, the gateway service can determine if the CEB is a suitable CEB, e.g., capable of enforcing defined application policies. If so, inoperation911, the CEB is allowed access to the web service, and can enforce the defined policies.
• If the gateway service determines that the HTTP client is not a CEB, the gateway service can cause a virtualized version of a CEB to be initialized and hosted on a remote server (e.g., anetwork device432 of cloud services408), inoperation907. In some embodiments, such a hosted CEB may already be available on anetwork device432, and can be selected for use. For example inoperation911, the CEB is allowed access to the web service, and can enforce the defined policies.
• If the gateway service determines that the HTTP client is a CEB, but that the CEB is not a suitable CEB, the gateway service can cause a virtualized version of a CEB to be initialized and hosted on a remote server (e.g., anetwork device432 of cloud services408), inoperation907. In some embodiments, such a hosted CEB may already be available on anetwork device432, and can be selected for use. For example inoperation911, the CEB is allowed access to the web service, and can enforce the defined policies.
• In some embodiments, if the user is requesting access to a web application located in a company data center, the gateway service (in cloud service or on premise) can allow access when the client application with CEB is detected. Otherwise, the request can be routed to a service with the hosted virtualized version of the CEB, and then access is authenticated and granted.
• Atoperation905 and/oroperation909 for instance, the decisions made on whether the HTTP client is a CEB and whether it is a suitable CEB may be determined by a number of factors. For example, to determine if the HTTP client is CEB, the gateway service may take into account factors, for example including at least one of: user Identity and strength of authentication, client Location, client IP Address, how trusted the user identity, client location, client IP are, jailbreak status of the client device, status of anti-malware software, compliance to corporate policy of the client device, and/or remote attestation or other evidence of integrity of the client software.
• To determine if the CEB is able to honor or support all defined application policies (which may vary by client version, client OS platform and other factors), the client device's software and gateway service may perform capability negotiation and/or exchange version information. In some embodiments, the gateway service can query or check a version number or identifier of the CEB to determine if the CEB is a suitable CEB to use.
• Driving all the traffic though the CEB then allows additional control of content accessing SaaS and Web based systems. Data Loss Prevention (DLP) of SaaS and Web traffic can be applied through the CEB app with features including copy and paste control to other CEB access applications or IT managed devices. DLP can also be enforced by enabling content to be downloaded only to designated file servers or services under IT control.
• Referring now toFIG.10, depicted is an example embodiment of a system for managing user access to webpages. Some webpages (or websites) are known to be safe while others may be suspect. A user may access a webpage via a corresponding URL through a standard browser. For example, the user may click on a link corresponding to the URL, which may be included in an email being viewed using a mail application. An access gateway (SWG) may intercept an access request generated by the clicking of the link, and can determine if the corresponding URL is safe or suspect. If the URL is known to be safe, the access gateway can allow the request to proceed to the corresponding website or web server. If the URL is suspect, the access gateway can redirect the request to be handled via a hosted secure browser. The secure browser can request access for, and access the webpage (on behalf of the standard browser), and can allow the webpage information to be conveyed to the standard browser, similar to the handling of a network application via browser redirection as discussed in connection with at leastFIGS.7 and5.
C. Systems and Methods for Traffic Accounting for Network Applications
• The present disclosure is directed towards systems and methods for traffic accounting for network applications, or disambiguating between enterprise and non-enterprise data transmitted via a network service provider. User devices or client devices may utilize data connections, such as cellular data, for both enterprise-related communications such as network applications or software-as-a-service applications provided by application servers, as well as non-enterprise-related communications, such as social media, general web browsing, voice or video communications, etc.
• For example,FIG.11 is a block diagram of a network environment with amobile device1100,application servers1112,data servers1114, andthird party servers1116. Themobile device1100 may communicate with the servers via anetwork1110. Enterprise communications A may flow between themobile device1110 andapplication servers1112 and/ordata servers1114, shown in solid black line. Non-enterprise communications to third party servers may flow directly between themobile device1110 andthird party servers1116, as shown with flow B in dashed line. In some implementations, non-enterprise communications to third-party servers may also flow indirectly to the servers, via anapplication server1112, as shown with flow C in dotted line. For example, in one such implementation, aclient application1102 comprising an embeddedbrowser1104 may connect to anapplication server1112 of an enterprise and access a network application, such as a media player application. The user may then load content for playback in the media player application hosted at athird party server1116. In some such implementations, requests to thethird party server1116 for content from the embedded browser may be transmitted to theapplication server1112, and then redirected to thethird party server1116, and responses may follow the same path. In another example, a user may use an embedded browser communicating via a private network with an application server to browser a social media site provided by athird party server1116.
• Communications flows A, B, and C in the example illustrated may all traverse a single network interface of themobile device1100, such as a cellular modem. The communications may thus utilize a single physical layer path from the mobile device to a gateway or access point of thenetwork1100. With redirected communications (e.g. flow C), the communications may also utilize the same network and/or transport layer connection between the mobile device and application server, making it difficult to disambiguate enterprise and non-enterprise communications. For example, a simple usage monitor that tracks data transmitted to and received by themobile device1100 vianetwork1110 at the physical layer may measure all data, regardless of type, and may not be able to distinguish between flows to the enterprise (flow A) and flows to third party servers (flow B). Furthermore, even a smarter monitor that tracks data transmitted to and from the device at the network layer or transport layer may be unable to distinguish between traffic that is communicated directly to an application server and traffic that is communicated indirectly via the application server to a third party server. In particular, traffic that is encrypted at a level above the transport layer may be ambiguous to a monitor that attempts to distinguish the traffic at lower layers of the network stack.
• The inability to distinguish between enterprise and non-enterprise data may impair network operations. For example, traffic redirected via an enterprise server to a third party server may require significantly less processing power by the enterprise server than traffic that is actually processed by the enterprise server (e.g. in providing a network application). However, if bandwidth to and from the server is measured without distinguishing between redirected traffic and processed traffic, the server may appear more utilized than it actually is. The system may attempt to rebalance loads by steering traffic to other application servers that may actually be more heavily utilized. In a similar implementation, a system may instantiate virtual machines of a server cloud to meet anticipated need based off identifying new connections to the cloud. However, if new connections are actually redirected to third party servers and do not need the processing functionality of the virtual machines, these efforts could be wasted. Instantiating virtual machines (and halting them) may take additional resources, further increasing inefficiency of the system.
• In another implementation, data may be pre-fetched for use by the embedded browser to reduce latency and increase application responsiveness. For example, when a user accesses a web application, it may be desirable to pre-fetch most-used data of the web application, such as user templates, preference files, commonly accessed documents, etc. This pre-fetching may be triggered, in some implementations, by the establishment of a connection from the embedded browser to an application server. However, if the communication is actually intended for a third party server and is merely redirected by the application server, none of the pre-fetched data may be required. As a result, pre-fetching the data may waste bandwidth and storage at the client device. Conversely, waiting to determine whether communications are actually directed to the application server or a third party server before pre-fetching data reduces the benefits of pre-fetching by adding additional latency.
• Accordingly, the inability to distinguish between enterprise communications and non-enterprise communications may result in network and device inefficiencies, slowdowns, and higher latency for crucial communications.
• Instead, in accordance with the systems and methods discussed herein, a client application installed on a client device may comprise a usage monitor configured to monitor communications flows between embedded browsers of the client application and one or more servers, including enterprise servers and non-enterprise servers, at upper layers of a network stack of the client device including the application layer, session layer, and presentation layer. Communications to different endpoints may be classified as enterprise or non-enterprise, measured, and aggregated to provide disambiguation of enterprise and non-enterprise communications of the device transiting a single communications link (e.g. cellular data connection). Server and network policies may be applied in accordance with the measurements with higher accuracy than policies based on total bandwidth utilized by the device without regard to its classification. These policies may include load balancing, communication pooling, multiplexing, buffering, pre-fetching or edge caching of data, instantiating or halting execution of virtual machines in a cloud environment, or other such functions.
• Still referring toFIG.11 and in more detail, amobile device1100 may communicate via anetwork1110 with one ormore application servers1112 and/or one ormore data servers1114 provided by an enterprise, as well as one or morethird party servers1116. Although primarily discussed as amobile device1100, in many implementations, the device may comprise a laptop computer, desktop computer, tablet computer, embedded computer, smart phone, smart television, gaming console, Internet-of-Things (IoT) appliance, smart car, or other such device, and may be referred to generally as a client device. The client device may communicate with anetwork1110 via any suitable communications medium, such as a cellular modem,802.11 (WiFi) modem, cable modem, Ethernet interface, Bluetooth interface, or other type and form of network interface.Network1110 may comprise any type and form of networks including cellular networks, satellite networks, cable networks, wide area networks (WANs) such as the Internet, local area networks (LANs), or combinations of these or other networks. In some implementations, connectivity for theclient device1100 may be provided by an Internet Service Provider (ISP).
• Client device1100 may execute aclient application1102, similar to client applications discussed above, that includes an embedded browser1104 (e.g. similar toclient application404 and embedded browser410) that can render information of a network application accessed via theclient application1100. Theclient application1102 may be an instance of theclient application404 previously detailed herein. Theclient application1102 with the embedded browser1104 (CEB) can include any element of aCEB410 as previously described herein. Theclient device1100 may also execute one or morethird party applications1108 in some implementations. Third party applications108 may comprise social media applications, web browsers, email applications, productivity applications, gaming applications, or any other type and form of applications, and may communicate withthird party servers1116 for data, either directly (e.g. flow B) or indirectly via redirect from an application server1112 (e.g. flow C).
• Each of the above-mentioned elements or entities is implemented in hardware, or a combination of hardware and software, in one or more embodiments. Each component of the system may be implemented using hardware or a combination of hardware or software detailed above in connection withFIG.1. For instance, each of these elements or entities can include any application, program, library, script, task, service, process or any type and form of executable instructions executing on hardware of a client device (e.g., the client applications1102). The hardware includes circuitry such as one or more processors in one or more embodiments.
• Client application1202 may comprise a usage monitor1106. Usage monitor1106 may comprise an application, service, server, daemon, routine, or other executable logic for identifying traffic flows at a layer above the transport layer of a network stack (e.g. session layer, presentation layer, application layer, etc.), for distinguishing between enterprise and non-enterprise communications, and for measuring and tracking total bandwidth utilization by said enterprise and non-enterprise communications. Although shown as part ofclient application1102, in many implementations, usage monitor1106 may comprise part of an operating system or network stack of the client device. Usage monitor1106 may monitor communications via an embedded browser of the client application (including non-enterprise communications via the embedded browser tothird party servers1116, either directly or indirectly), and, in some implementations, may also monitor communications ofthird party applications1108. In some implementations, usage monitor1106 may identify and distinguish different traffic flows based on header information of packets at layers above the transport layer (and, in some implementations, also utilizing network and transport layer information of the packets, such as destination IP and port addresses). For example, as part ofclient application1102, usage monitor1106 may have access to requests and responses prior to any encryption being applied at or below the application layer of the network stack. In some implementations, usage monitor1106 may examine executable code that triggered a request, such as HTTP POST or GET requests within a web application, in order to identify traffic flows. In some implementations, usage monitor1106 may examine metadata of transferred files, such as headers of images or data files, to determine corresponding applications and/or enterprise or non-enterprise sources or destinations and data sizes.
• FIG.12 is a flow chart of an implementation of a method for tracking of and disambiguation between enterprise and non-enterprise data communications. Atstep1400, a client device may establish a communication session with an external device, such as an application server, data server, or third-party server. The communication session may be established by a third party application or by a client application or embedded browser of the client application. Establishing the communication session may comprise establishing a connection, performing handshaking procedures, performing authentication procedures (e.g. logging in, providing an authentication token, etc.), or other processes.
• Atstep1402, in some implementations, the client application or a usage monitor of the client application may determine whether the communication session is associated with an enterprise application or a non-enterprise application. For example, in some implementations, the client application or usage monitor may determine if the session is established by the client application or another enterprise application, or a third-party application. If the session is established by a non-enterprise application, then atstep1404, the usage monitor or client application may track the bandwidth utilized by the session and aggregate the tracked bandwidth with measurements of bandwidth of other non-enterprise applications.
• If the session is associated with or established by an enterprise application, such as the client application or embedded browser, then atstep1406, the usage monitor may determine if the session is being redirected by an application server to a third-party server. In some implementations, the client application or usage monitor may transmit a request to the recipient application server and receive a response indicating whether the session is redirected or not. In other implementations, the client application or usage monitor may monitor responses from the application server for redirect addresses (e.g. an HTTP status code indicating a URL redirection, such as a303 or307 redirect code, or other such redirect codes). In still other implementation, the client application or usage monitor may monitor received packets of the session to determine a source identified in metadata or packet headers at any layer of the network stack, including application layer headers.
• If the communication session is being redirected to a third-party server, then the client application or usage monitor may track and aggregate bandwidth of the session with non-enterprise communications atstep1404. If the communication session is not being redirected, then the client application or usage monitor may track the bandwidth utilized by the session and aggregate the tracked bandwidth with measurements of bandwidth of other enterprise applications.
• This disambiguation and measurement process may be repeated iteratively for each additional communication session established within a predetermined time period (e.g. one day, one week, one month, etc.). In some implementations, the predetermined time period may be different for different applications and/or for enterprise communications as opposed to non-enterprise communications. Upon expiration of the predetermined time period or periods, the aggregated totals of bandwidth for enterprise and non-enterprise communications may be provided to a server atstep1410 by the client application or usage monitor, and atstep1412, the client application or usage monitor may reset aggregated bandwidth totals or counters. In some implementations, atstep1410, bandwidth totals for individual applications may be provided separately rather than being aggregated by the client application or usage monitor.
• In some implementations, the totals may be provided to a server of an Internet Service Provider for separate billing. For example, in some implementations, an enterprise may subsidize data communications of enterprise devices for its users, while the users may pay a proportion of costs associated with data communications for non-enterprise communications. As discussed above, an ISP server may not be able to distinguish between such communications, e.g. due to encryption at layers of the network stack above the transport layer, because non-enterprise communications are received and redirected by enterprise servers, etc., and thus the ISP may not be able to provide separate billing absent the additional information from the client application or usage monitor. This may be beneficial to enterprises that incur significant costs subsidizing data plans for users who utilize their devices for both enterprise and non-enterprise communications.
• Accordingly, the systems and methods discussed herein provide for monitoring and disambiguation of enterprise and non-enterprise communications via a client device. A client application installed on a client device may monitor communications flows between embedded browsers of the client application and one or more servers, including enterprise servers and non-enterprise servers, at upper layers of a network stack of the client device including the application layer, session layer, and presentation layer. Communications to different endpoints may be classified as enterprise or non-enterprise, measured, and aggregated to provide disambiguation of enterprise and non-enterprise communications of the device transiting a single communications link (e.g. cellular data connection). Server and network policies may be applied in accordance with the measurements with higher accuracy than policies based on total bandwidth utilized by the device without regard to its classification. These policies may include load balancing, communication pooling, multiplexing, buffering, pre-fetching or edge caching of data, instantiating or halting execution of virtual machines in a cloud environment, or other such functions.
• It should be understood that the systems described above may provide multiple ones of any or each of those components and these components may be provided on either a standalone machine or, in some embodiments, on multiple machines in a distributed system. The systems and methods described above may be implemented as a method, apparatus or article of manufacture using programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof. In addition, the systems and methods described above may be provided as one or more computer-readable programs embodied on or in one or more articles of manufacture. The term “article of manufacture” as used herein is intended to encompass code or logic accessible from and embedded in one or more computer-readable devices, firmware, programmable logic, memory devices (e.g., EEPROMs, ROMs, PROMs, RAMs, SRAMs, etc.), hardware (e.g., integrated circuit chip, Field Programmable Gate Array (FPGA), Application Specific Integrated Circuit (ASIC), etc.), electronic devices, a computer readable non-volatile storage unit (e.g., CD-ROM, USB Flash memory, hard disk drive, etc.). The article of manufacture may be accessible from a file server providing access to the computer-readable programs via a network transmission line, wireless transmission media, signals propagating through space, radio waves, infrared signals, etc. The article of manufacture may be a flash memory card or a magnetic tape. The article of manufacture includes hardware logic as well as software or programmable code embedded in a computer readable medium that is executed by a processor. In general, the computer-readable programs may be implemented in any programming language, such as LISP, PERL, C, C++, C#, PROLOG, or in any byte code language such as JAVA. The software programs may be stored on or in one or more articles of manufacture as object code.
• While various embodiments of the methods and systems have been described, these embodiments are illustrative and in no way limit the scope of the described methods or systems. Those having skill in the relevant art can effect changes to form and details of the described methods and systems without departing from the broadest scope of the described methods and systems. Thus, the scope of the methods and systems described herein should not be limited by any of the illustrative embodiments and should be defined in accordance with the accompanying claims and their equivalents.

Claims (20)

We claim:

1. A method comprising:

monitoring, by a usage monitor of a client device configured for both enterprise and non-enterprise communications, data in a traffic flow comprising both enterprise and non-enterprise communications, the usage monitor configured to distinguish between enterprise and non-enterprise communications of a traffic flow;

tracking, by the client device based at least on metadata of a first plurality of plackets of the traffic flow providing enterprise communications, a first amount of data of enterprise communications over a first time period, the first amount of data being encrypted and communication to a server of the enterprise via a first connection;

tracking, by the client device based at least on metadata of a second plurality of plackets of the traffic flow providing non-enterprise communications, a second amount of data of non-enterprise communications over the first time period, the second amount of data being communicated to a non-enterprise server; and

communicating, by the client device to another server of the enterprise, identification of the first amount of the data and the second amount of the data, the first amount of the data and the second amount of the data determined using the metadata of the first plurality of packets and the second plurality of packets of the traffic flow.

2. The method ofclaim 1, further comprising establishing, by a client application on the client device, communications between the client device and the server of the enterprise via the first connection.

3. The method ofclaim 2, further comprising establishing, by a browser of the client application via the first connection, one or more sessions with one or more applications on one or more non-enterprise servers.

4. The method ofclaim 1, wherein the second amount of data being encrypted to the server of the enterprise via the first connection and redirected by the server of the enterprise via a second connection to the non-enterprise server.

5. The method ofclaim 1, further comprising communicating, by the client device, the identification of the first amount of the data and the second amount of the data to the another server of the enterprise via a third connection.

6. The method ofclaim 1, further comprising communicating a name or type of application being used in the first amount of data.

7. The method ofclaim 1, further comprising communicating a name or type of application being used in the second amount of data.

8. A client device comprising:

a usage monitor configured for both enterprise and non-enterprise communication and to monitor data in a traffic flow comprising both enterprise and non-enterprise communications, the usage monitor configured to distinguish between enterprise and non-enterprise communications of a traffic flow;

wherein the client device is configured to:

track, based at least on metadata of a first plurality of plackets of the traffic flow providing enterprise communications, a first amount of data of enterprise communications over a first time period, the first amount of data being encrypted and communication to a server of the enterprise via a first connection;

track, based at least on metadata of a second plurality of plackets of the traffic flow providing non-enterprise communications, a second amount of data of non-enterprise communications over the first time period, the second amount of data being communicated to a non-enterprise server; and

communicate to another server of the enterprise, identification of the first amount of the data and the second amount of the data, the first amount of the data and the second amount of the data determined using the metadata of the first plurality of packets and the second plurality of packets of the traffic flow.

9. The client device ofclaim 8, further comprising a client application configured to establish communications between the client device and the server of the enterprise via the first connection.

10. The client device ofclaim 9, further comprising a browser of the client application configured to establish via the first connection, one or more sessions with one or more applications on one or more non-enterprise servers.

11. The client device ofclaim 8, wherein the second amount of data being encrypted to the server of the enterprise via the first connection and redirected by the server of the enterprise via a second connection to the non-enterprise server.

12. The client device ofclaim 8, further configured to communicate the identification of the first amount of the data and the second amount of the data to the another server of the enterprise via a third connection.

13. The client device ofclaim 8, further configured to communicate a name or type of application being used in the first amount of data.

14. The client device ofclaim 8, further configured to communicate a name or type of application being used in the second amount of data.

15. A non-transitory computer readable medium storing program instructions for causing one or more processors to:

monitor, using a usage monitor configured for both enterprise and non-enterprise communications, data in a traffic flow comprising both enterprise and non-enterprise communications, the usage monitor configured to distinguish between enterprise and non-enterprise communications of a traffic flow;

track, based at least on metadata of a first plurality of plackets of the traffic flow providing enterprise communications, a first amount of data of enterprise communications over a first time period, the first amount of data being encrypted and communication to a server of the enterprise via a first connection;

track, based at least on metadata of a second plurality of plackets of the traffic flow providing non-enterprise communications, a second amount of data of non-enterprise communications over the first time period, the second amount of data being communicated to a non-enterprise server; and

communicate to another server of the enterprise, identification of the first amount of the data and the second amount of the data, the first amount of the data and the second amount of the data determined using the metadata of the first plurality of packets and the second plurality of packets of the traffic flow.

16. The non-transitory computer readable medium ofclaim 15, wherein the program instructions further cause the one or more processors to establish communications between the client device and the server of the enterprise via the first connection.

17. The non-transitory computer readable medium ofclaim 15, wherein the second amount of data being encrypted to the server of the enterprise via the first connection and redirected by the server of the enterprise via a second connection to the non-enterprise server.

18. The non-transitory computer readable medium ofclaim 15, wherein the program instructions further cause the one or more processors to communicate the identification of the first amount of the data and the second amount of the data to the another server of the enterprise via a third connection.

19. The non-transitory computer readable medium ofclaim 15, wherein the program instructions further cause the one or more processors to communicate a name or type of application being used in the first amount of data.

20. The non-transitory computer readable medium ofclaim 15, wherein the program instructions further cause the one or more processors to communicate a name or type of application being used in the second amount of data

Images