US20130145442A1 - System and method for privilege delegation and control - Google Patents
System and method for privilege delegation and control Download PDFInfo
- Publication number
- US20130145442A1 US20130145442A1 US13/626,015 US201213626015A US2013145442A1 US 20130145442 A1 US20130145442 A1 US 20130145442A1 US 201213626015 A US201213626015 A US 201213626015A US 2013145442 A1 US2013145442 A1 US 2013145442A1
- Authority
- US
- United States
- Prior art keywords
- data processing
- processing unit
- privilege
- security token
- key
- 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
-
- 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/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
- G06F21/34—User authentication involving the use of external additional devices, e.g. dongles or smart cards
-
- 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/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/44—Program or device authentication
- G06F21/445—Program or device authentication by mutual authentication, e.g. between devices or programs
-
- 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
-
- 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/0853—Network architectures or network communication protocols for network security for authentication of entities using an additional device, e.g. smartcard, SIM or a different communication terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3234—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3271—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using challenge-response
- H04L9/3273—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using challenge-response for mutual authentication
Definitions
- the present invention relates generally to a data processing system and method and more specifically to a system and method for delegating privileges from one or more security tokens to one or more data processing units.
- Privilege delegation affords the ability to allow another to act as a surrogate for the delegator.
- a number of different strategies are relevant to accomplish the delegation process.
- U.S. Pat. No. 5,339,403 issued to Parker describes a privilege attribute certificate issued by an authentication server to allow a client access to distributed resources.
- U.S. Pat. No. 5,918,228 issued to Rich, et al. describes a privilege attribute certificate used to “impersonate” a client to other web-based servers.
- the privilege attribute certificate is generated and issued by a first web server and presented to other servers by the first server as a means to “impersonate” a client for access purposes.
- a popular form of privilege delegation designed for networks employing TCP/IP protocols is called Kerberos.
- Kerberos authenticates the identity of users attempting to log on to a network and includes secure messaging based on symmetric cryptography methods. Kerberos works by granting users “tickets,” as a form of credential which are then used to identify themselves to other network service providers. Each ticket includes information that allows another network service provider to determine that the user has been properly authenticated, analogous to a privilege attribute certificate. The proper ticket is automatically presented to the network service provider as a means to avoid multiple authentication procedures each time a different network service is attempted to be accessed.
- the privilege attribute certificates or tickets are generated and controlled by the issuing servers rather than the person using the system.
- the person using the system must therefore trust the delegation strategies employed on the system.
- the server-based systems may not provide sufficient flexibility in the delegation process where the necessary delegation criteria are role-based or rule-based rather than identity based.
- the privilege attribute certificates employed in the relevant art are somewhat vulnerable to attack by a person or entity having access to the certificate generating servers.
- the present invention is directed to a privilege delegation system and method that incorporates flexibility and control over the issuance and use of the delegable privileges.
- the invention includes a security token having the ability to transfer delegable privileges and associated attributes to another security token or computer system either of which are described generically herein as data processing units.
- Various embodiments are provided including a split privilege which allows access to a controlled resource when combined with all of the components to form a complete privilege.
- the receiving data processing unit includes the ability to operatively store and use the delegated privilege and perform data exchanges with the security token and optionally with at least a second data processing unit. Mutual authentications are performed between the delegating security token and receiving data processing unit before the delegated privilege is transferred.
- the information that may be communicated in the data exchange includes authentication data, one or more delegated privileges and the associated attributes.
- a secure messaging protocol is used during the data exchanges.
- the delegable privileges include a privilege attribute certificate, a key component, a cryptographic key, digital ticket, digital credential, password, biometric template, digital rights, license or loyalty credit.
- Typical uses for the delegated privileges include authentication, terminal activation, personalization of an intelligent device, accessing resources included in or accessible through the second data processing unit or another data processing unit, allowing the second data processing unit or another data processing unit to act as a surrogate for the delegating security token and loyalty credit management.
- the attributes included in the privilege attribute certificate or in the separate file define the scope of usage and security aspects required to use the delegated privilege. When the attributes are included in the separate file, a verifiable cross reference to the associated privilege is included.
- the attributes associated with the delegated privilege provide sufficient information to the receiving data processing unit to configure the privilege and enforce control aspects stated in the attributes including security policies and delegated privilege state.
- the security policies includes details related to validity period, remaining number of uses, time limits and cryptographic measures to be employed.
- the delegated privilege state includes storage requirements (transient or permanent), and state of the host (idle, booting, secure mode, insecure mode, suspended.)
- the control aspects determine when the privilege is to be activated and destroyed.
- Other information included in the attributes includes operational information such as username, user ID, domain name, client name or host name.
- Privilege delegation and control may be applied in maintaining the privacy of a person's medical records.
- a patient's medical records should only be accessible to those authorized or “privileged” to access the records.
- a terminal is activated by securely transferring a privilege following mutual authentications from a physician's security token to a security token associated with the terminal.
- the entire privilege may be transferred from the physician's security token or formed by combining the information transferred with pre-existing information contained in the terminal security token.
- the physician's delegated privilege allows activation of the terminal to read a patient's medical records stored in or otherwise accessible using information stored in the patient's security token.
- the attributes associated with the delegated privilege may limit activation of the terminal to the physician's normal office hours and/or specify that the delegated privilege remain in transient memory only.
- the attributes may also provide the ability to delegate privileges to another physician while the first physician is on vacation.
- To access a patient's medical records the patient presents his or her security token to the terminal.
- An authentication session follows which verifies to the patient's security token that the necessary privileges are present in the terminal security token to allow the terminal to access the patient's medical records.
- An office manager in the same office may have a delegable privilege necessary to activate the same terminal for reviewing account balances associated with the patient but would not have the necessary delegable privilege to review the patient's medical records.
- a first alternative to using the split master key approach utilizes a complete master symmetric key which is installed in all role-based authorizing security tokens equivalent to the physician level example described above.
- the entire master key is transferred to the security token associated with the terminal, rather than a key component. All other aspects of the second embodiment of the invention are the same.
- the symmetric keys in either approach may be based on algorithms supporting the data encryption standard (DES), triple data encryption standard (3DES), advanced encryption standard (AES), etc.
- a second alternative to using the split key approach involves the use of public key infrastructure (PKI) keys.
- PKI public key infrastructure
- a group private key representing a particular privilege is generated by the issuing authority and installed in all role-based authorizing security tokens equivalent to the physician level example described above.
- the public key counterpart to the group private key is likewise installed in all patient level security tokens equivalent to the patient security token described above.
- the PKI keys may based on algorithms utilizing elliptical curves, RSA, Diffie-Hellman, Pretty Good Privacy (PGP), El Gamal, etc.
- PGP Pretty Good Privacy
- Authentication of the terminal by the patient data processing unit is sufficient for using the transferred privileges.
- FIG. 1 is a generalized system block diagram for implementing the main embodiment of the invention.
- FIG. 1 A is a detailed block diagram depicting a mutual authentication cycle between a security token and a first data processing unit.
- FIG. 1 B is a detailed block diagram depicting privilege delegation including associated attributes from a security token to a first data processing unit.
- FIG. 1 C is a detailed block diagram depicting privilege verification by a second data processing unit.
- FIG. 1 D is a detailed block diagram depicting privilege usage by the first data processing unit whereby an example resource contained in a second data processing unit is accessed using the delegated privilege.
- FIG. 1 E is a detailed block diagram depicting an existing privilege contained in a first data processing unit having an expired attribute.
- FIG. 1 F is a detailed block diagram depicting replacement of the expired attribute associated with the existing privilege.
- FIG. 1 G is a detailed block diagram depicting a variation of the first inventive embodiment.
- FIG. 1 H is a detailed block diagram depicting a transfer of a partial privilege from the security token to the first data processing unit.
- FIG. 1 I is a detailed block diagram depicting the transfer of the partial privilege from the first data processing unit to the second data processing unit.
- FIG. 1 J is a detailed block diagram depicting the combined partial privileges inside the second data processing unit and access to a controlled resource.
- FIG. 1 K is a detailed block diagram depicting a variation of the first inventive embodiment where the second partial privilege is transferred from the second data processing unit to the first data processing unit.
- FIG. 1 L is a detailed block diagram depicting the combined partial privileges inside the first data processing unit and access to a controlled resource.
- FIG. 2 is a generalized block diagram depicting an alternate embodiment of the invention using symmetric key components as a form of delegable privilege.
- FIG. 2 A is a detailed block diagram depicting a mutual authentication cycle between a first and a second data processing unit.
- FIG. 2 B is a detailed block diagram depicting privilege delegation from the first data processing unit to the second data processing unit using a secure messaging protocol and symmetric master key regeneration.
- FIG. 2 C is a detailed block diagram depicting a unique identifier sent from a third data processing unit to the data processing unit as part of an authentication challenge.
- FIG. 2 D is a detailed block diagram depicting master key diversification using the unique identifier to generate a data processing unit specific key necessary to access resources controlled by the third data processing unit.
- FIG. 2 E is a detailed block diagram depicting response to the authentication challenge which incorporates the use of the data processing unit specific key.
- FIG. 2 F is a detailed block diagram depicting access to the resources controlled by the third data processing unit following authentication of the second data processing unit by the third data processing unit.
- FIG. 3 is a generalized block diagram depicting an alternate embodiment of the invention using a complete symmetric key as a form of delegable privilege.
- FIG. 3 A is a detailed block diagram depicting a mutual authentication cycle between a first data processing unit and a second data processing unit.
- FIG. 3 B is a detailed block diagram depicting privilege delegation from the first data processing unit to the second data processing unit using a secure messaging protocol.
- FIG. 4 is a generalized block diagram depicting an alternate embodiment of the invention using a group asymmetric private key as a form of delegable privilege.
- FIG. 4 A is a detailed block diagram depicting a mutual authentication cycle between a first data processing unit and a second data processing unit.
- FIG. 4 B is a detailed block diagram depicting privilege delegation and its associated attributes from the first data processing unit to the second data processing unit using a secure messaging protocol.
- FIG. 4 C is a detailed block diagram depicting an authentication challenge sent from a third data processing unit to the second data processing unit using a public key counterpart to the group private key.
- FIG. 4 D is a detailed block diagram depicting response to the authentication challenge which incorporates the use of the group private key.
- FIG. 4 E is a detailed block diagram depicting access to the resources controlled by the third data processing unit following authentication of the second data processing unit by the third data processing unit.
- FIG. 5 is a simplified flow chart that illustrates the steps involved in implementing the main embodiment of the invention.
- FIG. 6 is a table providing a summary of the types of delegable privileges and information included in the associated attributes.
- This invention provides novel implementations in delegating privileges and associated attributes from a security token to one or more data processing units.
- the security token and data processing units are assumed to include standardized cryptography modules, algorithms and services.
- data processing unit refers to a security token, an intelligent device or a computer system as appropriate.
- security token refers to hardware based security devices such as smart cards, integrated circuit cards, subscriber identification modules (SIM), wireless identification modules (WIM), identification tokens, secure application modules (SAM), hardware security modules (HSM), secure multi-media card (SMMC) and like devices.
- SIM subscriber identification modules
- WIM wireless identification modules
- SAM secure application modules
- HSMMC secure multi-media card
- data processing unit and security token are used interchangeably in the specification and no limitation is usage is implied.
- a security token 10 is shown operatively connected 12 to a client computer 15 .
- the client computer 15 is in processing communications 65 with a first data processing unit DPU 1 40 .
- the client computer 15 provides the necessary hardware and software interfaces to allow the security token 10 to communicate with the first data processing unit DPU 1 40 but otherwise does not affect the various embodiments of the invention described herein.
- the security token 10 includes at least one delegable privilege P 20 and its associated attributes A 30 .
- the delegable privilege P 20 may be used for authentication, terminal activation, personalization of an intelligent device, accessing resources 60 included in or accessible through a second data processing unit DPU 2 50 or another data processing unit, allowing the second data processing unit DPU 2 50 or another data processing unit to act as a surrogate for the delegating security token 10 or maintenance of loyalty credits.
- the attributes A 30 associated with the delegated privilege P 20 provide sufficient information to a receiving data processing unit to configure the privilege P 20 and enforce control aspects stated in the attributes A 30 including security policies and delegated privilege state.
- the security policies include details related to validity period, remaining number of uses, time limits and cryptographic measures to be employed.
- the delegated privilege state includes storage requirements (transient or permanent), and state of the host (idle, booting, secure mode, insecure mode, suspended.)
- the control aspects determine when the privilege is to be activated and destroyed.
- Other information included in the attributes A 30 includes operational information such as username, user ID, domain name, client name or host name.
- the Table of FIG. 6 provides a summary of the types of delegable privileges and information included in the associated attributes.
- the attributes A 30 are associated with the privilege P 20 by a unique signature, hash or message authentication code or hashed message authentication which unambiguously links the attributes 30 with the privilege 20 .
- the attributes A 30 are normally stored separately from the privilege 20 except when incorporated into certificate form (e.g. digital tickets, digital rights, license or privilege attribute certificates)
- the first data processing unit DPU 1 40 is in processing communications 65 with the second data processing unit DPU 2 50 .
- the second data processing unit DPU 2 50 includes the resource 60 which is only accessible using the valid privilege P 20 .
- the resource 60 is defined generically to include data or functions contained in the second data processing unit DPU 2 50 or otherwise accessible from another data processing unit using the resource 60 .
- the communications links 65 and 85 may be either local connections, remote network connections or any combination thereof.
- a prerequisite mutual authentication cycle 70 is initiated before privilege transfer.
- Mutual authentication 70 is preferred to ensure that both the sending data processing unit and receiving data processing are authorized to perform privilege transfer transactions.
- FIG. 1B once the mutual authentication cycle is successfully completed, a secure channel is established between the security token 10 and first data processing unit DPU 1 40 .
- the secure channel 75 may be implemented using secure messaging protocols such as secure socket layer encryption (SSL), transport layer security (TLS) or IPsec.
- SSL secure socket layer encryption
- TLS transport layer security
- IPsec IPsec
- the first data processing unit DPU 1 40 authenticates itself to the second data processing unit DPU 2 50 and a secure channel is established 80 .
- the privilege P′′ 20 ′′ is securely sent 85 to the second data processing unit DPU 2 50 where it is validated 90 .
- Access and use 95 of the resource 60 is shown in FIG. 1D .
- a privilege P′ 20 ′ and its associated attributes A′x 30 ′ are shown.
- the attributes A′x 30 ′ includes a parameter which has expired (for example validity period.)
- an update is required.
- the updated attributes A′′ 30 ′′ is securely sent from the security token 10 to the first data processing unit DPU 1 40 where the expired attributes A′x 30 ′ is replaced with the update attributes A′′x 30 ′′ as is shown in FIG. 1F .
- a partial privilege p/ 1 n 22 and its associated attributes A 30 are shown initially stored inside the security token 10 .
- a remaining portion of the privilege p 2 /n 22 ′ and its associated attributes A′ 30 ′ are shown stored inside a second security token 50 .
- This embodiment of the invention requires that the partial privileges p 1 /n 22 and p 2 /n 22 ′ be combined in order to gain access to a resource 60 .
- the attributes A 30 and A′ 30 ′ may be delegated by either the security token 10 or second data processing unit 50 , or combined together to form a complete set of attributes. It is also envisioned by the inventor that more than two partial privileges can be combined to form an operable privilege.
- the partial privilege p 1 /n 22 and its associated attributes A 30 are shown being delegated 12 from the security token 10 via a client 15 to 65 a first data processing unit DPU 1 40 .
- the delegation includes a secure channel 75 to prevent unauthorized monitoring of the transaction.
- the partial privilege p 1 /n 22 and its associated attributes A 30 are shown being delegated 85 again from the first data processing unit DPU 1 40 to the second data processing unit DPU 2 50 using a secure channel 95 .
- the combined partial privileges p 1 /n 22 and p 2 /n 22 ′ form a complete privilege P 24 including a complete set of associated attributes A 32 , which allows access to the controlled resource 60 by the second data processing unit DPU 2 50 .
- FIG. 1K an equivalent embodiment is shown where the partial privilege p 2 /n 22 ′ and its associated attributes A′ 30 ′ are shown being delegated 85 from the second data processing unit DPU 2 50 to the first data processing unit DPU 1 40 using a secure channel 95 .
- the combined partial privileges p 1 /n 22 and p 2 /n 22 ′ form a complete privilege P 24 including a complete set of associated attributes A 32 , which allows access to the controlled resource 60 ′ by the first data processing unit DPU 1 40 .
- the controlled resource 60 ′ is shown being transferred from the second data processing unit DPU 2 50 for consistency with the previous drawings only. The controlled resource 60 could remain on the second data processing unit DPU 2 50 and be accessible using the communications link 85 .
- FIG. 2 the major components and interrelationships are depicted for implementing another embodiment of the invention.
- privilege delegation is performed using symmetric cryptographic keys.
- a computer system 202 is shown operatively connected to a first security token 204 and second security token 206 .
- a middleware program (not shown) installed in the computer system 202 supports the use of two or more data processing units. An example of which is described in “Government Smart Card Interoperability Specification Contract Modification,” contract number GS00T00ALD0208 PS02, Aug. 29, 2000 and is herein incorporated by reference.
- the symmetric cryptography methods employed in this embodiment of the invention may be based on algorithms supporting the data encryption standard (DES), triple data encryption standard (3DES) or advanced encryption standard (AES.)
- DES data encryption standard
- 3DES triple data encryption standard
- AES advanced encryption standard
- an issuing authority initially generates a master key associated with a particular privilege.
- Separate master keys may be used to define a specific privilege within a select group of data processing units.
- the master key is then sequentially diversified with unique identifiers associated with a pre-defined group of security tokens, forming unique privilege keys.
- the privilege keys will be used to verify that another security token, generally associated with a terminal, has the required privilege before allowing access to a controlled resource 220 .
- the resulting privilege key(s) are then injected into the security token(s) by the issuing authority.
- the master key(s) are then diversified using a key splitting mechanism and installed in the designated data processing units, shown in FIGA as TOKEN 1 204 and TOKEN 2 206 .
- the first security token TOKEN 1 204 includes the key component MK 1 205 .
- the second security token TOKEN 2 206 includes the counterpart to the key component MK 2 210 and the means to combine the two key components to form the complete master key.
- the reconstructed master key is intended to be maintained in transient memory of the second security token 206 to prevent unauthorized disclosure as prescribed by attributes A 203 associated with the key component privilege MK 1 205 . Any tampering with the security token containing the master key results in the destruction of the master key.
- Controlled resources 220 associated with the computer system 202 are shown as a database for example only and is accessible only after privilege verification using a third data processing unit.
- the mutual authentication 280 cycle is performed as described above before privilege transfer.
- Mutual authentication 280 is preferred to ensure that both the sending data processing unit and receiving data processing are authorized to perform privilege transfer transactions.
- secure mutual authentications are performed using the mechanism described in co-pending U.S. patent application Ser. No. 10/058,734, Docket Number DWE-2, “A System And Method For Performing Mutual Authentication Between Security Tokens,” filed on Jan. 30, 2002 and assigned to a common assignee and herein incorporated by reference. Standard challenge/response authentication mechanisms may be employed as well.
- the transfer of the key component MK 1 205 and its associated attributes A 203 from the first security token TOKEN 1 204 to the second security token 206 is depicted in FIG. 2B .
- the second security token TOKEN 2 206 assembles the pair of key components MK 1 ′, MK 2 205 ′, 210 reconstructing the master key MK 12 240 .
- the operable master key MK 12 240 is stored in-volatile memory of the second security token TOKEN 2 206 as prescribed by the associated attributes A′ 203 ′.
- a secure channel 282 is employed during the key component transfer process.
- a third security token TOKEN 3 250 replaces the first security token.
- TOKEN 1 204 The third security token TOKEN 3 250 includes a privilege key KT 3 255 which was derived from the master key MK 12 240 by diversifying the master key MK 12 240 using a unique identifier ID 260 associated with the third security token 250 .
- the privilege key KT 3 255 was generated and injected into the third security token TOKEN 3 250 at time of issuance by the issuing authority.
- Each security token included in the defined privilege group has an operatively installed privilege key derived and installed in the same manner.
- the unique identifier ID 260 is sent 280 as part of an authentication challenge from the third security token 250 to the second security token 206 .
- the second security token TOKEN 2 206 diversifies the master key MK 12 240 with the received unique identifier ID′ 260 ′ and reconstructs the privilege key KT 3 ′ 255 ′.
- the reconstructed privilege key KT 3 ′ 255 ′ is likewise maintained in volatile memory as prescribed by the associated attributes A′ 203 ′.
- the reconstructed privilege key KT 3 ′ 255 ′ is used to generate a response to the challenge issued by the third security token TOKEN 3 250 as is shown in FIG. 2E .
- the successful authentication proves to the third security token that a valid privilege exists in the second security token TOKEN 2 206 which allows access to the controlled resources 220 by either providing information necessary to access a specific record 295 (e.g. social security number) or allowing access and transfer of a cryptographic key necessary to unlock the controlled resource as represented by an object′ 270 ′.
- a secure channel 290 is employed during any object′ 270 ′ transfer process.
- FIG. 3 another embodiment of the invention is depicted where a complete master key MK 305 representing a delegable privilege and associated attributes A 302 are shown.
- the master key MK 305 and its associated attributes A 302 are securely stored inside a first security token TOKEN 1 304 and operatively connected 380 to a client computer system 303 .
- a second security TOKEN 2 306 is likewise operatively connected 380 to a client computer system 303 and in processing communications with the first security token TOKEN 1 304 .
- a controlled resources 330 associated with the computer system 303 is shown as a database (for example only) and is accessible only after privilege verification using a third security token.
- the prerequisite mutual authentication 380 cycle as described above, is initiated before privilege transfer.
- the transfer of the master key MK 305 and its associated attributes A 302 from the first security token 304 to the second security token 306 is depicted in FIG. 3B .
- the second security token 306 operatively stores the received master key MK 305 in volatile memory as prescribed by the associated attributes A′ 302 ′.
- a secure channel 390 is employed during the master key transfer process. Additional aspects for using the symmetric master key are identical to those described above for the component key part.
- FIG. 4 another embodiment of the invention is depicted where a group private key Kpri 405 representing a particular privilege and associated attributes A 402 are generated by an issuing authority and installed in the first security token TOKEN 1 403 .
- the first security token is operatively connected 480 to a client computer system 404 .
- a second security TOKEN 2 406 is likewise operatively connected 480 to the client computer system 404 and in processing communications with the first security token TOKEN 1 403 .
- a controlled resources 440 associated with the computer system 404 is shown as a database (for example only) and is accessible only after privilege verification using a third security token.
- the public key counterpart to the group private key is likewise installed in all user level security tokens.
- the PKI keys may based on algorithms utilizing elliptical curves, RSA, Diffie-Hellman, Pretty Good Privacy (PGP), El Gamal, etc.
- FIG. 4A the mutual authentication 480 cycle as described above, is initiated before privilege transfer.
- the transfer of the private key Kpri 405 and its associated attributes A 402 from the first security token TOKEN 1 403 to the second security token TOKEN 2 406 is depicted in FIG. 4B .
- the second security token 406 operatively stores the received private key Kpri 405 in volatile memory as prescribed by the associated attributes A′ 402 ′.
- a secure channel 490 is employed during the private key transfer process.
- a third security token TOKEN 3 450 replaces the first security token TOKEN 1 403 .
- the third security token TOKEN 3 450 includes a public key Kpub 455 which is the counterpart to the private key Kpri′ 405 ′.
- the public key Kpub 455 was generated and injected into the third security token TOKEN 3 450 at time of issuance by the issuing authority.
- Each security token included in the defined privilege group has an operatively installed public key installed in the same manner.
- An authentication challenge is generated by the third security token TOKEN 3 450 which incorporates the use of the public key Kpub 455 .
- the challenge is sent 480 to the second security token TOKEN 2 406 .
- the second security token TOKEN 2 406 receives the authentication challenge and generates a response which incorporate the use of the group private key Kpri′ 405 ′.
- the response is sent 480 to the third security token TOKEN 3 450 for authentication.
- the successful authentication proves to the third security token TOKEN 3 450 that a valid privilege exists in the second security token TOKEN 2 406 which allows access to the controlled resources 440 by either providing information necessary to access a specific record 495 (e.g. social security number) or allowing access and transfer of a cryptographic key necessary to unlock the controlled resource as represented by an object′ 470 ′.
- a secure channel 490 is employed during any object′ 270 ′ transfer process.
- the process is initiated 500 by performing mutual authentications 502 between a delegating security token and a first data processing unit 502 .
- the privilege delegation process ends 526 . If the authentication process is successful 504 , a secure channel is established 506 and the delegable privileges and associated attributes are transferred from the security token to the receiving data processing unit 508 . In order to use the privilege, the receiving data processing unit is authenticated 510 by a second data processing unit. If the authentication process is successful 512 , a secure channel is established 514 and the delegable privilege is verified by the second data processing unit 516 . If the authentication process is unsuccessful 512 , the privilege delegation process ends 526 .
- the verification process is successful 518 , access and use of the delegable privilege is afforded 524 . If the verification process is unsuccessful 518 , the attributes associated with the privilege are updated 520 and the verification process reattempted 516 . If the verification process is successful 518 , access and use of the delegable privilege is afforded 524 as prescribed by the associated attributes. If the verification process fails a second time, the privilege delegation process ends 526 .
Abstract
Description
- The present invention relates generally to a data processing system and method and more specifically to a system and method for delegating privileges from one or more security tokens to one or more data processing units.
- Privilege delegation affords the ability to allow another to act as a surrogate for the delegator. A number of different strategies are relevant to accomplish the delegation process. For example, U.S. Pat. No. 5,339,403 issued to Parker, describes a privilege attribute certificate issued by an authentication server to allow a client access to distributed resources. In a second example, U.S. Pat. No. 5,918,228 issued to Rich, et al. describes a privilege attribute certificate used to “impersonate” a client to other web-based servers. The privilege attribute certificate is generated and issued by a first web server and presented to other servers by the first server as a means to “impersonate” a client for access purposes. A popular form of privilege delegation designed for networks employing TCP/IP protocols is called Kerberos.
- Kerberos authenticates the identity of users attempting to log on to a network and includes secure messaging based on symmetric cryptography methods. Kerberos works by granting users “tickets,” as a form of credential which are then used to identify themselves to other network service providers. Each ticket includes information that allows another network service provider to determine that the user has been properly authenticated, analogous to a privilege attribute certificate. The proper ticket is automatically presented to the network service provider as a means to avoid multiple authentication procedures each time a different network service is attempted to be accessed.
- In the above cited examples, the privilege attribute certificates or tickets are generated and controlled by the issuing servers rather than the person using the system. The person using the system must therefore trust the delegation strategies employed on the system. Secondly, the server-based systems may not provide sufficient flexibility in the delegation process where the necessary delegation criteria are role-based or rule-based rather than identity based. Lastly, the privilege attribute certificates employed in the relevant art are somewhat vulnerable to attack by a person or entity having access to the certificate generating servers.
- For the foregoing reasons, there is a need to incorporate a flexible privilege delegation mechanism into one or more security tokens where the holder of the security token has greater control over the issuance and use of the delegable privileges.
- The present invention is directed to a privilege delegation system and method that incorporates flexibility and control over the issuance and use of the delegable privileges. The invention includes a security token having the ability to transfer delegable privileges and associated attributes to another security token or computer system either of which are described generically herein as data processing units. Various embodiments are provided including a split privilege which allows access to a controlled resource when combined with all of the components to form a complete privilege.
- The receiving data processing unit includes the ability to operatively store and use the delegated privilege and perform data exchanges with the security token and optionally with at least a second data processing unit. Mutual authentications are performed between the delegating security token and receiving data processing unit before the delegated privilege is transferred.
- The information that may be communicated in the data exchange includes authentication data, one or more delegated privileges and the associated attributes. A secure messaging protocol is used during the data exchanges. The delegable privileges include a privilege attribute certificate, a key component, a cryptographic key, digital ticket, digital credential, password, biometric template, digital rights, license or loyalty credit.
- Typical uses for the delegated privileges include authentication, terminal activation, personalization of an intelligent device, accessing resources included in or accessible through the second data processing unit or another data processing unit, allowing the second data processing unit or another data processing unit to act as a surrogate for the delegating security token and loyalty credit management. The attributes included in the privilege attribute certificate or in the separate file define the scope of usage and security aspects required to use the delegated privilege. When the attributes are included in the separate file, a verifiable cross reference to the associated privilege is included.
- The attributes associated with the delegated privilege provide sufficient information to the receiving data processing unit to configure the privilege and enforce control aspects stated in the attributes including security policies and delegated privilege state. The security policies includes details related to validity period, remaining number of uses, time limits and cryptographic measures to be employed. The delegated privilege state includes storage requirements (transient or permanent), and state of the host (idle, booting, secure mode, insecure mode, suspended.) The control aspects determine when the privilege is to be activated and destroyed. Other information included in the attributes includes operational information such as username, user ID, domain name, client name or host name.
- Some advantages of the invention are illustrated below by way of example. Privilege delegation and control may be applied in maintaining the privacy of a person's medical records. A patient's medical records should only be accessible to those authorized or “privileged” to access the records. In order to access a patient's medical records, a terminal is activated by securely transferring a privilege following mutual authentications from a physician's security token to a security token associated with the terminal. The entire privilege may be transferred from the physician's security token or formed by combining the information transferred with pre-existing information contained in the terminal security token. The physician's delegated privilege allows activation of the terminal to read a patient's medical records stored in or otherwise accessible using information stored in the patient's security token.
- The attributes associated with the delegated privilege may limit activation of the terminal to the physician's normal office hours and/or specify that the delegated privilege remain in transient memory only. The attributes may also provide the ability to delegate privileges to another physician while the first physician is on vacation. To access a patient's medical records, the patient presents his or her security token to the terminal. An authentication session follows which verifies to the patient's security token that the necessary privileges are present in the terminal security token to allow the terminal to access the patient's medical records. An office manager in the same office, may have a delegable privilege necessary to activate the same terminal for reviewing account balances associated with the patient but would not have the necessary delegable privilege to review the patient's medical records. A first alternative to using the split master key approach utilizes a complete master symmetric key which is installed in all role-based authorizing security tokens equivalent to the physician level example described above. In this alternative, the entire master key is transferred to the security token associated with the terminal, rather than a key component. All other aspects of the second embodiment of the invention are the same. The symmetric keys in either approach may be based on algorithms supporting the data encryption standard (DES), triple data encryption standard (3DES), advanced encryption standard (AES), etc.
- A second alternative to using the split key approach involves the use of public key infrastructure (PKI) keys. In this alternative, a group private key representing a particular privilege is generated by the issuing authority and installed in all role-based authorizing security tokens equivalent to the physician level example described above. The public key counterpart to the group private key is likewise installed in all patient level security tokens equivalent to the patient security token described above. The PKI keys may based on algorithms utilizing elliptical curves, RSA, Diffie-Hellman, Pretty Good Privacy (PGP), El Gamal, etc. In all embodiments involving cryptographic key transfers, mutual authentications should be performed between the delegating and delegated security tokens to prevent unauthorized disclosure of the cryptographic keys. Authentication of the terminal by the patient data processing unit is sufficient for using the transferred privileges.
- A more complete understanding of the present invention may be accomplished by referring to the following Detailed Description and Claims, when viewed in conjunction with the following drawings:
- FIG. 1—is a generalized system block diagram for implementing the main embodiment of the invention.
- FIG. 1A—is a detailed block diagram depicting a mutual authentication cycle between a security token and a first data processing unit.
- FIG. 1B—is a detailed block diagram depicting privilege delegation including associated attributes from a security token to a first data processing unit.
- FIG. 1C—is a detailed block diagram depicting privilege verification by a second data processing unit.
- FIG. 1D—is a detailed block diagram depicting privilege usage by the first data processing unit whereby an example resource contained in a second data processing unit is accessed using the delegated privilege.
- FIG. 1E—is a detailed block diagram depicting an existing privilege contained in a first data processing unit having an expired attribute.
- FIG. 1F—is a detailed block diagram depicting replacement of the expired attribute associated with the existing privilege.
- FIG. 1G—is a detailed block diagram depicting a variation of the first inventive embodiment.
- FIG. 1H—is a detailed block diagram depicting a transfer of a partial privilege from the security token to the first data processing unit.
- FIG. 1I—is a detailed block diagram depicting the transfer of the partial privilege from the first data processing unit to the second data processing unit.
- FIG. 1J—is a detailed block diagram depicting the combined partial privileges inside the second data processing unit and access to a controlled resource.
- FIG. 1K—is a detailed block diagram depicting a variation of the first inventive embodiment where the second partial privilege is transferred from the second data processing unit to the first data processing unit.
- FIG. 1L—is a detailed block diagram depicting the combined partial privileges inside the first data processing unit and access to a controlled resource.
- FIG. 2—is a generalized block diagram depicting an alternate embodiment of the invention using symmetric key components as a form of delegable privilege.
- FIG. 2A—is a detailed block diagram depicting a mutual authentication cycle between a first and a second data processing unit.
- FIG. 2B—is a detailed block diagram depicting privilege delegation from the first data processing unit to the second data processing unit using a secure messaging protocol and symmetric master key regeneration.
- FIG. 2C—is a detailed block diagram depicting a unique identifier sent from a third data processing unit to the data processing unit as part of an authentication challenge.
- FIG. 2D—is a detailed block diagram depicting master key diversification using the unique identifier to generate a data processing unit specific key necessary to access resources controlled by the third data processing unit.
- FIG. 2E—is a detailed block diagram depicting response to the authentication challenge which incorporates the use of the data processing unit specific key.
- FIG. 2F—is a detailed block diagram depicting access to the resources controlled by the third data processing unit following authentication of the second data processing unit by the third data processing unit.
- FIG. 3—is a generalized block diagram depicting an alternate embodiment of the invention using a complete symmetric key as a form of delegable privilege.
- FIG. 3A—is a detailed block diagram depicting a mutual authentication cycle between a first data processing unit and a second data processing unit.
- FIG. 3B—is a detailed block diagram depicting privilege delegation from the first data processing unit to the second data processing unit using a secure messaging protocol.
- FIG. 4—is a generalized block diagram depicting an alternate embodiment of the invention using a group asymmetric private key as a form of delegable privilege.
- FIG. 4A—is a detailed block diagram depicting a mutual authentication cycle between a first data processing unit and a second data processing unit.
- FIG. 4B—is a detailed block diagram depicting privilege delegation and its associated attributes from the first data processing unit to the second data processing unit using a secure messaging protocol.
- FIG. 4C—is a detailed block diagram depicting an authentication challenge sent from a third data processing unit to the second data processing unit using a public key counterpart to the group private key.
- FIG. 4D—is a detailed block diagram depicting response to the authentication challenge which incorporates the use of the group private key.
- FIG. 4E—is a detailed block diagram depicting access to the resources controlled by the third data processing unit following authentication of the second data processing unit by the third data processing unit.
- FIG. 5—is a simplified flow chart that illustrates the steps involved in implementing the main embodiment of the invention.
- FIG. 6—is a table providing a summary of the types of delegable privileges and information included in the associated attributes.
- This invention provides novel implementations in delegating privileges and associated attributes from a security token to one or more data processing units. For purposes of this invention, the security token and data processing units are assumed to include standardized cryptography modules, algorithms and services.
- The term “data processing unit” refers to a security token, an intelligent device or a computer system as appropriate. The term security token refers to hardware based security devices such as smart cards, integrated circuit cards, subscriber identification modules (SIM), wireless identification modules (WIM), identification tokens, secure application modules (SAM), hardware security modules (HSM), secure multi-media card (SMMC) and like devices. The terms data processing unit and security token are used interchangeably in the specification and no limitation is usage is implied.
- Referring to
FIG. 1 , the major components and interrelationships are depicted for implementing the main embodiment of the invention. Asecurity token 10 is shown operatively connected 12 to aclient computer 15. Theclient computer 15 is inprocessing communications 65 with a first dataprocessing unit DPU1 40. Theclient computer 15 provides the necessary hardware and software interfaces to allow thesecurity token 10 to communicate with the first dataprocessing unit DPU1 40 but otherwise does not affect the various embodiments of the invention described herein. Thesecurity token 10 includes at least onedelegable privilege P 20 and its associated attributes A 30. - The
delegable privilege P 20 may used for authentication, terminal activation, personalization of an intelligent device, accessingresources 60 included in or accessible through a second dataprocessing unit DPU2 50 or another data processing unit, allowing the second dataprocessing unit DPU2 50 or another data processing unit to act as a surrogate for the delegatingsecurity token 10 or maintenance of loyalty credits. - The attributes A 30 associated with the delegated
privilege P 20 provide sufficient information to a receiving data processing unit to configure theprivilege P 20 and enforce control aspects stated in the attributes A 30 including security policies and delegated privilege state. The security policies include details related to validity period, remaining number of uses, time limits and cryptographic measures to be employed. - The delegated privilege state includes storage requirements (transient or permanent), and state of the host (idle, booting, secure mode, insecure mode, suspended.) The control aspects determine when the privilege is to be activated and destroyed. Other information included in the attributes A 30 includes operational information such as username, user ID, domain name, client name or host name. The Table of
FIG. 6 , provides a summary of the types of delegable privileges and information included in the associated attributes. - The attributes A 30 are associated with the
privilege P 20 by a unique signature, hash or message authentication code or hashed message authentication which unambiguously links theattributes 30 with theprivilege 20. The attributes A 30 are normally stored separately from theprivilege 20 except when incorporated into certificate form (e.g. digital tickets, digital rights, license or privilege attribute certificates) - The first data
processing unit DPU1 40 is inprocessing communications 65 with the second dataprocessing unit DPU2 50. The second dataprocessing unit DPU2 50 includes theresource 60 which is only accessible using thevalid privilege P 20. Theresource 60 is defined generically to include data or functions contained in the second dataprocessing unit DPU2 50 or otherwise accessible from another data processing unit using theresource 60. The communications links 65 and 85 may be either local connections, remote network connections or any combination thereof. - Referring to
FIG. 1A , a prerequisitemutual authentication cycle 70 is initiated before privilege transfer.Mutual authentication 70 is preferred to ensure that both the sending data processing unit and receiving data processing are authorized to perform privilege transfer transactions. InFIG. 1B , once the mutual authentication cycle is successfully completed, a secure channel is established between thesecurity token 10 and first dataprocessing unit DPU1 40. - The
secure channel 75 may be implemented using secure messaging protocols such as secure socket layer encryption (SSL), transport layer security (TLS) or IPsec. Theprivilege P 20 and its associated attributes A 30 are securely sent 65 through thesecure channel 75 and stored inside the first data processing unit DPU1 according to the control aspects specified by the attributes A′ 30′. (The privilege P′ 20′ and associated attribute A′ 30′ are shown with the apostrophes to indicate a duplicate copy of the originals.) - In
FIG. 1C , the first dataprocessing unit DPU1 40 authenticates itself to the second dataprocessing unit DPU2 50 and a secure channel is established 80. The privilege P″ 20″ is securely sent 85 to the second dataprocessing unit DPU2 50 where it is validated 90. Access and use 95 of theresource 60 is shown inFIG. 1D . - In
FIG. 1E , a privilege P′ 20′ and its associated attributes A′x 30′ are shown. The attributes A′x 30′ includes a parameter which has expired (for example validity period.) In order to use the privilege, an update is required. The updated attributes A″ 30″ is securely sent from thesecurity token 10 to the first dataprocessing unit DPU1 40 where the expired attributes A′x 30′ is replaced with the update attributes A″x 30″ as is shown inFIG. 1F . - Referring to
FIG. 1G , a partial privilege p/1n 22 and its associated attributes A 30 are shown initially stored inside thesecurity token 10. A remaining portion of the privilege p2/n 22′ and its associated attributes A′ 30′ are shown stored inside asecond security token 50. This embodiment of the invention requires that the partial privileges p1/n 22 and p2/n 22′ be combined in order to gain access to aresource 60. It is envisioned by the inventor that the attributes A 30 and A′ 30′ may be delegated by either thesecurity token 10 or seconddata processing unit 50, or combined together to form a complete set of attributes. It is also envisioned by the inventor that more than two partial privileges can be combined to form an operable privilege. - Referring to
FIG. 1H , the partial privilege p1/n 22 and its associated attributes A 30 are shown being delegated 12 from thesecurity token 10 via aclient 15 to 65 a first dataprocessing unit DPU1 40. The delegation includes asecure channel 75 to prevent unauthorized monitoring of the transaction. - In
FIG. 1I , the partial privilege p1/n 22 and its associated attributes A 30 are shown being delegated 85 again from the first dataprocessing unit DPU1 40 to the second dataprocessing unit DPU2 50 using asecure channel 95. Continuing withFIG. 1I , the combined partial privileges p1/n 22 and p2/n 22′ form acomplete privilege P 24 including a complete set of associated attributes A 32, which allows access to the controlledresource 60 by the second dataprocessing unit DPU2 50. - In
FIG. 1K , an equivalent embodiment is shown where the partial privilege p2/n 22′ and its associated attributes A′ 30′ are shown being delegated 85 from the second dataprocessing unit DPU2 50 to the first dataprocessing unit DPU1 40 using asecure channel 95. Continuing withFIG. 1L , the combined partial privileges p1/n 22 and p2/n 22′ form acomplete privilege P 24 including a complete set of associated attributes A 32, which allows access to the controlledresource 60′ by the first dataprocessing unit DPU1 40. The controlledresource 60′ is shown being transferred from the second dataprocessing unit DPU2 50 for consistency with the previous drawings only. The controlledresource 60 could remain on the second dataprocessing unit DPU2 50 and be accessible using the communications link 85. - Referring to
FIG. 2 , the major components and interrelationships are depicted for implementing another embodiment of the invention. In this embodiment of the invention, privilege delegation is performed using symmetric cryptographic keys. Acomputer system 202 is shown operatively connected to afirst security token 204 andsecond security token 206. A middleware program (not shown) installed in thecomputer system 202 supports the use of two or more data processing units. An example of which is described in “Government Smart Card Interoperability Specification Contract Modification,” contract number GS00T00ALD0208 PS02, Aug. 29, 2000 and is herein incorporated by reference. - The symmetric cryptography methods employed in this embodiment of the invention may be based on algorithms supporting the data encryption standard (DES), triple data encryption standard (3DES) or advanced encryption standard (AES.)
- To practice this embodiment of the invention, an issuing authority initially generates a master key associated with a particular privilege. Separate master keys may be used to define a specific privilege within a select group of data processing units. The master key is then sequentially diversified with unique identifiers associated with a pre-defined group of security tokens, forming unique privilege keys. The privilege keys will be used to verify that another security token, generally associated with a terminal, has the required privilege before allowing access to a controlled
resource 220. The resulting privilege key(s) are then injected into the security token(s) by the issuing authority. The master key(s) are then diversified using a key splitting mechanism and installed in the designated data processing units, shown in FIGA as TOKEN 1 204 and TOKEN 2 206. - The first
security token TOKEN1 204 includes thekey component MK1 205. The secondsecurity token TOKEN2 206 includes the counterpart to thekey component MK2 210 and the means to combine the two key components to form the complete master key. The reconstructed master key is intended to be maintained in transient memory of thesecond security token 206 to prevent unauthorized disclosure as prescribed by attributes A 203 associated with the keycomponent privilege MK1 205. Any tampering with the security token containing the master key results in the destruction of the master key.Controlled resources 220 associated with thecomputer system 202 are shown as a database for example only and is accessible only after privilege verification using a third data processing unit. - In
FIG. 2A , themutual authentication 280 cycle is performed as described above before privilege transfer.Mutual authentication 280 is preferred to ensure that both the sending data processing unit and receiving data processing are authorized to perform privilege transfer transactions. - In the preferred embodiment of the invention, secure mutual authentications are performed using the mechanism described in co-pending U.S. patent application Ser. No. 10/058,734, Docket Number DWE-2, “A System And Method For Performing Mutual Authentication Between Security Tokens,” filed on Jan. 30, 2002 and assigned to a common assignee and herein incorporated by reference. Standard challenge/response authentication mechanisms may be employed as well.
- The transfer of the
key component MK1 205 and its associated attributes A 203 from the firstsecurity token TOKEN1 204 to thesecond security token 206 is depicted inFIG. 2B . The secondsecurity token TOKEN2 206 assembles the pair of key components MK1′,MK2 205′, 210 reconstructing themaster key MK12 240. The operablemaster key MK12 240 is stored in-volatile memory of the secondsecurity token TOKEN2 206 as prescribed by the associated attributes A′ 203′. Asecure channel 282 is employed during the key component transfer process. - In
FIG. 2C , a thirdsecurity token TOKEN3 250 replaces the first security token.TOKEN1 204. The thirdsecurity token TOKEN3 250 includes a privilegekey KT3 255 which was derived from themaster key MK12 240 by diversifying themaster key MK12 240 using aunique identifier ID 260 associated with thethird security token 250. The privilegekey KT3 255 was generated and injected into the thirdsecurity token TOKEN3 250 at time of issuance by the issuing authority. Each security token included in the defined privilege group has an operatively installed privilege key derived and installed in the same manner. To regenerate the privilege key, theunique identifier ID 260 is sent 280 as part of an authentication challenge from thethird security token 250 to thesecond security token 206. - In
FIG. 2D , the secondsecurity token TOKEN2 206 diversifies themaster key MK12 240 with the received unique identifier ID′ 260′ and reconstructs the privilege key KT3′ 255′. The reconstructed privilege key KT3′ 255′ is likewise maintained in volatile memory as prescribed by the associated attributes A′ 203′. The reconstructed privilege key KT3′ 255′ is used to generate a response to the challenge issued by the thirdsecurity token TOKEN3 250 as is shown inFIG. 2E . - In
FIG. 2F , the successful authentication proves to the third security token that a valid privilege exists in the secondsecurity token TOKEN2 206 which allows access to the controlledresources 220 by either providing information necessary to access a specific record 295 (e.g. social security number) or allowing access and transfer of a cryptographic key necessary to unlock the controlled resource as represented by an object′ 270′. Asecure channel 290 is employed during any object′ 270′ transfer process. - Referring to
FIG. 3 , another embodiment of the invention is depicted where a completemaster key MK 305 representing a delegable privilege and associated attributes A 302 are shown. Themaster key MK 305 and its associated attributes A 302 are securely stored inside a first securitytoken TOKEN1 304 and operatively connected 380 to aclient computer system 303. Asecond security TOKEN2 306 is likewise operatively connected 380 to aclient computer system 303 and in processing communications with the firstsecurity token TOKEN1 304. A controlledresources 330 associated with thecomputer system 303 is shown as a database (for example only) and is accessible only after privilege verification using a third security token. - Referring to
FIG. 3A , the prerequisitemutual authentication 380 cycle as described above, is initiated before privilege transfer. The transfer of themaster key MK 305 and its associated attributes A 302 from thefirst security token 304 to thesecond security token 306 is depicted inFIG. 3B . Thesecond security token 306 operatively stores the receivedmaster key MK 305 in volatile memory as prescribed by the associated attributes A′ 302′. Asecure channel 390 is employed during the master key transfer process. Additional aspects for using the symmetric master key are identical to those described above for the component key part. - Referring to
FIG. 4 , another embodiment of the invention is depicted where a groupprivate key Kpri 405 representing a particular privilege and associated attributes A 402 are generated by an issuing authority and installed in the firstsecurity token TOKEN1 403. The first security token is operatively connected 480 to aclient computer system 404. - A
second security TOKEN2 406 is likewise operatively connected 480 to theclient computer system 404 and in processing communications with the firstsecurity token TOKEN1 403. A controlledresources 440 associated with thecomputer system 404 is shown as a database (for example only) and is accessible only after privilege verification using a third security token. The public key counterpart to the group private key is likewise installed in all user level security tokens. The PKI keys may based on algorithms utilizing elliptical curves, RSA, Diffie-Hellman, Pretty Good Privacy (PGP), El Gamal, etc. - Referring to
FIG. 4A , themutual authentication 480 cycle as described above, is initiated before privilege transfer. The transfer of theprivate key Kpri 405 and its associated attributes A 402 from the firstsecurity token TOKEN1 403 to the secondsecurity token TOKEN2 406 is depicted inFIG. 4B . Thesecond security token 406 operatively stores the receivedprivate key Kpri 405 in volatile memory as prescribed by the associated attributes A′ 402′. Asecure channel 490 is employed during the private key transfer process. - In
FIG. 4C , a thirdsecurity token TOKEN3 450 replaces the firstsecurity token TOKEN1 403. The thirdsecurity token TOKEN3 450 includes apublic key Kpub 455 which is the counterpart to the private key Kpri′ 405′. Thepublic key Kpub 455 was generated and injected into the thirdsecurity token TOKEN3 450 at time of issuance by the issuing authority. Each security token included in the defined privilege group has an operatively installed public key installed in the same manner. An authentication challenge is generated by the thirdsecurity token TOKEN3 450 which incorporates the use of thepublic key Kpub 455. The challenge is sent 480 to the secondsecurity token TOKEN2 406. - In
FIG. 4D , the secondsecurity token TOKEN2 406 receives the authentication challenge and generates a response which incorporate the use of the group private key Kpri′ 405′. The response is sent 480 to the third securitytoken TOKEN3 450 for authentication. - In
FIG. 4E , the successful authentication proves to the thirdsecurity token TOKEN3 450 that a valid privilege exists in the secondsecurity token TOKEN2 406 which allows access to the controlledresources 440 by either providing information necessary to access a specific record 495 (e.g. social security number) or allowing access and transfer of a cryptographic key necessary to unlock the controlled resource as represented by an object′ 470′. Asecure channel 490 is employed during any object′ 270′ transfer process. - Referring to
FIG. 5 , a simplified flowchart is presented which provides the steps necessary to implement the invention. The process is initiated 500 by performingmutual authentications 502 between a delegating security token and a firstdata processing unit 502. - If either part of the mutual authentication cycle fails 504, the privilege delegation process ends 526. If the authentication process is successful 504, a secure channel is established 506 and the delegable privileges and associated attributes are transferred from the security token to the receiving
data processing unit 508. In order to use the privilege, the receiving data processing unit is authenticated 510 by a second data processing unit. If the authentication process is successful 512, a secure channel is established 514 and the delegable privilege is verified by the seconddata processing unit 516. If the authentication process is unsuccessful 512, the privilege delegation process ends 526. - If the verification process is successful 518, access and use of the delegable privilege is afforded 524. If the verification process is unsuccessful 518, the attributes associated with the privilege are updated 520 and the verification process reattempted 516. If the verification process is successful 518, access and use of the delegable privilege is afforded 524 as prescribed by the associated attributes. If the verification process fails a second time, the privilege delegation process ends 526.
- The foregoing described embodiments of the invention are provided as illustrations and descriptions. They are not intended to limit the invention to precise form described. In particular, it is contemplated that functional implementation of the invention described herein may be implemented equivalently in hardware, software, firmware, and/or other available functional components or building blocks. Other variations and embodiments are possible in light of above teachings, and it is not intended that this Detailed Description limit the scope of invention, but rather by the Claims that follow herein.
Claims (11)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/626,015 US20130145442A1 (en) | 2002-08-15 | 2012-09-25 | System and method for privilege delegation and control |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/218,642 US7770212B2 (en) | 2002-08-15 | 2002-08-15 | System and method for privilege delegation and control |
US12/804,146 US8302171B2 (en) | 2002-08-15 | 2010-07-14 | System and method for privilege delegation and control |
US13/626,015 US20130145442A1 (en) | 2002-08-15 | 2012-09-25 | System and method for privilege delegation and control |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/804,146 Continuation US8302171B2 (en) | 2002-08-15 | 2010-07-14 | System and method for privilege delegation and control |
Publications (1)
Publication Number | Publication Date |
---|---|
US20130145442A1 true US20130145442A1 (en) | 2013-06-06 |
Family
ID=30770629
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/218,642 Active 2025-01-02 US7770212B2 (en) | 2002-08-15 | 2002-08-15 | System and method for privilege delegation and control |
US12/804,146 Expired - Lifetime US8302171B2 (en) | 2002-08-15 | 2010-07-14 | System and method for privilege delegation and control |
US13/626,015 Abandoned US20130145442A1 (en) | 2002-08-15 | 2012-09-25 | System and method for privilege delegation and control |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/218,642 Active 2025-01-02 US7770212B2 (en) | 2002-08-15 | 2002-08-15 | System and method for privilege delegation and control |
US12/804,146 Expired - Lifetime US8302171B2 (en) | 2002-08-15 | 2010-07-14 | System and method for privilege delegation and control |
Country Status (3)
Country | Link |
---|---|
US (3) | US7770212B2 (en) |
EP (2) | EP1389752B1 (en) |
ES (1) | ES2440826T3 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2017160394A1 (en) * | 2016-03-15 | 2017-09-21 | Intel Corporation | System, apparatus and method for key provisioning delegation |
Families Citing this family (94)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7673323B1 (en) | 1998-10-28 | 2010-03-02 | Bea Systems, Inc. | System and method for maintaining security in a distributed computer network |
IL147164A0 (en) * | 1999-06-18 | 2002-08-14 | Echarge Corp | Method and apparatus for ordering goods, services and content over an internetwork using a virtual payment account |
US7418500B1 (en) * | 2002-03-25 | 2008-08-26 | Network Appliance, Inc. | Mechanism for controlled sharing of files in a clustered application environment |
US20030226015A1 (en) * | 2002-05-31 | 2003-12-04 | Neufeld E. David | Method and apparatus for configuring security options in a computer system |
US7770212B2 (en) * | 2002-08-15 | 2010-08-03 | Activcard | System and method for privilege delegation and control |
US7177847B2 (en) * | 2002-10-15 | 2007-02-13 | Microsoft Corporation | Authorization token accompanying request and including constraint tied to request |
US7840806B2 (en) * | 2002-10-16 | 2010-11-23 | Enterprise Information Management, Inc. | System and method of non-centralized zero knowledge authentication for a computer network |
US20040153171A1 (en) * | 2002-10-21 | 2004-08-05 | Brandt David D. | System and methodology providing automation security architecture in an industrial controller environment |
US8909926B2 (en) * | 2002-10-21 | 2014-12-09 | Rockwell Automation Technologies, Inc. | System and methodology providing automation security analysis, validation, and learning in an industrial controller environment |
US20040107345A1 (en) * | 2002-10-21 | 2004-06-03 | Brandt David D. | System and methodology providing automation security protocols and intrusion detection in an industrial controller environment |
US9009084B2 (en) | 2002-10-21 | 2015-04-14 | Rockwell Automation Technologies, Inc. | System and methodology providing automation security analysis and network intrusion protection in an industrial environment |
US7603548B2 (en) * | 2003-10-10 | 2009-10-13 | Bea Systems, Inc. | Security provider development model |
US20050262362A1 (en) * | 2003-10-10 | 2005-11-24 | Bea Systems, Inc. | Distributed security system policies |
US20050125254A1 (en) * | 2003-12-03 | 2005-06-09 | Roy Schoenberg | Key maintenance method and system |
GB2409316B (en) * | 2003-12-17 | 2006-06-21 | Motorola Inc | Method and apparatus for programming electronic security token |
US20050171908A1 (en) * | 2004-01-29 | 2005-08-04 | Carlsen James K. | System and method for aggregating and delegating signature authority to third parties in commercial transactions |
GB0407369D0 (en) | 2004-03-31 | 2004-05-05 | British Telecomm | Trust tokens |
AU2005241560A1 (en) * | 2004-05-05 | 2005-11-17 | Ims Software Services, Ltd. | Data encryption applications for multi-source longitudinal patient-level data integration |
DE102004046153B4 (en) * | 2004-09-23 | 2006-10-12 | Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. | Method and network system for determining the digital reputation |
US7631348B2 (en) * | 2004-11-22 | 2009-12-08 | Standard Microsystems Corporation | Secure authentication using a low pin count based smart card reader |
US8312526B2 (en) * | 2004-11-30 | 2012-11-13 | Sap Aktiengesellschaft | Method and system for delegating authority with restricted access right in an online collaborative environment |
US20060224628A1 (en) * | 2005-03-29 | 2006-10-05 | Bea Systems, Inc. | Modeling for data services |
US8086615B2 (en) * | 2005-03-28 | 2011-12-27 | Oracle International Corporation | Security data redaction |
US7748027B2 (en) * | 2005-05-11 | 2010-06-29 | Bea Systems, Inc. | System and method for dynamic data redaction |
US7774827B2 (en) * | 2005-06-06 | 2010-08-10 | Novell, Inc. | Techniques for providing role-based security with instance-level granularity |
US7974395B2 (en) * | 2005-09-28 | 2011-07-05 | Avaya Inc. | Detection of telephone number spoofing |
US8775586B2 (en) * | 2005-09-29 | 2014-07-08 | Avaya Inc. | Granting privileges and sharing resources in a telecommunications system |
US20100235924A1 (en) * | 2006-01-20 | 2010-09-16 | Bulot Earl J | Secure Personal Medical Process |
US20070180259A1 (en) * | 2006-01-20 | 2007-08-02 | Bulot Earl J | Secure Personal Medical Process |
US8438657B2 (en) * | 2006-02-07 | 2013-05-07 | Siemens Aktiengesellschaft | Method for controlling the access to a data network |
US20080066158A1 (en) * | 2006-09-08 | 2008-03-13 | Microsoft Corporation | Authorization Decisions with Principal Attributes |
US8060931B2 (en) | 2006-09-08 | 2011-11-15 | Microsoft Corporation | Security authorization queries |
US8201215B2 (en) * | 2006-09-08 | 2012-06-12 | Microsoft Corporation | Controlling the delegation of rights |
US7814534B2 (en) * | 2006-09-08 | 2010-10-12 | Microsoft Corporation | Auditing authorization decisions |
US20080066169A1 (en) * | 2006-09-08 | 2008-03-13 | Microsoft Corporation | Fact Qualifiers in Security Scenarios |
US20080065899A1 (en) * | 2006-09-08 | 2008-03-13 | Microsoft Corporation | Variable Expressions in Security Assertions |
US8656503B2 (en) * | 2006-09-11 | 2014-02-18 | Microsoft Corporation | Security language translations with logic resolution |
US8938783B2 (en) * | 2006-09-11 | 2015-01-20 | Microsoft Corporation | Security language expressions for logic resolution |
US20080066147A1 (en) * | 2006-09-11 | 2008-03-13 | Microsoft Corporation | Composable Security Policies |
US20080077976A1 (en) * | 2006-09-27 | 2008-03-27 | Rockwell Automation Technologies, Inc. | Cryptographic authentication protocol |
US20080077967A1 (en) * | 2006-09-27 | 2008-03-27 | Matsushita Electric Industrial Co., Ltd. | Video receiving device, video data receiving system and authentication control method thereof |
US20080133571A1 (en) * | 2006-12-05 | 2008-06-05 | International Business Machines Corporation | Modifying Behavior in Messaging Systems According to Organizational Hierarchy |
US20080140784A1 (en) * | 2006-12-11 | 2008-06-12 | International Business Machines Corporation | Multiple Originators in an Electronic Message |
EP1942470A1 (en) | 2006-12-29 | 2008-07-09 | Legic Identsystems AG | Authentication system |
US8132020B2 (en) * | 2007-03-26 | 2012-03-06 | Zhu Yunzhou | System and method for user authentication with exposed and hidden keys |
JP5186790B2 (en) * | 2007-04-06 | 2013-04-24 | 日本電気株式会社 | Electronic money transaction method and electronic money system |
JP4548441B2 (en) * | 2007-04-11 | 2010-09-22 | 日本電気株式会社 | Content utilization system and content utilization method |
US20090007256A1 (en) * | 2007-06-28 | 2009-01-01 | Microsoft Corporation | Using a trusted entity to drive security decisions |
US20090055236A1 (en) * | 2007-08-23 | 2009-02-26 | International Business Machines Corporation | System and method for evaluating likelihood of meeting attendance |
CN100536565C (en) * | 2007-08-24 | 2009-09-02 | 北京市朝阳区信息网络中心 | User classification management system of image information management system |
US8091035B2 (en) * | 2007-11-08 | 2012-01-03 | International Business Machines Corporation | System and method for sharing data |
US10594695B2 (en) * | 2007-12-10 | 2020-03-17 | Nokia Technologies Oy | Authentication arrangement |
WO2009084601A1 (en) * | 2007-12-27 | 2009-07-09 | Nec Corporation | Access right managing system, access right managing method, and access right managing program |
US8180657B2 (en) * | 2007-12-31 | 2012-05-15 | International Business Machines Corporation | System and method for event slot negotiation |
DE102008000067C5 (en) * | 2008-01-16 | 2012-10-25 | Bundesdruckerei Gmbh | Method for reading attributes from an ID token |
EP2262164A1 (en) * | 2008-02-18 | 2010-12-15 | Microelectronica Española, S.A.U. | Secure data transfer |
JP2009258860A (en) * | 2008-04-14 | 2009-11-05 | Sony Corp | Information processing device and method, recording medium, program and information processing system |
US20090276853A1 (en) * | 2008-05-02 | 2009-11-05 | Mulval Technologies, Inc. | Filtering intrusion detection system events on a single host |
US20090287793A1 (en) * | 2008-05-19 | 2009-11-19 | O'sullivan Patrick Joseph | Markup elements in referenced content |
GB2460412B (en) * | 2008-05-28 | 2012-09-19 | Hewlett Packard Development Co | Information sharing |
US20090313075A1 (en) * | 2008-06-12 | 2009-12-17 | O'sullivan Patrick Joseph | System and method for adaptive scheduling |
US8544074B2 (en) | 2008-06-19 | 2013-09-24 | Microsoft Corporation | Federated realm discovery |
DE102008040416A1 (en) * | 2008-07-15 | 2010-01-21 | Bundesdruckerei Gmbh | Method for reading attributes from an ID token |
EP2338255B1 (en) * | 2008-09-22 | 2017-04-05 | Bundesdruckerei GmbH | Method, computer program product and system for authenticating a user of a telecommunications network |
US8775527B2 (en) * | 2008-12-15 | 2014-07-08 | International Business Machines Corporation | Collaborative email filtering |
US8589502B2 (en) * | 2008-12-31 | 2013-11-19 | International Business Machines Corporation | System and method for allowing access to content |
US8368525B2 (en) * | 2008-12-31 | 2013-02-05 | International Business Machines Corporation | System and method for distinguishing messages |
DE102009027682A1 (en) * | 2009-07-14 | 2011-01-20 | Bundesdruckerei Gmbh | Method for generating a soft token |
US9088580B2 (en) * | 2009-12-31 | 2015-07-21 | Microsoft Technology Licensing, Llc | Access control based on user and service |
JP5623234B2 (en) * | 2010-10-22 | 2014-11-12 | キヤノン株式会社 | Authority delegation system, authority delegation method, information processing apparatus, control method thereof, and program |
US8752143B2 (en) | 2011-08-15 | 2014-06-10 | Bank Of America Corporation | Method and apparatus for token-based reassignment of privileges |
US9361443B2 (en) * | 2011-08-15 | 2016-06-07 | Bank Of America Corporation | Method and apparatus for token-based combining of authentication methods |
US9172539B2 (en) * | 2011-09-14 | 2015-10-27 | Mastercard International Incorporated | In-market personalization of payment devices |
DE102012004484A1 (en) * | 2012-03-05 | 2013-09-05 | Giesecke & Devrient Gmbh | Procedure for creating a derived instance |
US9003507B2 (en) * | 2012-03-23 | 2015-04-07 | Cloudpath Networks, Inc. | System and method for providing a certificate to a third party request |
US10423952B2 (en) | 2013-05-06 | 2019-09-24 | Institutional Cash Distributors Technology, Llc | Encapsulated security tokens for electronic transactions |
WO2013166518A1 (en) * | 2012-05-04 | 2013-11-07 | Institutional Cash Distributors Technology, Llc | Secure transaction object creation, propagation and invocation |
US11334884B2 (en) * | 2012-05-04 | 2022-05-17 | Institutional Cash Distributors Technology, Llc | Encapsulated security tokens for electronic transactions |
DE102012017826A1 (en) * | 2012-09-10 | 2014-03-13 | Giesecke & Devrient Gmbh | Method of creating a derived instance of an original volume |
TWI456427B (en) | 2012-12-12 | 2014-10-11 | Inst Information Industry | Major management apparatus, authorized management apparatus, electronic apparatus for delegation management, and delegation management methods thereof |
GB2512062A (en) | 2013-03-18 | 2014-09-24 | Ibm | A method for secure user authentication in a dynamic network |
GB2524010A (en) * | 2014-03-10 | 2015-09-16 | Ibm | User authentication |
US9351098B2 (en) * | 2014-05-19 | 2016-05-24 | Lenovo (Singapore) Pte. Ltd. | Providing access to and enabling functionality of first device based on communication with second device |
US9760704B2 (en) * | 2014-05-23 | 2017-09-12 | Blackberry Limited | Security apparatus session sharing |
US9619012B2 (en) | 2014-05-30 | 2017-04-11 | Apple Inc. | Power level control using power assertion requests |
US10430577B2 (en) | 2014-05-30 | 2019-10-01 | Apple Inc. | Method and apparatus for inter process privilige transfer |
US9396089B2 (en) | 2014-05-30 | 2016-07-19 | Apple Inc. | Activity tracing diagnostic systems and methods |
CN104125335B (en) * | 2014-06-24 | 2017-08-25 | 小米科技有限责任公司 | Right management method, apparatus and system |
US9787685B2 (en) | 2014-06-24 | 2017-10-10 | Xiaomi Inc. | Methods, devices and systems for managing authority |
AU2017376110B2 (en) * | 2016-12-14 | 2020-06-11 | Pivotal Software, Inc. | Distributed validation of credentials |
US10484379B2 (en) * | 2017-03-16 | 2019-11-19 | Motorola Solutions, Inc. | System and method for providing least privilege access in a microservices architecture |
US10742646B2 (en) | 2018-05-10 | 2020-08-11 | Visa International Service Association | Provisioning transferable access tokens |
US11120452B2 (en) * | 2018-11-08 | 2021-09-14 | Capital One Services, Llc | Multi-factor authentication (MFA) arrangements for dynamic virtual transaction token generation via browser extension |
US20240070640A1 (en) * | 2022-08-30 | 2024-02-29 | Ncr Corporation | Systems and methods of encrypting transaction data |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5941947A (en) * | 1995-08-18 | 1999-08-24 | Microsoft Corporation | System and method for controlling access to data entities in a computer network |
US6678733B1 (en) * | 1999-10-26 | 2004-01-13 | At Home Corporation | Method and system for authorizing and authenticating users |
US20050262553A1 (en) * | 1999-03-08 | 2005-11-24 | Bialick William P | Method and system for enforcing access to a computing resource using a licensing attribute certificate |
US8302171B2 (en) * | 2002-08-15 | 2012-10-30 | Activcard | System and method for privilege delegation and control |
Family Cites Families (31)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB9010603D0 (en) | 1990-05-11 | 1990-07-04 | Int Computers Ltd | Access control in a distributed computer system |
USRE36310E (en) * | 1990-06-07 | 1999-09-21 | Kommunedata I/S | Method of transferring data, between computer systems using electronic cards |
GB2247662B (en) * | 1990-08-31 | 1994-11-02 | Instance Ltd David J | Labels and manufacture thereof |
US5309516A (en) * | 1990-12-07 | 1994-05-03 | Hitachi, Ltd. | Group cipher communication method and group cipher communication system |
US5649099A (en) | 1993-06-04 | 1997-07-15 | Xerox Corporation | Method for delegating access rights through executable access control program without delegating access rights not in a specification to any intermediary nor comprising server security |
US5473692A (en) * | 1994-09-07 | 1995-12-05 | Intel Corporation | Roving software license for a hardware agent |
US5694471A (en) * | 1994-08-03 | 1997-12-02 | V-One Corporation | Counterfeit-proof identification card |
FR2725537B1 (en) * | 1994-10-11 | 1996-11-22 | Bull Cp8 | METHOD FOR LOADING A PROTECTED MEMORY AREA OF AN INFORMATION PROCESSING DEVICE AND ASSOCIATED DEVICE |
JP3541522B2 (en) * | 1995-10-09 | 2004-07-14 | 松下電器産業株式会社 | Communication protection system and equipment between devices |
US5602918A (en) * | 1995-12-22 | 1997-02-11 | Virtual Open Network Environment Corp. | Application level security system and method |
US5907620A (en) | 1996-08-23 | 1999-05-25 | Cheyenne Property Trust | Method and apparatus for enforcing the use of cryptography in an international cryptography framework |
KR100213188B1 (en) * | 1996-10-05 | 1999-08-02 | 윤종용 | Apparatus and method for user authentication |
US5918228A (en) | 1997-01-28 | 1999-06-29 | International Business Machines Corporation | Method and apparatus for enabling a web server to impersonate a user of a distributed file system to obtain secure access to supported web documents |
JP3864401B2 (en) * | 1997-04-23 | 2006-12-27 | ソニー株式会社 | Authentication system, electronic device, authentication method, and recording medium |
US6044466A (en) | 1997-11-25 | 2000-03-28 | International Business Machines Corp. | Flexible and dynamic derivation of permissions |
US6279111B1 (en) * | 1998-06-12 | 2001-08-21 | Microsoft Corporation | Security model using restricted tokens |
US6308274B1 (en) | 1998-06-12 | 2001-10-23 | Microsoft Corporation | Least privilege via restricted tokens |
US6192349B1 (en) * | 1998-09-28 | 2001-02-20 | International Business Machines Corporation | Smart card mechanism and method for obtaining electronic tickets for goods services over an open communications link |
AU763847B2 (en) | 1999-04-07 | 2003-07-31 | Swisscom Mobile Ag | Method and system for ordering, loading and using access tickets |
JP2000341263A (en) * | 1999-05-27 | 2000-12-08 | Sony Corp | Information processing device and its method |
US20010020228A1 (en) | 1999-07-09 | 2001-09-06 | International Business Machines Corporation | Umethod, system and program for managing relationships among entities to exchange encryption keys for use in providing access and authorization to resources |
US6389542B1 (en) | 1999-10-27 | 2002-05-14 | Terence T. Flyntz | Multi-level secure computer with token-based access control |
US20020021804A1 (en) * | 2000-02-18 | 2002-02-21 | Ledzius Robert C. | System and method for data encryption |
US7350204B2 (en) * | 2000-07-24 | 2008-03-25 | Microsoft Corporation | Policies for secure software execution |
JP4608749B2 (en) * | 2000-07-24 | 2011-01-12 | ソニー株式会社 | Data processing apparatus, data processing method, license system, and program providing medium |
JP2002101087A (en) * | 2000-09-21 | 2002-04-05 | Hitachi Ltd | Information-preserving system, information moving system and storage medium used for them |
FI20002255A (en) | 2000-10-13 | 2002-04-14 | Nokia Corp | A method for controlling and controlling locks |
WO2002039237A2 (en) * | 2000-11-09 | 2002-05-16 | International Business Machines Corporation | Method and system for web-based cross-domain single-sign-on authentication |
US6842512B2 (en) * | 2000-11-14 | 2005-01-11 | Fuji Xerox Co., Ltd. | Systems and methods for managing electronic communications |
US7131000B2 (en) * | 2001-01-18 | 2006-10-31 | Bradee Robert L | Computer security system |
US7178027B2 (en) * | 2001-03-30 | 2007-02-13 | Capital One-Financial Corp. | System and method for securely copying a cryptographic key |
-
2002
- 2002-08-15 US US10/218,642 patent/US7770212B2/en active Active
-
2003
- 2003-08-08 EP EP03291992.0A patent/EP1389752B1/en not_active Revoked
- 2003-08-08 ES ES11195693.4T patent/ES2440826T3/en not_active Expired - Lifetime
- 2003-08-08 EP EP11195693.4A patent/EP2442204B1/en not_active Expired - Lifetime
-
2010
- 2010-07-14 US US12/804,146 patent/US8302171B2/en not_active Expired - Lifetime
-
2012
- 2012-09-25 US US13/626,015 patent/US20130145442A1/en not_active Abandoned
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5941947A (en) * | 1995-08-18 | 1999-08-24 | Microsoft Corporation | System and method for controlling access to data entities in a computer network |
US20050262553A1 (en) * | 1999-03-08 | 2005-11-24 | Bialick William P | Method and system for enforcing access to a computing resource using a licensing attribute certificate |
US6678733B1 (en) * | 1999-10-26 | 2004-01-13 | At Home Corporation | Method and system for authorizing and authenticating users |
US8302171B2 (en) * | 2002-08-15 | 2012-10-30 | Activcard | System and method for privilege delegation and control |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2017160394A1 (en) * | 2016-03-15 | 2017-09-21 | Intel Corporation | System, apparatus and method for key provisioning delegation |
US10516654B2 (en) | 2016-03-15 | 2019-12-24 | Intel Corporation | System, apparatus and method for key provisioning delegation |
Also Published As
Publication number | Publication date |
---|---|
ES2440826T3 (en) | 2014-01-30 |
US20110093934A1 (en) | 2011-04-21 |
EP1389752A2 (en) | 2004-02-18 |
EP1389752A3 (en) | 2007-10-10 |
EP1389752B1 (en) | 2016-01-13 |
US8302171B2 (en) | 2012-10-30 |
US7770212B2 (en) | 2010-08-03 |
US20040034774A1 (en) | 2004-02-19 |
EP2442204A1 (en) | 2012-04-18 |
EP2442204B1 (en) | 2013-10-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8302171B2 (en) | System and method for privilege delegation and control | |
US9160732B2 (en) | System and methods for online authentication | |
US7890767B2 (en) | Virtual smart card system and method | |
WO2018214133A1 (en) | Method, device and system for fido authentication based on blockchain | |
US9331991B2 (en) | Authenticating a client using linked authentication credentials | |
US7150038B1 (en) | Facilitating single sign-on by using authenticated code to access a password store | |
US8499147B2 (en) | Account management system, root-account management apparatus, derived-account management apparatus, and program | |
JP2002501218A (en) | Client-side public key authentication method and device using short-lived certificate | |
JP2006040307A (en) | Smart card | |
EP2957064B1 (en) | Method of privacy-preserving proof of reliability between three communicating parties | |
CN114666168B (en) | Decentralized identity certificate verification method and device, and electronic equipment | |
US20060129815A1 (en) | Generation of identities and authentication thereof | |
CN116112242B (en) | Unified safety authentication method and system for power regulation and control system | |
KR102288445B1 (en) | On-boarding method, apparatus and program of authentication module for organization |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: ACTIVCARD, FRANCE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:LE SAINT, ERIC F.;REEL/FRAME:029600/0677 Effective date: 20020625 |
|
AS | Assignment |
Owner name: ACTIVCARD S.A., FRANCE Free format text: ATTESTATION OF FULL LEGAL NAME OF ENTITY;ASSIGNOR:ACTIVCARD;REEL/FRAME:031520/0232 Effective date: 20131031 |
|
AS | Assignment |
Owner name: ACTIVIDENTITY EUROPE SA, FRANCE Free format text: CHANGE OF NAME;ASSIGNOR:ACTIVCARD S.A.;REEL/FRAME:031674/0407 Effective date: 19890329 |
|
AS | Assignment |
Owner name: ASSA ABLOY AB, SWEDEN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ACTIVIDENTITY EUROPE S.A.;REEL/FRAME:032403/0956 Effective date: 20131217 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |