SYSTEM FOR SECURELY PERFORMING A TRANSACTION

• US 20130061290A1
• Filed: 05/14/2012
• Published: 03/07/2013
• Est. Priority Date: 09/06/2011
• Status: Abandoned Application

• Current Assignee: Avago Technologies General IP PTE Limited (Broadcom, Inc.)
• Original Assignee: Avago Technologies General IP PTE Limited (Broadcom, Inc.)
• Inventors: Mendel, Jacob, Potievsky, Alexander
• Application Number:
  US13/470,704
• Publication Number:
  US 20130061290A1
• Time in Patent Office: Days
• US Class Current: 726/4
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules

Abstract

A system and method for performing a transaction are described. A transaction request to perform a transaction is received. Authorization information necessary to perform the transaction is gathered and stored in a secure memory. The gathered authorization information is verified. A final command to perform the transaction is received. When the final command is received, the transaction is performed and the stored authorization information in the secure memory is erased.

Claims

1. A system for performing a transaction, comprising:

a transaction module configured to gather authorization information necessary to perform a transaction, the transaction module configured to perform the transaction when a final instruction is received;

a secure memory configured to store the gathered authorization information; and

a transaction monitor configured monitor the transaction module and detect the received final instruction, where the transaction monitor erases the gathered authorization information from the secure memory when the received final instruction is detected.

2. The system of claim 1, further comprising a session counter configured to track a transaction parameter of the transaction, where the transaction monitor is configured to monitor the session counter.

3. The system of claim 2, where the session counter is configured to track a duration of the transaction, where the transaction monitor erases the gathered authorization information from the secure memory when the duration of the transaction exceeds a maximum duration threshold.

4. The system of claim 3, where session counter is configured to adjust the maximum duration threshold based on a type of the transaction.

5. The system of claim 2, where the session counter is configured to track an order of actions of the transaction, where the transaction monitor erases the gathered authorization information from the secure memory when the tracked order of actions does not match a required order of actions.

6. The system of claim 1, where the secure memory is configured to store the gathered authorized information in a first format and in a second format.

7. The system of claim 6, where the secure memory is configured to store the gathered authorized information in the first format at a first location, and the gathered authorized information in the second format at a second location.

8. The system of claim 6, where the first format represents an inverse of the second format.

9. A method of performing a transaction, comprising:

receiving a transaction request to perform a transaction;

gathering authorization information necessary to perform the transaction;

storing the authorization information in a secure memory;

receiving a final command to perform the transaction; and

erasing the stored authorization information in the secure memory when the final command is received.

10. The method of claim 9, further comprising:

performing the transaction when the final command is received.

11. The method of claim 9, further comprising:

comparing the gathered authorization information with expected authorization information; and

performing a security action when the gathered authorization information does not match the expected authorization information.

12. The method of claim 11, where the security action comprises erasing the stored authorization information in the secure memory.

13. The method of claim 9, where the authorization information includes a transaction key.

14. The method of claim 13, further comprising:

verifying the transaction key is valid;

erasing the stored authorization information in the secure memory when the transaction key is not valid; and

performing the transaction when the final command is received and the transaction key is valid.

15. The method of claim 13, where the transaction key includes a code and a piece of personal identification information.

16. A method of performing a transaction, comprising:

storing authorization information necessary to perform the transaction in a secure memory;

timing a duration of the transaction with a session counter;

comparing the timed duration to a maximum duration threshold;

tracking an order of operations of the transaction with the session counter;

comparing the tracked order of operations to a required order of operations; and

erasing the stored authorization information from the secure memory when the timed duration exceeds the maximum duration threshold or the tracked order of operations does not match the required order of operation.

17. The method of claim 16, further comprising performing an integrity check on the secure memory prior to storing the authorization information.

18. The method of claim 16, further comprising:

receiving a final command to perform the transaction; and

erasing the stored authorization information from the secure memory when the final command is received.

19. The method of claim 18, further comprising performing the transaction when the timed duration does not exceed the maximum duration threshold, the tracked order of operations matches the required order of operation, and the final command is received.

20. The method of claim 16, further comprising:

determining a type of the transaction; and

setting the maximum duration threshold based on the determined type of the transaction.