Method and system for auditing transaction data from database operations

• US 8,510,263 B2
• Filed: 06/15/2009
• Issued: 08/13/2013
• 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): Btit, Jacob F
• Assistant Examiner(s): Hocker, John P
• Application Number:
  US12/484,978
• Publication Number:
  US 20100318858A1
• Time in Patent Office: 1,520 Days
• Field of Search: 707/607, 707/703
• US Class Current: 707/607
• 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 a processor, for validating Shared Registration System (SRS) registry transaction data, the method comprising:

receiving, by the processor, online transaction processing (OLTP) transaction data associated with an SRS registry database, wherein the transaction data is associated with SRS 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;

parsing, by the processor, the OLTP transaction data;

comparing, by the processor, the parsed OLTP transaction data to one or more profiles, the profiles comprising metadata describing one or more SRS registry operations, wherein each profile corresponds to at least one known SRS registry operation associated with a known code path, wherein an alert is generated if an OLTP transaction does not match at least one of the one or more profiles;

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

parsing, by the processor, the log data associated with the OLTP transaction data; and

verifying, by the processor, that transactions represented by the OLTP transaction data came from a known source by correlating the parsed OLTP transaction data with the parsed log data,

wherein a chain of custody is established if the parsed OLTP transaction data correlates with the parsed log data, and

wherein an alert is generated if the parsed OLTP transaction data does not correlate with the parsed log data, indicating that at least one transaction represented by the OLTP transaction data did not come from a known source.

2. The method of claim 1 wherein generating an alert comprises generating at least one summary report.

3. The method of claim 2 wherein the at least one summary report comprises a detail report.

4. The method of claim 1 wherein the SRS registry database comprises a domain name registry database.

5. The method of claim 1 wherein the one or more profiles include profiles for at least one of adding a domain name, deleting a domain name, or renewing a domain name.

6. The method of claim 1 wherein the one or more profiles include profiles for at least one of adding a domain name server, deleting a domain name server, or modifying a domain name server.

7. A non-transitory computer-readable medium, for validating transaction data associated with a Shared Registration Registry (SRS) registry, the medium including instructions that when executed by a processor cause the processor to perform operations comprising:

receiving, by the processor, online transaction processing (OLTP) associated with an SRS registry, wherein the transaction data is associated with SRS 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;

parsing, by the processor, the OLTP transaction data;

comparing, by the processor, the parsed OLTP transaction data to one or more profiles, the profiles comprising metadata describing one or more SRS registry operations, wherein each profile corresponds to at least one known SRS registry operation associated with a known code path, wherein an alert is generated if a transaction does not match at least one of the one or more profiles;

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

parsing, by the processor, the log data associated with the OLTP transaction data; and

verifying, by the processor, that transactions represented by the OLTP transaction data came from a known source by correlating the parsed OLTP transaction data with the parsed log data,

wherein a chain of custody is established if the parsed transaction data correlates with the parsed log data, and

wherein an alert is generated if the parsed transaction data does not correlate with the parsed log data, indicating that at least one transaction represented by the transaction data did not come from a known source.

8. The non-transitory computer-readable medium of claim 7 wherein the metadata is provided in an XML file.

9. The non-transitory computer-readable medium of claim 7, the operations further comprising caching the parsed OLTP transaction data prior to correlating the parsed transaction data with the log data.

10. The non-transitory computer-readable medium of claim 7, the operations further comprising caching the log data prior to correlating the parsed OLTP transaction data with the log data.

11. The non-transitory computer-readable medium of claim 7, the operations further comprising determining a validation error.

12. The non-transitory computer-readable medium of claim 7, the operations further comprising providing at least one report.

13. A system for validating transaction data associated with a Shared Registration System (SRS) registry database with transaction log files stored in a transaction log database, the system comprising:

a processor; and

a memory communicatively connected to the processor and storing instructions executable by the processor to perform functions of;

a database reader operable to receive online transaction processing (OLTP) transaction data from the SRS registry database and parse the OLTP transaction data, wherein the transaction data is associated with SRS 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;

a database data validator coupled to the database reader and operable to compare the parsed OLTP transaction data with one or more profiles, the profiles comprising metadata describing one or more SRS registry operations, wherein each profile corresponds to at least one known SRS registry operation associated with a known code path, wherein an alert is generated if an OLTP transaction does not match at least one of the one or more profiles;

a transaction log file reader operable to receive a transaction log file from the transaction log database;

a transaction log file parser coupled to the transaction log file reader to parse the received transaction log file; and

a data correlator coupled to the database data validator and the transaction log file reader and operable to verify that transactions represented by the OLTP transaction data came from a known source by correlating the parsed OLTP transaction data with the parsed transaction log file,

wherein a chain of custody is established if the parsed OLTP transaction data correlates with the parsed transaction log file, and

wherein an alert is generated if the parsed OLTP transaction data does not correlate with the parsed transaction log file, indicating that at least one transaction represented by the OLTP transaction data did not come from a known source.

14. The system of claim 13 wherein the metadata is provided in XML files.

15. The system of claim 13 further comprising a first data cache coupled to the database data validator.

16. The system of claim 13 further comprising a second data cache coupled to the transaction log file reader.

17. The system of claim 13 further comprising a report generator coupled to the data correlator.