Secure system and method for enforcement of privacy policy and protection of confidentiality

• US 7,401,352 B2
• Filed: 08/30/2002
• Issued: 07/15/2008
• Est. Priority Date: 08/30/2002
• Status: Active Grant

• Current Assignee: Slingshot IOT LLC
• Original Assignee: International Business Machines Corporation
• Inventors: Singh, Moninder, Tang, Jung-Mu, Tresser, Charles P., Duri, Sastry S., Gruteser, Marco O., Liu, Xuan, Moskowitz, Paul A., Perez, Ronald, Schonberg, Edith G.
• Primary Examiner(s): Barron, Jr., Gilberto
• Assistant Examiner(s): Sandoval, Kristin D
• Application Number:
  US10/233,339
• Publication Number:
  US 20040054918A1
• Time in Patent Office: 2,146 Days
• Field of Search: 705/43, 705/44, 705/64, 705/74, 726/1
• US Class Current: 726/1
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/3829 involving key management
• CPC Class Codes: G06Q 20/383 Anonymous user system
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 2209/805 Lightweight hardware, e.g. radio-frequency identification [RFID] or sensor
• CPC Class Codes: H04L 2209/84 Vehicles
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/104 Grouping of entities
• CPC Class Codes: H04L 9/321 involving a third party or a trusted authority
• CPC Class Codes: H04L 9/3247 involving digital signatures
• CPC Class Codes: H04L 9/3263 involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements network architectures or network communication protocols for supporting authentication of entities using certificates in a packet data network H04L63/0823

Abstract

The invention includes various systems, architectures, frameworks and methodologies that can securely enforce a privacy policy. A method is include for securely guaranteeing a privacy policy between two enterprises, comprising: creating a message at a first enterprise, wherein the message includes a request for data concerning a third party and a privacy policy of the first enterprise; signing and certifying the message that the first enterprise has a tamper-proof system with a privacy rules engine and that the privacy policy of the first entity will be enforced by the privacy rules engine of the first enterprise; sending the message to a second enterprise; and running a privacy rules engine at the second enterprise to compare the privacy policy of the first enterprise with a set of privacy rules for the third party.

Claims

1. A method for securely guaranteeing a privacy policy between two enterprises, comprising:

creating a message at a first enterprise, wherein the message includes a request for data concerning a specifically identified third party for data stored by a second enterprise and a privacy policy of the first enterprise;

signing and certifying the message that the first enterprise has a tamper-proof system with a privacy rules engine and that the privacy policy of the first enterprise will be enforced by the privacy rules engine of the first enterprise;

sending the message to the second enterprise; and

running a privacy rules engine at the second enterprise to compare the privacy policy of the first enterprise with a set of privacy rules for the third party, wherein in response to a match between the privacy policy of the first enterprise and the set of privacy rules for the third party;

encrypting the data requested by the first enterprise; and

sending the encrypted requested data from the second enterprise to the first enterprise.

2. The method of claim 1, wherein:

the certifying step includes the preliminary act of registering the first enterprise with a trusted agency; and

the second enterprise checks the trusted agency to verify the certification.

3. The method of claim 1, wherein both the first and second enterprises include a secure co-processor.

4. The method of claim 1, wherein both the first and second enterprises each includes a hardware device built with a cryptographic identifier that allows the hardware device of the first enterprise and the hardware device of the second enterprise to recognize and certify each other.

5. The method of claim 1, wherein the first enterprise comprises a merchant system, the second enterprise comprises a financial institution system, and the data comprises credit card information regarding an individual.

6. The method of claim 1, wherein the first enterprise comprises a service provider, the second enterprise comprises a vehicle, and the data comprises information derived from the vehicle.

7. The method of claim 6 wherein the information comprises identification information and one of location and diagnostic information.

8. A method for securely guaranteeing a privacy policy between two enterprises, comprising:

creating a message at a first enterprise, wherein the message includes a request for data concerning a specifically identified third party for data stored by a second enterprise and a privacy policy of the first enterprise;

signing and certifying the message that the first enterprise has a tamper-proof system with a privacy rules engine and that the privacy policy of the first enterprise will be enforced by the privacy rules engine of the first enterprise, wherein;

the certifying step includes the preliminary act of registering the first enterprise with a trusted agency; and

the second enterprise checks the trusted agency to verify the certification;

sending the message to the second enterprise; and

running a privacy rules engine at the second enterprise to compare the privacy policy of the first enterprise with a set of privacy rules for the third party.

9. A method for securely guaranteeing a privacy policy between two enterprises, comprising:

creating a message at a first enterprise, wherein the message includes a request for data concerning a specifically identified third party for data stored by a second enterprise and a privacy policy of the first enterprise;

signing and certifying the message that the first enterprise has a tamper-proof system with a privacy rules engine and that the privacy policy of the first enterprise will be enforced by the privacy rules engine of the first enterprise;

sending the message to the second enterprise; and

running a privacy rules engine at the second enterprise to compare the privacy policy of the first enterprise with a set of privacy rules for the third party. wherein both the first and second enterprises each includes a hardware device built with a cryptographic identifier that allows the hardware device of the first enterprise and the hardware device of the second enterprise to recognize and certify each other.