U.S. patent number 11,328,077 [Application Number 16/402,899] was granted by the patent office on 2022-05-10 for systems and methods for providing data loss prevention via an embedded browser.
This patent grant is currently assigned to Citrix Systems, Inc.. The grantee listed for this patent is Citrix Systems, Inc.. Invention is credited to Christopher Fleck, Juan Rivera.
United States Patent |
11,328,077 |
Fleck , et al. |
May 10, 2022 |
Systems and methods for providing data loss prevention via an
embedded browser
Abstract
Described embodiments provide systems and methods for providing
data loss prevention via an embedded browser. An interprocess
communication (IPC) manager may interface with an embedded browser
to control the transfer of data from a first application to a
second application in accordance with a policy. The IPC manager may
detect a command to store data accessed on the first application
via the embedded browser and store the data onto a secure
container. The secure container may be dedicated to the embedded
browser. The IPC manager may subsequently detect a command to
retrieve data from the secure container and to replicate the data
onto the second application. The IPC manager may determine a policy
to apply to the data. The policy may specify whether the data from
the first application is permitted to be replicated onto the second
application. The IPC manager may subsequently replicate the data on
the second application.
Inventors: |
Fleck; Christopher (Fort
Lauderdale, FL), Rivera; Juan (Fort Lauderdale, FL) |
Applicant: |
Name |
City |
State |
Country |
Type |
Citrix Systems, Inc. |
Fort Lauderdale |
FL |
US |
|
|
Assignee: |
Citrix Systems, Inc. (Fort
Lauderdale, FL)
|
Family
ID: |
1000006298462 |
Appl.
No.: |
16/402,899 |
Filed: |
May 3, 2019 |
Prior Publication Data
|
|
|
|
Document
Identifier |
Publication Date |
|
US 20190340376 A1 |
Nov 7, 2019 |
|
Related U.S. Patent Documents
|
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
Issue Date |
|
|
62667199 |
May 4, 2018 |
|
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
G06F
13/20 (20130101); G06F 9/547 (20130101); H04L
67/5683 (20220501); G06F 21/602 (20130101); G06F
21/6218 (20130101); G06F 16/27 (20190101); H04L
67/01 (20220501) |
Current International
Class: |
G06F
21/62 (20130101); G06F 16/27 (20190101); G06F
9/54 (20060101); H04L 67/5683 (20220101); G06F
13/20 (20060101); G06F 21/60 (20130101); H04L
67/01 (20220101) |
References Cited
[Referenced By]
U.S. Patent Documents
Other References
Examination Report on AU Appl. 2019262187 dated Mar. 5, 2021. cited
by applicant .
International Preliminary Report of Patentability on PCT Appl No.
PCT/US2019/030619 dated Nov. 19, 2020. cited by applicant .
International Search Report and Written Opinion for
PCT/US2019/030619, dated Jul. 3, 2019. cited by applicant .
Examination Report on AU Appl. No. 2019262187 dated Nov. 12, 2021.
cited by applicant .
Examiner's Report on CA Appl. No. 3096504 dated Nov. 2, 2021. cited
by applicant.
|
Primary Examiner: Tsai; Henry
Assistant Examiner: Roche; John B
Attorney, Agent or Firm: Foley & Lardner LLP
Parent Case Text
CROSS REFERENCE TO RELATED APPLICATION
This application claims priority under 35 U.S.C. .sctn. 119(e) to
U.S. Provisional Patent Application No. 62/667,199, titled "SYSTEMS
AND METHODS FOR PROVIDING DATA LOSS PREVENTION VIA AN EMBEDDED
BROWSER," filed May 4, 2018, which is incorporated herein by
reference in its entirety.
Claims
We claim:
1. A method of managing access to data in secured containers, the
method comprising: providing, via an embedded browser of a client
application on a client device, access to a first network
application hosted on a server, the client application providing
the client device with access to a plurality of network
applications including the first network application; detecting a
command on the client device to store data accessed from the first
network application via the embedded browser; storing, responsive
to detecting the command, the data in a secure container accessible
by the embedded browser; and applying, in response to a request to
access the stored data, a rule to manage access to the data stored
in the secure container by a second network application of the
plurality of network applications.
2. The method of claim 1, further comprising determining, in
accordance to the application of the rule, whether to restrict a
replication of the data stored in the secure container onto a
second network application of the plurality of network
applications.
3. The method of claim 1, further comprising detecting, via the
embedded browser, a command on the client to replicate the data
stored in the secure container; and wherein applying the rule
further comprises applying the rule in response to detecting the
command to replicate.
4. The method of claim 3, further comprising identifying the data
to be replicated corresponding to the command to replicate to apply
the rule.
5. The method of claim 1, further comprising modifying at least a
portion of the data stored on the secure container to replicate
onto a second network application of the plurality of network
applications.
6. The method of claim 1, further comprising presenting, via the
embedded browser, a prompt indicating a restriction of replication,
responsive to determining to restrict the replication of the
data.
7. The method of claim 1, wherein applying the rule further
comprises applying the rule based on at least one of: a source
application, a destination application, a device type, a data type,
a device location, or an account identifier.
8. The method of claim 1, wherein detecting the command further
comprises detecting a user interaction corresponding to the command
to store the data accessed from the first network application.
9. The method of claim 1, wherein storing the data in the secure
container further comprises encrypting the data to be stored.
10. The method of claim 1, wherein the secure container resides on
at least one of the client device and the server hosting the first
network application.
11. A system for managing access to data in secured containers,
comprising: an embedded browser of a client application executable
on one or more processors, wherein the client application is
configured to provide the client device with access to a plurality
of network applications via the embedded browser including a first
network application hosted on a server; and an interprocess
communication (IPC) manager interfacing with the client
application, the IPC manager configured to: detect a command at the
client device to store data accessed from the first network
application via the embedded browser; store, responsive to
detecting the command, the data in a secure container accessible by
the embedded browser; and apply, in response to a request to access
the stored data, a rule to manage access to the data stored in the
secure container by a second network application of the plurality
of network applications.
12. The system of claim 11, wherein the IPC manager is further
configured to determine, in accordance to the application of the
rule, whether to restrict a replication of the data stored in the
secure container onto a second network application of the plurality
of network applications.
13. The system of claim 11, wherein the IPC manager is further
configured to: detect, via the embedded browser, a command on the
client to replicate the data stored in the secure container; and
apply the rule in response to detecting the command to
replicate.
14. The system of claim 13, wherein the IPC manager is further
configured to identify the data to be replicated corresponding to
the command to replicate to apply the rule.
15. The system of claim 11, wherein the IPC manager is further
configured to modify at least a portion of the data stored on the
secure container to replicate onto a second network application of
the plurality of network applications.
16. The system of claim 11, wherein the IPC manager is further
configured to present, via the embedded browser, a prompt
indicating a restriction of replication, responsive to determining
to restrict the replication of the data.
17. The system of claim 11, wherein the IPC manager is further
configured to apply the rule based on at least one of: a source
application, a destination application, a device type, a data type,
a device location, or an account identifier.
18. The system of claim 11, wherein the IPC manager is further
configured to detect a user interaction corresponding to the
command to store the data accessed from the first network
application.
19. The system of claim 11, wherein the IPC manager is further
configured to encrypt the data to be stored on the secure
container.
20. The system of claim 11, wherein the secure container resides on
at least one of the client device and the server hosting the first
network application.
Description
FIELD OF THE DISCLOSURE
The present application generally relates to data loss prevention,
including but not limited to systems and methods for providing data
loss prevention via embedded browsers.
BACKGROUND
A data buffer (sometimes referred to as clipboard) may be used to
temporarily store data selected from an application on memory for
future use. Upon command, the temporarily stored data may be
transferred to or copied onto other applications.
BRIEF SUMMARY
This summary is provided to introduce a selection of concepts in a
simplified form that are further described below in the Detailed
Description. This summary is not intended to identify key features
or essential features, nor is it intended to limit the scope of the
claims included herewith.
A client application with an embedded browser (CEB) may be used to
access applications and resources hosted on various servers. These
applications may include, for example, web applications accessed
via the browser, cloud hosted applications (e.g., as part of
Software as a Service (SaaS), Infrastructure as a Service (IaaS),
and Platform as a Service (PaaS)), and virtual applications hosted
on a virtual machine, among others. Data accessed via the
applications may be selected and stored on a temporary data cache
or buffer, and then replicated onto other applications as part of a
copy-and-paste operation. Without any additional controls, however,
data security may be compromised, with potentially sensitive
information leaked from the applications.
To prevent such lapses in data security, access to data on
applications and resources hosted on servers may be restricted
through the CEB. Within the CEB, a copy command along with selected
data (e.g., text or images) from one application may be received
via activation of a copy button of the CEB or a preset keystroke
(e.g., CTRL+C). Instead of or in addition to storing the selected
content into a local operating system (OS) clipboard, the data may
be stored in a secure container. The secure container may cache the
data and can encrypt the data using a cryptographic key. The secure
container may reside in a cache of the CEB locally at the client
and/or remotely on one of the servers hosting the applications or a
cloud-based service. When the secure container resides remotely,
the data and the cryptographic key used to encrypt the data may be
shared between multiple client devices (e.g., that the user has
signed into).
Another application may be subsequently accessed through the CEB.
When a paste command is then received on the subsequent application
using a paste button of the CEB or a preset keystroke (e.g.,
CTRL+V), the application may be checked against a data loss
prevention policy. The policy may specify which applications
accessed via the CEB, which device types running the CEB, which
user accounts, and/or which location at which the client running
the CEB, among other considerations, have permission to the data
maintained on the secure container. The policy may also specify
whether sensitive information contained the data is to be removed,
even if there is permission to access. If the policy permits the
subsequent application to access the secure container, data
maintained in the stored container can be retrieved and replicated
onto or provided to the application. In addition, if the policy
specifies that the sensitive information contained in the data is
to be redacted for the subsequent application, the data may be
parsed to determine whether the data contains any sensitive data,
and portions of the data may be redacted in accordance with the
policy. In this manner, data loss prevention may be achieved and
data security may be enhanced.
In one aspect, the present disclosure is directed to a system and
method of providing data loss prevention via embedded browsers. An
interprocess communication (IPC) manager may interface with an
embedded browser to control the transfer of data from a first
application to a second application in accordance with a policy.
Both the first application and the second application may be
accessed by a user via the embedded browser. The IPC manager may
detect a first command to store data accessed on the first
application via the embedded browser. Responsive to the detection
of the first command, the IPC manager may store the data onto a
secure container. The secure container may be dedicated to the
embedded browser. The IPC manager may subsequently detect a second
command to retrieve data from the secure container and to replicate
the data onto the second application via the embedded browser.
Responsive to detection of the second command, the IPC manager may
determine a policy to apply to the data maintained on the secure
container. The policy may specify whether the data from the first
application is permitted to be replicated onto the second
application. If the data is permitted to be replicated in the
second application under the policy, the IPC manager may determine
whether a portion of the data is to be removed (e.g., via redaction
or deletion) prior to the replication. The policy may also specify
an information type of the data is to be removed prior to
replication onto the second application. The IPC manager may parse
the data to identify whether a portion of the data matches the
information type specified by the policy. The IPC manager may
remove the portion matching the information type specified by the
policy. The IPC manager may subsequently replicate the data with
the portion removed on the second application.
At least one aspect of the present disclosure is directed to a
method of managing access to data in secured containers. An
embedded browser may of a client application on a client device may
provide access to a first network application hosted on a server.
The client application may provide the client device with access to
a plurality of network applications including the first network
application. The method may include detecting a command on the
client device to store data accessed from the first network
application via the embedded browser. The method may include
storing, responsive to detecting the command, the data in a secure
container accessible by the embedded browser. The method may
include applying, in response to a request to access the stored
data, a policy to manage access to the data stored in the secure
container.
In some embodiments, the method may include determining, in
accordance to the application of the policy, whether to restrict a
replication of the data stored in the secure container onto a
second network application of the plurality of network
applications. In some embodiments, the method may include
detecting, via the embedded browser, a command on the client to
replicate the data stored in the secure container. In some
embodiments, applying the policy may include applying the policy in
response to detecting the command to replicate. In some
embodiments, the method may include identifying the data to be
replicated corresponding to the command to replicate to apply the
policy.
In some embodiments, the method may include modifying at least a
portion of the data stored on the secure container to replicate
onto a second network application of the plurality of network
applications. In some embodiments, the method may include
presenting, via the embedded browser, a prompt indicating a
restriction of replication, responsive to determining to restrict
the replication of the data.
In some embodiments, applying the policy may include applying the
policy based on at least one of: a source application, a
destination application, a device type, a data type, a device
location, and an account identifier. In some embodiments, detecting
the command may include detecting a user interaction corresponding
to the command to store the data accessed from the first network
application.
In some embodiments, storing the data in the secure container may
include encrypting the data to be stored. In some embodiments, the
secure container resides on at least one of the client device and
the server hosting the first network application.
At least one aspect of the present disclosure is directed to a
system for managing access to data in secured containers. The
system may include an embedded browser may of a client application
on a client device. The embedded browser may provide access to a
first network application hosted on a server. The client
application may provide the client device with access to a
plurality of network applications including the first network
application. The system may include an interprocess communication
(IPC) manager interfacing with the client application. The IPC
manager may detect a command on the client device to store data
accessed from the first network application via the embedded
browser. The IPC manager may store, responsive to detecting the
command, the data in a secure container accessible by the embedded
browser. The IPC manager may apply, in response to a request to
access the stored data, a policy to manage access to the data
stored in the secure container.
In some embodiments, the IPC manager may determine in accordance to
the application of the policy, whether to restrict a replication of
the data stored in the secure container onto a second network
application of the plurality of network applications. In some
embodiments, the IPC manager may detect, via the embedded browser,
a command on the client to replicate the data stored in the secure
container. In some embodiments, IPC manager may apply the policy in
response to detecting the command to replicate. In some
embodiments, IPC manager may identify the data to be replicated
corresponding to the command to replicate to apply the policy.
In some embodiments, the IPC manager may modify at least a portion
of the data stored on the secure container to replicate onto a
second network application of the plurality of network
applications. In some embodiments, IPC manager may present, via the
embedded browser, a prompt indicating a restriction of replication,
responsive to determining to restrict the replication of the
data.
In some embodiments, the IPC manager may apply the policy based on
at least one of: a source application, a destination application, a
device type, a data type, a device location, and an account
identifier. In some embodiments, the IPC manager may detect a user
interaction corresponding to the command to store the data accessed
from the first network application.
In some embodiments, the IPC manager may encrypt the data to be
stored onto the secure container. In some embodiments, the secure
container resides on at least one of the client device and the
server hosting the first network application.
BRIEF DESCRIPTION OF THE DRAWING FIGURES
Objects, aspects, features, and advantages of embodiments disclosed
herein will become more fully apparent from the following detailed
description, the appended claims, and the accompanying drawing
figures in which like reference numerals identify similar or
identical elements. Reference numerals that are introduced in the
specification in association with a drawing figure may be repeated
in one or more subsequent figures without additional description in
the specification in order to provide context for other features,
and not every element may be labeled in every figure. The drawing
figures are not necessarily to scale, emphasis instead being placed
upon illustrating embodiments, principles and concepts. The
drawings are not intended to limit the scope of the claims included
herewith.
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 a system 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 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 a system for managing interprocess
communications of applications running across networked
environments;
FIG. 12 is a flow diagram a method of managing interprocess
communications of applications running across networked
environments; and
FIG. 13 is a flow diagram of a method of managing access to data in
secure containers.
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 embodiments of systems and methods for
providing data loss prevention via embedded browsers.
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 in FIG. 1, computer 101 may include one or more processors
103, volatile memory 122 (e.g., random access memory (RAM)),
non-volatile memory 128 (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 or more
communications interfaces 118, and communication bus 150. User
interface 123 may include graphical user interface (GUI) 124 (e.g.,
a touchscreen, a display, etc.) and one or more input/output (I/O)
devices 126 (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 memory 128 stores operating system 115, one or more
applications 116, and data 117 such that, for example, computer
instructions of operating system 115 and/or applications 116 are
executed by processor(s) 103 out of volatile memory 122. In some
embodiments, volatile memory 122 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 of
GUI 124 or received from I/O device(s) 126. Various elements of
computer 101 may communicate via one or more communication buses,
shown as communication bus 150.
Computer 101 as shown in FIG. 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 interfaces 118 may include one or more interfaces to
enable computer 101 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, the computing device 101 may execute an
application on behalf of a user of a client computing device. For
example, the computing device 101 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. The computing device 101 may also execute a
terminal services session to provide a hosted desktop environment.
The computing device 101 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.
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 mobility technical architecture
200, which can include an access gateway 260 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 device 204 (e.g., a mobile or other device) to both
access enterprise or personal resources from a client device 202,
and use the client device 204 for personal use. The user may access
such enterprise resources 204 or enterprise services 208 via a
client application executing on the client device 204. The user may
access such enterprise resources 204 or enterprise services 208
using a client device 204 that is purchased by the user or a client
device 202 that is provided by the enterprise to user. The user may
utilize the client device 202 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 device 204.
The policies may be implemented 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 device 204 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 managed partition 210 and an unmanaged
partition 212. The managed partition 210 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 a secure application launcher 218. The
secure applications may be secure native applications 214, secure
remote applications 222 executed by the secure application launcher
218, virtualization applications 226 executed by the secure
application launcher 218, and the like. The secure native
applications 214 may be wrapped by a secure application wrapper
220. The secure application wrapper 220 may include integrated
policies that are executed on the client device 202 when the secure
native application is executed on the device. The secure
application wrapper 220 may include meta-data that points the
secure native application 214 running on the client device 202 to
the resources hosted at the enterprise that the secure native
application 214 may require to complete the task requested upon
execution of the secure native application 214. The secure remote
applications 222 executed by a secure application launcher 218 may
be executed within the secure application launcher application 218.
The virtualization applications 226 executed by a secure
application launcher 218 may utilize resources on the client device
202, at the enterprise resources 204, and the like. The resources
used on the client device 202 by the virtualization applications
226 executed by a secure application launcher 218 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
the enterprise resources 204, and the like. The resources used at
the enterprise resources 204 by the virtualization applications 226
executed by a secure application launcher 218 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 a secure data
container 228 in the managed partition 210 of the client device.
The data secured in the secure data container may be accessed by
the secure wrapped applications 214, applications executed by a
secure application launcher 222, virtualization applications 226
executed by a secure application launcher 218, and the like. The
data stored in the secure data container 228 may include files,
databases, and the like. The data stored in the secure data
container 228 may include data restricted to a specific secure
application 230, shared among secure applications 232, and the
like. Data restricted to a secure application may include secure
general data 234 and highly secure data 238. 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
data 238 may use a very strong form of encryption such as AES
256-bit encryption. Data stored in the secure data container 228
may be deleted from the device upon receipt of a command from the
device manager 224. The secure applications may have a dual-mode
option 240. The dual mode option 240 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 an unsecured data container
242 on the unmanaged partition 212 of the client device 202. The
data stored in an unsecured data container may be personal data
244. The data stored in an unsecured data container 242 may also be
accessed by unsecured applications 246 that are running on the
unmanaged partition 212 of the client device 202. The data stored
in an unsecured data container 242 may remain on the client device
202 when the data stored in the secure data container 228 is
deleted from the client device 202. 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 device 202 may connect to enterprise resources 204 and
enterprise services 208 at an enterprise, to the public Internet
248, and the like. The client device may connect to enterprise
resources 204 and enterprise services 208 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
microVPNs 250), particular devices, particular secured areas on the
client device (e.g., as illustrated by O/S VPN 252), 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 processes 254. The single-sign-on processes may
allow a user to provide a single set of authentication credentials,
which are then verified by an authentication service 258. The
authentication service 258 may then grant to the user access to
multiple enterprise resources 204, without requiring the user to
provide authentication credentials to each individual enterprise
resource 204.
The virtual private network connections may be established and
managed by an access gateway 260. The access gateway 260 may
include performance enhancement features that manage, accelerate,
and improve the delivery of enterprise resources 204 to the client
device 202. The access gateway may also re-route traffic from the
client device 202 to the public Internet 248, enabling the client
device 202 to access publicly available and unsecured applications
that run on the public Internet 248. The client device may connect
to the access gateway via a transport network 262. The transport
network 262 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.
The enterprise resources 204 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. The enterprise resources
204 may be premise-based resources, cloud based resources, and the
like. The enterprise resources 204 may be accessed by the client
device 202 directly or through the access gateway 260. The
enterprise resources 204 may be accessed by the client device 202
via a transport network 262. The transport network 262 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 an access gateway 260 and/or enterprise
services 208. The enterprise services 208 may include
authentication services 258, threat detection services 264, device
manager services 224, file sharing services 268, policy manager
services 270, social integration services 272, application
controller services 274, and the like. Authentication services 258
may include user authentication services, device authentication
services, application authentication services, data authentication
services and the like. Authentication services 258 may use
certificates. The certificates may be stored on the client device
202, by the enterprise resources 204, and the like. The
certificates stored on the client device 202 may be stored in an
encrypted location on the client device. The certificate may be
temporarily stored on the client device 202 for use at the time of
authentication, and the like. Threat detection services 264 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
services 224 may include configuration, provisioning, security,
support, monitoring, reporting, and decommissioning services. File
sharing services 268 may include file management services, file
storage services, file collaboration services, and the like. Policy
manager services 270 may include device policy manager services,
application policy manager services, data policy manager services,
and the like. Social integration services 272 may include contact
integration services, collaboration services, integration with
social networks such as Facebook, Twitter, and LinkedIn, and the
like. Application controller services 274 may include management
services, provisioning services, deployment services, assignment
services, revocation services, wrapping services, and the like.
The enterprise mobility technical architecture 200 may include an
application store 278. The application store 278 may include
unwrapped applications 280, pre-wrapped applications 282, and the
like. Applications may be populated in the application store 278
from the application controller 274. The application store 278 may
be accessed by the client device 202 through the access gateway
260, through the public Internet 248, or the like. The application
store may be provided with an intuitive and easy to use User
Interface.
A software development kit 284 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 the software development kit 284 may then be made
available to the client device 202 by populating it in the
application store 278 using the application controller 274.
The enterprise mobility technical architecture 200 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 enterprise
mobility management system 300. Some of the components of the
mobility management system 200 described above with reference to
FIG. 2 have been omitted for the sake of simplicity. The
architecture of the system 300 depicted in FIG. 3 is similar in
many respects to the architecture of the system 200 described above
with reference to FIG. 2 and may include additional features not
mentioned above.
In this case, the left hand side represents an enrolled client
device 302 with a client agent 304, which interacts with gateway
server 306 to access various enterprise resources 308 and services
309 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. The gateway server 306 can include embodiments of features
and functionalities of the cloud services, such as access gateway
260 and application controller functionality. Although not
specifically shown, the client agent 304 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.
The client agent 304 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. The client agent 304 can also support the installation
and management of native applications on the client device 302,
such as native iOS or Android applications. For example, the
managed applications 310 (mail, browser, wrapped application) shown
in the figure above are native applications that execute locally on
the device. Client agent 304 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/services 308. The client agent 304
handles primary user authentication to the enterprise, for instance
to access gateway (AG) with SSO to other gateway server components.
The client agent 304 obtains policies from gateway server 306 to
control the behavior of the managed applications 310 on the client
device 302.
The Secure interprocess communication (IPC) links 312 between the
native applications 310 and client agent 304 represent a management
channel, which allows client agent to supply policies to be
enforced by the application management framework 314 "wrapping"
each application. The IPC channel 312 also allows client agent 304
to supply credential and authentication information that enables
connectivity and SSO to enterprise resources 308. Finally, the IPC
channel 312 allows the application management framework 314 to
invoke user interface functions implemented by client agent 304,
such as online and offline authentication.
Communications between the client agent 304 and gateway server 306
are essentially an extension of the management channel from the
application management framework 314 wrapping each native managed
application 310. The application management framework 314 requests
policy information from client agent 304, which in turn requests it
from gateway server 306. The application management framework 314
requests authentication, and client agent 304 logs into the gateway
services part of gateway server 306 (also known as NetScaler access
gateway). Client agent 304 may also call supporting services on
gateway server 306, which may produce input material to derive
encryption keys for the local data vaults 316, or provide client
certificates which may enable direct authentication to PKI
protected resources, as more fully explained below.
In more detail, the application management framework 314 "wraps"
each managed application 310. This may be incorporated via an
explicit build step, or via a post-build processing step. The
application management framework 314 may "pair" with client agent
304 on first launch of an application 310 to initialize the Secure
IPC channel and obtain the policy for that application. The
application management framework 314 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 the
application 310.
The application management framework 314 may use services provided
by client agent 304 over the Secure IPC channel 312 to facilitate
authentication and internal network access. Key management for the
private and shared data vaults 316 (containers) may be also managed
by appropriate interactions between the managed applications 310
and client agent 304. Vaults 316 may be available only after online
authentication, or may be made available after offline
authentication if allowed by policy. First use of vaults 316 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 managed applications 310 through access gateway 306. The
application management framework 314 is responsible for
orchestrating the network access on behalf of each application 310.
Client agent 304 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 tunnels 318.
The Mail and Browser managed applications 310 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 server 306 (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 wherein gateway server 306 may
identify managed native applications 310 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 vaults 316 (containers) on the client device 302. The vaults
316 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 server 306), 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 the device 302 in the secure
container 316, it is preferred that a minimum of AES 256 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 an application 310 are logged and reported
to the backend. Data wiping may be supported, such as if the
application 310 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 is 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 the application management framework 314 may be
prevented in other ways. For example, when an application 310 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 an OTP 320 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 an OTP 320. 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 those applications 310 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, the client agent 304
may require the user to set a custom offline password and the AD
password is not used. Gateway server 306 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 for certain applications 310 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 the client agent 304 may be
retrieved by gateway server 306 and used in a keychain. Each
managed application may have one associated client certificate,
identified by a label that is defined in gateway server 306.
Gateway server 306 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.
The client agent 304 and the application management framework 314
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 a client device 302 is authenticated to
the enterprise, and vice versa. Virtual smart cards for
authentication to gateway server 306 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 an
application 310 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, managed applications 310 may be allowed to access a
certificate and private key via an API (example OpenSSL). Trusted
managed applications 310 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 to FIG. 4, depicted is a block diagram of a system
400 of an embedded browser. In brief overview, the system 400 may
include a client device 402 with a digital workspace for a user, a
client application 404, cloud services 408 operating on at least
one network device 432, and network applications 406 served from
and/or hosted on one or more servers 430. The client application
404 can for instance include at least one of: an embedded browser
410, a networking agent 412, a cloud services agent 414, a remote
session agent 416, or a secure container 418. The cloud services
408 can for instance include at least one of: secure browser(s)
420, an access gateway 422 (or CIS, e.g., for registering and/or
authenticating the client application and/or user), or analytics
services 424 (or CAS, e.g., for receiving information from the
client application for analytics). The network applications 406 can
include sanctioned applications 426 and non-sanctioned applications
428.
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 200 may be implemented
using hardware or a combination of hardware or software detailed
above in connection with FIG. 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 the client device 402, the at
least one network device 432 and/or the one or more servers 430.
The hardware includes circuitry such as one or more processors in
one or more embodiments. For example, the at least one network
device 432 and/or the one or more servers 430 can include any of
the elements of a computing device described above in connection
with at least FIG. 1 for instance.
The client device 402 can include any embodiment of a computing
device described above in connection with at least FIG. 1 for
instance. The client device 402 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. The client device
402 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 the client device 402. The digital workspace can include or
extend to one or more networks accessible by the client device 402,
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 the
client application 404 with embedded browser 410 (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).
The client application 404 can include one or more components, such
as an embedded browser 410, a networking agent 412, a cloud
services agent 414 (sometimes referred to as management agent), a
remote session agent 416 (sometimes referred to as HDX engine),
and/or a secure container 418 (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 the client application 404
or CEB, or separately acquired or downloaded and
installed/integrated into an existing installation of the client
application 404 or CEB for instance. For instance, the client
device may download or otherwise receive the client application 404
(or any component) from the network device(s) 432. In some
embodiments, the client device may send a request for the client
application 404 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 agent 414) 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 embedded browser 410 can include elements and functionalities
of a web browser application or engine. The embedded browser 410
can locally render network application(s) as a component or
extension of the client application. For instance, the embedded
browser 410 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 a secured container 418, 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 the secured container 418. 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 the client application 404, such as the cloud
services agent 414, remote session agent 416 and/or secure
container 418. For instance, a user can use the cloud services
agent 414 of the embedded browser to interoperate with the access
gateway 422 (sometimes referred to as CIS) to access a network
application. For example, the cloud services agent 414 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, the cloud services agent 414
can include a HTML5 web client that allows end users to access
remote desktops and/or applications on the embedded browser.
The client application 404 and CEB operates on the application
layer of the operational (OSI) stack of the client device. The
client application 404 can include and/or execute one or more
agents that interoperate with the cloud services 408.
For example, the cloud services agent 414 can convey or feed
information to analytics services 424 of the cloud services 408,
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, the
cloud services agent 414 does not execute within the embedded
browser. In these embodiments, a user can similarly use the cloud
services agent 414 to interoperate with the access gateway (or CIS)
422 to access a network application. For instance, the cloud
services agent 414 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. The cloud
services agent 414 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, the cloud services agent 414 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, the cloud
services agent 414 can include a HTML5 web client that allows end
users to access remote desktops and/or applications on the embedded
browser.
In some embodiments, the cloud services agent 414 provides single
sign on (SSO) capability for the user and/or client device to
access a plurality of network applications. The cloud services
agent 414 can perform user authentication to access network
applications as well as other network resources and services, by
communicating with the access gateway 422 for instance. For
example, the cloud services agent 414 can authenticate or register
with the access gateway 422, to access other components of the
cloud services 408 and/or the network applications 406. Responsive
to the authentication or registration, the access gateway 422 can
perform authentication and/or SSO for (or on behalf of) the user
and/or client application, with the network applications.
In some embodiments, the cloud services agent 414 provides policy
driven management capabilities and features related to the use
and/or access of network applications. For example, the cloud
services agent 414 can include a policy engine to apply one or more
policies to determine access control and/or connectivity to
resources such as network applications. When a session is
established between the client application and a server 430
providing a SaaS application for instance, the cloud services agent
414 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.
The client application 404 can include a networking agent 412. The
networking agent 412 is sometimes referred to as a software-defined
wide area network (SD-WAN) agent, mVPN agent, or microVPN agent.
The networking agent 412 can establish or facilitate establishment
of a network connection between the client application and one or
more resources (e.g., server 430 serving a network application).
The networking agent 412 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). The networking agent 412 can
connect to enterprise resources (including services) for instance
via a virtual private network (VPN). For example, the networking
agent 412 can establish a secure socket layer (SSL) VPN between the
client application and a server 430 providing the network
application 406. 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 with FIG. 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 agent 416 (sometimes referred to as HDX engine)
can include features of the client agent 304 discussed above in
connection with FIG. 2 for instance, to support display a remoting
protocol (e.g., HDX or ICA). In some embodiments, the remote
session agent 416 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, the remote session agent 416 can establish a
remote application session for a user of the client device to
access an enterprise network application. The remote session agent
416 can establish the remote application session within or over a
secure connection (e.g., a VPN) established by the networking agent
412 for instance.
The client application or CEB can include or be associated with a
secure container 418. 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, the secure container 418 can refer to the entirety of
the secured portion of the digital workspace, or particular
aspect(s) of the secured portion. In some embodiments, the secure
container 418 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 the secure data container 228 discussed above in
connection with FIG. 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., embedded browser 410 or secure
browser 420) 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.
The network applications 406 can include sanctioned network
applications 426 and non-sanctioned network applications 428. By
way of a non-limiting example, sanctioned network applications 426
can include network applications from Workday, Salesforce, Office
365, SAP, and so on, while non-sanctioned network applications 426
can include network applications from Dropbox, Gmail, and so on.
For instance, FIG. 4 illustrates a case where sanctioned
applications 426 are accessed via a CEB. In operation (1), a user
instance of a client application 404, that is installed on client
device 402, can register or authenticate with the access gateway
422 of cloud services 408. For example, the user can authenticate
the user to the client device and login to the client device 402.
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 the access gateway 422.
In operation (2), in response to the registration or
authentication, the access gateway 422 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., the networking agent
412 and/or the remote session agent 416) 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 the servers
430.
In operation (6), the client application can provide information to
the analytics services 424 of cloud services 408, for analytics
processing. For example, the cloud services agent 414 of the client
application 404 can monitor for or capture user interaction events
with the selected network application. The cloud services agent 414
can convey the user interaction events to the analytics services
424, 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 includes cloud services 408,
network applications 406 and client device 402. In some
embodiments, various elements of the system are similar to that
described above for FIG. 4, but that the client application (with
embedded browser) is not available in the client device 402. 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 a network device 432 of the cloud
services 408 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 services 408. 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 the server 430.
In operation (3), the gateway service and/or the server can direct
(or redirect) all traffic to a secure browser 420 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 the secure browser 420. The
secure browser 420 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 the secure browser 420 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 the secure browser 420 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 the
secure browser 420. 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, the secured browser 420 comprises a browser
that is hosted on a network device 432 of the cloud services 408.
The secured browser 420 can include one or more features of the
secured browser 420 described above in connection with at least
FIG. 4 for instance. The hosted browser can include an embedded
browser of a CEB that is hosted on the network device 432 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 the network device 432. 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 a web browser 512 with a secure browser
plug-in 516 operating on a client device, and a hosted web browser
(or secure browser) 522 residing on a network device. The web
browser 512 can correspond to a standard browser, instead of an
embedded browser as discussed above in connection with FIG. 4 for
example. The secure browser plug-in 516 can execute within a first
network 510 and access a server 532 in a second network 530. The
first network 510 and the second network 530 are for illustration
purposes and may be replaced with fewer or additional computer
networks. A secure browser plug-in 516 can be installed on the
standard browser 512. 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-in 516, 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 the secured browser 420 for securing, using
and/or accessing resources within the secured portion of the
digital workspace.
By using the secure browser plug-in 516 operating within the
standard browser 512 network applications accessed via the standard
browser 512 can be redirected to a hosted secure browser. For
instance, the secure browser plug-in 516 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-in 516 and/or a client agent 514 for rendering and/or display
for example. The client agent 514 can execute within the web
browser 512 and/or the secure browser plug-in, and can include
certain elements or features of the client application 404
discussed above in connection with at least FIG. 4 for example. For
instance, the client agent 514 can include a remote session agent
418 for rendering the network application at the web browser 512.
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-in 516 and/or the client agent
514 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 the standard browser 512 executing in the first network
510, in which the first network 510 may comprise an unsecure
network. The server 430 that the user wants to access may be on the
second network 530, in which the second network 530 comprises a
secure corporate network for instance. The user might not be able
to access the server 430 from the unsecure first network 510 by
clicking on an internal uniform record locator (URL) for the secure
website 532. That is, the user may need to utilize a different URL
(e.g., an external URL) while executing the standard browser 512
from the external unsecure network 510. The external URL may be
directed to or may address one or more hosted web browsers 522
configured to access server(s) 430 within the second network 530
(e.g., secure network). To maintain secure access, the secure
browser plug-in 516 may redirect an internal URL to an external URL
for a hosted secure browser.
The secure browser plug-in 516 may be able to implement network
detection in order to identify whether or not to redirect internal
URLs to external URLs. The standard browser 512 may receive a
request comprising an internal URL for a web site executing within
the secure network. For example, the standard browser 512 may
receive the request in response to a user entering a web address
(e.g., for secure website 532) in the standard browser. The secure
browser plug-in 516 may redirect the user web browser application
512 from the internal URL to an external URL for a hosted web
browser application. For example, the secure browser plug-in 516
may replace the internal URL with an external URL for the hosted
web browser application 522 executing within the secure network
530.
The secure browser plug-in 516 may allow the client agent 514 to be
connected to the hosted web browser application 522. The client
agent 514 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 the standard
browser 512. For example, the client agent 514 may comprise an
ActiveX control loaded and run by a standard browser 512, such as
in the memory space or context of the user web browser application
512. The client agent 514 may be pre-configured to present the
content of the hosted web browser application 522 within the user
web browser application 512.
The client agent 514 may connect to a server or the cloud/hosted
web browser service 520 using a thin-client or remote-display
protocol to present display output generated by the hosted web
browser application 522 executing on the service 520. 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 hosted web browser application 522 may navigate to the
requested network application in full-screen mode, and can render
the requested network application. The client agent 514 may present
the content or rendition of the network application on the web
browser application 512 in a seamless and transparent manner such
that it appears that the content is being displayed by the standard
browser 512, e.g., based on the content being displayed in full
screen mode. In other words, the user may be given the impression
that the website content is displayed by the user web browser
application 512 and not by the hosted web browser application 522.
The client agent 514 may transmit navigation commands generated by
the user web browser application 512 to the hosted web browser
application 522 using the thin-client or remote-display protocol.
Changes to the display output of the hosted web browser application
522, due to the navigation commands, may be reflected in the user
web browser application 512 by the client agent 514, giving the
impression to the user that the navigation commands were executed
by the user web browser application 512.
Referring again to FIG. 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 with FIG. 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 includes cloud
services 408, network applications 406 and the client device 402.
In some embodiments, various elements of the system are similar to
that described above for FIG. 5. A client application with embedded
browser is not available in the client device 402. A standard or
typical (e.g., HTML5) 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 a network device 432 of the
cloud services 408 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 in FIG. 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 the secure browser 420. The
secure browser 420 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 the cloud services
408, 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 the server
430. 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 with FIGS. 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 browsers 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 to FIG. 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 of client
devices 402A, 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 in FIGS. 4, 5 and 7 can be used to
support each 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 in FIG. 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, in operation 901, a HTTP client can attempt to access a
web service (e.g., server of a network application). In operation
903, the web service can redirect the HTTP client to a gateway
service for authentication. In operation 905, the gateway service
can determine if the HTTP client is a CEB. If so, in operation 909,
the gateway service can determine if the CEB is a suitable CEB,
e.g., capable of enforcing defined application policies. If so, in
operation 911, 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., a network
device 432 of cloud services 408), in operation 907. In some
embodiments, such a hosted CEB may already be available on a
network device 432, and can be selected for use. For example in
operation 911, 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., a network device 432 of cloud services
408), in operation 907. In some embodiments, such a hosted CEB may
already be available on a network device 432, and can be selected
for use. For example in operation 911, 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.
At operation 905 and/or operation 909 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 to FIG. 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 least FIGS.
7 and 5.
C. Systems and Methods for Providing Data Loss Prevention Via
Embedded Browsers
A client application with an embedded browser (CEB) may be used to
access applications and resources hosted on various servers. These
applications may include, for example, web applications accessed
via the browser, cloud hosted applications (e.g., as part of
Software as a Service (SaaS), Infrastructure as a Service (IaaS),
and Platform as a Service (PaaS)), and virtual applications hosted
on a virtual machine, among others. Data accessed via the
applications may be selected and stored on a temporary data cache
or buffer, and then replicated onto other applications as part of a
copy-and-paste operation. Without any additional controls, however,
data security may be compromised, with potentially sensitive
information leaked from the applications.
To prevent such lapses in data security, access to data on
applications and resources hosted on servers may be restricted
through the CEB. Within the CEB, a copy command along with selected
data (e.g., text or images) from one application may be received
via activation of a copy button of the CEB or a preset keystroke
(e.g., CTRL+C). Instead of or in addition to storing the selected
content into a local operating system (OS) clipboard, the data may
be stored in a secure container. The secure container may cache the
data and can encrypt the data using a cryptographic key. The secure
container may reside in a cache of the CEB locally at the client
and/or remotely on one of the servers hosting the applications or a
cloud-based service. When the secure container resides remotely,
the data and the cryptographic key used to encrypt the data may be
shared between multiple client devices (e.g., that the user has
signed into).
Another application may be subsequently accessed through the CEB.
When a paste command is then received on the subsequent application
using a paste button of the CEB or a preset keystroke (e.g.,
CTRL+V), the application may be checked against a data loss
prevention policy. The policy may specify which applications
accessed via the CEB, which device types running the CEB, which
user accounts, and/or which location at which the client running
the CEB, among other considerations, have permission to the data
maintained on the secure container. The policy may also specify
whether sensitive information contained the data is to be removed,
even if there is permission to access. If the policy permits the
subsequent application to access the secure container, data
maintained in the stored container can be retrieved and replicated
onto or provided to the application. In addition, if the policy
specifies that the sensitive information contained in the data is
to be redacted for the subsequent application, the data may be
parsed to determine whether the data contains any sensitive data,
and portions of the data may be redacted in accordance with the
policy. In this manner, data loss prevention may be achieved and
data security may be enhanced.
Referring to FIG. 11, depicted is a block diagram of a system 1100
for managing interprocess communications of applications running
across networked environments. The system 1100 may include one or
more client applications 404A-N and a set of network applications
1105 on a cloud (e.g., provisioned by servers 430). Each client
application 404A-N may be an instance of the client application 404
previously detailed herein, and may include an embedded browser
410A-N and a secure container 418A-N, among other components. In
some embodiments, the client applications 404A-N may execute on
different client devices associated with a single user account. In
some embodiments, at least two of the client applications 404A-N
may execute on a single client device, and may be associated with a
single digital workspace and/or user account. The network
application 1105 may correspond to a cloud-based service for an
electronic clipboard, and can include an interprocess communication
(IPC) manager 1110, one or more applications 1115A-N, and a secure
container 1120. The network application 1105 can be part of cloud
services 408 as described above in connection with at least FIGS.
4-5 for instance.
Each application 1115A-N may include the sanctions applications 426
and the non-sanctioned applications 428 of the network applications
406 as previously detailed herein. The IPC manager 1110 may include
a data transfer engine 1130, a policy enforcer engine 1135, a data
analysis engine 140, and/or a policy 1145. In some embodiments, the
IPC manager 1110 may reside on one or more servers or a cloud-based
resource with the network application 1105. In some embodiments,
the IPC manager 1110 may reside on each client application 404A-N
(e.g., as part of the embedded browser 410A-N). In some
embodiments, the functionalities of the IPC manager 1110 may be
divided between the client application 404A-N and the network
applications 1105, e.g., in the form of an IPC agent executing in
each client application 404A-N.
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 1100 may be implemented
using hardware or a combination of hardware or software detailed
above in connection with FIG. 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 applications 404A-N) or one or more servers (e.g., network
applications 1105). The hardware includes circuitry such as one or
more processors in one or more embodiments.
Each of the secure container 1120, 418 can include embodiments of
elements of the secure container 316, 418 described above in
connection with at least FIGS. 3 and 4. Each of the secure
container 1120, 418 can include an electronic, digital or virtual
clipboard (e.g., rolling clipboard), cache or buffer. In some
embodiments, the secure containers 1120, 418 are implemented to
operate in place of, or independently of a client device's
operating system (OS) clipboard. In some embodiments, the client
applications 404A-N can have one or more policies that control
whether data can be transferred or shared between any of the secure
containers 1120, 418 and a client device's OS clipboard.
The data transfer engine 1130 may detect a command to copy data
1125 accessed on a first application 1115A (sometimes referred to
as a source application) via a first embedded browser 410A of a
first client application 404A. In some embodiments, the data
transfer engine 1130 may detect the command to copy the data 1125
via an interaction event listener, the command activated via a copy
user interface element (e.g., a copy button) on the first embedded
browser 410A of the first client application 404A. In some
embodiments, the data transfer engine 1130 may detect the command
to copy the data 1125 via an interaction event listener, the
command activated via a preset keystroke (e.g., CTRL+C). In some
embodiments, the copy user interface element and/or preset
keystroke are implemented as features particular to the embedded
browser 410A of the first client application 404A, so as to
differentiate from and operate independently from the client
device's operating system (OS) clipboard. Upon detection of the
command to copy, the data transfer engine 1130 may identify the
data 1125 to be copied from the first application 1115A. In some
embodiments, the data transfer engine 1130 may identify the
selected data 1125 to be copied (e.g., via highlighting). The data
1125 may include, for example, text, an image, a video, an audio
clip, or a file of any format (e.g., .DOC, .XLS, .AVI, or .TXT). In
some embodiments, the data transfer engine 1130 can generate
metadata of the data 1125 to be copied. For instance, the metadata
may include or identify a data type of the data 1125 to be copied
(e.g., text, image, video, or file format). The data transfer
engine 1130 may store the metadata with the data 1125 onto the
secure container 1120. In some embodiments, the data transfer
engine 1130 may identify an identifier for the first embedded
browser 410A, an identifier for the first client application 404A,
or an identifier for the first application 1115A, in connection
with the command to copy. These information can be used for
instance by a user to identify or determine which corresponding
data 1125 to retrieve subsequently from the secure container 1120.
With the identification of the data 1125 from the first application
1115A, the data transfer engine 1130 may store the data 1125 onto
the secure container 1120. In some embodiments, the data transfer
engine 1130 may store (e.g., as metadata with the data 1125) the
identifier for the first embedded browser 410A, the identifier for
the first client application 404A, or the identifier for the first
application 1115A onto the secure container 1120. The data transfer
engine 1130 may index the data 1125 by the identifier for the first
embedded browser 410A, the identifier for the first client
application 404A, or the identifier for the first application 1115A
onto the secure container 112. The data transfer engine 1130 or the
first client application 404A may store the data 1125, along with
the identifier for the first embedded browser 410A, the identifier
for the first client application 404A, or the identifier for the
first application 1115A onto the secure container 1120. In some
embodiments, by storing the data 1125 onto a local secure container
418 for transfer between different network applications accessed by
a corresponding client device, less bandwidth may be consumed in
relative to transferring the data 1125 back and forth between the
client device and the cloud (e.g., where the secure container 1120
is hosted).
The data transfer engine 1130 may maintain the data 1125 from the
first application 1115A on the secure container 1120. The secure
container 1120 may include memory (e.g., a data buffer or cache)
and/or disk space on a server dedicated (or assigned or allocated)
to the first application 1105A and/or the first client application
404A. In some embodiments, the data transfer engine 1130 may
encrypt the data 1125 using a cryptographic key. In certain
embodiments, the contents of the entire secure container 1120 is
encrypted or otherwise protected from access. The data transfer
engine 1130 may generate the cryptographic key using asymmetric
cryptographic or symmetric cryptographic algorithms (e.g., public
key cryptography). In some embodiments, the cryptographic key may
be particular to the data 1125 and/or a user. In some embodiments,
the cryptographic key may be used for all data including the data
1125 maintained on the secure container 1120. Having applied the
cryptographic key, the data transfer engine 1130 may store the
encrypted data 1125 and/or the cryptographic key on the secure
container 1120. The data transfer engine 1130 may also store
metadata such as the identifier for the first embedded browser
410A, the identifier for the first client application 404A, and/or
the identifier for the first application 1115A indexing the data
1125 with the cryptographic key onto the secure container 112. In
some embodiments, the data transfer engine 1130 may also store the
data type of the data 1125 along with the data 1125 onto the secure
container 1120. In some embodiments, the data transfer engine 1130
or the first client application 404A may maintain, encrypt, copy
and/or store the data 1125 onto the local secure container
418A.
The data transfer engine 1130 may continue to maintain, for at
least a predetermined period of time, the data 1125 on the secure
container 1120 for future replication, even after termination of
the first client application 404A, the first embedded browser 418A
of the first client application 404A, or the first application
1115A accessed via the first embedded browser 410A. In some
embodiments, the termination of the first client application 404A
or the first embedded browser 418A may occur in connection with or
may correspond to a termination of a user session (e.g., logging
off). The termination of the first application 1115A may occur in
connection with or may correspond to the termination of the user
session (e.g., logging off or navigating to another application
1115B-N). In some embodiments, the termination of the first client
application 404A or the first embedded browser 418A may occur in
connection with or may correspond to a shutting down of the client
device running the first client application 404A. In some
embodiments, the data transfer engine 1130 may detect the
termination of the first client application 404A, the first
embedded browser 418A of the first client application 404A, or the
first application 1115A. Upon detecting the termination, or prior
to the termination, the data transfer engine 1130 may store an
account identifier and/or other account information (e.g., a user
profile and/or biometric information for login) associated with the
command to copy the data 1125 onto the secure container 1120. In
some embodiments, when the data 1125 is stored in the local secure
container 418A, the data transfer engine 1130 may (e.g.,
automatically) retrieve the data 1125 from the local secure
container 418A and store the data 1125 on the secure container
1120. The data transfer engine 1130 can back-up or synchronize the
data 1125 across one or more local secure containers 418A and the
secure container 1120 (e.g., when each local secure containers
418A-N is online or otherwise connected with the secure container
1120). For example, when a user signs/logs into, or uses a client
device, the CEB on that client device can retrieve and/or match to
a user profile for the user, and connect the local secure container
418 to a corresponding secure container 1120 (or portion thereof)
assigned or linked to the same user profile (or user). The local
secure container 418 can be synchronized with the corresponding
secure container 1120, on data maintained for the user or user
profile. This synchronization can occur in the background, e.g.,
before a request for any of the data is issued locally on the
client device. In some embodiments, a requested data is transferred
from the secure container 1120 upon local request, and applied to
the local secure container 418 and/or to a destination
application/location. In this manner, the data 1125 may be accessed
from the secure container 1120 across multiple client applications
404A-N and multiple client devices running the client applications
404A-N. Additionally, the data 1125 maintained on the secure
container 1120 may be accessed by the user and/or other
applications 1115A-N in future user sessions.
Subsequent to detection of the command to copy from the first
application 1115A, the data transfer engine 1130 may detect a
command to replicate (e.g., paste, enter, input or load) the data
1125 onto a second application 1115B (sometimes referred to as a
target application). In some embodiments, the second application
1115B may be the same (e.g., type and/or version) as, or may differ
from the first application 1115A. In some embodiments, the data
transfer engine 1130 may detect the command to replicate the data
1125 via an interaction event listener, initiated on a client
device using a copy user interface element. In some embodiments,
the data transfer engine 1130 may detect the command to replicate
the data 1125 via an interaction event listener, initiated on a
client device via a preset keystroke (e.g., CTRL+V). In some
embodiments, the copy user interface element and/or present
keystroke is implemented specifically for the embedded browser 410
of a client device. In some embodiments, the second application
1115B may be accessed from the first embedded browser 410A of the
first client application 404A which is the same as the first
application 1115A. In some embodiments, the second application
1115B may be accessed from a second embedded browser 410B of a
second client application 404B. The second embedded browser 410B
may be running on a client device different from a client device
running the first embedded browser 410A. The client device running
the first embedded browser 410A may be of a different device type
from the client device running the second embedded browser 410B.
For example, the client device executing the first embedded browser
410A may be a laptop, while the client device running the second
embedded browser 410B may be a smartphone. In some embodiments, the
first client application 404A and the second client application
404B may be accessed using a single user account and/or under a
same user profile. For example, a user may have logged into both
the first client application 404A to access the first application
1115A and the second client application 404B to access the second
application 1115B, using a single account identifier and an account
passcode. In some embodiments, the first client application 404A
and the second client application 404B may be accessed under
different user accounts. The different user accounts may be part of
a user share group. For example, a first user may have logged into
the first client application 404A and a second user may have logged
into the second client application 404B using respective user
accounts tied via the user share group. In view of the foregoing,
the data 1125 may be shared among different client applications,
client devices and/or user accounts/profiles.
Upon receipt of the command to replicate the data 1125 to the
second application 1115B, the data transfer engine 1130 may
identify the data 1125 maintained on the secure container 1120. In
some embodiments, when the data 1125 is stored at the local secure
container 418A of the first client application 404A, the data
transfer engine 1130 may identify the data 1125 from the local
secure container 418A for replication onto the second application
1115B. In this manner, the policy enforcer engine 1135 may allow
for peer-to-peer transfer of the data 1125. In some embodiments,
when the data 1125 is stored at the local secure container 418A of
the first client application 404A, the data transfer engine 1130
may retrieve the data 1125 from the local secure container 418A and
may store the data 1125 on the secure container 1120. In some
embodiments, for identification and/or replication of the data
1125, the data transfer engine 1130 may identify the identifier for
the first embedded browser 410A, the identifier for the first
client application 404A, the identifier for the first application
1115A, and/or the data type of the data 1125 from the secure
container 1120 or the local secure container 418A. The data
transfer engine 1130 may also identify the identifier for the
second application 1115B, a device type of the client device
accessing the second application 1115B, a location of the client
device, and/or an account identifier used to access the second
application 1115B in connection with the command to replicate the
data 1125.
Once the data 1125 is identified, the policy enforcer engine 1135
may apply the policy 1145 in replicating the data 1125. The policy
1145 may specify whether the data 1125 on the secure container 1120
or 418A from one application (e.g., the first application 1115A) is
permitted to be replicated on another application (e.g., the second
application 1115B). In some embodiments, the policy 1145 may be
particular to a source application of the data 1125, such as the
first application 1115A, the first client application 404A, or the
first embedded browser 410A. In some embodiments, the policy 1145
may specify which destination applications 1115B-N are permitted to
replicate the data 1125. In some embodiments, the policy 1145 may
specify which device types of the client accessing the second
application 1115B are permitted to replicate the data 1125. In some
embodiments, the policy 1145 may specify which data types of the
data 1125 permitted to be replicated to the second application
1115B. The policy 1145 may also be context-specific in specifying
whether the replication of the data 1125 is to be permitted. In
some embodiments, the policy 1145 may specify locations from which
the client accessing the second application 1115B are permitted to
replicate the data 1125. In some embodiments, the policy 1145 may
specify which account identifiers with which the second application
1115B is accessed are permitted to replicate the data 1125. In some
embodiments, the policy 1145 may specify whether one or more
portions of the data 1125 are to be altered or removed (e.g.,
redacted, obscured, blacked-out, deleted) prior to replication onto
the second application 1115B.
In accordance with the policy 1145, the policy enforcer engine 1135
may determine whether the data 1125 is to be replicated onto the
second application 1115B. In some embodiments, the policy enforcer
engine 1135 may check the identifier for the first embedded browser
410A, the identifier for the first client application 404A, the
identifier for the first application 1115A, the data type of the
data 1125, and/or the identifier for the second application 1115B
against the policy 1145. In some embodiments, using the identifier
for the first application 1115A, the identifier for the first
embedded browser 410A, or the identifier for the first client
application 404A, the policy enforcer engine 1135 may identify the
policy 1145 particular to the source application (including the
first application 1115A, the first embedded browser 410A, or the
first client application 404A).
Using the identifier for the second application 1115B, the policy
enforcer engine 1135 may determine whether the second application
1115B is permitted to replicate the data 1125 under the policy
1145. If the policy 1145 specifies that the replication of the data
1125 onto the second application 1115B is not permitted, the policy
enforcer engine 1135 may restrict the replication of the data 1125
onto the second application 1115B. In some embodiments, the policy
enforcer engine 1135 may send a message to the client application
404A or 404B accessing the second application 1115B indicating that
the data 1125 is not allowed to be replicated. The client
application 404A or 404B may in turn cause the embedded browser
410A or 410B accessing the second application 1115B to display a
prompt notifying that the data 1125 is not permitted to be
replicated onto the second application 1115B. On the other hand, if
the policy 1145 specifies that the replication of the data 1125
onto the second application 1115B is permitted, the policy enforcer
engine 1135 may allow the data 1125 to be replicated onto the
second application 1115B (e.g., without issuing a notification or
alert) and/or perform additional checks with the policy 1145.
The policy enforcer engine 1135 may check the device type of the
client device accessing the second application 1115B against the
policy 1145. If the policy 1145 specifies that the replication of
the data 1125 is not permitted with the device type of the client
device accessing the second application 1115B, the policy enforcer
engine 1135 may restrict the replication of the data 1125 onto the
second application 1115B. In some embodiments, the policy enforcer
engine 1135 may send a message to the client application 404A or
404B accessing the second application 1115B indicating that the
data 1125 is not allowed to be replicated. The client application
404A or 404B may in turn cause the embedded browser 410A or 410B
accessing the second application 1115B to display a prompt
notifying that the data 1125 is not permitted to be replicated onto
the second application 1115B. On the other hand, if the policy 1145
specifies that the replication of the data 1125 is permitted with
the device type of the client device accessing the second
application 1115B, the policy enforcer engine 1135 may allow the
data 1125 to be replicated onto the second application 1115B or
perform additional checks with the policy 1145.
The policy enforcer engine 1135 may check the data type of the data
1125 against the policy 1145. If the policy 1145 specifies that the
data 1125 of the data type is not permitted to be replicated onto
the second application 1115B, the policy enforcer engine 1135 may
restrict the replication of the data 1125 onto the second
application 1115B. In some embodiments, the policy enforcer engine
1135 may send a message to the client application 404A or 404B
accessing the second application 1115B indicating that the data
1125 is not allowed to be replicated. The client application 404A
or 404B may in turn cause the embedded browser 410A or 410B
accessing the second application 1115B to display a prompt
notifying that the data 1125 is not permitted to be replicated onto
the second application 1115B. On the other hand, if the policy 1145
specifies that the data 1125 of the data type is permitted to be
replicated onto the second application 1115B, the policy enforcer
engine 1135 may allow the data 1125 to be replicated onto the
second application 1115B and/or perform additional checks with the
policy 1145.
The policy enforcer engine 1135 may check the location of the
client device accessing the second application 1115B against the
policy 1145. If the policy 1145 specifies that the replication of
the data 1125 is not permitted with the location of the client
device accessing the second application 1115B, the policy enforcer
engine 1135 may restrict the replication of the data 1125 onto the
second application 1115B. In some embodiments, the policy enforcer
engine 1135 may send a message to the client application 404A or
404B accessing the second application 1115B indicating that the
data 1125 is not allowed to be replicated. The client application
404A or 404B may in turn cause the embedded browser 410A or 410B
accessing the second application 1115B to display a prompt
notifying that the data 1125 is not permitted to be replicated onto
the second application 1115B. On the other hand, if the policy 1145
specifies that the replication of the data 1125 is permitted with
the location of the client device accessing the second application
1115B, the policy enforcer engine 1135 may allow the data 1125 to
be replicated onto the second application 1115B and/or perform
additional checks with the policy 1145.
The policy enforcer engine 1135 may check the account identifier
used to access the second application 1115B against the policy
1145. As previously discussed, the user account used to access the
first application 1115A from which the data 1125 originated may
differ from the user account used to access the second application
1115B. If the policy 1145 specifies that the replication of the
data 1125 is not permitted with the account identifier used to
access the second application 1115B, the policy enforcer engine
1135 may restrict the replication of the data 1125 onto the second
application 1115B. In some embodiments, the policy enforcer engine
1135 may send a message to the client application 404A or 404B
accessing the second application 1115B indicating that the data
1125 is not allowed to be replicated. The client application 404A
or 404B may in turn cause the embedded browser 410A or 410B
accessing the second application 1115B to display a prompt
notifying that the data 1125 is not permitted to be replicated onto
the second application 1115B. On the other hand, if the policy 1145
specifies that the replication of the data 1125 is permitted with
the account identifier used to access the second application 1115B,
the policy enforcer engine 1135 may allow the data 1125 to be
replicated onto the second application 1115B or perform additional
checks with the policy 1145.
With the determination that the replication of the data 1125 onto
the second application 1115B is restricted, the policy enforcer
engine 1135 may determine whether one or more portions of the data
1125 are to be altered or removed under the policy 1145. The policy
1145 may specify the removal predefined types of information from
the data 1125 prior to replication. In some embodiments, the
predefined types of information may include personally identified
information (PII), such as physical home address, email address,
passport number, vehicle registration plate number, driver's
license number, credit card numbers, telephone number, dollar
amounts, and date of birth, and among others. In some embodiments,
the predefined types of information may include confidential or
restricted information, such as customer information, pricing
information, and so on. In some embodiments, the predefined types
of information may include metadata, sender name, and recipient
name, among others. In some embodiments, the policy enforcer engine
1135 may invoke the data analysis engine 1140 to identify the one
or more portions of the data 1125 are to be altered or removed
prior to replication onto the second application 1115B.
The data analysis engine 1140 may use a model to identify the one
or more portions of the data 1125 to be altered or removed. In some
embodiments, the model may be part of a natural language processing
algorithm. The model may include formats or regular expressions for
the predefined types of information. In some embodiments, the model
may include an artificial neural network with one or more weights.
The data analysis engine 1140 may train the model using a training
dataset. The training dataset may include textual corpus labeled as
correlating to the predefined types of information in the data 1125
to be altered or removed. The textual corpus of the training
dataset may include sample physical home addresses, email
addresses, passport numbers, vehicle registration plate numbers,
driver's license numbers, credit card numbers, telephone numbers,
dollar amounts, and dates of births, other among others. Once the
model is trained, the data analysis engine 1140 may use the model
to parse the data 1125. In parsing the data 1125, the data analysis
engine 1140 may recognize or identify the one or more portions of
the data 1125 as matching one of the predefined types of
information in accordance with the policy 1145. In some
embodiments, the data analysis engine 1140 may assign a score for
the one or more portions of the data 1125 identified as matching
one of the predefined types of information. The score may indicate
a likelihood of match or a security risk measure. If the data 1125
includes strings of text, the one or more portions may each include
a set of characters within the data 1125 identified by the data
analysis engine 1140 as matching the predefined types of
information.
With the one or more portions identified within the data 1125, the
policy enforcer engine 1135 may alter or remove the one or more
portions from the data 1125 in accordance with the policy 11145.
The policy 1145 may specify that the one or more portions from the
data 1125 are to be altered or removed based on the user account
used to access the second application 1115B. In some embodiments,
the policy 1145 may specify that the one or more portions within
the data 1125 are to be preserved, if the user account used to
access the second application 1115B is the same as the user account
used to access the source application for the data 1125. In some
embodiments, the policy 1145 may specify that the one or more
portions within the data 1125 are to be altered or removed, if the
user account used to access the second application 1115B is the
differs from the user account used to access the source application
for the data 1125. The policy 1145 may further specify that the one
or more portions are to be altered or removed if the score is above
a predetermined threshold.
In some embodiments, the policy enforcer engine 1135 may delete the
set of characters corresponding to the one or more portions
identified by the data analysis engine 1140. In some embodiments,
the policy enforcer engine 1135 may replace the set of characters
corresponding to the one or more portions with a predefined string.
In some embodiments, the policy enforcer engine 1135 may add the
predefined string at a pre-specified location within the data 1125
with the one or more portions removed. The predefined string may
include a message indicating that the corresponding portion has
been removed from the data 1125 in accordance with the policy 1145.
In some embodiments, the policy enforcer engine 1135 may send a
message to an administrator of the first application 1115A
indicating an attempted withdrawal or retrieval of sensitive
information. The message may also include the account identifier
used to access the second application 1115B, the identifier of the
second application 1115B, the identifier for the client application
404A or 404B accessing the second application 1115B, and the
identifier for the embedded browser 410A or 414B accessing the
second application 1115B.
When the replication of the data 1125 onto the second application
1115B is determined to be permitted, the data transfer engine 1130
may replicate the data 1125 onto the second application 1115B. The
data transfer engine 1130 may also identify the cryptographic key
used to encrypt the data 1125 from the secure container 1120. Once
identified, the data transfer engine 1130 may decrypt the data 1125
prior to replication onto the second application 1115B. In some
embodiments, the data transfer engine 1130 may copy the text,
image, video, and/or the file corresponding to the data 1125 onto
the second application 1115B. In some embodiments, the data
transfer engine 1130 may insert the data 1125 onto a location
within a graphical user interface of the second application 1115B
accessed via the embedded browser 418A or 418B. In some
embodiments, the data transfer engine 1130 may replicate the data
1125 with the one or more portions removed by the policy enforcer
engine 1135 in accordance with the policy 1145. In this manner, the
IPC manager 1110 may prevent potentially sensitive data from
leaking.
Referring to FIG. 12, depicted is a flow diagram a method 1200 of
managing interprocess communications of applications running across
networked environments. The functionalities of the method 1200 may
be implemented using, or performed by, the components detailed
herein in connection with FIGS. 1-11A. In brief overview, an
interprocess communication (IPC) manager may identify shared data
from a first application (1205). The IPC manager may apply a policy
to the shared data (1210). The IPC manager may remove sensitive
information from the shared data (1215). The IPC manager may permit
replication of the shared data to a second application (1220).
In further detail, the IPC manager may identify shared data from a
first application (1205). The first application may be accessed via
an embedded browser of a client application. The IPC manager may
detect a command to copy the shared data on the first application
accessed via the embedded browser. Upon detecting the command to
copy, the IPC manager may identify the selected data and may store
the selected data onto a secure container. The secure container may
be storage (e.g., memory and/or hard disk) dedicated, assigned or
allocated to the embedded browser. The IPC manager may then
subsequently detect a command to replicate (e.g., paste, enter,
input, load) the shared data onto a second application. The second
application may be accessed via the same embedded browser as the
first application or another embedded browser across different user
accounts and various client applications.
The IPC manager may apply a policy to the shared data (1210). The
policy may specify whether the shared data is permitted to be
replicated onto the second application based on a number of
factors, such as the user account used to access the second
application, a data type of the shared data, a location of the
client accessing the second application, a device of the client
accessing the second application, and the second application
itself, among others. By applying the policy, the IPC manager may
determine whether the data is permitted to be replicated onto the
second application. If the replication of data is determined not to
be permitted, the IPC manager may send a message to the embedded
browser accessing the second application that replication cannot be
carried out.
The IPC manager may remove sensitive information from the shared
data (1215). The policy may also specify removal of one or more
portions from the data, prior to replication. The one or more
portions may correspond to potentially sensitive data (e.g.,
personally identifiable information). The IPC manager may apply
machine learning algorithms such as natural language processing to
identify the one or more portions in the data. A model may be used
for the machine learning algorithm. The model may have been trained
used a training dataset with labeled sample data. Once identified,
the IPC manager may remove the one or more portions in accordance
with the policy.
The IPC manager may permit replication of the shared data to the
second application (1220). If the replication of data is determined
to be permitted, the IPC manager may access the secure container to
retrieve the data. The IPC manager may then replicate the data in
the second application. The data replicated in the second
application may have one or more portions identified as potentially
sensitive removed in accordance with the policy.
Referring now to FIG. 13, depicted is a flow diagram of a method
1300 of managing access to data in secure containers. The
functionalities of the method 1300 may be implemented using, or
performed by, the components detailed herein in connection with
FIGS. 1-12. In brief overview, an embedded browser of the client
application may access to a first network application (1305). An
interprocess communication (IPC) manager of the client application
may detect a command to store data (1310). The IPC manager may
store the data onto a secure container (1315). The IPC manager may
detect a command to access from a second network application
(1320). The IPC manager may apply a policy to accessing the data
(1325). The IPC manager may determine whether to restrict access
(1330). If access is determined to be restricted, the IPC manager
may restrict access of the data (1335). Conversely, if access is
determined to be permitted, the IPC manager may permit access of
the data (1340).
In further detail, an embedded browser (e.g., the embedded browser
410) of the client application (e.g., the client application 404)
may access to a first network application (e.g., the application
1115A) (1305). The client application may provide access to
multiple network applications (e.g., applications 1115A-N). The
embedded browser may provide access to the first network
application via a secure communications channel to exchange data
with a server hosting the first network application. The embedded
browser may send data to the first network application via the
secure communications channel in response to a user interaction on
the embedded browser. Upon receipt of the data from the embedded
browser, the first network application in turn may send data to the
embedded browser via the secure communications. In some
embodiments, the embedded browser may present (e.g., rendering or
playing) the data received from the network application. The data
may be rendered as text or a visual component of the embedded
browser on a display of a client device (e.g., the client device
402). The data may also be played as an audio signal from the
client device (e.g., using a speaker communicatively coupled with
the client device). In some embodiments, the embedded browser may
store and maintain the data received from the network application
via the secure communication channel. For example, the embedded
browser may store files received from the network application.
An interprocess communication (IPC) manager (e.g., the IPC manager
1110) of the client application may detect a command to store data
(e.g., the shared data 1125) (1310). The IPC manager can be part of
the client application or can be accessed by the client
application. In some embodiments, the IPC manager may monitor for
user interactions on the embedded browser in accessing the first
network application using an interaction event listener. For each
detected user interaction, the IPC manager may determine whether
the user interaction corresponds to the command to store the data.
For example, the IPC manager may detect a preset keystroke (e.g.,
CTRL+C) or an interaction with a user interface element (e.g., a
copy button) corresponding to the command to copy. The command to
store may identify the data accessed from the first network
application to be stored. For example, the command to copy may be
for a highlighted portion of text displayed on the embedded browser
in accessing the first network application. When the user
interaction is determined to not correspond to the command to
store, the IPC manager may pass over the user interaction and
continue to monitor for user interactions on the embedded browser.
When the user interaction is determined to correspond to the
command to store, the IPC manager may identify the user interaction
as the detection of the command to store the data.
The IPC manager may store the data onto a secure container (e.g.,
the secure container 418 or 1120) (1315). With the detection of the
command to store, the IPC manager may store the corresponding data
onto the secure container. The secure container may be local to the
client device executing the embedded browser (e.g., local secure
container 418). The secure container may remotely hosted on the
server for one or more first network applications (e.g., remote
secure container 1120). Upon detecting, the IPC manager may
identify the data to be stored as selected in the command to store.
For example, the IPC manager may identify the highlighted files
from the first network application displayed via the embedded
browser in conjunction with the keystrokes CTRL+C. The IPC manager
may copy and store the identified data onto the secure container.
The IPC manager may also encrypt the data stored and maintained on
the secure container. For example, the IPC manager may apply a
cryptographic algorithm with a key onto the data maintained on the
secure container to encrypt the data.
The IPC manager may detect a command to access from a second
network application (e.g., the application 1115B) (1320).
Subsequent to the storage onto the secure container, the IPC
manager may detect the command to access the data stored on the
secure container. The command to access may include a command to
replicate the data onto the second network application (or onto the
original first network application). In some embodiments, the IPC
manager may monitor for user interactions on the embedded browser
in accessing the second network application using an interaction
event listener. For each detected user interaction, the IPC manager
may determine whether the user interaction corresponds to the
command to replicate the data from the secure container. For
example, the IPC manager may detect a preset keystroke (e.g.,
CTRL+V) or an interaction with a user interface element (e.g., a
load or paste button) corresponding to the command to replicate
onto the second network application. The command to replicate may
identify the data accessed from the secure container to be
replicated onto the second network application (or onto the first
network application). When the user interaction is determined to
not correspond to the command to replicate, the IPC manager may
pass over the user interaction and continue to monitor for user
interactions on the embedded browser. When the user interaction is
determined to correspond to the command to replicate, the IPC
manager may identify the user interaction as the detection of the
command to replicate the data from the secure container onto the
second network application.
The IPC manager may apply a policy (e.g., the administrative policy
1145) to accessing the data (1325). Upon detecting the command to
access, the IPC manager may apply the policy in accessing the data.
The policy may specify whether the data maintained on the secure
container from one application (e.g., the first network
application) is permitted to be accessed by or replicated to
another application (e.g., the second network application). In some
embodiments, the policy may specify alteration or removal of one or
more portions of the data. The specification of the policy may be
based on any number of factors, such as a source application, a
destination application, a device type, a data type, a device
location, and an account identifier, among others, or any
combination thereof. The source application may correspond to the
application from which the data stored on the secure container
originates. The destination application may correspond to the
application from which the data on the secure container is to be
accessed or to which the data is to be replicated. The device type
may correspond to a classification of the client device (e.g., a
smart phone, a laptop, and a desktop) executing the embedded
browser attempting to access the data maintained on the secure
container. The data type may correspond to a category of the data
(e.g., text, image, video, or file format) maintained on the secure
container. The device location may correspond to a geographic
location or a network location of the client executing the embedded
browser. The account identifier may correspond to a user account of
the user operating the client used to access the network
application from which the data is to be accessed.
To apply the policy, the IPC manager identify the one or more
factors on which the specifications of the policy may be based. In
some embodiments, the IPC manager may identify the first network
application as the source application for the data stored in the
secure container. In some embodiments, the IPC manager may identify
the second network application as the destination application from
which the data stored on the secure container is to be accessed. In
some embodiments, the IPC manager may identify the device type of
the client device executing the embedded browser through which the
second network application is accessed. In some embodiments, the
IPC manager may identify the data type of the data maintained on
the secure container to be accessed by the command to access. In
some embodiments, the IPC manager may the device location of the
client device running the embedded browser through which the second
network application is accessed. In some embodiments, the IPC
manager may identify the user account authenticated onto the second
network application as the account identifier.
With the identification, the IPC manager may check the factors
against the specifications of the policy. When all the factors
specified by the policy match, the IPC manager may apply the policy
to the data stored in the secure container to manage access. In
some embodiments, the IPC manager may also identify the data from
the secure container to which to apply the policy. On the other
hand, when at least one factor specified by the policy does not
match, the IPC manager may not apply the policy to the data. In
some embodiments, the IPC manager identify another policy to which
to compare against.
The IPC manager may determine whether to restrict access (1330). By
applying the policy, the IPC manager may determine whether to
restrict access to the data maintained on the secure container. As
discussed above, the policy may specify whether the data maintained
on the secure container from one application is permitted to be
accessed by or replicated to another application based on the one
or more factors. In applying, the IPC manager may identify the
specifications of the policy with respect to the identified
factors. When the policy specifies that the access is to be
restricted for the identified factors, the IPC manager may
determine to restrict access to the data maintained on the secure
container. On the other hand, when the policy specifies that access
is to be permitted, the IPC manager may determine to permit access
to the data maintained on the secure container.
If access is determined to be restricted, the IPC manager may
restrict access of the data (1335). In response to the
determination, the IPC manager may block the access of at least a
portion of the data by the second network application. The IPC
manager may also block the replication of at least a portion of the
data onto the second network application. In some embodiments, the
IPC manager may identify the one or more portions to be altered or
removed in accordance with the policy. As discussed above, the
policy may specify one or more portions to be modified or deleted
in accessing the data maintained on the secure container. With the
identification, the IPC manager may alter the portion or may delete
the portion in accordance with the policy. In some embodiments, the
IPC manager may decrypt the data accessed from the secure container
using the cryptographic algorithm and key used to encrypt the data,
prior to the alteration or the removal. Once altered or removed,
the IPC manager may permit access to a remaining portion of the
data by the second network application. In some embodiments, the
IPC manager may permit the replication of the remaining portion of
data from the secure container onto the second network application.
In some embodiments, the IPC manager may present a prompt on the
embedded browser indicating that at least a portion of the data is
altered or removed. The prompt may also indicate the restriction in
replication.
Conversely, if access is determined to be permitted, the IPC
manager may permit access of the data (1340). The IPC manager may
allow the replication of the data stored on the secure container
onto the second network application. For example, the IPC manager
may allow the data from the secure container to be copied and
displayed on a user interface element of the second network
application rendered on the client device via the embedded browser.
In some embodiments, the IPC manager may decrypt the data accessed
from the secure container using the cryptographic algorithm and key
used to encrypt the data. Once decrypted, the IPC manager may allow
the replication of the data onto the second network
application.
Various elements, which are described herein in the context of one
or more embodiments, may be provided separately or in any suitable
subcombination. For example, the processes described herein may be
implemented in hardware, software, or a combination thereof.
Further, the processes described herein are not limited to the
specific embodiments described. For example, the processes
described herein are not limited to the specific processing order
described herein and, rather, process blocks may be re-ordered,
combined, removed, or performed in parallel or in serial, as
necessary, to achieve the results set forth herein.
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.
It will be further understood that various changes in the details,
materials, and arrangements of the parts that have been described
and illustrated herein may be made by those skilled in the art
without departing from the scope of the following claims.
* * * * *