Patent Application
20190098020
Computer systems are designed to execute software applications and processes. While most of these applications are innocuous, some applications, traditionally referred to as malware, are harmful. These malware applications compromise computer systems and render them unsafe for use. The malware applications may even attempt to exfiltrate sensitive information, destroy sensitive data, hold data hostage, spread itself, or perform any number of other malicious activities. Many existing solutions to preventing malware, such as hardware-based firewalls, attempt to block the malware from ever reaching the computing systems that reside behind the firewalls. Elaborate defensive protections are implemented which are often costly and difficult to maintain. Unfortunately, even with these defensive systems in place, malware applications still reach the computer systems and networks lying behind the implemented defensive protections.
Methods and systems are disclosed for preventing malware from contacting a command and control server while still providing an authorized user of computing devices access to untrusted devices, such as those available via the internet. The host computer system may include a memory and a processor. The processor may be configured to implement a workspace and an isolated computing environment. The workspace may be configured to enable operation of a first set of one or more applications or processes via a first memory space. The isolated computing environment may be configured to enable operation of a second set of one or more applications or processes via a second memory space. The isolated computing environment may be configured to authenticate with an authorization device. The isolated computing environment may be a sandboxed computing environment enforced by a sandbox container process that enables the internal isolation firewall. The processor may be configured to isolate the isolated computing environment from the workspace using an internal isolation firewall. The internal isolation firewall may be configured to prevent data from being communicated between the isolated computing environment and the workspace, for example, without an explicit user input.
The processor may be configured to implement one or more mechanisms that prevent malware received by the host computer system from receiving external communications from an external source, the one or more mechanisms configured to prevent control of the malware by the external source. The external communications may include instructions to gather data, instructions to exfiltrate data, instructions to destroy data, instructions to encrypt data, instructions to download additional malware, and/or instructions to execute the additional malware. The one or more mechanisms may be configured to prevent the malware from establishing a command channel with the external source. The one or more mechanisms may include a host-based firewall. When the host computer system is connected to a trusted network, the host-based firewall may be configured to block incoming traffic from other devices on the trusted network. When the host computer system is connected to an untrusted network, the host-based firewall may be configured to block outgoing traffic from and incoming traffic to the workspace of the host computer system. The one or more mechanisms may include the processor being configured to communicate through one or more of a border firewall or a proxy device. When the host computer system is connected to the trusted network, the external communications from the external source to the malware may be prevented by the border firewall and/or the proxy device. When the host computer system is connected to the untrusted network, the external communications from the external source to the malware may be prevented by the host-based firewall.
When malware is received by the workspace, the internal isolation firewall may be configured to prevent the malware from communicating with the external source via the isolated computing environment. The processor may be configured to terminate a browser process operating in the isolated computing environment upon expiration of a predetermined amount of time without receiving or sending data. The processor may be configured to classify network destinations as trusted or untrusted based on one or more of a whitelist comprising a list of trusted network destinations or a blacklist comprising a list of untrusted network destinations.
A system (e.g., such as an internet isolation system) may include a local network, an authorization device, a border firewall, and/or a proxy device. The local network may include a first device and a second device connected thereto. The first device and/or the second device may be a host computer system, as described herein. The authorization device may be configured to receive authentication credential from an isolated computing environment implemented on the first device and/or the second device. The authorization device may be configured to authenticate the isolated computing environment(s) using the received authentication credentials. The border firewall may be configured to prevent unauthorized communication between the local network and untrusted network destinations. The border firewall may be configured to block data received for a session associated with a process operating in the isolated computing environment when the session has been terminated.
The proxy device may be configured to proxy communications between the untrusted network destinations and the isolated computing environment(s). The proxy device may be configured to receive, from an application and or process operating in the authenticated isolated computing environment of the first device, a request to communicate with an untrusted network destination. The proxy device may be configured to allow, based on the authentication of the authenticated isolated computing environment, the application or process operating in the authenticated isolated computing environment to communicate with the untrusted network destination. The proxy device may be configured to receive, from the malware on the workspace of the first device, a request to communicate with an untrusted network destination. The proxy device may be configured to prevent the malware from communicating with the untrusted network destination. The authorization device and the proxy device may be the same device.
Examples described herein are generally directed to providing systems and methods for preventing malware from contacting a command and control server while still providing an authorized user of computing devices access to untrusted devices, such as those available via the internet. A computing device may become infected with malicious code such as malware, often without the knowledge of an authorized user. One operation malware can perform is contacting a command and control server that is under the control of the malware author or administrator. Through the command and control server the malware is able to receive instructions and execute corresponding commands within the infected computer system. The received commands may include such nefarious actions as exfiltrating data, encrypting data in order to hold it hostage, destroying data, propagating throughout a computer system and local network, and other similar activities.
In examples, a process running on a host computer system, which may be connected to a trusted (e.g., secured) network, attempts to communicate with a particular entity. A device on the trusted network determines that the request is utilizing web-based protocols and routes the communication request to a proxy device. The proxy device may be a web proxy, an email proxy, and/or a split DNS. The proxy device may permit (e.g., only permit) communication requests received on an authenticated communication channel or communication requests that are explicitly allowed, blocking other (e.g., all other) requests. Upon determining that the communication request was received on a properly authenticated communication channel or expressly permitted, the proxy device forwards the communication request to the originally requested destination.
In examples, a process running on a host computer system, which may be connected to a trusted (e.g., secured) network, attempts to communicate with a particular entity. A device on the trusted network determines that the request is utilizing a specific service protocol such as email or DNS and routes the communication request to an intermediate device that is configured to specifically handle the service protocol. The intermediate device permits (e.g., only permits) communication requests received on the specified service protocol from predetermined devices, which generally do not include user-based computing devices unless explicitly allowed, blocking other (e.g., all other) requests.
In examples, a process running on a host computer system, which may be connected to a trusted (e.g., secured) network, attempts to communicate with a particular entity. A device on the trusted network determines that the request is utilizing non-standard or otherwise unspecified protocols and routes the communication request to a perimeter firewall (also referred to as a “border firewall”) device. The perimeter firewall device permits (e.g., only permits) communication requests received from predetermined devices on predetermined ports, which generally do not include user-based computing devices unless explicitly allowed, blocking other (e.g., all other) requests.
In examples, a trusted host computer system (also referred to as simply a “host computer system”) attempts to communicate with a particular entity utilizing another host computer system as an intermediate communication device, otherwise known as pivoting or lateral movement communication. Host computer systems permit (e.g., only permit) communication requests received from predetermined devices on predetermined ports, which generally do not include user-based computing devices unless explicitly allowed, blocking other (e.g., all other) requests.
Many times, when malicious users succeed in penetrating a computer network, they attempt to contact a command-and-control server in order to receive instructions and/or download additional payloads. Instructions received from a command-and-control server may include instructions to gather and exfiltrate data, instructions to destroy data, instructions to encrypt and hold data hostage, instructions to download and execute additional malware, and other similar instructions. Command-and-control servers can be particularly dangerous because oftentimes malware is able to communicate system and local network specific information to the command-and-control server. The command-and-control server is then able to provide specific payloads to the malware that are specifically selected to exploit the computer system and local network.
The examples described herein prevent such contact with an external source (e.g., a command and control server) using a variety of different techniques. For instance, the systems herein prohibit direct communication between a host computer system and untrusted network destinations, such as command-and-control servers. Various network devices and/or applications including, but not limited to, routers, firewalls and proxies block or reroute any such attempts. Moreover, the systems herein permit communication between a host computer system and untrusted network destinations via an authenticated communication channel through a proxy device when initiated or approved by a user. The authenticated communication channel, however, originates from within an isolated computing environment (e.g., a sandboxed environment), and as such, is heavily limited in what computer system resources it is able to access and manipulate.
As used herein, host computer systems include any computing device capable of executing software applications and receiving and/or transmitting network communications. Further, a host computer system may also include the operating system and software running in the operating system. Examples of host computer systems include desktop computers, laptop computers, mobile computing devices, and other similar devices. The host computer systems can be thought of additionally or alternatively as “trusted devices,” or “protected, trusted devices”. One will appreciate, however, that not all host computer systems can be generically considered trusted. Instead, as used herein, a trusted host computer system is deemed “trusted” by a network administrator or some similar individual. For example, a network administrator may deem a local network trusted when that local network has implemented specific security protocols that create a security layer between the local network and external networks.
The systems disclosed herein allow communication between a trusted device and untrusted network destinations via a process within an isolated computing environment (e.g., a sandbox environment) running on the trusted device. As used herein, a sandbox environment, also known as a container or sandbox herein, includes its own segregated, protected memory space. Additionally, when a host computer system is connected to a local, trusted network, perimeter (border) firewalls may block direct communication between the trusted device and untrusted network destinations. Additionally or alternatively web proxy devices may block direct communication between the trusted device and untrusted network destinations, unless certain conditions are met, for example, the use of an authenticated channel. A host-based firewall may block direct communication between the trusted device and other trusted devices (e.g. lateral movement). Moreover, an internal isolation firewall (e.g., a sandbox firewall) blocks direct communication between a sandbox environment and the remaining memory space, including the operating system, of the trusted host computer system.
Any communications into or out of the sandbox environment are governed by the sandbox firewall. The sandbox firewall can be thought of additionally or alternatively as a “software-based” firewall, meaning a firewall installed to essentially surround and govern the in/out-bound communications between the sandbox environment and the remaining memory space, including the operating system, of the trusted host system. Thus, a sandbox firewall, or software-based firewall, can be distinguished from an operating system firewall (or “host” firewall) in that the sandbox firewall is meant to regulate the sandbox environment itself.
The host firewall (also referred to herein as “host-based firewall”) governs and/or serves as a barrier to activity (e.g., all activity) between any application on the host computer system and the connected network. The host firewall may be implemented using software that is, at least in some cases, commercially available, such as available from MACAFEE or SYMANTEC. The host firewall may also or alternatively be implemented using software built into the operating system of the host computer system. Additionally or alternatively, the host firewall may be implemented using software that configures and/or implements restrictive ingress and/or egress policies on the host computer system.
Examples herein may include one or more perimeter firewalls, such as a network firewall (also referred to as a “hardware-based” firewall) that governs communications between the host computer system and other computer systems on a network. In examples, the perimeter firewall is integrated with a network router. One will appreciate that the term “firewall” can be understood to include any combination of software and/or hardware components needed to execute the purposes stated herein.
Even if malware is introduced into a network, or onto a host computer system, any attempt to communicate by the malware from the host computer system's trusted environment (e.g. the environment not included within the segregated, protected memory space or sandbox environment) cannot reach an untrusted network destination.
Processor(s) 12 may include one or more of a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGA) circuits, any other type of integrated circuit (IC), a state machine, and/or the like. The Processor(s) 12 may perform data processing, input/output processing, instantiate operating system(s), execute application(s), and/or any other functionality that enables the use of sandbox isolation of one or more applications and/or processes.
Memory 14 may include volatile and/or non-volatile memory. Memory 14 may include read-only memory (ROM), random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as, but not limited to, internal hard disks and removable disks, magneto-optical media, and/or optical media such as CD-ROM disks, and/or digital versatile disks (DVDs), and/or the like. Memory 14 may be configured to store computer readable instructions that when implemented by Processor(s) 12 may cause Processor(s) 12 to implement one or more of the functions or procedures described herein. For example, Memory 14 may be configured to store software code implemented by Processor(s) 12 that instantiate a restricted operating system environment for operation of the sandboxed browser and/or other sandboxed applications(s) and/or process(es). The software may restrict sandbox-based access to one more file descriptors, memory, file system space, etc. For example, the applications and/or processes operating within the sandboxed computing environment may be permitted to certain portions of Memory 14 but may not be allowed access to other portions of Memory 14. As an example, Memory 14 may be partitioned into a first memory space and a second memory space. The first memory space may be configured to enable storage and/or operation of a workspace configured to execute a first set of one or more applications and/or processes running on the operating system of the Host Computer System 10. The second memory space may be configured to enable storage and/or operation of a second set of one or more applications and/or processes running within the sandboxed computing environment. The sandboxed computing environment may be enforced via a sandbox container process. The sandbox container process may segregate the workspace associated with the first memory space from the sandboxed computing environment associated with the second memory space. For example, the sandbox container process may include an internal isolation firewall. The internal isolation firewall may enforce the segregation of the first and second memory spaces.
The Host Computer System 10 may include I/O Device(s) 16. The I/O Devices 16 may include one or more of a monitor, keyboard, mouse, touchscreen interface, digital camera, a digital display, a graphical user interface, and/or the like. The I/O Device(s) 16 can allow user interaction with the Host Computer System 10, for example to allow certain interactions between an application or a process operating within the sandboxed computing environment and non-sandboxed resources.
The Network Interface Adapter(s) 18 may be configured to allow communication between the Host Computer System 10 and other devices. The Network Interface Adapter(s) 18 may include one or more wired and/or wireless communication devices.
The sandbox container process may be configured to protect the host computer system from one or more malware toolsets. For example, the Network Interface Adapter(s) 18 may include one or more of a modem, Ethernet adapter, radio, wired and/or wireless transceiver, computer port, network socket, network interface controller, and/or the like. The Processor(s) 12 may maintain rules related to access to the Network Interface Adapter(s) 18 for both access via the sandboxed computing environment and via the workspace. Further, the Processor(s) 12 may enforce a host-based firewall that implements additional rules related to access to the Network Interface Adapter(s) 18.
Based on the network connection type (at 104), the host computer system 202 follows one of two paths. For example, the malware 205 may make many different attempts contact a command-and-control server while the host computer system 202 is connected to an unsecure network (at 103). In examples, when the host computer system 202 is connected to an unsecure network, a host firewall (e.g., host-based firewall 207 in
At 111 for example, the malware 205 attempts to contact a command and control server using a non-web-based protocol (secure shell (SSH) or server message block (SMB)) and is blocked by the host firewall. At 106, the malware 205 attempts to contact a command-and-control server using a web-based protocol (e.g., hypertext transfer protocol (http) or secure hypertext transfer protocol (https)), which is also blocked by the host firewall.
The malware 205 may attempt at 107 to contact a command-and-control server through the sandbox environment 204. In such a scenario, a sandbox firewall (e.g., internal isolation firewall 203 in
Attempts to exit the host computing system using a web proxy (at 108) or via email (at 109) may similarly be blocked by the host firewall 207. Likewise, attempts at contacting a command-and-control server using domain name system (DNS) spoofing or other DNS techniques may be blocked by the host firewall 207 (at 110). Indeed, as noted above, direct communications to other networks (including the internet) are blocked by the host firewall 207. Restricted access is permitted (e.g., only permitted) from an application within a sandbox environment 204, which does not have communications with applications in other memory space, including the operating system, of the host computer system. In examples, additional access from non-sandbox memory space of the host computer system to an external network (e.g., network 201 in
If the host computer system is connected to a secure, trusted network (at 105), the malware 205 may attempt to send outbound communications through the trusted network. As with the unsecure network (at 103), the malware 205 may try to communicate with a command and control server using a non-web-based protocol (at 117) and the attempt may be blocked by a perimeter firewall (e.g., border firewall 303 in
In examples, attempts by the malware 205 to communicate to a command-and-control server using a web-based protocol (at 112) may be redirected by a router (e.g., router 305 in
The attempt to access untrusted network 201 illustrated in
The only direct communication allowed may be from the sandbox environments 204 of the host computer system 202 to the untrusted network 201. Because the sandbox environment 204 is executed within segregated memory, processes within the sandbox environment 204 do not have access to data stored in other memory space or other system resources, including the operating system of the host computer system 202. As such, communications from within the sandbox environment 204 are incapable of exfiltrating data, executing payloads outside the sandbox environment, or otherwise impacting the computer system or local network. Further, as explained above, the sandbox firewall 203 prevents processes (e.g., malware 205) external to the sandbox environment 204 from injecting data and communicating through the sandbox environment 204.
As shown in
The malware 205 may attempt to exit the network through the web proxy 304. However, the web proxy 304 may be configured to accept (e.g., only accept) communication requests that are properly authenticated. For example, the web proxy 304 may be configured to receive outbound web traffic requests on port 1234. The web proxy 304 may be further configured to accept (e.g., only accept) web traffic from cryptographically authenticated processes, such as the sandbox environments 204. In examples, the authentication mechanism between the web proxy 304 and the sandbox environment 204 utilizes a public-private key encryption or a pre-shared key encryption such that the communication channel between the sandbox environment 204 and the web proxy 304 is encrypted within the local trusted network 311. Such a configuration may prevent malware 205 from stealing authentication credentials and exiting through the web proxy 304.
If the malware 205 on the host computer system 202 attempts to directly communicate with an external network using web-based protocols, a local router 305 forwards the communication attempt to the web proxy 304 on a port other than that used by the sandbox environment 204, for example port 4321. Because the communication attempt is not authenticated, not received on the expected port (e.g., port 1234), or otherwise explicitly allowed, the web proxy 304 drops the communication attempt and the malware 205 is prevented from communicating with a command-and-control server. Similarly, if the malware 205 attempts to communicate to an external network using a non-web-based communication protocol, the local router 305 forwards the communication to the firewall 303 where it is blocked.
Security of a host computer system 202 is increased with no method to communicate with untrusted network destinations without user interaction. Direct communication attempts using DNS are blocked using a split DNS system 302. Direct access attempts through email are routed by internal router 305 to email proxy 301, which requires proper authentication credentials that the malware 205 will not have. Other attempts are routed by router 305 to the web proxy 304 or perimeter firewall 303 where they are dropped. Network traffic flows related to routed communication attempts to the web proxy 304 by the router 305 may be handled using the web cache communication protocol (WCCP) or using other protocols. Any direct communication attempts between the host computer system 202 and another trusted device are blocked by an inbound and/or outbound host firewall 207 on either or both host computer systems, thereby preventing lateral movement of malware 205 between trusted devices.
The host computer system 202 may instantiate a sandbox firewall 203 in relation to a sandbox environment 204. Any communications into and out of the sandbox environment 204 are regulated by the sandbox firewall 203. Assuming the sandbox environment 204 will eventually contract malware 205 and become compromised, the sandbox firewall 203 is designed to look for requests to access resources outside of the isolated memory space of the sandbox environment of the host computer system 202. The sandbox firewall 203 will determine that the request was received from the sandbox environment 204 and not user initiated and/or user approved and will block the request. As such, the sandbox firewall 203 blocks access between the sandbox environment 204 and other memory space, including the operating system, of the host computer system. This prevents the malware's ability to spread from a sandbox environment 204 to a host computer system's main operating environment.
As noted herein, even if the malware 205 were to reach the host computer system's operating system, any attempts to communicate with a command and control server (whether on a trusted network or on an untrusted network) would be blocked by the sandbox firewall 203, the email proxy 301, the split DNS 302, the border firewall 303, the web proxy 304 or by the host firewall 207. Accordingly, communication to a command-and-control server from such a system is extremely difficult and highly unlikely.
The host computer system 202 may be location-aware. As such, the host computer system 202 may determine when it is on a protected or trusted network (e.g., at 311), and when it is on an untrusted network (e.g., at 402). When the host computer system 202 is on an untrusted network 402, sandboxed browsing (e.g., only sandboxed browsing) is permitted. Moreover, firewall protection is increased. Even when the host computer system 202 is on a trusted network 311, the host computer system 202 may be prevented from openly communicating with other computer systems such as 414 and 415 by a host firewall 207.
The host computer system 202 may be allowed or prevented from communicating with server 401 or 403 through trusted network 311. If, for example, a user or malicious program tries to communicate out to the internet through the trusted network 311, the request will be blocked by the perimeter firewall 303 or will be rerouted by the router 305 to the web proxy 304 in the case of web-based protocols, where the request will be dropped if not explicitly permitted. Authenticated requests sent from a sandbox environment 204 may be sent through the web proxy 304 to the perimeter firewall 303 or border router 404 where they are routed to untrusted servers (e.g., 403).
The example resilient network architecture shown in
Externally bound web protocols from internal hosts are automatically directed to the web proxy 304 on a specific port, such as 4321. In some cases, the location of this “redirection” is a router 305 just prior to the perimeter firewall 303. Traffic received by the web proxy 304 on this port is automatically dropped unless explicitly permitted. Thus, within the network, internet traffic is limited to a single outlet, greatly reducing the amount of overall traffic, leading to a much quieter network that is easier to maintain and monitor. Moreover, requests that appear out of the ordinary are easy to identify and stop, as they likely come from a malicious or unknown program.
Access to the internet via the web proxy 304 requires encrypted authentication credentials unless explicitly permitted, to which malware 205 programs would not have access. Utilization of the web proxy 304 to gain internet access may be provided via a secondary port, such as 4321. Improperly (e.g., all improperly) authenticated or unauthenticated traffic received would be automatically dropped. Authenticated access to the web proxy 304 is available (e.g., only available) using an application within a sandbox environment 204. Encrypted authentication credentials may be stored locally in further encrypted configuration files. These encrypted configuration files that store the encrypted authentication credentials are loaded on startup or restart of the sandbox environment 204. The sandbox firewall 203 allows specific, user prompted actions to transfer data between the trusted environment and the segregated memory associated with the sandbox environment 204. Other (e.g., all other) connectivity between these environments is blocked.
By being location aware, a host computer system 202 may determine whether it is connected to a secured network (e.g., on network) or connected to an “unprotected” network (e.g., off network). The host firewall 207 run on the host computer system 202 permits browser traffic originating from the sandbox environment 204 to exit the host computer system 202 when off network. The host firewall 207 may also permit authorized virtual private network (VPN) clients to exit the host computer system 202 when off network. The host firewall 207 drops other (e.g., all other) traffic including malware 205 trying to exit the host computer system 202 when off network.
The sandbox firewall 203 may be configured to automatically create a browser process within a sandbox environment 204. The sandbox firewall 203 automatically creates a browser process within the sandbox environment 204 for destinations (e.g., all destinations) considered “untrusted”. The sandbox firewall 203 may also be configured to automatically create a browser process within trusted memory (e.g., outside of the sandbox environment 204) on the host computer system 202 for destinations (e.g., all destinations) considered “trusted”.
When a sandbox environment 204 is compromised, the sandbox environment 204 may be reverted to a known good image, thereby removing any malware 205 a malicious user may have added. This may happen on a periodic basis (e.g., daily), by user request, or by detection of the sandbox environment 204 operating in an unexpected or unusual manner. As such, any adversary would need to re-enter the malware 205 into the sandbox environment 204. Any attempts by an attacker at lateral movement are prevented by a host firewall 207 that refuses incoming (e.g., all incoming) connections, except traffic from predetermined devices using predetermined ports. The malware 205 may attempt to exit through the web proxy 304 or directly through the perimeter firewall 303, but traffic (e.g., all traffic) is dropped from internal hosts, except for traffic from predetermined devices using predetermined ports. A remaining (e.g., the only remaining) path is to exit through a sandbox environment 204, but the sandbox firewall 203 refuses connection (e.g., all connections) from the host computer system 202.
Location-aware laptops, tablets, and/or other mobile devices may be protected both on and off the network. Different security levels may automatically be created utilizing different security policies based on the network the host computer system 202 is connected. Should an attacker gain access to a host, armed with malware 205 designed to wait for an unfiltered internet connection, the host firewall 207 will still block the malware 205 from connecting to the internet, hence protecting the data. Users are still able to surf the internet through the sandbox environment 204. On occasions where a direct internet connection is required, a whitelist exception process may allow for such a connection. However, even these types of access may be tightened using configurable access controls. For instance, an administrator may limit the access to a third or fourth level domain, limit the address to the employees who require it, and/or add a user agent string so only that person or application has access.
The examples described herein may be implemented on various types of host computer systems 202. As noted above, these host computer systems 202 may, for example, be mobile phones, electronic appliances, laptop computers, tablet computers, wearable devices, desktop computers, mainframes, and the like. As used herein, the term “host computer system” includes any device, system, or combination thereof that includes at least one processor, and a physical and tangible computer readable memory capable of having thereon computer-executable instructions that are executable by the processor. The processor may be one of many processors in a distributed computing system or cloud-based computing system. The host computer system may also establish virtual systems including virtual operating systems that run on a host device or in a cloud-based system. In examples, an Internet Service Provider (ISP) or some similar entity may provide some or all of the services described herein to its end users. For example, the Internet Service Provider may provide a web proxy through which its users may send authenticated network traffic. Unauthenticated traffic, unless expressly whitelisted, is then block by the ISP. As such, a cloud-based solution is available to users who do not have the resources to install their own web proxy and routers. A computing system may be distributed over a network environment and may include multiple constituent computing systems (e.g., a cloud computing environment). In a cloud computing environment, program modules may be located in both local and remote memory storage devices.
As described herein, a computing system may also include communication channels that allow the computing system to communicate with other message processors over a wired or wireless network. Such communication channels may include hardware-based receivers, transmitters or transceivers, which are configured to receive data, transmit data or perform both. Examples described herein also include physical computer-readable media for carrying or storing computer-executable instructions and/or data structures. Such computer-readable media may be any available physical media that may be accessed by a general-purpose or special-purpose computing system.
System architectures described herein may include a plurality of independent components that each contribute to the functionality of the system as a whole. This modularity allows for increased flexibility when approaching issues of platform scalability and, to this end, provides a variety of advantages. System complexity and growth may be managed more easily through the use of smaller-scale parts with limited functional scope. Platform fault tolerance is enhanced through the use of these loosely coupled modules. Individual components may be grown incrementally as business needs dictate. Modular development also translates to decreased time to market for new functionality. New functionality may be added or subtracted without impacting the core system.
Accordingly, methods, systems and computer program products are provided which prevent exfiltration of data from a network. The concepts and features described herein may be embodied in other specific forms without departing from their spirit or descriptive characteristics. The described examples are to be considered in all respects only as illustrative and not restrictive. The scope of the disclosure is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
This application claims the benefit of U.S. Provisional Patent Application No. 62/564,927, filed Sep. 28, 2017, the contents of which is hereby incorporated by reference in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| 62564927 | Sep 2017 | US |
