Abstract: A Data Loss Prevention (DLP) system is enhanced according to this disclosure by augmenting the information obtained from OS API hooking with “context” information obtained from other sources, such as by monitoring an endpoint's user interface (UI). In one embodiment, the additional “context” information is obtained from one or more user interface hooks that provide the DLP system with additional information, such as the contents of one or more application windows, the UI elements contained in a particular display window, window activation or deactivation, window resizing, user input, pointer operations, and the like. This UI information defines a “context” of the application, namely, its operating state (including, without limitation, its display state), and associated user actions that define that state. When a particular OS API hook is invoked by the application, the DLP solution uses the context information to make a more accurate enforcement decision, preferably based on the UI context.

Abstract: A method, data processing system, and computer program product for processing information. A server-side agent running on a server data processing system monitors for a selected event for processing by the server-side agent. In response to detecting the selected event for processing by the server-side agent, the server-side agent requests information to process the selected event from a client-side agent running on a client data processing system. The server-side agent performs a subset of functions performed by the client-side agent. In response to receiving a response with the information to process the selected event from the client-side agent, the server-side agent performs a set of steps to process the selected event using the information received from the client-side agent.

Abstract: A Data Loss Prevention (DLP) system is enhanced according to this disclosure by augmenting the information obtained from OS API hooking with “context” information obtained from other sources, such as by monitoring an endpoint's user interface (UI). In one embodiment, the additional “context” information is obtained from one or more user interface hooks that provide the DLP system with additional information, such as the contents of one or more application windows, the UI elements contained in a particular display window, window activation or deactivation, window resizing, user input, pointer operations, and the like. This UI information defines a “context” of the application, namely, its operating state (including, without limitation, its display state), and associated user actions that define that state. When a particular OS API hook is invoked by the application, the DLP solution uses the context information to make a more accurate enforcement decision, preferably based on the UI context.

Abstract: A web browser for communicating with an application at an application server, a smart card driver for accessing a smart card reader, a client agent monitoring events at the browser as a result of interaction between the browser and the application and a set of access profiles. The client agent is controlled by an access profile that defines a trigger event and an action to be performed by the client agent in response to an occurrence of the event.