Thwarting data leakage from a webpage
Thwarting data leakage from a webpage. In some embodiments, a method may include detecting, at a browser on the network device, a visit to the webpage, directing a headless browser on the network device to visit the webpage in parallel to the browser visiting the webpage, detecting, at the headless browser, data leakage from the webpage, presenting, at the browser, a notification regarding the data leakage that allows a user to indicate whether the data leakage should be allowed, receiving, at the browser, an indication that the data leakage should not be allowed, and in response to receiving the indication that the data leakage should not be allowed, thwarting the data leakage by performing a remedial action at the network device to protect the network device from the data leakage.
1. A computer-implemented method for thwarting data leakage from a webpage, at least a portion of the method being performed by a network device comprising at least one processor, the method comprising:
detecting, at a browser on the network device, a first visit to the webpage;
directing a headless browser on the network device to perform a separate second visit the webpage in parallel to the first visit to the webpage by the browser, the headless browser having the same functionality as the browser but without a graphical user interface;
detecting, at the headless browser, data leakage from the webpage;
presenting, at the browser, a notification regarding the data leakage that allows a user to indicate whether the data leakage should be allowed;
receiving, at the browser, an indication that the data leakage should not be allowed; and
in response to receiving the indication that the data leakage should not be allowed, thwarting the data leakage by performing a remedial action at the network device to protect the network device from the data leakage.
2. The method of claim 1 , wherein the performing of the remedial action at the network device comprises one or more of blocking the network device from communicating with a third-party system over a network, preventing data associated with the data leakage from being gathered at the webpage, or preventing data associated with the data leakage from being stored at the network device, or some combination thereof.
3. The method of claim 1 , wherein the detecting, at the headless browser, of the data leakage from the webpage comprises detecting, at the headless browser, the data leakage due to a third-party script of the webpage listening for input events on the webpage.
4. The method of claim 3 , wherein the input events comprise one or more of keyboard input events, or mouse input events, or some combination thereof.
5. The method of claim 1 , wherein the detecting, at the headless browser, of the data leakage from the webpage comprises detecting, at the headless browser, the data leakage due to outbound data flows from the webpage to a third-party system.
6. The method of claim 5 , wherein the outbound data flows from the webpage to the third-party system comprise an outbound request to a third-party domain that is different than a domain of the webpage.
7. The method of claim 1 , wherein the detecting, at the headless browser, of data leakage from the webpage comprises detecting, at the headless browser, the data leakage to a third-party system that is configured to occur on the webpage without the data leakage being presented in the browser or being known to the user.
8. One or more non-transitory computer-readable media comprising one or more computer-readable instructions that, when executed by one or more processors of a network device, cause the network device to perform a method for thwarting data leakage from a webpage, the method comprising:
detecting, at a browser on the network device, a first visit to the webpage;
directing a headless browser on the network device to perform a separate second visit the webpage in parallel to the first visit to the webpage by the browser, the headless browser having the same functionality as the browser but without a graphical user interface;
detecting, at the headless browser, data leakage from the webpage;
presenting, at the browser, a notification regarding the data leakage that allows a user to indicate whether the data leakage should be allowed;
receiving, at the browser, an indication that the data leakage should not be allowed; and
in response to receiving the indication that the data leakage should not be allowed, thwarting the data leakage by performing a remedial action at the network device to protect the network device from the data leakage.
9. The one or more non-transitory computer-readable media of claim 8 , wherein the performing of the remedial action at the network device comprises one or more of blocking the network device from communicating with a third-party system over a network, preventing data associated with the data leakage from being gathered at the webpage, or preventing data associated with the data leakage from being stored at the network device, or some combination thereof.
10. The one or more non-transitory computer-readable media of claim 8 , wherein the detecting, at the headless browser, of the data leakage from the webpage comprises detecting, at the headless browser, the data leakage due to a third-party script of the webpage listening for input events on the webpage.
11. The one or more non-transitory computer-readable media of claim 10 , wherein the input events comprise one or more of keyboard input events, or mouse input events, or some combination thereof.
12. The one or more non-transitory computer-readable media of claim 8 , wherein the detecting, at the headless browser, of the data leakage from the webpage comprises detecting, at the headless browser, the data leakage due to outbound data flows from the webpage to a third-party system.
13. The one or more non-transitory computer-readable media of claim 12 , wherein the outbound data flows from the webpage to the third-party system comprise an outbound request to a third-party domain that is different than a domain of the webpage.
14. The one or more non-transitory computer-readable media of claim 8 , wherein the detecting, at the headless browser, of data leakage from the webpage comprises detecting, at the headless browser, the data leakage to a third-party system that is configured to occur on the webpage without the data leakage being presented in the browser or being known to the user.
15. A network device comprising:
one or more processors; and
one or more non-transitory computer-readable media comprising one or more computer-readable instructions that, when executed by the one or more processors, cause the network device to perform a method for thwarting data leakage from a webpage, the method comprising:
detecting, at a browser on the network device, a first visit to the webpage;
directing a headless browser on the network device to perform a separate second visit the webpage in parallel to the first visit to the webpage by the browser, the headless browser having the same functionality as the browser but without a graphical user interface;
detecting, at the headless browser, data leakage from the webpage;
presenting, at the browser, a notification regarding the data leakage that allows a user to indicate whether the data leakage should be allowed;
receiving, at the browser, an indication that the data leakage should not be allowed; and
in response to receiving the indication that the data leakage should not be allowed, thwarting the data leakage by performing a remedial action at the network device to protect the network device from the data leakage.
16. The network device of claim 15 , wherein the performing of the remedial action at the network device comprises one or more of blocking the network device from communicating with a third-party system over a network, preventing data associated with the data leakage from being gathered at the webpage, or preventing data associated with the data leakage from being stored at the network device, or some combination thereof.
17. The network device of claim 15 , wherein:
the detecting, at the headless browser, of the data leakage from the webpage comprises detecting, at the headless browser, the data leakage due to a third-party script of the webpage listening for input events on the webpage; and
the input events comprise one or more of keyboard input events, or mouse input events, or some combination thereof.
18. The network device of claim 15 , wherein the detecting, at the headless browser, of the data leakage from the webpage comprises detecting, at the headless browser, the data leakage due to outbound data flows from the webpage to a third-party system.
19. The network device of claim 18 , wherein the outbound data flows from the webpage to the third-party system comprise an outbound request to a third-party domain that is different than a domain of the webpage.
20. The network device of claim 15 , wherein the detecting, at the headless browser, of data leakage from the webpage comprises detecting, at the headless browser, the data leakage to a third-party system that is configured to occur on the webpage without the data leakage being presented in the browser or being known to the user.