Systems and methods for data loss prevention

A system for data loss prevention, the system comprising:

• a proxy system that comprises both memory and at least one processor;
• a receiving module, stored in the memory of the proxy system, that receives, from a hypertext-transfer-protocol server, a web page comprising a web form for a client system;
• an injection module, stored in the memory of the proxy system, that injects a script into the web page that:
• scans the web page for at least one of user-editable fields and non-user-editable fields:
• generates custom metadata for the web page that:
• marks user-editable fields within the web page as being subject to data-loss-prevention analysis;
• marks non-user-editable fields within the web page as not being subject to data-loss-prevention analysis;
• an identification module, stored in the memory of the proxy system, that identifies a hypertext-transfer-protocol POST request issued in connection with the web from by the client system to the hypertext-transfer-protocol server;
• a metadata module, stored in the memory of the proxy system, that:
• identifies, within the hypertext-transfer-protocol POST request, the custom metadata generated by the script;
• removes the custom metadata from the hypertext-transfer-protocol POST;
• an analysis module, stored in the memory of the proxy system, that subjects, based on the custom metadata, the user-editable field to a data-loss-prevention analysis and omits the non-user-editable field from the data-loss-prevention analysis;
• a performing module, stored in the memory of the proxy system, that performs a data-loss-prevention action based on the data-loss-prevention analysis by blocking the user-editable field from reaching the hypertext-transfer-protocol server.

A non-transitory computer-readable-storage medium comprising one or more computer-executable instructions that, when executed by at least one processor of a proxy system, cause the proxy system to:

• receive, at the proxy system from a hypertext-transfer-protocol server, a web page comprising a web form for a client system;
• inject, at the proxy system, a script into the web page that:
• scans the web page for at least one of user-editable fields and non-user-editable fields;
• generates custom metadata for the web page that:
• marks user-editable fields within the web page as being subject to data-loss-prevention analysis;
• marks non-user-editable fields within the web page as not being subject to data-loss-prevention analysis;
• identify, at the proxy system, a hypertext-transfer-protocol POST request issued in connection with the web form by the client system to the hypertext-transfer-protocol server;
• identify, at the proxy system, the custom metadata within the hypertext-transfer-protocol POST request that was generated by the script;
• subject, at the proxy system based on the custom metadata, the user-editable field to a data-loss-prevention analysis and omit the non-user-editable field from the data-loss-prevention analysis;
• remove, at the proxy system, the custom metadata from the hypertext-transfer-protocol POST;
• perform, at the proxy system, a data-loss-prevention action based on the data-loss-prevention analysis by blocking the user-editable field from reaching the hypertext-transfer-protocol server.