Network security
A gateway or other network device may be configured to monitor endpoint behavior, and to request a verification of user presence at the endpoint under certain conditions suggesting, e.g., malware or other endpoint compromise. For example, when a network request is directed to a low-reputation or unknown network address, user presence may be verified to ensure that this action was initiated by a human user rather than automatically by malware or the like. User verification may be implicit, based on local behavior such as keyboard or mouse activity, or the user verification may be explicit, such as where a notification is presented on a display of the endpoint requesting user confirmation to proceed.
1. A computer program product for monitoring network security based on endpoint user presence, the computer program product comprising computer executable code embodied in a non-transitory computer readable medium that, when executing on a gateway in an enterprise network, performs the steps of:
connecting an endpoint of the enterprise network to a data network through the gateway;
receiving a network request at the gateway, the network request received from a process executing on the endpoint and the network request to a remote resource on the data network outside the enterprise network;
determining, by the gateway, that the network request includes a potential security risk of requesting to download an executable in violation of a security policy of the enterprise network;
in response to determining that the network request includes the potential security risk,
(i) requesting from the endpoint, by the gateway connecting the endpoint to the data network, a historical record of keyboard or mouse activity on the endpoint for a predetermined time window prior to receipt, by the gateway, of the network request that includes the potential security risk, and
(ii) determining, by the gateway, based at least in part on the historical record of keyboard or mouse activity received from the endpoint, whether the network request was initiated as a result of user interaction by a human user; and
in response to detecting that the network request includes the potential security risk of downloading an executable and determining that the network request was not initiated by a human user, initiating, at the gateway, a remedial action that includes executing a security measure on the endpoint in response to the potential security risk presented by the network request.
2. The computer program product of claim 1 wherein determining whether the network request was initiated by a human user includes transmitting a request to the endpoint for a user input.
3. The computer program product of claim 1 wherein determining whether the network request was initiated by a human user includes determining whether a user is logged in to the endpoint.
4. The computer program product of claim 1 wherein determining whether the network request was initiated by a human user includes determining whether a display of the endpoint is locked.
5. A method of operating a gateway comprising:
connecting an endpoint of an enterprise network to a data network through the gateway;
determining, by the gateway, that a network request by a process executing on the endpoint to a remote resource on a data network outside the enterprise network includes a potential security risk of requesting to download an executable in violation of a security policy of the enterprise network;
in response to determining that the network request includes the potential security risk,
(i) requesting from the endpoint, by the gateway connecting the endpoint to the data network, a historical record of keyboard or mouse activity on the endpoint for a predetermined time window prior to receipt, by the gateway, of the network request that includes the potential security risk, and
(ii) determining, by the gateway, based at least in part on the historical record of keyboard or mouse activity received from the endpoint, whether the network request was initiated as a result of user interaction by a human user; and
initiating, at the gateway, a remedial action that includes executing a security measure on the endpoint in response to detecting the network request by the process executing on the endpoint that includes the potential security risk, evaluating a status of the endpoint, and determining that the network request was not initiated by a human user.
6. The method of claim 5 wherein the network request includes a request for a download of an executable from the data network.
7. The method of claim 5 wherein the network request includes a request directed to an unknown address.
8. The method of claim 5 wherein the network request includes a request directed to a known source of malware.
9. The method of claim 5 wherein evaluating the status of the endpoint includes querying the endpoint about whether the user is present.
10. The method of claim 5 wherein evaluating the status of the endpoint includes transmitting a request to the endpoint for a user input.
11. The method of claim 5 wherein the status includes whether a user is logged in to the endpoint.
12. The method of claim 5 wherein the status includes whether a display of the endpoint is locked.
13. A system comprising:
a gateway including a network interface configured to couple in a communicating relationship with a data network;
a memory on the gateway; and
a processor on the gateway, the processor configured to execute instructions stored in the memory to perform the steps of
connecting an endpoint of an enterprise network to the gateway through the network interface so as to establish a communicating relationship between the endpoint and the data network,
determining, by the gateway, that a network request by a process executing on the endpoint to a remote resource on the data network outside the enterprise network includes a potential security risk of requesting to download an executable in violation of a security policy of the enterprise network,
in response to determining that the network request includes the potential security risk,
(i) requesting from the endpoint, by the gateway connecting the endpoint to the data network, a historical record of keyboard or mouse activity on the endpoint for a predetermined time window prior to receipt, by the gateway, of the network request that includes the potential security risk, and
(ii) determining, by the gateway, based at least in part on the historical record of keyboard or mouse activity received from the endpoint, whether the network request was initiated as a result of a user interaction by a human user, and
in response to detecting the network request that includes the potential security risk and a determination that the network request was not initiated by the human user, initiating a remedial action that includes executing a security measure on the endpoint.
14. The system of claim 13 wherein the network request includes a request for a download of an executable from the data network.
15. The system of claim 13 wherein the network request includes a request directed to an unknown address.
16. The system of claim 13 wherein the network request includes a request directed to a known source of malware.
17. The system of claim 13 wherein determining whether the network request was initiated as a result of the user interaction includes querying the endpoint about whether the user is present.
18. The system of claim 13 wherein determining whether the network request was initiated as a result of the user interaction includes transmitting a request to the endpoint for a user input.
19. The system of claim 13 wherein determining whether the network request was initiated as a result of the user interaction includes determining whether a user is logged in to the endpoint.
20. The system of claim 13 wherein determining whether the network request was initiated as a result of the user interaction includes determining whether a display of the endpoint is locked.