Controlling Exposure of Sensitive Data and Operation Using Process Bound Security Tokens in Cloud Computing Environment

• US 20170026179A1
• Filed: 10/05/2016
• Published: 01/26/2017
• Est. Priority Date: 01/21/2013
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Park, Ki H., Chang, John Y-C., Chao, Ching-Yun, Chiu, Bertrand Be-Chung
• Granted Patent: US 9,712,322 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0815 providing single-sign-on or federations
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 65/61 for supporting one-way streaming services, e.g. Internet radio
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 9/3213 using tickets or tokens, e.g. Kerberos network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807
• CPC Class Codes: H04L 9/3247 involving digital signatures

Abstract

Exposure of sensitive information to users is controlled using a first security token containing user identity and user credentials to represent the user who requests services, and a second security token containing two other identities, one identifying the token issuer and the other identifying the owning process. When requesting services, the token-owning process sends a security token to indicate who is making the request, and uses its key to digitally sign the request. The token-owning process signs the request to indicate that it endorses the request. A receiving server accepts a request if (1) the token-owning process endorses the request by signing the request; (2) the token is valid (token is signed by its issuer and the digital signature is verified and unexpired); (3) user entity, which can be a real user or a deployment or a server process, that is represented by the token has the authorization to access the specified resources; and (4) the token-owning process is authorized to endorse the user entity represented by the token to access the specified resources.

Claims

1. A method for controlling exposure of sensitive data using process-bound security tokens comprising:

receiving, by a downstream server process, from an owning process a first request message for a separate requester to access or communicate to a targeted server, wherein the request message is signed with a first token issuer cryptographic key a first security token that is owned by the owning process;

endorsing, by the downstream server process, the first request message by attaching a second security token representing the downstream server, wherein the second security token is signed by a second token issuer cryptographic key;

sending, by the downstream server, the endorsed first request message to the targeted server;

receiving, by the downstream server, from the targeted server a user token;

forwarding, by the downstream server process, the user token to the owning process; and

responsive to receiving, by the downstream server process, one or more additional request messages with the user token, endorsing and forwarding each additional request message to the targeted server;

thereby binding the plurality of request messages together through endorsement by the downstream server process.

2. The method as set forth in claim 1 wherein the separate requester comprises a user device.

3. The method as set forth in claim 1 wherein the separate requester comprises a user process.

4. The method as set forth in claim 3 wherein the second security token comprises an identification of the token issuer, and comprises an identification of the owning process.

5. A computer program product for controlling exposure of sensitive data using process-bound security tokens comprising:

a computer-readable storage memory which is not a propagating signal per se; and

program instructions embodied by the computer-readable storage memory which cause one or more processors to, when executed, perform the steps of;

receiving, by a downstream server process, from an owning process a first request message for a separate requester to access or communicate to a targeted server, wherein the request message is signed with a first token issuer cryptographic key a first security token that is owned by the owning process;

endorsing, by the downstream server process, the first request message by attaching a second security token representing the downstream server, wherein the second security token is signed by a second token issuer cryptographic key;

sending, by the downstream server, the endorsed first request message to the targeted server;

receiving, by the downstream server, from the targeted server a user token;

forwarding, by the downstream server process, the user token to the owning process; and

responsive to receiving, by the downstream server process, one or more additional request messages with the user token, endorsing and forwarding each additional request message to the targeted server;

thereby binding the plurality of request messages together through endorsement by the downstream server process.

6. The computer program product as set forth in claim 5 wherein the separate requester comprises a user device.

7. The computer program product as set forth in claim 5 wherein the separate requester comprises a user process.

8. The computer program product as set forth in claim 7 wherein the second security token comprises an identification of the token issuer, and comprises an identification of the owning process.

9. A system for controlling exposure of sensitive data using process-bound security tokens comprising:

a computing system having a processor; and

a computer-readable storage memory which is not a propagating signal per se;

program instructions embodied by the computer-readable storage memory which cause the processor to, when executed, perform the steps of;

receiving, by a downstream server process, from an owning process a first request message for a separate requester to access or communicate to a targeted server, wherein the request message is signed with a first token issuer cryptographic key a first security token that is owned by the owning process;

endorsing, by the downstream server process, the first request message by attaching a second security token representing the downstream server, wherein the second security token is signed by a second token issuer cryptographic key;

sending, by the downstream server, the endorsed first request message to the targeted server;

receiving, by the downstream server, from the targeted server a user token;

forwarding, by the downstream server process, the user token to the owning process; and

responsive to receiving, by the downstream server process, one or more additional request messages with the user token, endorsing and forwarding each additional request message to the targeted server;

thereby binding the plurality of request messages together through endorsement by the downstream server process.

10. The system as set forth in claim 9 wherein the separate requester comprises a user device.

11. The system as set forth in claim 9 wherein the separate requester comprises a user process.

12. The system as set forth in claim 11 wherein the second security token comprises an identification of the token issuer, and comprises an identification of the owning process.