Method and system for securing a third party communication with a hosting web page

1. A computer system including a processor coupled to a memory and configured to generate a secure agent for securing a hosting web page from a malicious at least one third party module, comprising:

a sand-box proxy configured to proxy between the at least one third party module and the hosting web page;

a sand-box engine configured to execute a validated script of the at least one third party module over the hosting web page, wherein the sand-box engine is further configured to:

upload the third party module to the hosting web page;

validate a proxy application programming interface (API) call received from the third party module, wherein the proxy API call includes at least an executable script provided by the third party module;

generate an engine API call to include at least the script of a validated proxy call; and

send the engine API call to the sand-box engine.

2. The secure agent of claim 1 , wherein the sand-box proxy is further configured to:

check if the engine API call is received from a known sand-box proxy; and

validate the script included in the engine API call.

3. The secure agent of claim 2 , wherein the validation of the proxy API call and the engine API call is performed using at least one validation rule being selected from a set of predefined rules.

4. The secure agent of claim 3 , wherein the sand-box engine and the sand-box proxy are embedded in the hosting web page.

5. The secure agent of claim 1 , wherein the hosting web page is at least a mashup web page.

6. The secure agent of claim 1 , wherein the third party module is at least an online advertisement downloaded from a third party server.

7. A publisher server, comprising:

a network interface for communicating with a plurality of vendor servers for receiving third party modules;

a processor; and

a memory coupled to the processor and configured to store at least instructions that when executed by the processor, configure the publisher server to:

render hosting web pages, wherein each of the rendered hosting web pages includes at least one of the received third party modules that is being denied from a direct access to application programming interfaces (APIs) of the hosting web page;

validate a proxy AP call received from the at least one third party module, wherein the proxy API call includes at least a payload parameter provided by the third party module;

generate an engine API call including at least the payload parameter;

validate the engine API call; and

execute the payload parameter if the engine API call is validated.

8. The publisher server of claim 7 , wherein the processor is further configured to check the contents of the payload parameter against at least one validation rule being selected from a set of predefined rules.

9. The publisher server of claim 8 , wherein the payload parameter includes at least an executable script.

10. The publisher server of claim 7 , wherein the third party module is at least an online advertisement.

11. The publisher server of claim 7 , is further configured to upload the hosting web page to a client device.

12. The publisher server of claim 7 , wherein the hosting web page is at least a mashup web page.