US20030131115A1 - System and method for using internet based caller ID for controlling access to an object stored in a computer - Google Patents
System and method for using internet based caller ID for controlling access to an object stored in a computer Download PDFInfo
- Publication number
- US20030131115A1 US20030131115A1 US10/295,515 US29551502A US2003131115A1 US 20030131115 A1 US20030131115 A1 US 20030131115A1 US 29551502 A US29551502 A US 29551502A US 2003131115 A1 US2003131115 A1 US 2003131115A1
- Authority
- US
- United States
- Prior art keywords
- identifier
- platform
- processor
- server
- access
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0823—Network architectures or network communication protocols for network security for authentication of entities using certificates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
- G06Q20/341—Active cards, i.e. cards including their own processing means, e.g. including an IC or chip
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/388—Payment protocols; Details thereof using mutual authentication without cards, e.g. challenge-response
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
- G06Q20/4014—Identity check for transactions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/409—Device specific authentication in transaction processing
- G06Q20/4097—Device specific authentication in transaction processing using mutual authentication between devices and transaction partners
- G06Q20/40975—Device specific authentication in transaction processing using mutual authentication between devices and transaction partners using encryption therefor
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07F—COIN-FREED OR LIKE APPARATUS
- G07F7/00—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus
- G07F7/08—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means
- G07F7/10—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means together with a coded signal, e.g. in the form of personal identification information, like personal identification number [PIN] or biometric data
- G07F7/1008—Active credit-cards provided with means to personalise their use, e.g. with PIN-introduction/comparison system
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/12—Applying verification of the received information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/16—Implementing security features at a particular protocol layer
- H04L63/168—Implementing security features at a particular protocol layer above the transport layer
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2129—Authenticate client device independently of the user
Definitions
- the present invention relates generally to the field of access control, and particularly to a system and method for verifying the identity of a platform or other device prior to granting access to a private communication channel, to data or to programs.
- the Internet has become a convenient way for a broad class of computer users to access, distribute and exchange information—evident from the large number of individuals, companies and other organizations that have established web sites on the World Wide Web.
- the Internet permits users to easily access publicly available information, to communicate over private channels, and to access restricted information, such as medical records and bank accounts.
- Tokens provide stronger authentication, but are expensive to deploy and maintain.
- a digital signature may not reliably identify a user, if the user either accidentally or intentionally gives imposters access to the user's private key.
- broad deployment of this authentication method requires a public key infrastructure that does not yet exist.
- the present invention relates to a system and method for controlling access to an object.
- the system stores an object and a processor identifier.
- the system includes a verification agent that can access information embedded in a processor and then calculate from that embedded information a value that may be compared with the stored processor identifier.
- a comparison agent is used to compare that value with the processor identifier to determine whether the processor corresponds to the processor identifier. If the value that the verification agent returns matches the processor identifier, then the user is granted access to the object.
- processor identifier There are many applications for a processor identifier, or other platform identifier, as will be described in more detail below. Some examples include: Internet based communication; Internet based activities restricted to only certain users; web surfing pattern tracking, which may enable content providers and on-line retailers to tailor their products to meet customer preferences; on-line voting, surveys or similar user preference activity; and for verifying the identity of a user seeking access over a virtual private network.
- FIG. 1 is a block diagram illustrating one embodiment of the system of the present invention for controlling access to an object.
- FIG. 2 is a block diagram illustrating a second embodiment of the system of the present invention wherein the system for controlling access to an object resides in a server.
- FIG. 3 is a flow diagram illustrating a method for controlling access to an object stored on the server shown in FIG. 2.
- FIG. 4 is a block diagram illustrating a third embodiment of the present invention wherein the system for controlling access to an object resides in a web server.
- FIG. 5 is a flow diagram illustrating a method for controlling access to confidential records stored on the web server shown in FIG. 4.
- FIG. 6 is a flow diagram illustrating an embodiment of the present invention where a “caller ID” function is employed to verify the identity of those seeking to participate in a private teleconference.
- FIG. 1 is a block diagram that illustrates one embodiment of such a system.
- System 100 stores object 101 .
- Object 101 may consist of data and/or executable code. Such executable code may, for example, contain a program that permits a user to communicate with one or more other users over the Internet.
- Object 101 may be stored in a machine readable storage medium such as, for example, a floppy or hard disk drive.
- System 100 may be a type of computer, including for example a network server, web server, desktop or notebook PC, or hand held computing device.
- system 100 may comprise consumer electronics apparatus that can control access to object 101 .
- a RAID storage unit may be associated with system 100 , which may store object 101 .
- System 100 stores a processor identifier 102 . Access to object 101 is limited to devices that contain a processor, which corresponds to processor identifier 102 .
- Processor identifier 102 preferably is a “processor number” (as defined below) or a hash of a processor number with another value.
- processor identifier 102 may be stored in an associated RAID storage unit.
- system 100 For determining whether a device's processor corresponds to processor identifier 102 , system 100 includes a verification agent 103 and a comparison agent 104 .
- Verification agent 103 can access information embedded in a processor, e.g., a processor number, and calculate from that embedded information a value that may be compared with processor identifier 102 .
- Comparison agent 104 compares to processor identifier 102 the value that verification agent 103 returns. If that value matches processor identifier 102 , then the device is granted access to object 101 .
- Verification agent 103 and comparison agent 104 may reside on a network or web server. Alternatively, they may reside on the device that includes the processor with the embedded information or on a separate machine readable storage medium for use with the network or web server, the device containing the embedded information or some other device. Verification agent 103 thus comprises any software, hardware or combination of software and hardware that can access information embedded in a processor and calculate from that information a value that may be compared with the processor identifier—irrespective of where or how verification agent is physically stored or located. Likewise, comparison agent 104 comprises any software, hardware or combination of software and hardware that can compare with the processor identifier the value that verification agent 103 returns—irrespective of where or how comparison agent 104 is physically stored or located.
- FIG. 2 is a block diagram illustrating an embodiment of the present invention where client computer 200 seeks access through client/server communication link 203 to object 202 (which may include data and/or programming instructions) stored on server 201 .
- Server 201 includes session identifier generator 204 , verification agent module 205 , selection agent 206 , comparison agent 207 , transmitter 208 , processor identifier 209 , and timer 217 .
- Client computer 200 includes a processor 210 and embedded information 211 , such as a processor number, which identifies processor 210 .
- Processor 210 may be a member of the Pentium® processor family of microprocessors, or a member of a later generation of X86 instruction set compatible processors.
- Embedded information 211 may be stored in processor 210 in a processor ID register or, alternatively, in a constant ROM that holds data that microcode instructions (stored in a microcode ROM) may use—such as is described in U.S. Pat. Nos. 5,790,834 and 5,794,066, assigned to this application's assignee, and as described in the Pentium® Pro Family Developer's Manual.
- Future Intel processors will add a new value to those described in the Developer's Manual that can be loaded into a processor ID register. That new value is intended to be statistically unique for a given processor, analogous to its “fingerprint.” That statistically unique information can be said to constitute a “processor number” for a given processor. Because such a processor number is only statistically unique, it is possible for more than one platform or device to have the same processor number.
- Processor identifier 209 may be a processor number loaded onto server 201 from a client computer. Alternatively, processor identifier 209 may be the value resulting from applying a function to the combination of a processor number and another value, e.g., a server identifier.
- Session identifier generator 204 randomly selects a session identifier 213 , when client computer 200 attempts to access object 202 .
- Session identifier 213 provides a means for matching a value returned from a client computer 200 with a specific attempt to access object 202 .
- Session identifier generator 204 may be a random number generator for producing session identifiers 213 , which each comprise a randomly generated number.
- Verification agent module 205 includes a plurality of verification agents 212 , each containing programming instructions for accessing embedded information 211 , a secret key 214 , and a calculator 215 for calculating a return value from the combination of embedded information 211 , secret key 214 , and session identifier 213 .
- Each verification agent 212 may also include programming instructions for requesting client computer 200 to send the return value to server 201 .
- processor identifier 209 is derived from applying a function to the combination of a processor number and another value
- verification agent 212 can include that other value in addition to secret key 214 .
- Each verification agent 212 has a different secret key 214 .
- Calculator 215 may calculate a return value that is a function of embedded information 211 , secret key 214 , and session identifier 213 .
- a function could perform an XOR on embedded information 211 and secret key 214 to generate an intermediate value, followed by a second XOR on that intermediate value and session identifier 213 to yield the return value.
- calculator 215 may employ a hash function, such as SHA-1 or MD5, to calculate a return value that is a function of embedded information 211 , secret key 214 , session identifier 213 and that additional value.
- SHA-1 hash function
- Secret key 214 included in verification agent 212 , may be generated using conventional techniques known in the art, such as generating a random number using a random number generator.
- Selection agent 206 may randomly select a verification agent 212 from verification agent module 205 in the following manner. Initially, selection agent 206 sequentially assigns a number to each verification agent 212 . When a user subsequently seeks access to object 202 , selection agent 206 randomly generates a number that falls within the range of those assigned to the verification agents 212 included in verification module 205 , then selects the verification agent 212 that corresponds to that randomly selected number.
- the software or hardware constituting verification agent 212 does not have to be physically located or stored on server 201 .
- Server 201 also includes timer 217 .
- timer 217 may disconnect server 201 from client computer 200 , when verification agent 212 fails to return to server 201 within a prescribed amount of time a return value for comparison to processor identifier 209 .
- FIG. 3 is a flow diagram that shows the steps server 201 follows to determine whether client computer 200 should have access to object 202 , where both processor identifier 209 and embedded information 211 are processor numbers.
- the process begins with client computer 200 requesting access to object 202 , over client/server communication link 203 (block 300 ).
- server 201 causes selection agent 206 to randomly select a verification agent 212 from verification agent module 205 , and causes session identifier generator 204 to randomly select a session identifier 213 (block 310 ).
- Transmitter 208 then transmits verification agent 212 (which includes secret key 214 , calculator 215 , and programming instructions for accessing processor number 211 and for requesting client computer 200 to send a return value to server 201 ) and session identifier 213 from server 201 through client/server communication link 203 to client computer 200 (block 320 ).
- verification agent 212 which includes secret key 214 , calculator 215 , and programming instructions for accessing processor number 211 and for requesting client computer 200 to send a return value to server 201
- session identifier 213 from server 201 through client/server communication link 203 to client computer 200 (block 320 ).
- software may be loaded onto client computer 200 that enables client computer 200 to retrieve verification agent 212 , after it is selected by selection agent 206 . That same software can then facilitate the transmission of verification agent 212 from server 201 to client computer 200 .
- software pre-installed onto client computer 200 rather than software downloaded from server 201 , may perform the functions that verification agent 212 would otherwise perform.
- Server 201 copies and stores secret key 214 and session identifier 213 prior to transmission of verification agent 212 to client computer 200 .
- Processor 210 executes the programming instructions included in verification agent 212 to cause verification agent 212 to read embedded information 211 , then calculate a return value from the combination of processor number 211 , secret key 214 and session identifier 213 (block 330 ).
- Processor 210 then executes additional code included in verification agent 212 to cause client computer 200 to send the return value over client/server communication link 203 to server 201 (block 340 ).
- comparison agent 207 performs a reverse function calculation on the return value to generate a processor number (block 360 ). If the return value includes the XOR generated result described above, comparison agent 207 uses the stored session identifier 213 when applying the reverse function to generate the intermediate value, and then uses the stored secret key 214 when applying the reverse function to generate the processor number. In this example, comparison agent 207 acts as a processor number generator for generating a processor number from the return value, secret key 214 , and session identifier 213 . Comparison agent 207 then compares that generated processor number with processor number 209 (block 370 ). If they are identical, server 201 permits client computer 200 to access object 202 (block 380 ). If they are not identical, server 201 disconnects from client computer 200 (block 390 ).
- FIG. 4 illustrates an embodiment of the present invention where the server is web server 400 , object 401 is stored in web site 402 and the verification agent is downloaded as a dynamically linked library (“DLL”) file 407 from web server 400 to browser 404 , which is loaded onto client computer 405 .
- server identifier 406 is associated with web server 400 .
- Web server 400 includes certificate 408 for certifying the identity of the owner of web site 402 and the owner's public key, by signing values reflecting that identity and public key with the private key of a certificate authority—such as VerisignTM. In this way, certificate 408 binds the web site owner's identity with its public key.
- a certificate authority such as VerisignTM.
- Signing engine 413 signs either a Cabinet file or Jar file, depending upon whether a Microsoft® or Netscape® browser is used as browser 404 , using the web site owner's private key. Alternatively, signing engine 413 may sign a hash of that Cabinet or Jar file with that private key.
- the Cabinet or Jar file will enclose a JavaTM applet, which will include Java applet class file 410 , wrapper file 409 (which may be a DLL file that enables the applet to interface with browser 404 ), and a DLL file 407 that selection agent 411 will select from DLL file module 412 .
- Wrapper file 409 may differ for different browsers, e.g., being designed for Raw Native InterfaceTM for Internet ExplorerTM or for Java Native Method InvocationTM for Netscape NavigatorTM.
- FIG. 4 also shows processor identifier 403 , comparison agent 414 , transmitter 415 , session identifier 416 and timer 417 , which each perform functions like those provided by their counterparts shown in FIG. 2.
- Object 401 may include data and/or instructions that a user may want to access over the Internet.
- object 401 may include medical records or bank or stock brokerage account records.
- Object 401 may include a computer program, such as a program accessed to join a chat room or other on-line communication group.
- Object 401 could include video, audio or other content to be downloaded to subscribers or may relate to certain services that the web site owner provides to its customers.
- object 401 it may be desirable to restrict access to object 401 .
- object 401 is content, the owner of web site 402 may only want to permit access to paying subscribers.
- object 401 includes certain confidential records or accounts pertaining to an individual, it may be desirable to restrict access to that individual. If object 401 is invoked to permit access to a chat room, it may be desirable to register participants in advance—then revoke privileges for those who misbehave.
- the system shown in FIG. 4 provides a means for identifying the platform or device trying to access object 401 , enabling web site 402 to grant access to those having permission only.
- Web server 400 may want to identify those seeking access to object 401 for reasons other than access control. For example, when object 401 relates to certain services, the service provider may want the ability to identify particularly valuable customers who should receive special benefits—e.g., discounts, special offers, premium service, free goods and services.
- special benefits e.g., discounts, special offers, premium service, free goods and services.
- the system shown in FIG. 4 provides such an identification capability in addition to enabling access control.
- FIG. 5 is a flow diagram that shows how web server 400 enables authorized client computers 405 to access confidential records stored as object 401 .
- web server 400 registers the client computers 405 for which server 400 will allow access. Registration requires providing server 400 with information embedded in a client computer's processor. Such information may comprise a processor number, which the client computer may send over the Internet to web server 400 , using a Secured Socket Layer or other data encryption means. Alternatively, the computer owner may deliver the processor number, for entry into web server 400 , by electronic or regular mail, by phone or other conventional communications means (block 500 ).
- server 400 may store a processor identifier 403 corresponding to that computer or device when storing that medical record.
- Processor identifier 403 may be the computer's processor number or a value resulting from applying a function to the combination of that processor number and a value associated with web server 400 , such as server identifier 406 .
- server 400 can generate a hash value calculated from the combination of the computer's processor number and server identifier 406 .
- Server 400 can then store the resulting hash value as processor identifier 403 (block 505 ).
- client computer 405 can request access to the confidential records or documents stored as object 401 .
- Browser 404 may transmit such a request over the Internet to web server 400 via standard network protocols using a standard format to address object 401 —such as a Uniform Resource Locator (URL).
- URL Uniform Resource Locator
- web server 400 determines whether to grant the request in the following manner. First, selection agent 411 randomly selects a DLL file 407 from DLL file module 412 .
- DLL file 407 includes secret key 418 , calculator 419 , and server identifier 406 . Each DLL file 407 included in DLL file module 412 preferably has a different secret key 418 .
- Web server 400 assembles either a Cabinet file or Jar file, depending upon the browser client computer 405 uses for browser 404 , that encloses a Java applet, which includes Java applet class file 410 , wrapper file 409 (for enabling the processor verification file to interface with browser 404 ), and DLL file 407 .
- Web server 400 then causes signing engine 413 to sign that Java applet containing file, or a hash of that file, with the web site owner's private key.
- session identifier generator 420 randomly selects a session identifier 416 (block 515 ).
- Web server 400 stores copies of secret key 418 and session identifier 416 that comparison agent 414 will use when checking whether a return value matches processor identifier 403 .
- transmitter 415 sends the signed Java applet containing file (or a signed hash of that file along with the applet), a copy of certificate 408 , and session identifier 416 , from web server 400 to browser 404 (block 520 ).
- Browser 404 includes Java applet authorization agent 421 , which notifies the user of client computer 405 that a Java applet seeks access to information embedded in processor 423 , which may be processor number 422 .
- the user decides whether to grant access. If the user refuses to grant access to processor number 422 , web server 400 disconnects from client computer 405 . If the user grants access, then processor 423 will execute DLL file 407 (block 525 ).
- the Java applet containing file was signed by the web site owner's private key, that file must be decrypted prior to execution using the web site owner's public key, which is derived from certificate 408 .
- the signed hash is decrypted and then compared to a hash of that file to check the integrity of the file. If the decrypted hash matches the hash of the file, then integrity is verified and the applet can be executed.
- the user can instruct browser 404 to handle subsequent transactions involving the trusted applet by directly loading the applet onto client computer 405 without requesting additional authorization.
- Execution of DLL file 407 enables access to processor number 422 , calculation of a hash value from the combination of processor number 422 , server identifier 406 , secret key 418 , and session identifier 416 , and delivery of a request to client computer 405 to return that hash value to web server 400 .
- DLL file 407 may be constructed in a tamper resistant manner, such as by using the techniques described in copending U.S. patent application Ser. No. 08/662,679, filed Jun. 13, 1996, assigned to this application's assignee.
- web server 400 may require the user to enter a user ID and password, using techniques well known to those skilled in the art, before transmitting the Java applet containing file to client computer 405 .
- client computer 405 may include a pre-installed browser plug-in that can perform the functions that the Java applet performs.
- a plug-in can retrieve verification file 407 (after selection agent 411 selects it), cause that file to be transmitted from web server 400 to client computer 405 , then perform those functions that would otherwise be performed by the Java applet.
- Such a browser plug-in may be stored on client computer 405 or, alternatively, on a separate machine readable medium, e.g., a portable disk.
- browser 404 sends that hash value over the Internet to web server 400 (block 530 ).
- the hash value preferably is sent using the Secured Socket Layer or another means for encrypting that value.
- comparison agent 414 calculates a hash value from the combination of processor identifier 403 , secret key 418 and session identifier 416 (block 540 ). If that hash value matches the hash value that arrived from client computer 405 (block 545 ), then the client is granted access to object 401 (block 550 ). If not, then the client is denied access (block 555 ).
- web server 400 can select a different DLL file 407 each time a client computer requests access to object 401 . Similarly, web server 400 can repeat the verification process multiple times, each time using a different DLL file 407 that will have a different secret key 418 , prior to granting access.
- a new set of DLL files may be generated for DLL file module 412 relatively quickly—when desired. Rather than generate DLL files for storage in DLL file module 412 , to ensure that stale DLL files will not be susceptible to tampering DLL files can alternatively be dynamically generated only in response to access requests.
- Different web sites may impose different requirements relating to the frequency with which different verification agents must be used when access to an object is requested.
- a web site may require that a verification agent be used once only, then discarded.
- a web site may permit a client computer to download a verification agent when first requesting access to the web site, then permit the client computer to use that same verification agent for each subsequent access request. Under that scenario, in response to each access request, web server 400 will download a new session identifier.
- a web site can assign a time period during which a verification agent remains valid. In some instances, that time period may be a day or less, in others perhaps as long as a year or more. The time period may be equal to the time period timer 417 sets, which may enable the same verification agent to be used until the time set by timer 417 for return of the return value to the server expires.
- FIGS. 4 and 5 use a Java applet to download the DLL file that includes the verification agent
- other real time dynamic software capable of downloading an executable program from a web server to a client computer, such as ActiveXTM, may be used instead.
- FIG. 6 is a flow diagram illustrating an embodiment of the present invention where a “caller ID” function is employed to verify the identity of those seeking to participate in a private teleconference.
- This embodiment addresses, for example, the current difficulty of identifying the origin of a personal computer user who seeks to join such a teleconference through an Internet connection. Such difficulties may arise from the current ISP vendor practice of recycling the IP addresses of personal computers that seek access to web site URLs, and because IP addresses can be counterfeited.
- FIG. 6 further depicts the dynamic renewal of the “call-back” process, which provides even greater protection against imposter access (block 620 ).
- this “caller ID” application for the Internet may employ many of the features that other forms of telecommunications currently provide, such as “call waiting” and “call priority.”
- features can enable a service provider to provide customized services for different customers, identified by their computers' different platform identifiers.
- the description that accompanies those figures refers to a processor number, or hash value based on that number
- the present invention may use other means to identify the platform.
- the above described Internet caller ID usage concept may employ any hardware based platform identifier that may identify a particular platform—whether it be a smartcard, an embedded certified private/public key pair, or some other identifier embedded in a semiconductor device.
- the embodiments described apply a hash value to a platform identifier, other encryption algorithms may be applied instead.
- the present invention is not limited to the particular usage models described above. Many others exist, including those relating to: video conferencing, teleconferencing and on-line group activity; customer tracking; on-line voting, surveys, or similar activities; or virtual private networks.
- the device controlling the communication connection may grant access only to those users who present a valid machine “fingerprint” based on the device's platform identifier.
- the server can check each caller for the presence of a valid platform identifier before allowing each participant to join the conference.
- This usage model may be applied to various business conferencing activities, including video conferencing and those involving document exchange in addition to the conventional audio conference.
- the server may play a more limited role. For example, where a receiving device controls the connection, the server may simply receive the platform identifier from the calling device then forward it to the receiving device. If the platform identifier for the calling device matches one stored on the receiving device, then the receiving device may authorize the connection.
- a web server may act as a gate keeper that checks the identity of two remote users who seek to exchange data or information by checking their platform identifiers against those stored on the web server, then permits the exchange to go forward after verifying each user's identity.
- a similar usage model can be applied to restrict who can access certain sites—in effect, creating a “gated community.” Such a usage model may be particularly attractive for creating protected sites for children, senior citizens, particular religious or ethnic groups, or teenage girls. Various chat rooms, on-line gaming activities, bulletin boards, and message postings could benefit from such a protected environment. Requiring those accessing such protected sites to provide their platform identifiers makes it easy to identify those engaged in abusive activity. Such abusive users can be banned from accessing such web sites by maintaining a record of platform identifiers that are associated with abusive users, thereby, ensuring a safe and friendly community of users.
- Another valuable application for the platform identifier is to permit only certain authorized devices to modify the contents of a web site. For example, only certain platforms, with earlier registered platform identifiers, could be permitted to alter web site contents that pertain to on-line auction postings, on-line auction bids, and a wide variety of commercial information.
- Such conferencing and on-line group activity usage models may advantageously require two factors to validate a user, e.g., a user ID/password combination (or other form of user identification) and the device identification via its processor number or other statistically unique identifier.
- a user ID/password combination or other form of user identification
- the device identification via its processor number or other statistically unique identifier.
- a specific platform identifier and user ID/password combination could be required to obtain access.
- an unauthorized user who obtains only an authorized user's ID/password may be denied access when trying to establish a connection from a different platform.
- the server can be programmed to trigger a particular response when the user's ID/password combination is used with a platform other than the one typically employed. For example, the server can request additional information about the user prior to permitting the user to log-in, or can deny access, or can contact security.
- a user ID can be altered or duplicated by a malicious user, which is made fairly easy by the open enrollment culture of the Internet, combining such a user ID with a platform identifier provides a web server or computer user with the option of accepting or rejecting log-in requests, when the user ID does not match its companion platform identifier.
- such a platform identifier can be used to track customer buying habits, which may enable on-line retailers to tailor their delivery of marketing materials, special offers, etc. . . . to particular customers.
- a platform identifier can enable global tracking of a user's surfing patterns to enable a content provider to deliver or offer content that is customized to the user's tastes.
- One advantage a hardware based platform identifier has over a software based tracking mechanism, e.g., a cookie is that it is not stored on a device's disk drive or other “publicly accessible” component.
- This usage model further enables on-line retailers to reward valuable customers with various benefits, prizes, discounts, frequent buyer points, etc. . . . , or to offer them special access privileges, e.g., to an exclusive buying club.
- the user ID, platform identifier combination can be particularly useful. By requiring both factors, one can better ensure that a given user is permitted to vote or answer a survey only once, or given a single reward, lottery or raffle ticket. This can be easily accomplished by relying on the platform identifier to register receipt or usage.
- the platform identifier can be a more reliable indicator of identity than a software identification mechanism.
- the platform identifier can be used with a software based public/private key pair as a further check on the identity of a user claiming to rightfully possess a given software based public/private key pair.
Abstract
A system and method for controlling access to an object. The system stores an object and a processor identifier. The system includes a verification agent that can access information embedded in a processor and then calculate from that embedded information a value that may be compared with the stored processor identifier. A comparison agent is used to compare that value with the processor identifier to determine whether the processor corresponds to the processor identifier. If the value that the verification agent returns matches the processor identifier, then the computer grants the user access to the object.
Description
- The present invention relates generally to the field of access control, and particularly to a system and method for verifying the identity of a platform or other device prior to granting access to a private communication channel, to data or to programs.
- The Internet has become a convenient way for a broad class of computer users to access, distribute and exchange information—evident from the large number of individuals, companies and other organizations that have established web sites on the World Wide Web. The Internet permits users to easily access publicly available information, to communicate over private channels, and to access restricted information, such as medical records and bank accounts.
- Although the user's identity is of little importance when granting access to a publicly available web site, strong user authentication is needed to limit access to private teleconferences and restricted information. As users begin to adopt the Internet as a communication channel, the need to identify those calling in from the other end of the line, i.e., the need for a “caller ID” feature like the one telephone companies provide, is becoming more important. Such a “caller ID” feature may apply to on-line banking, remote user dial in to access confidential information, and communications (e.g., to control access to chat rooms or private teleconferences, or to facilitate on-line game usage). In addition, such a “caller ID” feature may enable parental control to prevent children from accessing various web sites.
- Although at first glance current authentication methods, such as user identification/password combinations, tokens, and digital signatures, may seem capable of providing such a “caller ID” function, there are drawbacks to using such methods. Although the combination of a user name (or other user identification) with a user password is easy to implement, such a combination is not very reliable. Passwords may be derived from guesswork or using relatively unsophisticated cracking tools. They also may be shared. Content providers are especially vulnerable to password sharing, which can result in unintentionally supplying content to non-subscribers who obtained access to a subscriber's password. Storing a user identification, password combination in a “cookie”, which a web server can read prior to permitting browser access, does not solve this inherent problem, as cookies can be shared, too.
- Tokens provide stronger authentication, but are expensive to deploy and maintain. A digital signature may not reliably identify a user, if the user either accidentally or intentionally gives imposters access to the user's private key. Moreover, broad deployment of this authentication method requires a public key infrastructure that does not yet exist.
- Given the drawbacks inherent in currently available authentication methods, there is a need for an inexpensive, scaleable, tamper resistant, and user friendly way to verify a user's identity. As the user generally relies on a computer or other device to obtain access to data and programming instructions, one way to help identify the user—e.g., to ensure access is restricted to authorized users only—is to identify the platform or other device the user employs when trying to obtain access. As described below, the present invention proposes a system and method for identifying such a platform or device prior to granting access to an object.
- The present invention relates to a system and method for controlling access to an object. The system stores an object and a processor identifier. The system includes a verification agent that can access information embedded in a processor and then calculate from that embedded information a value that may be compared with the stored processor identifier. A comparison agent is used to compare that value with the processor identifier to determine whether the processor corresponds to the processor identifier. If the value that the verification agent returns matches the processor identifier, then the user is granted access to the object.
- There are many applications for a processor identifier, or other platform identifier, as will be described in more detail below. Some examples include: Internet based communication; Internet based activities restricted to only certain users; web surfing pattern tracking, which may enable content providers and on-line retailers to tailor their products to meet customer preferences; on-line voting, surveys or similar user preference activity; and for verifying the identity of a user seeking access over a virtual private network.
- FIG. 1 is a block diagram illustrating one embodiment of the system of the present invention for controlling access to an object.
- FIG. 2 is a block diagram illustrating a second embodiment of the system of the present invention wherein the system for controlling access to an object resides in a server.
- FIG. 3 is a flow diagram illustrating a method for controlling access to an object stored on the server shown in FIG. 2.
- FIG. 4 is a block diagram illustrating a third embodiment of the present invention wherein the system for controlling access to an object resides in a web server.
- FIG. 5 is a flow diagram illustrating a method for controlling access to confidential records stored on the web server shown in FIG. 4.
- FIG. 6 is a flow diagram illustrating an embodiment of the present invention where a “caller ID” function is employed to verify the identity of those seeking to participate in a private teleconference.
- An improved system and method for controlling access to an object is described. FIG. 1 is a block diagram that illustrates one embodiment of such a system. System100
stores object 101.Object 101 may consist of data and/or executable code. Such executable code may, for example, contain a program that permits a user to communicate with one or more other users over the Internet.Object 101 may be stored in a machine readable storage medium such as, for example, a floppy or hard disk drive. - System100 may be a type of computer, including for example a network server, web server, desktop or notebook PC, or hand held computing device. Alternatively, system 100 may comprise consumer electronics apparatus that can control access to
object 101. When a network or web server, a RAID storage unit may be associated with system 100, which may storeobject 101. - System100 stores a
processor identifier 102. Access toobject 101 is limited to devices that contain a processor, which corresponds toprocessor identifier 102.Processor identifier 102 preferably is a “processor number” (as defined below) or a hash of a processor number with another value. When system 100 is a network or web server,processor identifier 102 may be stored in an associated RAID storage unit. - For determining whether a device's processor corresponds to
processor identifier 102, system 100 includes averification agent 103 and acomparison agent 104.Verification agent 103 can access information embedded in a processor, e.g., a processor number, and calculate from that embedded information a value that may be compared withprocessor identifier 102.Comparison agent 104 compares toprocessor identifier 102 the value thatverification agent 103 returns. If that valuematches processor identifier 102, then the device is granted access toobject 101. -
Verification agent 103 andcomparison agent 104 may reside on a network or web server. Alternatively, they may reside on the device that includes the processor with the embedded information or on a separate machine readable storage medium for use with the network or web server, the device containing the embedded information or some other device.Verification agent 103 thus comprises any software, hardware or combination of software and hardware that can access information embedded in a processor and calculate from that information a value that may be compared with the processor identifier—irrespective of where or how verification agent is physically stored or located. Likewise,comparison agent 104 comprises any software, hardware or combination of software and hardware that can compare with the processor identifier the value thatverification agent 103 returns—irrespective of where or howcomparison agent 104 is physically stored or located. - FIG. 2 is a block diagram illustrating an embodiment of the present invention where
client computer 200 seeks access through client/server communication link 203 to object 202 (which may include data and/or programming instructions) stored onserver 201.Server 201 includessession identifier generator 204,verification agent module 205,selection agent 206,comparison agent 207,transmitter 208,processor identifier 209, andtimer 217. -
Client computer 200 includes aprocessor 210 and embeddedinformation 211, such as a processor number, which identifiesprocessor 210.Processor 210 may be a member of the Pentium® processor family of microprocessors, or a member of a later generation of X86 instruction set compatible processors. Embeddedinformation 211 may be stored inprocessor 210 in a processor ID register or, alternatively, in a constant ROM that holds data that microcode instructions (stored in a microcode ROM) may use—such as is described in U.S. Pat. Nos. 5,790,834 and 5,794,066, assigned to this application's assignee, and as described in the Pentium® Pro Family Developer's Manual. Future Intel processors will add a new value to those described in the Developer's Manual that can be loaded into a processor ID register. That new value is intended to be statistically unique for a given processor, analogous to its “fingerprint.” That statistically unique information can be said to constitute a “processor number” for a given processor. Because such a processor number is only statistically unique, it is possible for more than one platform or device to have the same processor number. -
Processor identifier 209 may be a processor number loaded ontoserver 201 from a client computer. Alternatively,processor identifier 209 may be the value resulting from applying a function to the combination of a processor number and another value, e.g., a server identifier. -
Session identifier generator 204 randomly selects asession identifier 213, whenclient computer 200 attempts to accessobject 202.Session identifier 213 provides a means for matching a value returned from aclient computer 200 with a specific attempt to accessobject 202.Session identifier generator 204 may be a random number generator for producingsession identifiers 213, which each comprise a randomly generated number.Verification agent module 205 includes a plurality ofverification agents 212, each containing programming instructions for accessing embeddedinformation 211, a secret key 214, and a calculator 215 for calculating a return value from the combination of embeddedinformation 211, secret key 214, andsession identifier 213. Eachverification agent 212 may also include programming instructions for requestingclient computer 200 to send the return value toserver 201. Whereprocessor identifier 209 is derived from applying a function to the combination of a processor number and another value,verification agent 212 can include that other value in addition to secret key 214. - Each
verification agent 212 has a different secret key 214. Calculator 215 may calculate a return value that is a function of embeddedinformation 211, secret key 214, andsession identifier 213. For example, such a function could perform an XOR on embeddedinformation 211 and secret key 214 to generate an intermediate value, followed by a second XOR on that intermediate value andsession identifier 213 to yield the return value. Alternatively, as in the case whereverification agent 212 includes another value, e.g., a server identifier, in addition to secret key 214, calculator 215 may employ a hash function, such as SHA-1 or MD5, to calculate a return value that is a function of embeddedinformation 211, secret key 214,session identifier 213 and that additional value. - Secret key214, included in
verification agent 212, may be generated using conventional techniques known in the art, such as generating a random number using a random number generator.Selection agent 206 may randomly select averification agent 212 fromverification agent module 205 in the following manner. Initially,selection agent 206 sequentially assigns a number to eachverification agent 212. When a user subsequently seeks access to object 202,selection agent 206 randomly generates a number that falls within the range of those assigned to theverification agents 212 included inverification module 205, then selects theverification agent 212 that corresponds to that randomly selected number. - The software or hardware constituting
verification agent 212 does not have to be physically located or stored onserver 201. As will be readily apparent to those skilled in the art, some or all of the software and/or hardware that performs theverification agent 212 function—i.e., accessing embeddedinformation 211 and calculating from that embedded information a return value for comparison toprocessor identifier 209—may be located or stored remotely fromserver 201, such as onclient computer 200 or another device, or on a separate machine readable medium, e.g., a portable disk. -
Server 201 also includestimer 217. To prevent a malicious user from having enough time to interceptverification agent 212, and use that verification agent to calculate a return value,timer 217 may disconnectserver 201 fromclient computer 200, whenverification agent 212 fails to return toserver 201 within a prescribed amount of time a return value for comparison toprocessor identifier 209. - FIG. 3 is a flow diagram that shows the
steps server 201 follows to determine whetherclient computer 200 should have access to object 202, where bothprocessor identifier 209 and embeddedinformation 211 are processor numbers. The process begins withclient computer 200 requesting access toobject 202, over client/server communication link 203 (block 300). In response,server 201 causesselection agent 206 to randomly select averification agent 212 fromverification agent module 205, and causessession identifier generator 204 to randomly select a session identifier 213 (block 310).Transmitter 208 then transmits verification agent 212 (which includes secret key 214, calculator 215, and programming instructions for accessingprocessor number 211 and for requestingclient computer 200 to send a return value to server 201) andsession identifier 213 fromserver 201 through client/server communication link 203 to client computer 200 (block 320). - As an alternative to having
transmitter 208 sendverification agent 212 toclient computer 200, software may be loaded ontoclient computer 200 that enablesclient computer 200 to retrieveverification agent 212, after it is selected byselection agent 206. That same software can then facilitate the transmission ofverification agent 212 fromserver 201 toclient computer 200. In addition, software pre-installed ontoclient computer 200, rather than software downloaded fromserver 201, may perform the functions thatverification agent 212 would otherwise perform. -
Server 201 copies and stores secret key 214 andsession identifier 213 prior to transmission ofverification agent 212 toclient computer 200.Processor 210 executes the programming instructions included inverification agent 212 to causeverification agent 212 to read embeddedinformation 211, then calculate a return value from the combination ofprocessor number 211, secret key 214 and session identifier 213 (block 330).Processor 210 then executes additional code included inverification agent 212 to causeclient computer 200 to send the return value over client/server communication link 203 to server 201 (block 340). - If the return value arrives at
server 201 beforetimer 217disconnects server 201 from client computer 200 (block 350),comparison agent 207 performs a reverse function calculation on the return value to generate a processor number (block 360). If the return value includes the XOR generated result described above,comparison agent 207 uses the storedsession identifier 213 when applying the reverse function to generate the intermediate value, and then uses the stored secret key 214 when applying the reverse function to generate the processor number. In this example,comparison agent 207 acts as a processor number generator for generating a processor number from the return value, secret key 214, andsession identifier 213.Comparison agent 207 then compares that generated processor number with processor number 209 (block 370). If they are identical,server 201permits client computer 200 to access object 202 (block 380). If they are not identical,server 201 disconnects from client computer 200 (block 390). - FIG. 4 illustrates an embodiment of the present invention where the server is
web server 400,object 401 is stored inweb site 402 and the verification agent is downloaded as a dynamically linked library (“DLL”) file 407 fromweb server 400 tobrowser 404, which is loaded ontoclient computer 405. In this particular embodiment,server identifier 406 is associated withweb server 400. -
Web server 400 includescertificate 408 for certifying the identity of the owner ofweb site 402 and the owner's public key, by signing values reflecting that identity and public key with the private key of a certificate authority—such as Verisign™. In this way,certificate 408 binds the web site owner's identity with its public key. Those skilled in the art will recognize how to obtain or create such certificates verifying a web site owner's identity and public key, associated with a public key/private key pair.Signing engine 413 signs either a Cabinet file or Jar file, depending upon whether a Microsoft® or Netscape® browser is used asbrowser 404, using the web site owner's private key. Alternatively, signingengine 413 may sign a hash of that Cabinet or Jar file with that private key. - The Cabinet or Jar file will enclose a Java™ applet, which will include Java
applet class file 410, wrapper file 409 (which may be a DLL file that enables the applet to interface with browser 404), and aDLL file 407 thatselection agent 411 will select fromDLL file module 412.Wrapper file 409 may differ for different browsers, e.g., being designed for Raw Native Interface™ for Internet Explorer™ or for Java Native Method Invocation™ for Netscape Navigator™. FIG. 4 also showsprocessor identifier 403,comparison agent 414,transmitter 415,session identifier 416 andtimer 417, which each perform functions like those provided by their counterparts shown in FIG. 2. -
Object 401 may include data and/or instructions that a user may want to access over the Internet. For example, object 401 may include medical records or bank or stock brokerage account records.Object 401 may include a computer program, such as a program accessed to join a chat room or other on-line communication group.Object 401 could include video, audio or other content to be downloaded to subscribers or may relate to certain services that the web site owner provides to its customers. - In each of these instances, and in many others that will be readily apparent to those skilled in the art, it may be desirable to restrict access to
object 401. Whenobject 401 is content, the owner ofweb site 402 may only want to permit access to paying subscribers. Whenobject 401 includes certain confidential records or accounts pertaining to an individual, it may be desirable to restrict access to that individual. Ifobject 401 is invoked to permit access to a chat room, it may be desirable to register participants in advance—then revoke privileges for those who misbehave. The system shown in FIG. 4 provides a means for identifying the platform or device trying to accessobject 401, enablingweb site 402 to grant access to those having permission only. -
Web server 400 may want to identify those seeking access to object 401 for reasons other than access control. For example, whenobject 401 relates to certain services, the service provider may want the ability to identify particularly valuable customers who should receive special benefits—e.g., discounts, special offers, premium service, free goods and services. The system shown in FIG. 4 provides such an identification capability in addition to enabling access control. - FIG. 5 is a flow diagram that shows how
web server 400 enables authorizedclient computers 405 to access confidential records stored asobject 401. When such records are stored inweb site 402,web server 400 registers theclient computers 405 for whichserver 400 will allow access. Registration requires providingserver 400 with information embedded in a client computer's processor. Such information may comprise a processor number, which the client computer may send over the Internet toweb server 400, using a Secured Socket Layer or other data encryption means. Alternatively, the computer owner may deliver the processor number, for entry intoweb server 400, by electronic or regular mail, by phone or other conventional communications means (block 500). - If
object 401 is a patient's medical record, for example, and that patient has a computer or other device that can accessweb site 402,server 400 may store aprocessor identifier 403 corresponding to that computer or device when storing that medical record.Processor identifier 403 may be the computer's processor number or a value resulting from applying a function to the combination of that processor number and a value associated withweb server 400, such asserver identifier 406. To register a client computer for permitted access toobject 401, such as the patient's computer described above,server 400 can generate a hash value calculated from the combination of the computer's processor number andserver identifier 406.Server 400 can then store the resulting hash value as processor identifier 403 (block 505). - Through
browser 404,client computer 405 can request access to the confidential records or documents stored asobject 401.Browser 404 may transmit such a request over the Internet toweb server 400 via standard network protocols using a standard format to addressobject 401—such as a Uniform Resource Locator (URL). - When
client computer 405 requests access to object 401 (block 510),web server 400 determines whether to grant the request in the following manner. First,selection agent 411 randomly selects aDLL file 407 fromDLL file module 412. DLL file 407 includessecret key 418,calculator 419, andserver identifier 406. Each DLL file 407 included inDLL file module 412 preferably has a differentsecret key 418.Web server 400 assembles either a Cabinet file or Jar file, depending upon thebrowser client computer 405 uses forbrowser 404, that encloses a Java applet, which includes Javaapplet class file 410, wrapper file 409 (for enabling the processor verification file to interface with browser 404), and DLL file 407.Web server 400 then causessigning engine 413 to sign that Java applet containing file, or a hash of that file, with the web site owner's private key. Concurrently,session identifier generator 420 randomly selects a session identifier 416 (block 515).Web server 400 stores copies ofsecret key 418 andsession identifier 416 thatcomparison agent 414 will use when checking whether a return value matchesprocessor identifier 403. - Next,
transmitter 415 sends the signed Java applet containing file (or a signed hash of that file along with the applet), a copy ofcertificate 408, andsession identifier 416, fromweb server 400 to browser 404 (block 520).Browser 404 includes Javaapplet authorization agent 421, which notifies the user ofclient computer 405 that a Java applet seeks access to information embedded inprocessor 423, which may beprocessor number 422. After the user establishes that the Java applet is a trusted applet, e.g., after the certificate authority's public key is used to decryptcertificate 408 to reveal the identity of the web site owner, the user decides whether to grant access. If the user refuses to grant access toprocessor number 422,web server 400 disconnects fromclient computer 405. If the user grants access, thenprocessor 423 will execute DLL file 407 (block 525). - Because the Java applet containing file was signed by the web site owner's private key, that file must be decrypted prior to execution using the web site owner's public key, which is derived from
certificate 408. In the alternative embodiment, where a signed hash is transmitted tobrowser 404 along with the unsigned Java applet containing file, the signed hash is decrypted and then compared to a hash of that file to check the integrity of the file. If the decrypted hash matches the hash of the file, then integrity is verified and the applet can be executed. - After the user establishes a Java applet as a trusted applet, the user can instruct
browser 404 to handle subsequent transactions involving the trusted applet by directly loading the applet ontoclient computer 405 without requesting additional authorization. - Execution of
DLL file 407 enables access toprocessor number 422, calculation of a hash value from the combination ofprocessor number 422,server identifier 406,secret key 418, andsession identifier 416, and delivery of a request toclient computer 405 to return that hash value toweb server 400. -
DLL file 407 may be constructed in a tamper resistant manner, such as by using the techniques described in copending U.S. patent application Ser. No. 08/662,679, filed Jun. 13, 1996, assigned to this application's assignee. In some embodiments,web server 400 may require the user to enter a user ID and password, using techniques well known to those skilled in the art, before transmitting the Java applet containing file toclient computer 405. - As an alternative to transmitting from
web server 400 to client computer 405 a Cabinet or Jar file that contains Javaapplet class file 410,wrapper file 409, and DLLverification agent file 407,client computer 405 may include a pre-installed browser plug-in that can perform the functions that the Java applet performs. Such a plug-in can retrieve verification file 407 (afterselection agent 411 selects it), cause that file to be transmitted fromweb server 400 toclient computer 405, then perform those functions that would otherwise be performed by the Java applet. Such a browser plug-in may be stored onclient computer 405 or, alternatively, on a separate machine readable medium, e.g., a portable disk. - After the hash value has been calculated from the combination of
processor number 422,server identifier 406,secret key 418, andsession identifier 416,browser 404 sends that hash value over the Internet to web server 400 (block 530). The hash value preferably is sent using the Secured Socket Layer or another means for encrypting that value. Ifweb server 400 receives the hash value within the time set by timer 417 (block 535), thencomparison agent 414 calculates a hash value from the combination ofprocessor identifier 403,secret key 418 and session identifier 416 (block 540). If that hash value matches the hash value that arrived from client computer 405 (block 545), then the client is granted access to object 401 (block 550). If not, then the client is denied access (block 555). - To provide further confidence that
client computer 405matches processor identifier 403 associated withweb site 402,web server 400 can select adifferent DLL file 407 each time a client computer requests access toobject 401. Similarly,web server 400 can repeat the verification process multiple times, each time using adifferent DLL file 407 that will have a differentsecret key 418, prior to granting access. In addition, because the only action required to generate new DLL files for verification agents is to generate new secret keys, a new set of DLL files may be generated forDLL file module 412 relatively quickly—when desired. Rather than generate DLL files for storage inDLL file module 412, to ensure that stale DLL files will not be susceptible to tampering DLL files can alternatively be dynamically generated only in response to access requests. - Different web sites may impose different requirements relating to the frequency with which different verification agents must be used when access to an object is requested. At one extreme, a web site may require that a verification agent be used once only, then discarded. At the other extreme, a web site may permit a client computer to download a verification agent when first requesting access to the web site, then permit the client computer to use that same verification agent for each subsequent access request. Under that scenario, in response to each access request,
web server 400 will download a new session identifier. The client computer will then use the previously retrieved permanent verification agent to calculate a return value based on the processor number, the secret key associated with the permanent verification agent, and the new session identifier, then return that value to the web server for comparison toprocessor identifier 403, as described above. As an alternative to either single use or permanent use of a verification agent, a web site can assign a time period during which a verification agent remains valid. In some instances, that time period may be a day or less, in others perhaps as long as a year or more. The time period may be equal to thetime period timer 417 sets, which may enable the same verification agent to be used until the time set bytimer 417 for return of the return value to the server expires. - Although the embodiments of the present invention shown in FIGS. 4 and 5 use a Java applet to download the DLL file that includes the verification agent, other real time dynamic software capable of downloading an executable program from a web server to a client computer, such as ActiveX™, may be used instead.
- FIG. 6 is a flow diagram illustrating an embodiment of the present invention where a “caller ID” function is employed to verify the identity of those seeking to participate in a private teleconference. This embodiment addresses, for example, the current difficulty of identifying the origin of a personal computer user who seeks to join such a teleconference through an Internet connection. Such difficulties may arise from the current ISP vendor practice of recycling the IP addresses of personal computers that seek access to web site URLs, and because IP addresses can be counterfeited.
- As is apparent from the above description, a potential solution to this problem is to use a “caller ID” like function that uses dynamic call-back software to match a statistically unique platform ID with a platform ID previously authorized to participate in such a teleconference.
- As shown in FIG. 6, to use such a “caller ID” feature in such an Internet teleconferencing application, all the platform IDs for the computers or other devices belonging to users who are authorized to call-in to the teleconference must be delivered to the web site, which will control access to the teleconference (block600). When a user requests access to the teleconference, the web server initiates a “call-back” process for dynamically validating the user's platform ID (block 610). Such a dynamic call-back process may comprise downloading a Java applet that includes a “caller ID” plug in—such as is described above in connection with the apparatus and flow chart shown in FIGS. 4 and 5. Such a process may employ hash and encryption functions, and a timing mechanism, to ensure the integrity of the data returned to the web server that is used to verify a user's platform's identity. FIG. 6 further depicts the dynamic renewal of the “call-back” process, which provides even greater protection against imposter access (block 620).
- If the “call-back” process confirms that the user is authorized to join the teleconference, access is granted (block630). Otherwise, access is denied (block 640).
- As those skilled in the art will readily appreciate, this “caller ID” application for the Internet may employ many of the features that other forms of telecommunications currently provide, such as “call waiting” and “call priority.” In addition to using such features for voice or even video conferencing, such features can enable a service provider to provide customized services for different customers, identified by their computers' different platform identifiers.
- What makes these types of applications, or usage models, possible is the presence of a statistically unique platform identifier. Although the apparatus represented in block diagram form in FIGS. 2 and 4 may be used to implement such applications, those skilled in the art will recognize that many variations of such systems may be used instead. Any mechanism that permits access to the platform identifier, for the purpose of identifying a particular platform, falls within the spirit and scope of the present invention.
- Although the description that accompanies those figures refers to a processor number, or hash value based on that number, the present invention may use other means to identify the platform. For example, the above described Internet caller ID usage concept may employ any hardware based platform identifier that may identify a particular platform—whether it be a smartcard, an embedded certified private/public key pair, or some other identifier embedded in a semiconductor device. In addition, although the embodiments described apply a hash value to a platform identifier, other encryption algorithms may be applied instead.
- The present invention is not limited to the particular usage models described above. Many others exist, including those relating to: video conferencing, teleconferencing and on-line group activity; customer tracking; on-line voting, surveys, or similar activities; or virtual private networks.
- For Internet based conferencing, the device controlling the communication connection may grant access only to those users who present a valid machine “fingerprint” based on the device's platform identifier. Where all parties to the conference are connected through a server, the server can check each caller for the presence of a valid platform identifier before allowing each participant to join the conference. This usage model may be applied to various business conferencing activities, including video conferencing and those involving document exchange in addition to the conventional audio conference.
- Where the connection is from one device to another, the server may play a more limited role. For example, where a receiving device controls the connection, the server may simply receive the platform identifier from the calling device then forward it to the receiving device. If the platform identifier for the calling device matches one stored on the receiving device, then the receiving device may authorize the connection. Alternatively, a web server may act as a gate keeper that checks the identity of two remote users who seek to exchange data or information by checking their platform identifiers against those stored on the web server, then permits the exchange to go forward after verifying each user's identity.
- A similar usage model can be applied to restrict who can access certain sites—in effect, creating a “gated community.” Such a usage model may be particularly attractive for creating protected sites for children, senior citizens, particular religious or ethnic groups, or teenage girls. Various chat rooms, on-line gaming activities, bulletin boards, and message postings could benefit from such a protected environment. Requiring those accessing such protected sites to provide their platform identifiers makes it easy to identify those engaged in abusive activity. Such abusive users can be banned from accessing such web sites by maintaining a record of platform identifiers that are associated with abusive users, thereby, ensuring a safe and friendly community of users.
- Another valuable application for the platform identifier is to permit only certain authorized devices to modify the contents of a web site. For example, only certain platforms, with earlier registered platform identifiers, could be permitted to alter web site contents that pertain to on-line auction postings, on-line auction bids, and a wide variety of commercial information.
- Such conferencing and on-line group activity usage models may advantageously require two factors to validate a user, e.g., a user ID/password combination (or other form of user identification) and the device identification via its processor number or other statistically unique identifier. To reduce the likelihood of improper access, by a hacker or undesirable caller, both a specific platform identifier and user ID/password combination could be required to obtain access. When two factors are required, an unauthorized user who obtains only an authorized user's ID/password may be denied access when trying to establish a connection from a different platform. Alternatively, because such a platform identifier enables a server to track usage patterns, the server can be programmed to trigger a particular response when the user's ID/password combination is used with a platform other than the one typically employed. For example, the server can request additional information about the user prior to permitting the user to log-in, or can deny access, or can contact security.
- Those skilled in the art will readily appreciate the advantages such a two factor approach provides. Although a user ID can be altered or duplicated by a malicious user, which is made fairly easy by the open enrollment culture of the Internet, combining such a user ID with a platform identifier provides a web server or computer user with the option of accepting or rejecting log-in requests, when the user ID does not match its companion platform identifier.
- For the customer tracking usage model, such a platform identifier can be used to track customer buying habits, which may enable on-line retailers to tailor their delivery of marketing materials, special offers, etc. . . . to particular customers. Similarly, such a platform identifier can enable global tracking of a user's surfing patterns to enable a content provider to deliver or offer content that is customized to the user's tastes. One advantage a hardware based platform identifier has over a software based tracking mechanism, e.g., a cookie, is that it is not stored on a device's disk drive or other “publicly accessible” component. This usage model further enables on-line retailers to reward valuable customers with various benefits, prizes, discounts, frequent buyer points, etc. . . . , or to offer them special access privileges, e.g., to an exclusive buying club.
- For the usage model addressing limited access, the user ID, platform identifier combination can be particularly useful. By requiring both factors, one can better ensure that a given user is permitted to vote or answer a survey only once, or given a single reward, lottery or raffle ticket. This can be easily accomplished by relying on the platform identifier to register receipt or usage.
- For the virtual private network usage model, the platform identifier can be a more reliable indicator of identity than a software identification mechanism. In addition, like the user ID example described above, in a virtual private network the platform identifier can be used with a software based public/private key pair as a further check on the identity of a user claiming to rightfully possess a given software based public/private key pair.
- Those skilled in the art will recognize many additional applications for a platform identifier that can verify the identity of a user. The foregoing thus serves only as a detailed description of particular embodiments of the present invention. The invention embraces all alternatives, modifications and variations that fall within the letter and spirit of the claims, as well as all equivalents of the claimed subject matter.
Claims (41)
1. A system for controlling access to an object comprising:
an accessible object;
a processor identifier associated with the object;
a verification agent for accessing information embedded in a processor and calculating from that embedded information a value that may be compared with the processor identifier; and
a comparison agent for comparing the value with the processor identifier to determine whether the processor corresponds to the processor identifier.
2. The system of claim 1 further comprising a server that includes:
a session identifier generator for generating a session identifier;
a plurality of verification agents, each including a different secret key and a calculator for calculating a return value that is a function of the embedded information, the secret key and a session identifier;
a selection agent for selecting a verification agent; and
a transmitter for transmitting a selected verification agent from the server to a client computer that contains the processor.
3. The system of claim 2 wherein the server is a web server that stores the object in a web site, and the processor identifier comprises a hash value calculated from the combination of a processor number and a server identifier.
4. The system of claim 3 wherein the calculator is a hash engine for calculating a return value comprising a hash value calculated from the combination of the embedded information, the server identifier, a secret key and a session identifier.
5. The system of claim 4 wherein the comparison agent compares the return value to a hash value calculated from the combination of the processor identifier, the secret key and the session identifier.
6. The system of claim 5 wherein the web server further includes a timer for disconnecting the web server from a client computer when the verification agent does not return to the web server within a prescribed amount of time a hash value that matches the hash value calculated from the combination of the processor identifier, the secret key and the session identifier.
7. The system of claim 2 wherein the server includes a processor number generator for generating a processor number from the return value, the secret key and the session identifier.
8. A machine readable storage medium having stored therein programming instructions which, when executed by a central processing unit, permit access to information embedded in a processor and subsequently calculate from that embedded information a value that may be compared with a processor identifier stored in a server.
9. The machine readable storage medium of claim 8 wherein the programming instructions include instructions for:
selecting a verification agent from a plurality of verification agents; and
transmitting a selected verification agent from the server to a client computer.
10. The machine readable storage medium of claim 9 wherein each verification agent includes programming instructions for calculating a hash value.
11. The machine readable storage medium of claim 10 wherein the programming instructions further include instructions for comparing a hash value calculated from the combination of the embedded information, a server identifier, a secret key, and a session identifier, to a hash value calculated from the combination of the processor identifier, the secret key and the session identifier.
12. The machine readable storage medium of claim 11 wherein the programming instructions further include instructions for disconnecting a server from a client computer when the verification agent does not return to the server within a prescribed amount of time a hash value that matches the hash value calculated from the combination of the processor identifier, the secret key and the session identifier.
13. A system for controlling access to an object comprising:
means for storing the object;
means for storing a processor identifier;
means for accessing information embedded in a processor;
means for calculating from that embedded information a value that may be compared with the processor identifier; and
means for comparing the value with the processor identifier to determine whether the processor corresponds to the processor identifier.
14. The system of claim 13 wherein:
the means for storing the object is a web server that stores the object on a web site; and
the processor identifier comprises a hash value calculated from the combination of a processor number and a server identifier.
15. The system of claim 14 wherein the web server includes:
means for generating a session identifier;
a plurality of verification agents, each containing a different secret key and means for calculating a hash value from the combination of the embedded information, the server identifier, the secret key and a session identifier;
means for selecting a verification agent; and
means for transmitting a selected verification agent from the web server to a client computer.
16. The system of claim 15 wherein the web server further includes means for disconnecting the web server from the client computer when the selected verification agent does not return to the web server within a prescribed amount of time a hash value that matches the hash value calculated from the combination of the processor identifier, a secret key and a session identifier.
17. A method for controlling access to an object comprising the steps of:
storing the object in a computer;
storing a processor identifier in the computer;
accessing information embedded in a processor;
calculating from that embedded information a value that may be compared with the processor identifier; and
comparing the value with the processor identifier to determine whether the processor corresponds to the processor identifier.
18. The method of claim 17 wherein:
the computer is a web server that stores the object on a web site; and
the processor identifier is stored in the web server and comprises a hash value calculated from the combination of a processor number and a server identifier.
19. The method of claim 18 further including the steps of:
generating a session identifier; and
calculating a hash value from the combination of the embedded information, the server identifier, a secret key and a session identifier.
20. A method for enabling a platform to access via the Internet an object stored on a web server comprising:
storing a platform identifier on the web server;
receiving a request from a platform for access to the object;
initiating a dynamic call-back process for dynamically accessing a hardware based platform identifier associated with the platform;
comparing the platform identifier associated with the platform to the platform identifier stored on the web server; and
granting access to the object if the platform identifier associated with the platform matches the platform identifier stored on the web server.
21. A method for connecting a platform to a conference, comprising:
receiving a request to access a conference from a platform having a platform identifier;
checking the platform identifier against a set of platform identifiers that are authorized to participate in the conference; and
allowing the platform to join the conference if its platform identifier matches one included in the set of platform identifiers.
22. The method of claim 21 wherein the platform identifier is a processor number.
23. The method of claim 21 wherein the platform identifier is a hash of a value comprising a processor number.
24. A method for restricting access to a web site, comprising:
receiving a request to access the web site from a platform having a platform identifier;
checking the platform identifier against a set of platform identifiers that are authorized to access the web site; and
allowing the platform to access the web site if its platform identifier matches one included in the set of platform identifiers.
25. The method of claim 24 wherein the platform identifier is a processor number.
26. The method of claim 24 wherein the platform identifier is a hash of a value comprising a processor number.
27. The method of claim 24 further comprising the step of preventing access to the web site if the platform identifier matches a list of those to be denied access to the web site.
28. The method of claim 24 wherein the set of platform identifiers that are authorized to access the web site are restricted to those platform identifiers that correspond to platforms authorized to modify the web site's content.
29. A method for permitting access to a web site, comprising:
receiving a request to access the web site from a user having a user identification and a password, and using a platform having a hardware based platform identifier;
checking the user's identification and password for authorization to access the web site;
checking the platform identifier; and
allowing the user to access the web site.
30. The method of claim 29 wherein the platform identifier is a processor number.
31. The method of claim 29 wherein the platform identifier is a hash of a value comprising a processor number.
32. A method for tracking a platform's web surfing activity, comprising:
recording a platform's hardware based platform identifier when the platform accesses a web site.
33. A method of claim 32 wherein the platform identifier is a processor number.
34. The method of claim 32 wherein the platform identifier is a hash of a value comprising a processor number.
35. The method of claim 32 wherein the web site is a commercial web site.
36. The method of claim 32 wherein the web site is an on-line voting web site.
37. The method of claim 32 wherein the web site is a web site for an on-line survey.
38. A method for permitting access to a server through a virtual private network, comprising:
receiving a request to access the server from a remote user having a certificate for verifying the user's identity and public key, and using a platform having a hardware based platform identifier;
decrypting the certificate using a certificate authority's public key;
checking the platform identifier; and
allowing the user to access the server.
39. A method of claim 38 wherein the platform identifier is a processor number.
40. The method of claim 38 wherein the platform identifier is a hash of a value comprising a processor number.
41. The system of claim 6 wherein the same verification agent is used to access information embedded in a processor until the timer disconnects the web server from the client computer.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/295,515 US20030131115A1 (en) | 1999-01-19 | 2002-11-15 | System and method for using internet based caller ID for controlling access to an object stored in a computer |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/234,051 US6418472B1 (en) | 1999-01-19 | 1999-01-19 | System and method for using internet based caller ID for controlling access to an object stored in a computer |
US10/121,174 US6523067B2 (en) | 1999-01-19 | 2002-04-12 | System and method for using internet based caller ID for controlling access to an object stored in a computer |
US10/295,515 US20030131115A1 (en) | 1999-01-19 | 2002-11-15 | System and method for using internet based caller ID for controlling access to an object stored in a computer |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/121,174 Division US6523067B2 (en) | 1999-01-19 | 2002-04-12 | System and method for using internet based caller ID for controlling access to an object stored in a computer |
Publications (1)
Publication Number | Publication Date |
---|---|
US20030131115A1 true US20030131115A1 (en) | 2003-07-10 |
Family
ID=22879686
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/234,051 Expired - Lifetime US6418472B1 (en) | 1999-01-19 | 1999-01-19 | System and method for using internet based caller ID for controlling access to an object stored in a computer |
US10/121,174 Expired - Fee Related US6523067B2 (en) | 1999-01-19 | 2002-04-12 | System and method for using internet based caller ID for controlling access to an object stored in a computer |
US10/295,515 Abandoned US20030131115A1 (en) | 1999-01-19 | 2002-11-15 | System and method for using internet based caller ID for controlling access to an object stored in a computer |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/234,051 Expired - Lifetime US6418472B1 (en) | 1999-01-19 | 1999-01-19 | System and method for using internet based caller ID for controlling access to an object stored in a computer |
US10/121,174 Expired - Fee Related US6523067B2 (en) | 1999-01-19 | 2002-04-12 | System and method for using internet based caller ID for controlling access to an object stored in a computer |
Country Status (1)
Country | Link |
---|---|
US (3) | US6418472B1 (en) |
Cited By (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030142806A1 (en) * | 2001-02-02 | 2003-07-31 | Stefan Unger | Method for verifying telephone call back information for return calls which are initiated via the internet |
US20040117616A1 (en) * | 2002-12-16 | 2004-06-17 | Silvester Kelan C. | Method and mechanism for validating legitimate software calls into secure software |
WO2005119396A1 (en) * | 2004-06-04 | 2005-12-15 | Nokia Corporation | A method and device for determining whether an application should access protected digital content |
US20060277607A1 (en) * | 2003-05-01 | 2006-12-07 | Chung Hyun-Kwon | Authenticating method and apparatus |
US20080162484A1 (en) * | 2006-12-27 | 2008-07-03 | Ryo Yoshida | Technique for controlling access to data |
EP2082518A2 (en) * | 2006-11-02 | 2009-07-29 | Legitimi Limited | Access control system based on a hardware and software signature of a requesting device |
US20100313256A1 (en) * | 2009-06-05 | 2010-12-09 | Tomoki Sekiguchi | Virtual computer system, access control method and communication device for the same |
US8195625B1 (en) * | 2005-08-01 | 2012-06-05 | Fonseca Danilo E | Datacentroid |
US20130179350A1 (en) * | 2012-01-11 | 2013-07-11 | Rawllin International Inc. | Electronic signature security algorithms |
US20140025949A1 (en) * | 2012-07-20 | 2014-01-23 | Google Inc. | Method and system for browser identity |
US8804731B2 (en) * | 2010-10-27 | 2014-08-12 | Intel Corporation | Generating platform identification for certification version signaling |
US9047456B2 (en) * | 2012-03-20 | 2015-06-02 | Canon Information And Imaging Solutions, Inc. | System and method for controlling access to a resource |
US9444620B1 (en) * | 2010-06-24 | 2016-09-13 | F5 Networks, Inc. | Methods for binding a session identifier to machine-specific identifiers and systems thereof |
US9571634B1 (en) | 2015-08-03 | 2017-02-14 | International Business Machines Corporation | Digital signature-over-voice for caller ID verification |
US10474807B2 (en) | 2005-08-01 | 2019-11-12 | Danilo E. Fonseca | Password/encryption protection |
US11063758B1 (en) | 2016-11-01 | 2021-07-13 | F5 Networks, Inc. | Methods for facilitating cipher selection and devices thereof |
Families Citing this family (166)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH0761340A (en) * | 1993-08-25 | 1995-03-07 | Nippon Denshi Kogyo Kk | Control point detecting method in abs device |
US6745245B1 (en) * | 1998-04-09 | 2004-06-01 | Webtv Networks, Inc. | Managing access to set-top box objects using television conditional access system |
US6986062B2 (en) * | 1998-04-09 | 2006-01-10 | Microsoft Corporation | Set top box object security system |
US7047416B2 (en) * | 1998-11-09 | 2006-05-16 | First Data Corporation | Account-based digital signature (ABDS) system |
US6820202B1 (en) * | 1998-11-09 | 2004-11-16 | First Data Corporation | Account authority digital signature (AADS) system |
US7277947B1 (en) * | 1998-12-04 | 2007-10-02 | Koninklijke Philips Electronics N.V. | System and method for supporting ongoing activities and relocating the ongoing activities from one terminal to another terminal |
US6418472B1 (en) * | 1999-01-19 | 2002-07-09 | Intel Corporation | System and method for using internet based caller ID for controlling access to an object stored in a computer |
IL128720A (en) * | 1999-02-25 | 2009-06-15 | Cidway Technologies Ltd | Method for certification of over the phone transactions |
US7107612B1 (en) | 1999-04-01 | 2006-09-12 | Juniper Networks, Inc. | Method, apparatus and computer program product for a network firewall |
US6701432B1 (en) * | 1999-04-01 | 2004-03-02 | Netscreen Technologies, Inc. | Firewall including local bus |
US7093130B1 (en) * | 2000-01-24 | 2006-08-15 | The Regents Of The University Of California | System and method for delivering and examining digital tickets |
US6954854B1 (en) * | 1999-06-21 | 2005-10-11 | Hitachi, Ltd. | Electronic authentication method, electronic authentication apparatus and electronic authentication storage medium |
AUPQ278799A0 (en) * | 1999-09-13 | 1999-10-07 | Telstra R & D Management Pty Ltd | An access control method |
US6578199B1 (en) * | 1999-11-12 | 2003-06-10 | Fujitsu Limited | Automatic tracking system and method for distributable software |
US7363361B2 (en) * | 2000-08-18 | 2008-04-22 | Akamai Technologies, Inc. | Secure content delivery system |
US7946913B2 (en) * | 1999-12-10 | 2011-05-24 | Elottery, Inc. | System and method for operating on-line governmental lottery games |
US7315950B1 (en) * | 1999-12-20 | 2008-01-01 | International Business Machines Corporation | Method of securely sharing information over public networks using untrusted service providers and tightly controlling client accessibility |
US6985901B1 (en) | 1999-12-23 | 2006-01-10 | Accenture Llp | Controlling data collection, manipulation and storage on a network with service assurance capabilities |
EP1113361A1 (en) * | 2000-01-03 | 2001-07-04 | Wimba.Com S.A. | Process of communication between an applet and a local agent using a socket communication channel |
US6952770B1 (en) * | 2000-03-14 | 2005-10-04 | Intel Corporation | Method and apparatus for hardware platform identification with privacy protection |
FR2809555B1 (en) * | 2000-05-26 | 2002-07-12 | Gemplus Card Int | SECURING DATA EXCHANGES BETWEEN CONTROLLERS |
CA2960857C (en) * | 2000-06-07 | 2019-07-09 | Kount Inc. | Online machine data collection and archiving process |
US7149803B2 (en) * | 2000-06-08 | 2006-12-12 | At&T Corp. | Method for content distribution in a network supporting a security protocol |
US7024696B1 (en) | 2000-06-14 | 2006-04-04 | Reuben Bahar | Method and system for prevention of piracy of a given software application via a communications network |
US6766353B1 (en) * | 2000-07-11 | 2004-07-20 | Motorola, Inc. | Method for authenticating a JAVA archive (JAR) for portable devices |
US7143163B1 (en) * | 2000-07-26 | 2006-11-28 | Lucent Technologies Inc. | System and method for exacting a system resource access cost |
US7096354B2 (en) * | 2000-08-04 | 2006-08-22 | First Data Corporation | Central key authority database in an ABDS system |
US6983368B2 (en) * | 2000-08-04 | 2006-01-03 | First Data Corporation | Linking public key of device to information during manufacture |
EP1316171A4 (en) * | 2000-08-04 | 2006-05-03 | First Data Corp | Person-centric account-based digital signature system |
US6789189B2 (en) * | 2000-08-04 | 2004-09-07 | First Data Corporation | Managing account database in ABDS system |
US7082533B2 (en) * | 2000-08-04 | 2006-07-25 | First Data Corporation | Gauging risk in electronic communications regarding accounts in ABDS system |
US7010691B2 (en) * | 2000-08-04 | 2006-03-07 | First Data Corporation | ABDS system utilizing security information in authenticating entity access |
US6978369B2 (en) * | 2000-08-04 | 2005-12-20 | First Data Corporation | Person-centric account-based digital signature system |
US7178166B1 (en) * | 2000-09-19 | 2007-02-13 | Internet Security Systems, Inc. | Vulnerability assessment and authentication of a computer by a local scanner |
US6895504B1 (en) * | 2000-09-29 | 2005-05-17 | Intel Corporation | Enabling secure communications with a client |
US20050149364A1 (en) * | 2000-10-06 | 2005-07-07 | Ombrellaro Mark P. | Multifunction telemedicine software with integrated electronic medical record |
JP3692290B2 (en) * | 2000-11-24 | 2005-09-07 | 株式会社エヌ・ティ・ティ・ドコモ | Data acquisition method and terminal |
US8380862B2 (en) * | 2000-11-30 | 2013-02-19 | Fan Chiang Holdings, Llc | Method and apparatus for user-specific website claiming |
US6839692B2 (en) * | 2000-12-01 | 2005-01-04 | Benedor Corporation | Method and apparatus to provide secure purchase transactions over a computer network |
US20020143869A1 (en) * | 2001-01-03 | 2002-10-03 | Hal Cohen | Method and apparatus for making random introductions electronically |
US7103666B2 (en) * | 2001-01-12 | 2006-09-05 | Siemens Medical Solutions Health Services Corporation | System and user interface supporting concurrent application operation and interoperability |
US7334031B2 (en) * | 2001-01-12 | 2008-02-19 | Siemens Medical Solutions Health Services Corporation | System and user interface supporting processing and activity management for concurrently operating applications |
US7043752B2 (en) * | 2001-01-12 | 2006-05-09 | Siemens Medical Solutions Health Services Corporation | System and user interface supporting concurrent application initiation and interoperability |
US20020184351A1 (en) * | 2001-02-07 | 2002-12-05 | Istvan Anthony F. | Information access in user model-based interactive television |
US20020152461A1 (en) * | 2001-02-07 | 2002-10-17 | Istvan Anthony F. | Coordination of favorites among disparate devices in an interactive video casting system |
US20020152475A1 (en) * | 2001-02-07 | 2002-10-17 | Istvan Anthony F. | User model for interactive television system |
US6895104B2 (en) | 2001-02-16 | 2005-05-17 | Sac Technologies, Inc. | Image identification system |
US6983375B2 (en) | 2001-04-13 | 2006-01-03 | Ge Medical Technology Services, Inc. | Method and system to grant indefinite use of software options resident on a device |
US7467298B2 (en) * | 2001-04-16 | 2008-12-16 | Microsoft Corporation | Methods and arrangements for selectively maintaining parental access consent in a network environment |
US7526480B2 (en) | 2001-06-08 | 2009-04-28 | Cisco Technology, Inc. | Method and apparatus for controlled access of requests from virtual private network devices to managed information objects using simple network management protocol and multi-topology routing |
US7099947B1 (en) * | 2001-06-08 | 2006-08-29 | Cisco Technology, Inc. | Method and apparatus providing controlled access of requests from virtual private network devices to managed information objects using simple network management protocol |
US7008288B2 (en) * | 2001-07-26 | 2006-03-07 | Eastman Kodak Company | Intelligent toy with internet connection capability |
DE50104221D1 (en) * | 2001-08-10 | 2004-11-25 | Siemens Ag | Method, communication arrangement, data network server and private branch exchange for expanding a data network connection |
JP2003084979A (en) * | 2001-09-07 | 2003-03-20 | Internatl Business Mach Corp <Ibm> | Method for starting electronic device, electronic device, and program |
US7624439B2 (en) * | 2001-10-29 | 2009-11-24 | Seventh Knight | Authenticating resource requests in a computer system |
US7171468B2 (en) * | 2001-11-10 | 2007-01-30 | Kabushiki Kaisha Toshiba | System and method for accessing a document management repository |
US7587613B2 (en) * | 2001-12-21 | 2009-09-08 | Creative Mines Llc | Method and apparatus for selectively enabling a microprocessor-based system |
US7356845B2 (en) * | 2002-01-30 | 2008-04-08 | Lucent Technologies Inc. | Method and apparatus for identification tagging documents in a computer system |
US7275109B1 (en) * | 2002-04-02 | 2007-09-25 | Nortel Networks Limited | Network communication authentication |
US7644434B2 (en) * | 2002-04-25 | 2010-01-05 | Applied Identity, Inc. | Computer security system |
US8910241B2 (en) | 2002-04-25 | 2014-12-09 | Citrix Systems, Inc. | Computer security system |
US6931132B2 (en) * | 2002-05-10 | 2005-08-16 | Harris Corporation | Secure wireless local or metropolitan area network and related methods |
EP1510032A4 (en) * | 2002-05-15 | 2007-05-30 | Bio Key Int Inc | Match template protection within biometric security systems |
US6905414B2 (en) * | 2002-05-16 | 2005-06-14 | Microsoft Corporation | Banning verbal communication to and from a selected party in a game playing system |
US7797744B2 (en) | 2002-06-17 | 2010-09-14 | At&T Intellectual Property Ii, L.P. | Method and device for detecting computer intrusion |
US7823203B2 (en) * | 2002-06-17 | 2010-10-26 | At&T Intellectual Property Ii, L.P. | Method and device for detecting computer network intrusions |
US7152243B2 (en) * | 2002-06-27 | 2006-12-19 | Microsoft Corporation | Providing a secure hardware identifier (HWID) for use in connection with digital rights management (DRM) system |
EP1527550A4 (en) * | 2002-07-25 | 2008-10-01 | Bio Key Int Inc | Trusted biometric device |
US20040039781A1 (en) * | 2002-08-16 | 2004-02-26 | Lavallee David Anthony | Peer-to-peer content sharing method and system |
US7343301B1 (en) | 2002-08-30 | 2008-03-11 | Signiant, Inc. | Method and apparatus for notification of data transfer |
US7152108B1 (en) * | 2002-08-30 | 2006-12-19 | Signiant Inc. | Data transfer system and method with secure mapping of local system access rights to global identities |
US20040064725A1 (en) * | 2002-09-18 | 2004-04-01 | Microsoft Corporation | Method and system for detecting a communication problem in a computer network |
US7818519B2 (en) | 2002-12-02 | 2010-10-19 | Silverbrook Research Pty Ltd | Timeslot arbitration scheme |
US20090319802A1 (en) * | 2002-12-02 | 2009-12-24 | Silverbrook Research Pty Ltd | Key Genaration In An Integrated Circuit |
US20040123105A1 (en) * | 2002-12-19 | 2004-06-24 | International Business Machines Corporation | Security object with CPU attributes |
US8881270B2 (en) | 2002-12-20 | 2014-11-04 | Creative Mines Llc | Method and apparatus for selectively enabling a microprocessor-based system |
US7962760B2 (en) * | 2002-12-20 | 2011-06-14 | The Invention Science Fund I | Method and apparatus for selectively enabling a microprocessor-based system |
US20110202565A1 (en) * | 2002-12-31 | 2011-08-18 | American Express Travel Related Services Company, Inc. | Method and system for implementing and managing an enterprise identity management for distributed security in a computer system |
US7143095B2 (en) * | 2002-12-31 | 2006-11-28 | American Express Travel Related Services Company, Inc. | Method and system for implementing and managing an enterprise identity management for distributed security |
US20040207508A1 (en) * | 2003-04-16 | 2004-10-21 | Jyh-Han Lin | Method and apparatus for a dynamically customizable smart phonebook |
US20050091311A1 (en) * | 2003-07-29 | 2005-04-28 | Lund Christopher D. | Method and apparatus for distributing multimedia to remote clients |
US20050071208A1 (en) * | 2003-09-29 | 2005-03-31 | Danamichele Brennen | Open architecture technology platform having front end administratively driven delivery management system |
US7770204B2 (en) * | 2003-09-30 | 2010-08-03 | Novell, Inc. | Techniques for securing electronic identities |
US7673046B2 (en) * | 2003-11-14 | 2010-03-02 | Microsoft Corporation | Trusted network transfer of content using off network input code |
US7831519B2 (en) * | 2003-12-17 | 2010-11-09 | First Data Corporation | Methods and systems for electromagnetic initiation of secure transactions |
US8234699B2 (en) * | 2003-12-31 | 2012-07-31 | Citrix Systems, Inc. | Method and system for establishing the identity of an originator of computer transactions |
US7272728B2 (en) * | 2004-06-14 | 2007-09-18 | Iovation, Inc. | Network security and fraud detection system and method |
US7526557B2 (en) | 2004-06-30 | 2009-04-28 | Signiant, Inc. | System and method for transferring data in high latency firewalled networks |
WO2006034564A1 (en) * | 2004-09-30 | 2006-04-06 | Avaya Canada Corp. | Information distribution system, method and network devices |
EP1643336A1 (en) * | 2004-09-30 | 2006-04-05 | Siemens Aktiengesellschaft | Clear product identification |
US20060067327A1 (en) * | 2004-09-30 | 2006-03-30 | Behrouz Poustchi | Information distribution system, method and network devices |
US20060153367A1 (en) * | 2005-01-07 | 2006-07-13 | Beeson Curtis L | Digital signature system based on shared knowledge |
US20060156013A1 (en) * | 2005-01-07 | 2006-07-13 | Beeson Curtis L | Digital signature software using ephemeral private key and system |
US7490239B2 (en) * | 2005-01-07 | 2009-02-10 | First Data Corporation | Facilitating digital signature based on ephemeral private key |
US20060153370A1 (en) * | 2005-01-07 | 2006-07-13 | Beeson Curtis L | Generating public-private key pair based on user input data |
US7936869B2 (en) * | 2005-01-07 | 2011-05-03 | First Data Corporation | Verifying digital signature based on shared knowledge |
US7693277B2 (en) * | 2005-01-07 | 2010-04-06 | First Data Corporation | Generating digital signatures using ephemeral cryptographic key |
US20060153364A1 (en) * | 2005-01-07 | 2006-07-13 | Beeson Curtis L | Asymmetric key cryptosystem based on shared knowledge |
US7869593B2 (en) * | 2005-01-07 | 2011-01-11 | First Data Corporation | Software for providing based on shared knowledge public keys having same private key |
US7593527B2 (en) * | 2005-01-07 | 2009-09-22 | First Data Corporation | Providing digital signature and public key based on shared knowledge |
US20060153369A1 (en) * | 2005-01-07 | 2006-07-13 | Beeson Curtis L | Providing cryptographic key based on user input data |
US8069206B2 (en) * | 2005-03-18 | 2011-11-29 | Clearone Communications, Inc. | System and method for real-time feedback with conservative network usage in a teleconferencing system |
US8457614B2 (en) | 2005-04-07 | 2013-06-04 | Clearone Communications, Inc. | Wireless multi-unit conference phone |
US20060248578A1 (en) * | 2005-04-28 | 2006-11-02 | International Business Machines Corporation | Method, system, and program product for connecting a client to a network |
US7781224B2 (en) * | 2005-08-10 | 2010-08-24 | Lawrence Livermore National Security, Llc | Safe biodegradable fluorescent particles |
US20070100956A1 (en) * | 2005-10-29 | 2007-05-03 | Gopesh Kumar | A system and method for enabling prospects to contact sponsoring advertisers on the telephone directly from an Internet-based advertisement with just a single-click, and efficiently tracking from what Internet location (URL) the telephone contacts are initiated. |
US20070143601A1 (en) * | 2005-12-15 | 2007-06-21 | Arroyo Diana J | System and method for authorizing information flows |
US7647630B2 (en) * | 2005-12-15 | 2010-01-12 | International Business Machines Corporation | Associating security information with information objects in a data processing system |
US8274979B2 (en) * | 2005-12-30 | 2012-09-25 | Telecom Italia S.P.A. | Method and system for secure communication between a public network and a local network |
US7865730B2 (en) * | 2006-01-30 | 2011-01-04 | Kronos Technology Systems Limited Partnership | Bcencryption (BCE)—a public-key based method to encrypt a data stream |
JP3996939B2 (en) * | 2006-03-30 | 2007-10-24 | 株式会社シー・エス・イー | Offline user authentication system, method thereof, and program thereof |
US7873835B2 (en) * | 2006-03-31 | 2011-01-18 | Emc Corporation | Accessing data storage devices |
US8959596B2 (en) * | 2006-06-15 | 2015-02-17 | Microsoft Technology Licensing, Llc | One-time password validation in a multi-entity environment |
US8826023B1 (en) * | 2006-06-30 | 2014-09-02 | Symantec Operating Corporation | System and method for securing access to hash-based storage systems |
US20080016571A1 (en) * | 2006-07-11 | 2008-01-17 | Larry Chung Yao Chang | Rootkit detection system and method |
CA2658057C (en) * | 2006-07-13 | 2013-04-23 | Mobivox Corporation | Methods and systems for selecting a buddy from a buddy list and for placing call to a buddy |
US8751815B2 (en) * | 2006-10-25 | 2014-06-10 | Iovation Inc. | Creating and verifying globally unique device-specific identifiers |
US8818904B2 (en) | 2007-01-17 | 2014-08-26 | The Western Union Company | Generation systems and methods for transaction identifiers having biometric keys associated therewith |
US7933835B2 (en) * | 2007-01-17 | 2011-04-26 | The Western Union Company | Secure money transfer systems and methods using biometric keys associated therewith |
CA2672294A1 (en) | 2007-01-18 | 2008-07-24 | Coupons, Inc. | System and method for controlling distribution of electronic coupons |
DE102007010789A1 (en) | 2007-03-02 | 2008-09-04 | Deutsche Thomson Ohg | Method for operating network, particularly home network, involves generating functional command, which is configured to carry out assigned function into network station |
US8504473B2 (en) * | 2007-03-28 | 2013-08-06 | The Western Union Company | Money transfer system and messaging system |
US8726041B2 (en) * | 2007-05-09 | 2014-05-13 | Sony Corporation | Methods and apparatus for generating a random number in one or more isolated processors |
US20080282341A1 (en) * | 2007-05-09 | 2008-11-13 | Sony Computer Entertainment Inc. | Methods and apparatus for random number generation in a multiprocessor system |
US7890570B2 (en) * | 2007-09-12 | 2011-02-15 | Citrix Systems, Inc. | Methods and systems for providing, by a remote machine, access to graphical data associated with a resource provided by a local machine |
US8516539B2 (en) * | 2007-11-09 | 2013-08-20 | Citrix Systems, Inc | System and method for inferring access policies from access event records |
US8990910B2 (en) * | 2007-11-13 | 2015-03-24 | Citrix Systems, Inc. | System and method using globally unique identities |
JP4970221B2 (en) * | 2007-11-16 | 2012-07-04 | 株式会社東芝 | Power saving control apparatus and method |
US7817636B2 (en) * | 2008-01-30 | 2010-10-19 | Cisco Technology, Inc. | Obtaining information on forwarding decisions for a packet flow |
JP5072629B2 (en) * | 2008-02-04 | 2012-11-14 | 株式会社東芝 | Control device, controlled device, control method |
US9240945B2 (en) * | 2008-03-19 | 2016-01-19 | Citrix Systems, Inc. | Access, priority and bandwidth management based on application identity |
US8943575B2 (en) | 2008-04-30 | 2015-01-27 | Citrix Systems, Inc. | Method and system for policy simulation |
US20100066488A1 (en) * | 2008-09-18 | 2010-03-18 | Alan Roy Hollander | System and method for validated guest reviews |
US8990573B2 (en) | 2008-11-10 | 2015-03-24 | Citrix Systems, Inc. | System and method for using variable security tag location in network communications |
US8165078B2 (en) * | 2008-11-19 | 2012-04-24 | Coupons.Com Incorporated | System and method for controlling use of a network resource |
US9047450B2 (en) * | 2009-06-19 | 2015-06-02 | Deviceauthority, Inc. | Identification of embedded system devices |
US9047458B2 (en) * | 2009-06-19 | 2015-06-02 | Deviceauthority, Inc. | Network access protection |
US9654505B2 (en) | 2009-06-22 | 2017-05-16 | Citrix Systems, Inc. | Systems and methods for encoding the core identifier in the session identifier |
US8601556B2 (en) | 2009-06-22 | 2013-12-03 | Citrix Systems, Inc. | Systems and methods for handling SSL session not reusable across multiple cores |
US20100333213A1 (en) * | 2009-06-24 | 2010-12-30 | Craig Stephen Etchegoyen | Systems and Methods for Determining Authorization to Operate Licensed Software Based on a Client Device Fingerprint |
US8213907B2 (en) * | 2009-07-08 | 2012-07-03 | Uniloc Luxembourg S. A. | System and method for secured mobile communication |
US8726407B2 (en) * | 2009-10-16 | 2014-05-13 | Deviceauthority, Inc. | Authentication of computing and communications hardware |
TW201121280A (en) * | 2009-12-10 | 2011-06-16 | Mao-Cong Lin | Network security verification method and device and handheld electronic device verification method. |
CN102104527B (en) * | 2009-12-22 | 2013-04-17 | 华为终端有限公司 | Access control method and equipment |
US9667626B2 (en) | 2010-01-27 | 2017-05-30 | Keypasco Ab | Network authentication method and device for implementing the same |
CN102142974B (en) * | 2010-01-28 | 2015-05-13 | 中兴通讯股份有限公司 | Method and system for authorizing management of terminals of internet of things |
US8676684B2 (en) | 2010-04-12 | 2014-03-18 | Iovation Inc. | System and method for evaluating risk in fraud prevention |
AU2011100168B4 (en) | 2011-02-09 | 2011-06-30 | Device Authority Ltd | Device-bound certificate authentication |
AU2011101295B4 (en) | 2011-06-13 | 2012-08-02 | Device Authority Ltd | Hardware identity in multi-factor authentication layer |
US8516563B2 (en) * | 2011-06-29 | 2013-08-20 | Infosys Technologies, Ltd. | Methods for authenticating a user without personal information and devices thereof |
AU2011101297B4 (en) | 2011-08-15 | 2012-06-14 | Uniloc Usa, Inc. | Remote recognition of an association between remote devices |
US8930475B1 (en) | 2012-03-30 | 2015-01-06 | Signiant Inc. | Systems and methods for secure cloud-based media file sharing |
US9692799B2 (en) | 2012-07-30 | 2017-06-27 | Signiant Inc. | System and method for sending and/or receiving digital content based on a delivery specification |
US20140067603A1 (en) * | 2012-08-31 | 2014-03-06 | Anthony Okoro | Online marketplace for wholesale deals |
US20140181985A1 (en) * | 2012-12-21 | 2014-06-26 | Broadcom Corporation | Content Specific Data Scrambling |
US9143496B2 (en) | 2013-03-13 | 2015-09-22 | Uniloc Luxembourg S.A. | Device authentication using device environment information |
US9286466B2 (en) | 2013-03-15 | 2016-03-15 | Uniloc Luxembourg S.A. | Registration and authentication of computing devices using a digital skeleton key |
US9735968B2 (en) * | 2014-10-20 | 2017-08-15 | Microsoft Technology Licensing, Llc | Trust service for a client device |
US9558493B2 (en) | 2014-11-12 | 2017-01-31 | BenedorTSE LLC | Secure authorizations using independent communications and different one-time-use encryption keys for each party to a transaction |
US9569776B2 (en) | 2014-11-12 | 2017-02-14 | BenedorTSE LLC | Secure authorizations using independent communications and different one-time-use encryption keys for each party to a transaction |
US10614457B2 (en) | 2014-11-12 | 2020-04-07 | BenedorTSE LLC | Secure authorizations using independent communications and different one-time-use encryption keys for each party to a transaction |
US9558492B2 (en) | 2014-11-12 | 2017-01-31 | Benedoretse Llc | Secure authorizations using independent communications and different one-time-use encryption keys for each party to a transaction |
JP6489835B2 (en) * | 2015-01-09 | 2019-03-27 | キヤノン株式会社 | Information processing system, information processing apparatus control method, and program |
US10460349B2 (en) | 2015-02-11 | 2019-10-29 | Oath Inc. | Systems and methods for opting-out of targeted advertising in an online advertising environment |
US10505736B1 (en) * | 2018-07-26 | 2019-12-10 | Meixler Technologies, Inc. | Remote cyber security validation system |
US10735516B1 (en) | 2019-02-15 | 2020-08-04 | Signiant Inc. | Cloud-based authority to enhance point-to-point data transfer with machine learning |
Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5790663A (en) * | 1996-03-28 | 1998-08-04 | Advanced Micro Devices, Inc. | Method and apparatus for software access to a microprocessor serial number |
US5944821A (en) * | 1996-07-11 | 1999-08-31 | Compaq Computer Corporation | Secure software registration and integrity assessment in a computer system |
US5987376A (en) * | 1997-07-16 | 1999-11-16 | Microsoft Corporation | System and method for the distribution and synchronization of data and state information between clients in a distributed processing system |
US6072463A (en) * | 1993-12-13 | 2000-06-06 | International Business Machines Corporation | Workstation conference pointer-user association mechanism |
US6085321A (en) * | 1998-08-14 | 2000-07-04 | Omnipoint Corporation | Unique digital signature |
US6366950B1 (en) * | 1999-04-02 | 2002-04-02 | Smithmicro Software | System and method for verifying users' identity in a network using e-mail communication |
US20020077885A1 (en) * | 2000-12-06 | 2002-06-20 | Jared Karro | Electronic voting system |
US6463537B1 (en) * | 1999-01-04 | 2002-10-08 | Codex Technologies, Inc. | Modified computer motherboard security and identification system |
US6487664B1 (en) * | 1998-11-24 | 2002-11-26 | E-Com Defense, Inc. | Processes and systems for secured information exchange using computer hardware |
US20040128350A1 (en) * | 2002-03-25 | 2004-07-01 | Lou Topfl | Methods and systems for real-time virtual conferencing |
US6839417B2 (en) * | 2002-09-10 | 2005-01-04 | Myriad Entertainment, Inc. | Method and apparatus for improved conference call management |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4545012A (en) * | 1981-05-22 | 1985-10-01 | Data General Corporation | Access control system for use in a digital computer system with object-based addressing and call and return operations |
US4866769A (en) * | 1987-08-05 | 1989-09-12 | Ibm Corporation | Hardware assist for protecting PC software |
US5224166A (en) * | 1992-08-11 | 1993-06-29 | International Business Machines Corporation | System for seamless processing of encrypted and non-encrypted data and instructions |
JP2519390B2 (en) * | 1992-09-11 | 1996-07-31 | インターナショナル・ビジネス・マシーンズ・コーポレイション | DATA COMMUNICATION METHOD AND DEVICE |
US5542087A (en) * | 1993-10-15 | 1996-07-30 | Hewlett-Packard Company | Linear hashing for distributed records |
US5793861A (en) * | 1996-06-11 | 1998-08-11 | Executone Information Systems, Inc. | Transaction processing system and method |
US6408336B1 (en) * | 1997-03-10 | 2002-06-18 | David S. Schneider | Distributed administration of access to information |
US6105027A (en) * | 1997-03-10 | 2000-08-15 | Internet Dynamics, Inc. | Techniques for eliminating redundant access checking by access filters |
US5913227A (en) * | 1997-03-24 | 1999-06-15 | Emc Corporation | Agent-implemented locking mechanism |
US6317838B1 (en) * | 1998-04-29 | 2001-11-13 | Bull S.A. | Method and architecture to provide a secured remote access to private resources |
US6189103B1 (en) * | 1998-07-21 | 2001-02-13 | Novell, Inc. | Authority delegation with secure operating system queues |
US6418472B1 (en) * | 1999-01-19 | 2002-07-09 | Intel Corporation | System and method for using internet based caller ID for controlling access to an object stored in a computer |
US6081900A (en) * | 1999-03-16 | 2000-06-27 | Novell, Inc. | Secure intranet access |
-
1999
- 1999-01-19 US US09/234,051 patent/US6418472B1/en not_active Expired - Lifetime
-
2002
- 2002-04-12 US US10/121,174 patent/US6523067B2/en not_active Expired - Fee Related
- 2002-11-15 US US10/295,515 patent/US20030131115A1/en not_active Abandoned
Patent Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6072463A (en) * | 1993-12-13 | 2000-06-06 | International Business Machines Corporation | Workstation conference pointer-user association mechanism |
US5790663A (en) * | 1996-03-28 | 1998-08-04 | Advanced Micro Devices, Inc. | Method and apparatus for software access to a microprocessor serial number |
US5944821A (en) * | 1996-07-11 | 1999-08-31 | Compaq Computer Corporation | Secure software registration and integrity assessment in a computer system |
US5987376A (en) * | 1997-07-16 | 1999-11-16 | Microsoft Corporation | System and method for the distribution and synchronization of data and state information between clients in a distributed processing system |
US6085321A (en) * | 1998-08-14 | 2000-07-04 | Omnipoint Corporation | Unique digital signature |
US6487664B1 (en) * | 1998-11-24 | 2002-11-26 | E-Com Defense, Inc. | Processes and systems for secured information exchange using computer hardware |
US6463537B1 (en) * | 1999-01-04 | 2002-10-08 | Codex Technologies, Inc. | Modified computer motherboard security and identification system |
US6366950B1 (en) * | 1999-04-02 | 2002-04-02 | Smithmicro Software | System and method for verifying users' identity in a network using e-mail communication |
US20020077885A1 (en) * | 2000-12-06 | 2002-06-20 | Jared Karro | Electronic voting system |
US20040128350A1 (en) * | 2002-03-25 | 2004-07-01 | Lou Topfl | Methods and systems for real-time virtual conferencing |
US6839417B2 (en) * | 2002-09-10 | 2005-01-04 | Myriad Entertainment, Inc. | Method and apparatus for improved conference call management |
Cited By (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030142806A1 (en) * | 2001-02-02 | 2003-07-31 | Stefan Unger | Method for verifying telephone call back information for return calls which are initiated via the internet |
US7715543B2 (en) * | 2001-02-02 | 2010-05-11 | Siemens Aktiengesellschaft | Method for verifying telephone call back information for return calls which are initiated via the internet |
US20040117616A1 (en) * | 2002-12-16 | 2004-06-17 | Silvester Kelan C. | Method and mechanism for validating legitimate software calls into secure software |
US7263720B2 (en) * | 2002-12-16 | 2007-08-28 | Intel Corporation | Method and mechanism for validating legitimate software calls into secure software |
US20060277607A1 (en) * | 2003-05-01 | 2006-12-07 | Chung Hyun-Kwon | Authenticating method and apparatus |
US20080282357A1 (en) * | 2004-06-04 | 2008-11-13 | Jason Sharpe | Method and Device for Determining Whether an Application Should Access Protected Digital Content |
WO2005119396A1 (en) * | 2004-06-04 | 2005-12-15 | Nokia Corporation | A method and device for determining whether an application should access protected digital content |
US9819681B1 (en) * | 2005-08-01 | 2017-11-14 | Danilo E. Fonseca | Datacentroid |
US10225257B2 (en) * | 2005-08-01 | 2019-03-05 | Danilo E. Fonseca | Datacentroid |
US8195625B1 (en) * | 2005-08-01 | 2012-06-05 | Fonseca Danilo E | Datacentroid |
US10474807B2 (en) | 2005-08-01 | 2019-11-12 | Danilo E. Fonseca | Password/encryption protection |
EP2082518A2 (en) * | 2006-11-02 | 2009-07-29 | Legitimi Limited | Access control system based on a hardware and software signature of a requesting device |
EP2082518A4 (en) * | 2006-11-02 | 2011-07-20 | Legitimi Ltd | Access control system based on a hardware and software signature of a requesting device |
US20080162484A1 (en) * | 2006-12-27 | 2008-07-03 | Ryo Yoshida | Technique for controlling access to data |
US8949202B2 (en) * | 2006-12-27 | 2015-02-03 | International Business Machines Corporation | Technique for controlling access to data |
US8510815B2 (en) * | 2009-06-05 | 2013-08-13 | Hitachi, Ltd. | Virtual computer system, access control method and communication device for the same |
US20100313256A1 (en) * | 2009-06-05 | 2010-12-09 | Tomoki Sekiguchi | Virtual computer system, access control method and communication device for the same |
US9444620B1 (en) * | 2010-06-24 | 2016-09-13 | F5 Networks, Inc. | Methods for binding a session identifier to machine-specific identifiers and systems thereof |
US8804731B2 (en) * | 2010-10-27 | 2014-08-12 | Intel Corporation | Generating platform identification for certification version signaling |
US8799165B2 (en) * | 2012-01-11 | 2014-08-05 | Rawllin International Inc. | Electronic signature security algorithms |
US20140304172A1 (en) * | 2012-01-11 | 2014-10-09 | Rawllin International Inc. | Electronic signature security algorithms |
US20130179350A1 (en) * | 2012-01-11 | 2013-07-11 | Rawllin International Inc. | Electronic signature security algorithms |
US9047456B2 (en) * | 2012-03-20 | 2015-06-02 | Canon Information And Imaging Solutions, Inc. | System and method for controlling access to a resource |
US20140025949A1 (en) * | 2012-07-20 | 2014-01-23 | Google Inc. | Method and system for browser identity |
US9887965B2 (en) * | 2012-07-20 | 2018-02-06 | Google Llc | Method and system for browser identity |
US9641675B2 (en) | 2015-08-03 | 2017-05-02 | International Business Machines Corporation | Digital signature-over-voice for caller ID verification |
US9635155B2 (en) | 2015-08-03 | 2017-04-25 | International Business Machines Corporation | Digital signature-over-voice for caller ID verification |
US9571634B1 (en) | 2015-08-03 | 2017-02-14 | International Business Machines Corporation | Digital signature-over-voice for caller ID verification |
US11063758B1 (en) | 2016-11-01 | 2021-07-13 | F5 Networks, Inc. | Methods for facilitating cipher selection and devices thereof |
Also Published As
Publication number | Publication date |
---|---|
US20020116616A1 (en) | 2002-08-22 |
US6523067B2 (en) | 2003-02-18 |
US6418472B1 (en) | 2002-07-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6418472B1 (en) | System and method for using internet based caller ID for controlling access to an object stored in a computer | |
JP5695120B2 (en) | Single sign-on between systems | |
US7290699B2 (en) | Protected content distribution system | |
US7310729B2 (en) | Digital rights management license delivery system and method | |
JP4274421B2 (en) | Pseudo-anonymous user and group authentication method and system on a network | |
US7496751B2 (en) | Privacy and identification in a data communications network | |
US8151112B2 (en) | Deliver-upon-request secure electronic message system | |
JP5274096B2 (en) | Non-repudiation for digital content distribution | |
US20020002678A1 (en) | Internet authentication technology | |
US20040199768A1 (en) | System and method for enabling enterprise application security | |
JP2002132730A (en) | System and method for authentication or access management based on reliability and disclosure degree of personal information | |
EP1102157A1 (en) | Method and arrangement for secure login in a telecommunications system | |
KR20050083594A (en) | Biometric private key infrastructure | |
WO2003038578A2 (en) | User access control to distributed resources on a data communications network | |
JP2003534589A (en) | Authentication system and method | |
JP2001197055A (en) | Device, method, and service system for proxy authentication and computer-readable recording medium | |
US20030135734A1 (en) | Secure mutual authentication system | |
US20170104748A1 (en) | System and method for managing network access with a certificate having soft expiration | |
US6611916B1 (en) | Method of authenticating membership for providing access to a secure environment by authenticating membership to an associated secure environment | |
KR20100029102A (en) | Identity assertion | |
JP2002007345A (en) | User authenticating method | |
KR20060056319A (en) | Method for securing an electronic certificate | |
US20070204167A1 (en) | Method for serving a plurality of applications by a security token | |
US7660770B2 (en) | System and method for providing a secure contact management system | |
JP2003338816A (en) | Service providing system for verifying personal information |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |