Script Verification Using a Hash

1. A system, comprising at least one processor executing instructions within a memory coupled to a first server computer coupled to a network, the instructions causing the first server computer to: query a data store, coupled to the network and comprising a list of hosted scripts and associated valid hashes, to identify: a web page, hosted on the first server computer and including a script tag comprising: a source attribute, within the script tag, referencing a uniform resource locator (URL) defining a location for requesting a script file, separate from the web page and hosted on a second server computer coupled to the network and operated by a hosting entity other than a first hosting entity operating the first server computer; a first hash data, within a hash attribute of the script tag, generated automatically by the second server when the script file is new or updated using a hash function algorithm, and using the script file as input to the hash function algorithm, wherein the hash function algorithm does not apply cryptography to the contents of the script file; execute, at a regular time interval, a hypertext transfer protocol (HTTP) request running on the first server computer and configured to access: the script file using the URL; and a second hash data generated in association with the script file and stored on the second server computer; responsive to a determination that the second hash data does not match the first hash data: disable, by the first server computer, execution of the script tag in the web page; and generate a notification that the second hash data does not match the first hash data; and transmit a notification to a security center operating the first server computer; run a script or tag management software: comprising a plurality of rules for managing a plurality of script tags; receiving input from at least one user defining a rule to disable execution of the script file; and configured, responsive to the determination that the second hash data does not match the first hash data, to automatically disable the execution of the script file.

2. The system of claim 1 , wherein the first hash data and the second hash data are generated as output from a one-way cryptographic hash function algorithm using the script file, or a data associated with the script file, as an input.

3. The system of claim 1 , wherein the second hash data is generated subsequent to an access of the script file.

4. The system of claim 1 , wherein the instructions further cause the first server computer, responsive to a determination that the first hash data matches the second hash data, to download and execute the script file.

5. The system of claim 1 , wherein the script file is a JavaScript file.

6. The system of claim 1 , wherein the HTTP request: executes a request of the web page analogous to a web browser; and is run on a plurality of servers at a plurality of IP address locations within the network.

7. The system of claim 1 , further comprising a web browser running on a client computer coupled to the network, the web browser configured to: request the web page; download the script file; generate the second hash data; authenticate the second hash data; and execute the script file.

8. The system of claim 1 , wherein: the web page is hosted on the first server computer; and the script file, and the second hash data is hosted on the second server computer, which is operated by a third party script vendor.

9. A method, comprising: querying, by a first server computer coupled to a network and comprising at least one processor executing instructions within a memory, a data store coupled to the network and comprising a list of hosted scripts and associated valid hashes, to identify: a web page, hosted on the first server computer and including a script tag comprising: a source attribute within the script tag, referencing a uniform resource locator (URL) defining a location for requesting a script file, separate from the web page and hosted on a second server computer coupled to the network and operated by a hosting entity other than a first hosting entity operating the first server computer; a first hash data, within a hash attribute of the script tag, generated automatically by the second server when the script file is new or updated using a hash function algorithm, and using the script file as input to the hash function algorithm, wherein the hash function algorithm does not apply cryptography to the contents of the script file; executing, by the first server computer, at a regular time interval, a hypertext transfer protocol (HTTP) request running on the first server computer and configured to access: the script file using the URL; and a second hash data generated in association with the script file and stored on the second server computer; responsive to a determination that the second hash data does not match the first hash data: disabling, by the first server computer, execution of the script tag in the web page; and generating, by the first server computer, a notification that the second hash data does not match the first hash data; transmit a notification to a security center operating the first server computer; running, by the first server computer, a script or tag management software: comprising a plurality of rules for managing a plurality of script tags; receiving input from at least one user defining a rule to disable execution of the script file; and configured, responsive to the determination that the second hash data does not match the first hash data, to automatically disable the execution of the script file.

10. The method of claim 9 , wherein the first hash data and the second hash data are generated as output from a one-way cryptographic hash function algorithm using the script file, or a data associated with the script file, as an input.

11. The method of claim 9 , wherein the second hash data is generated subsequent to an access of the script file.

12. The method of claim 9 , wherein the instructions further cause the first server computer, responsive to a determination that the first hash data matches the second hash data, to download and execute the script file.

13. The method of claim 9 , wherein the script file is a JavaScript file.

14. The method of claim 9 , wherein the HTTP request: executes a request of the web page analogous to a web browser; and is run on a plurality of servers at a plurality of IP address locations within the network.

15. The method of claim 9 , further comprising a web browser running on a client computer coupled to the network, the web browser configured to: request the web page; download the script file; generate the second hash data; authenticate the second hash data; and execute the script file.

16. The method of claim 9 , wherein: the web page is hosted on the first server computer; and the script file, and the second hash data is hosted on the second server computer, which is operated by a third party script vendor.