US2004230825A1PendingUtilityA1

Secure browser

Priority: May 16, 2003Filed: Mar 2, 2004Published: Nov 18, 2004
Est. expiryMay 16, 2023(expired)· nominal 20-yr term from priority
G06F 21/6209H04L 63/08G06F 2221/2149G06F 21/62H04L 63/168
42
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A secure user interface method, for interacting with a user through a browser, comprising the steps of controlling the browser to request a document from a cooperative server, the browser providing data export support functionality; receiving data with the browser in response to the request; determining, based on a type encoding of the received data, whether a secure browser is to be employed, the secure browser having a set of functionality restricted with respect to a normal browser, to enhance security of a received document against data export; authenticating the secure browser, to assure that the secure browser having the restricted set of functionality is available for presentation of secure content; receiving the secure content for presentation in the secure browser; and communicating an input from the user, through the secure browser, to a cooperative server.

Claims

exact text as granted — not AI-modified
What is claimed is  
     
         1 . A secure user interface method, for interacting with a user through a browser, comprising: 
 controlling the browser to request a document from a cooperative server, the browser providing data export support functionality;    receiving data with the browser in response to the request;    automatically determining, based on a type encoding of the received data, whether a secure browser is to be employed, the secure browser having a set of functionality restricted with respect to a normal browser, to enhance security of a received document against data export;    receiving the secure content for presentation in the secure browser; and    communicating an input from the user, through the secure browser, to a cooperative server.    
     
     
         2 . The user interface method according to  claim 1 , further comprising the step of limiting access of a user, with the secure browser, to documents outside of a specified set.  
     
     
         3 . The user interface method according to  claim 1 , further comprising the step of authenticating the secure browser, to assure that the secure browser having the restricted set of functionality is available for presentation of secure content.  
     
     
         4 . The user interface method according to  claim 1 , wherein the secure browser lacks one or more of the following functions: print, save, cache, cut and copy.  
     
     
         5 . The user interface method according to  claim 1 , wherein the secure browser renders text information as graphic objects.  
     
     
         6 . The user interface method according to  claim 1 , wherein the secure browser restricts termination of its own execution.  
     
     
         7 . The user interface method according to  claim 3 , wherein the secure browser restricts termination of its own execution.  
     
     
         8 . A computer readable media storing a program for a general purpose computer for performing the method of  claim 3 .  
     
     
         9 . A secure user interface method, for interacting with a user through a browser, the browser providing a set of navigational functionality, comprising: 
 requesting a document from a cooperative server;    receiving data in response to the request;    automatically determining whether a secure browser is required to be employed by a content provider, the secure browser restricting interaction of the user with tasks other than those permitted by the secure browser;    invoking the secure browser;    receiving the secure content for presentation in the secure browser; and    communicating an input from the user, through the secure browser, to a cooperative server.    
     
     
         10 . The method according to  claim 9 , wherein the secure browser provides restricted navigational functionality with respect to the navigational functionality of the browser alone.  
     
     
         11 . The user interface method according to  claim 6 , further comprising the step of limiting access of a user, with the secure browser, to access of documents within a specified set.  
     
     
         12 . The user interface method according to  claim 6 , further comprising the step of authenticating the secure browser at a remote server prior to presenting the secure content to ensure that the content will only be delivered in the secure browser.  
     
     
         13 . The user interface method according to  claim 6 , wherein the secure browser prevents use of the following functions: save, copy, and navigate to unrestricted documents.  
     
     
         14 . The user interface method according to  claim 6 , wherein the secure browser restricts termination of its own execution.  
     
     
         15 . The user interface method according to  claim 6 , wherein the secure browser is initiated based on a type encoding of the received data.  
     
     
         16 . The user interface method according to  claim 6 , wherein the secure browser is initiated based on a code associated with the secure content.  
     
     
         17 . The user interface method according to  claim 6 , wherein the secure browser is granted principal application level control over graphic user interface inputs from a user.  
     
     
         18 . The user interface method according to  claim 6 , wherein the secure browser is granted exclusive control over graphic user interface functionality when invoked.  
     
     
         19 . The user interface method according to  claim 6 , further comprising the step of authenticating the server by the secure browser prior to presenting the secure content.  
     
     
         20 . A computer readable media storing a program for a general purpose computer for performing the method of  claim 6.

Join the waitlist — get patent alerts

Track US2004230825A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.