PRIVILEGED STATIC HOSTED WEB APPLICATIONS

• US 20150180875A1
• Filed: 10/24/2014
• Published: 06/25/2015
• Est. Priority Date: 12/19/2013
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Kay, Erik
• Granted Patent: US 10,104,081 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/9566 URL specific, e.g. using aliases, detecting broken or misspelled links
• CPC Class Codes: G06F 21/128 involving web programs, i.e. using technology especially used in internet, generally interacting with a web browser, e.g. hypertext markup language [HTML], applets, java
• CPC Class Codes: G06F 21/56 Computer malware detection or handling, e.g. anti-virus arrangements
• CPC Class Codes: G06F 21/629 to features or functions of an application
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 63/1441 Countermeasures against malicious traffic countermeasures against attacks on cryptographic mechanisms H04L9/002
• CPC Class Codes: H04L 63/145 the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04W 12/08 Access security
• CPC Class Codes: H04W 12/12 Detection or prevention of fraud
• CPC Class Codes: H04W 12/128 Anti-malware arrangements, e.g. protection against SMS fraud or mobile malware

Abstract

A method can include receiving a static web application at a trusted server, validating assurance characteristics of the static web application, and upon successful validation of the static web application, providing access to the static web application via a URL that identifies the static web application at a trusted server location. The static web application, when executed on the browser running on the client device, can be granted at least one permission to utilize local resources of the client device during execution of the static web application by the browser. Upon receiving a change to an object of the static web application, the validating of the assurance characteristics of the static web application, as a whole, can be performed before the change to the object is made accessible via the URL.

Claims

1. A method comprising:

receiving a static web application at a trusted server;

validating assurance characteristics of the static web application; and

upon successful validation of the static web application, providing access to the static web application via a uniform resource locator (URL) that identifies the static web application at a trusted server location within a public Internet and that can be used to navigate to the static web application from a browser running on a client device, wherein

the static web application, when executed on the browser running on the client device, is granted at least one permission to utilize local resources of the client device during execution of the static web application by the browser, and

upon receiving a change to an object of the static web application, the validating of the assurance characteristics of the static web application, as a whole, is performed before the change to the object is made accessible via the URL.

2. The method of claim 1, wherein the static web application is granted the at least one permission based on a prior verification and vetting process based on at least one permission that the web application seeks to declare.

3. The method of claim 1, wherein the static web application is granted the at least one permission based on a prior maliciousness ranking and a threshold value.

4. The method of claim 1, wherein the static web application contains all of the resources necessary to execute the application on the client computing device and wherein code needed to execute the application by the client computing device is not dynamically generated.

5. The method of claim 1, further comprising:

hosting the static web application on the trusted server, wherein the hosting includes providing access to the static web application, and code associated with the static web application, to a web crawler.

6. The method of claim 1, wherein validating assurance characteristics of the static web application includes verifying an object of the static web application does not include an object identified as at least one of a malware, a virus, and a Trojan.

7. The method of claim 1, wherein validating assurance characteristics of the static web application includes verifying a trustworthiness ranking of a developer of the static web application.

8. The method of claim 1, wherein updating the static web application includes replacing objects of the static web application with a revalidated entire application.

9. The method of claim 1, wherein prior to requesting at least one permission to utilize local resources of the client device during execution of the static web application by the browser the static web application executes, on the client device, without permission to utilize local resources of the client device.

10. A server comprising:

a memory configured to store a static web application;

a verification module configured to validate assurance characteristics of the static web application; and

an application server, upon successful validation of the static web application, configured to provide access to the static web application via a uniform resource locator (URL) that identifies the static web application at a trusted server location within a public Internet and that can be used to navigate to the static web application from a browser running on a client device, wherein

the static web application, when executed on the browser running on the client device, is granted at least one permission to utilize local resources of the client device during execution of the static web application by the browser, and

the verification module, upon receiving a change to an object of the static web application, is further configured to repeat the validating of the assurance characteristics of the static web application, as a whole, before the change to the object is made accessible via the URL.

11. The server of claim 10, wherein the static web application is granted the at least one permission based on a prior verification and vetting process based on at least one permission that the web application seeks to declare.

12. The server of claim 10, wherein the static web application is granted the at least one permission based on a prior maliciousness ranking and a threshold value.

13. The server of claim 10, wherein the static web application contains all of the resources necessary to execute the application on the client computing device and wherein code needed to execute the application by the client computing device is not dynamically generated.

14. The server of claim 10, further comprising:

hosting the static web application on the server, wherein the hosting includes providing access to the static web application, and code associated with the static web application, to a web crawler.

15. The server of claim 10, wherein validating assurance characteristics of the static web application by the verification module includes verifying an object of the static web application does not include an object identified as at least one of a malware, a virus, and a Trojan.

16. The server of claim 10, wherein validating assurance characteristics of the static web application by the verification module includes verifying a trustworthiness ranking of a developer of the static web application.

17. The server of claim 10, wherein updating the static web application includes replacing objects of the static web application with a revalidated entire application.

18. A non-transitory computer-readable storage medium having stored thereon computer executable program code which, when executed on a computer system, causes the computer system to perform steps comprising:

receiving a static web application at a trusted server;

validating assurance characteristics of the static web application; and

upon successful validation of the static web application, providing access to the static web application via a uniform resource locator (URL) that identifies the static web application at a trusted server location within a public Internet and that can be used to navigate to the static web application from a browser running on a client device, wherein

the static web application, when executed on the browser running on the client device, is granted at least one permission to utilize local resources of the client device during execution of the static web application by the browser, and

upon receiving a change to an object of the static web application, the validating of the assurance characteristics of the static web application, as a whole, is performed before the change to the object is made accessible via the URL.

19. The non-transitory computer-readable storage medium of claim 18, wherein the static web application is granted the at least one permission based on a prior verification and vetting process based on at least one permission that the web application seeks to declare.

20. The non-transitory computer-readable storage medium of claim 18, wherein the static web application contains all of the resources necessary to execute the application on the client computing device and wherein code needed to execute the application by the client computing device is not dynamically generated.