# US 2005/0097149 A1 · Data audit system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2005/0097149 A1
- Document ID: US20050097149A1
- Status: Published application
- Kind: A1
- Application number: 10/702,127
- Filed: 2003-11-05
- Published: 2005-05-05
- Earliest claimed: 2003-11-05
- Assignees: Lumigent Technologies, Inc.
- Inventors: Lev Vaitzblit; Jonathan Jesse; Jason Orendorff; Stephen Ng; Murray Mazer
- Web page: https://patentgrep.com/patent/US20050097149A1

## CPC

- G06F 21/6227: {where protection concerns the structure of data, e.g. records, types, queries}
- G06F 16/2358: {Change logging, detection, and notification (replication G06F16/27)}
- G06F 2221/2101: Auditing as a secondary aspect
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Described is a database audit system used to monitor, and optionally alert on database activity, providing a complete record of access to data and database structure. The data audit system may also provide an audit trail of data accesses and changes to database schema and permissions. A database audit may be performed by collecting data from database transaction logs and traces, exporting the collected data into a repository, and analyzing the data in the repository to create data audit reports and to provide data audit browsing capabilities.

## Claims

### Claim 1

A database audit process for a database which maintains a transaction log, said process comprising:
maintaining a trace of database activities including session activities after session establishment; and
collecting information from the transaction log and the trace;

### Claim 2 (depends on 1)

The database audit process of claim 1, wherein the audit trail of data modifications is constructed based on the information from the transaction log.

### Claim 3 (depends on 2)

The database audit process of claim 2, wherein collecting information from the transaction log further comprises traversing records using rollback techniques.

### Claim 4 (depends on 3)

The database audit process of claim 3, wherein checkpoint markers are used to keep track of the information collected from the transaction log.

### Claim 5 (depends on 1)

The database audit process of claim 1, further comprising:
correlating the transaction log and the trace data.

### Claim 6 (depends on 1)

The database audit process of claim 1, further comprising:
generating an audit trail report.

### Claim 7 (depends on 6)

The database audit process of claim 6, wherein the audit trail report conforms to an industry auditing standard.

### Claim 8 (depends on 1)

The database audit process of claim 1, wherein collecting the trace data further comprises collecting SELECT commands.

### Claim 9 (depends on 8)

The database audit process of claim 8, wherein collecting the trace data further comprises correlating SPIDs from SELECT commands with SPIDs gathered from other commands.

### Claim 10 (depends on 8)

The database audit process of claim 8, wherein the SELECT commands are stored in a file between collections.

### Claim 11 (depends on 8)

The database audit process of claim 8, further comprising:
determining data viewed by a SELECT command.

### Claim 12 (depends on 11)

The database audit process of claim 11, wherein determining data viewed by a SELECT command further comprises analyzing a WHERE clause.

### Claim 13 (depends on 11)

The database audit process of claim 11, wherein determining data viewed by a SELECT command further comprises issuing an augmented SELECT command to the database.

### Claim 14 (depends on 1)

The database audit process of claim 1, wherein collecting transaction log and trace information further comprises ensuring that there are no information gaps or overlaps.

### Claim 15 (depends on 14)

The database audit process of claim 14, further comprising:
maintaining a collection table with records about information collections.

### Claim 16 (depends on 15)

The database audit process of claim 15, wherein collecting the transaction log and trace information further comprises collecting the trace information on a continuous basis.

### Claim 17 (depends on 14)

The database audit process of claim 14, wherein the step of collecting transaction log and trace information is performed periodically or in response to a command.

### Claim 18 (depends on 17)

The database audit process of claim 17, wherein database checkpoint markers are used to denote boundaries of a collection process.

### Claim 19 (depends on 1)

The database audit process of claim 1, further comprising:
generating an alert in response to a command executed on the database.

### Claim 20 (depends on 19)

The database audit process of claim 19, wherein the command executed on the database is one of: a database schema changing command and a database structure changing command.

### Claim 21 (depends on 19)

The database audit process of claim 19, wherein generating an alert further comprises generating the alert based on the trace information.

### Claim 22 (depends on 1)

The database audit process of claim 1, further comprising collecting audit information for a second database.

### Claim 23 (depends on 22)

The database audit process of claim 22, wherein the database and the second database are of different type.

### Claim 24 (depends on 23)

The database audit process of claim 23, further comprising:
capturing the audit trail of accesses and modifications of both databases in a repository.

### Claim 25 (depends on 1)

The database audit of claim 1, further comprising:
collecting information indicative of database structure changes.

### Claim 26 (depends on 25)

The database audit process of claim 25, further comprising:
collecting information indicative of system activity.

### Claim 27 (depends on 25)

The database audit process of claim 25, wherein the information indicative of database structure changes comprises data definition language commands.

### Claim 28 (depends on 1)

The database audit process of claim 1, further comprising:
providing a user interface for defining logical keys for the database.

### Claim 29 (depends on 28)

The database audit process of claim 28, further comprising:
generating a report of data accesses based on the logical keys.

### Claim 30 (depends on 1)

The database audit process of claim 1, further comprising:
exporting the collected information into a repository.

### Claim 31 (depends on 30)

The database audit process of claim 30, further comprising:
creating an audit trail of data modifications.

### Claim 32 (depends on 30)

The database audit process of claim 30, further comprising:
providing a user interface for browsing a record revision history for a particular record selected by a user.

### Claim 33 (depends on 30)

