Method and system for auditing transaction data from database operations

• US 9,535,971 B2
• Filed: 08/09/2013
• Issued: 01/03/2017
• Est. Priority Date: 06/15/2009
• Status: Active Grant

• Current Assignee: VeriSign, Inc.
• Original Assignee: VeriSign, Inc.
• Inventors: Essawi, Tarik R., Chigurupati, Nageswararao
• Primary Examiner(s): Morrison, Jay
• Application Number:
  US13/963,339
• Publication Number:
  US 20140074772A1
• Time in Patent Office: 1,243 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 16/21 Design, administration or maintenance of databases
• CPC Class Codes: G06F 16/283 Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP

Abstract

A method for validating SRS registry transaction data includes receiving OLTP transaction data from a first database, parsing the OLTP transaction data, and comparing the parsed OLTP transaction data to one or more of a set of profiles. Each of the one or more of the set of profiles includes metadata in XML files. The method also includes caching the parsed OLTP transaction data in a first data cache, receiving log data associated with the OLTP transaction data; and caching the log data in a second data cache. The method further includes correlating the parsed transaction data cached in the first data cache with the log data cached in the second data cache.

Claims

1. A method, implemented by at least one processor, for validating domain name system (DNS) registry transaction data, the method comprising:

receiving, by the at least one processor, transaction data associated with a DNS registry database, wherein the transaction data is associated with DNS registry operations comprising at least one of;

adding an Internet domain name, deleting an Internet domain name, renewing an Internet domain name, modifying an Internet domain name, restoring an Internet domain name, transferring an Internet domain name, adding an Internet domain name server, deleting an Internet domain name server, or modifying an Internet domain name server;

obtaining one or more profiles from a profile database communicatively coupled with the DNS registry, wherein the one or more profiles comprise metadata describing one or more DNS registry operations comprising at least;

adding an Internet domain name, deleting an Internet domain name, renewing an Internet domain name, modifying an Internet domain name, restoring an Internet domain name, transferring an Internet domain name, adding an Internet domain name server, deleting an Internet domain name server, and modifying an Internet domain name server;

comparing, by the processor, the transaction data to the one or more profiles, wherein an alert is generated for transactions that do not match at least one of the one or more profiles; and

determining, based on the one or more profiles, whether the transaction data is supposed to correlate with log data, wherein, for transaction data that is not supposed to correlate with log data, providing an indication that the transaction data is valid, and wherein, for transaction data that is supposed to correlate with log data;

receiving, by the processor, log data associated with the transaction data; and

correlating the transaction data with the log data associated with the transaction data, wherein a chain of custody is established for transaction data that correlates with the log data associated with the transaction data, and wherein an alert is generated for transaction data that is supposed to correlate with log data but does not correlate with the log data associated with the transaction data, indicating that at least one transaction represented by the transaction data is potentially invalid.

2. The method of claim 1, wherein the comparing comprises:

generating a key derived from the transaction data; and

retrieving a corresponding profile using the key.

3. The method of claim 1, further comprising storing, in association with keys, profiles for transactions that are not supposed to correlate with log data.

4. The method of claim 1, wherein each of the one or more profiles comprise an indication of whether transaction data is supposed to correlate with log data.

5. The method of claim 1, further comprising caching the one or more profiles in a data cache.

6. The method of claim 1, wherein the one or more profiles are in an XML format.

7. The method of claim 1 further comprising:

determining that the transaction data does not match at least one of the one or more profiles; and

generating an alert indicating a validation error.

8. The method of claim 7 wherein generating an alert comprises generating at least one report including the potential validation error.

9. The method of claim 8 wherein the at least one report comprises a detail report.

10. The method of claim 1 wherein the transaction data comprises OTLP transaction data.

11. A system for validating domain name system (DNS) registry transaction data, the system comprising:

at least one electronic processor; and

at least one persistent memory storing instructions which, when executed by the at least one electronic processor, cause the at least one processor to;

receive transaction data associated with a DNS registry database, wherein the transaction data is associated with DNS registry operations comprising at least one of;

adding an Internet domain name, deleting an Internet domain name, renewing an Internet domain name, modifying an Internet domain name, restoring an Internet domain name, transferring an Internet domain name, adding an Internet domain name server, deleting an Internet domain name server, or modifying an Internet domain name server;

obtain one or more profiles from a profile database communicatively coupled with the DNS registry, wherein the one or more profiles comprise metadata describing one or more DNS registry operations comprising at least;

adding an Internet domain name, deleting an Internet domain name, renewing an Internet domain name, modifying an Internet domain name, restoring an Internet domain name, transferring an Internet domain name, adding an Internet domain name server, deleting an Internet domain name server, and modifying an Internet domain name server;

compare the transaction data to the one or more profiles, wherein an alert is generated for transactions that do not match at least one of the one or more profiles; and

determine, based on the one or more profiles, whether the transaction data is supposed to correlate with log data, wherein, for transaction data that is not supposed to correlate with log data, provide an indication that the transaction data is valid, and wherein for transaction data that is supposed to correlate with log data, then;

receive log data associated with the transaction data; and

correlate the transaction data with the log data associated with the transaction data, wherein a chain of custody is established for transaction data that correlates with the log data associated with the transaction data, and wherein an alert is generated for transaction data that is supposed to correlate with log data but does not correlate with the log data associated with the transaction data, indicating that at least one transaction represented by the transaction data is potentially invalid.

12. The system of claim 11, wherein the at least one processor is further configured to compare the transaction data to one or more profiles by:

generating a key derived from the transaction data; and

retrieving a corresponding profile using the key.

13. The system of claim 11, in the at least one processor is further configured to store, in association with keys, profiles for transactions that are not supposed to correlate with log data.

14. The system of claim 11, wherein each of the one or more profiles comprise an indication of whether transaction data is supposed to correlate with log data.

15. The system of claim 11, wherein the at least one processor is further configured to cache the one or more profiles in a data cache.

16. The system of claim 11, wherein the one or more profiles are in an XML format.

17. The system of claim 11, wherein the at least one processor is further configured to:

generate an alert indicating a validation error in response to determining that the transaction data does not match at least one of the one or more profiles.

18. The system of claim 17 wherein generating an alert comprises generating at least one report including the potential validation error.

19. The system of claim 18 wherein the at least one report comprises a detail report.

20. The system of claim 11 wherein the transaction data comprises OTLP transaction data.