The database audit process of claim 30, further comprising:
providing a user interface for browsing a history of data modifications by a particular user.

### Claim 34 (depends on 30)

The database audit process of claim 30, wherein exporting the collected information further comprises maintaining a collection table with records about information transfers.

### Claim 35 (depends on 30)

The database audit process of claim 30, further comprising:
providing a user interface for browsing a record revision history for a particular record selected by a user.

### Claim 36 (depends on 30)

The database audit process of claim 30, further comprising:
generating a report of data accesses.

### Claim 37 (depends on 30)

The database audit process of claim 30, further comprising:
generating a report of data modifications.

### Claim 38 (depends on 30)

The database audit process of claim 30, further comprising:
archiving collected transaction log and trace information.

### Claim 39 (depends on 30)

The database audit process of claim 30, further comprising:
analyzing information in the repository and reporting thereon.

### Claim 40 (depends on 39)

The database audit process of claim 39, further comprising:
analyzing data access patterns.

### Claim 41

A method of collecting audit trail information for a database which maintains a database transaction log about database accesses and modifications, said method comprising:
maintaining a trace of database activities including session activities after session establishment; and
collecting information from the transaction log and trace.

### Claim 42 (depends on 41)

The method of collecting audit trail information of claim 41, further comprising:
using database checkpoint markers as delineation for information collection.

### Claim 43 (depends on 42)

The method of collecting audit trail information of claim 42, further comprising:
maintaining a record of collection activities.

### Claim 44 (depends on 43)

The method of collecting audit trail information of claim 43, further comprising:
collecting information not collected during a previous collection process, as determined from the record of the collection activities.

### Claim 45

A database audit system for a database maintaining a transaction log, said system comprising:
a trace of database activities including session activities after session establishment; and
a data collection agent collecting information from the transaction log and the trace.

### Claim 46 (depends on 45)

The database audit system of claim 45, further comprising:
a repository agent receiving collected information from the data collection agent.

### Claim 47 (depends on 46)

The database audit system of claim 46, further comprising:
a data analyzer creating an audit trail of data modifications.

### Claim 48 (depends on 47)

The database audit system of claim 47, further comprising:
a user interface for browsing a record revision history for a particular record selected by a user.

### Claim 49 (depends on 47)

The database audit system of claim 47, further comprising:
a user interface for browsing a history of data modifications by a particular user.

### Claim 50 (depends on 45)

The database audit system of claim 45, wherein the trace information further comprises data about SELECT commands.

### Claim 51 (depends on 45)

The database audit system of claim 45, wherein the trace information further comprises information about commands relevant to session establishment.

### Claim 52 (depends on 50)

The database audit system of claim 50, wherein the collection agent correlates the information about commands relevant to session establishments with information collected from the transaction log.

### Claim 53

A database audit system for a database maintaining a transaction log, said system comprising:
means for maintaining a trace of database activities not available through the transaction log; and
means for collecting information from the transaction log and trace.

### Claim 54 (depends on 53)

The database audit system of claim 53, further comprising:
means for analyzing the collected information and reporting thereon.

### Claim 55

A data collection agent for collecting information about database accesses and modifications, said collection agent comprising:
a collector collecting information from a database transaction log;
a collector collecting database trace information; and
a communicator transferring the database transaction log information and the database trace information to a repository.

### Claim 56 (depends on 54)

The data collection agent of claim 54, wherein the collection agent sends alerts in response to predetermined events.

### Claim 57 (depends on 54)

The data collection agent of claim 54, wherein the communicator ensures reliable information transfer.

### Claim 58

A data collection agent for collecting information about database accesses, said collection agent comprising:
means for collecting information from a database transaction log; and
means for collecting database trace information including session information after session establishment.

### Claim 59 (depends on 58)

The data collection agent of claim 58, further comprising:
means for transferring the database transaction log data and the database trace data to a repository.

### Claim 60 (depends on 58)

The data collection agent of claim 58, further comprising:
means for sending alerts in response to predetermined events.

### Claim 61 (depends on 58)

The data collection agent of claim 58, wherein means for transferring the database transaction log and trace information further comprise means for ensuring a reliable transfer.

### Claim 62

The method for collecting information by a data collection agent about database accesses, said method comprising:
collecting information from a database transaction log;
collecting database trace information including session information after session establishment.

### Claim 63 (depends on 62)

The method of collecting information of claim 62, further comprising:
transferring the database transaction log data and the database trace data to a repository.

### Claim 64 (depends on 62)

The method of claim 62, further comprising:
sending alerts in response to predetermined events.

### Claim 65

A database audit system for multiple databases, each maintaining a transaction log, said system comprising:
a trace of database activities including session activities after session establishment for each database; and
a data collection agent associated with each database, the agent collecting information from an associated transaction log and an associated trace.

### Claim 66 (depends on 65)

The database audit system of claim 65, wherein at least two databases of the multiple databases are of different type.

### Claim 67 (depends on 65)

The database audit system of claim 65, further comprising:
a repository storing database audit information.

### Claim 68 (depends on 67)

The database audit system of claim 67, further comprising:
a repository agent receiving collected information from data collection agents.

### Claim 69 (depends on 67)

The database audit system of claim 67, further comprising:
a data analyzer creating an audit trail of data modifications.

### Claim 70 (depends on 67)

The database audit system of claim 67, wherein audit information from the multiple databases is correlated into a coherent data set.
