# US 2004/0024736 A1 · Method and apparatus for monitoring a database system

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

- Number: US 2004/0024736 A1
- Document ID: US20040024736A1
- Status: Published application
- Kind: A1
- Application number: 10/375,691
- Filed: 2003-02-24
- Published: 2004-02-05
- Earliest claimed: 2002-02-22
- Assignees: IPLocks, Inc.
- Inventors: Akio Sakamoto; Amarnath Mukherjee; Frank Sudia; Seshan S. Raj
- Web page: https://patentgrep.com/patent/US20040024736A1

## CPC

- G06F 21/55: Detecting local intrusion or implementing counter-measures
- G06F 16/2365: {Ensuring data consistency and integrity}
- Y10S 707/99931: Database or file accessing
- Y10S 707/99939: Privileged access
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- Y10S: TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS

## Abstract

Techniques are provided for monitoring a database system. A set of data elements may be read from a database system into a device. The device may be external to the database system. From the device, a set of analysis operations are performed on the data elements in order to identify if any of the date elements satisfy a criteria for being considered potentially anomalous. A notification is signaled if potentially anomalous data is identified.

## Claims

### Claim 1

A method for monitoring a database system, wherein the database system is operated using a set of one or more processors, the steps comprising:
reading data elements managed by the database system, wherein the data elements include data stored as content within a database of the database system;
performing a set of analysis operations on the data elements in order to identify one or more data elements that are anomalous based on criteria defined by the set of analysis operations; and
automatically signaling a notification after identifying the one or more data elements are potentially anomalous;
wherein steps comprising the method are substantially performed using processing resources that are external to the set of one or more processors.

### Claim 2 (depends on 1)

The method of claim 1, wherein the steps of the method are performed without executing any agents on the database system.

### Claim 3 (depends on 1)

The method of claim 1, wherein the step of performing a set of analysis operations on the data elements are performed without executing any code on the set of one or more processors.

### Claim 4 (depends on 1)

The method of claim 1, wherein reading data elements managed by the database system include reading metadata about a schema of the database.

### Claim 5 (depends on 1)

The method of claim 1, wherein reading data elements managed by the database system include reading data representing a set of privileges for enabling one or more users of the database system to do at least one of view, change or delete data within the database.

### Claim 6 (depends on 1)

The method of claim 1, wherein the step of automatically signaling a notification includes sending an email to at least a first designated email address.

### Claim 7 (depends on 1)

The method of claim 1, wherein the step of automatically signaling a notification includes paging at least a first designated phone number.

### Claim 8 (depends on 1)

The method of claim 1, performing a set of analysis operations includes comparing at least some of the data elements to data elements read at an earlier instance of time.

### Claim 9 (depends on 4)

The method of claim 4, wherein reading data elements includes reading a system catalog of the database, and wherein performing a set of analysis operations on the data elements in order to identify one or more data elements includes comparing the system catalog to a system catalog that was read from the database at an earlier instance.

### Claim 10

A method for monitoring a database system, the method comprising:
identifying a set of data elements stored as content within a database of the database system; and
performing a series of analysis processes on the set of data elements in order to identify data within the database that is potentially anomalous.

### Claim 11 (depends on 10)

The method of claim 10, wherein identifying a set of data includes reading the set of data from the database system.

### Claim 12 (depends on 11)

The method of claim 11, further comprising reading the set of data from the database system from an external machine.

### Claim 13 (depends on 10)

The method of claim 10, wherein performing a series of analysis processes includes performing a first process on the data elements for making a first determination as to whether any data in the database is anomalous based on a first characteristic of the set of data elements, and a second process on the data elements for making a second determination as to whether any data in the database is anomalous based on a second characteristic of the set of data elements.

### Claim 14 (depends on 13)

The method of claim 13, wherein performing a series of analysis processes includes performing a third process on the data elements for making a third determination as to whether any data in the database is anomalous based on a third characteristic of the set of data elements.

### Claim 15 (depends on 10)

The method of claim 10, wherein performing a series of analysis processes includes comparing the set of data elements to a set of parameters defined by a user.

### Claim 16 (depends on 13)

The method of claim 13, wherein performing a series of analysis processes includes determining a maximum value of two or more data element in the set of data elements, a minimum value of two or more data element in the set of data elements, and an average value of two or more data elements in the set of data elements.

### Claim 17 (depends on 16)

The method of claim 16, wherein performing a series of analysis processes includes comparing at least one of the maximum value, the minimum value, and the average value to values determined from a previous time period.

### Claim 18 (depends on 13)

The method of claim 13, wherein performing a series of analysis processes includes selecting a group of data from the set of data elements, and determining a characteristic of the group of data.

### Claim 19 (depends on 18)

The method of claim 18, wherein determining a characteristic of the group of data includes determining one or more of a maximum value data element in the group of data, a minimum value data element in the group of data, and an average value of the group of data.

### Claim 20 (depends on 18)

The method of claim 18, wherein selecting a group of data includes selecting the group of data based on one or more user-defined parameters.

### Claim 21 (depends on 10)

The method of claim 10, wherein performing a series of analysis processes includes clustering values identified from the set of data elements using a statistical distribution, and then identifying data within the database that is potentially anomalous using the statistical distribution.

### Claim 22 (depends on 21)

The method of claim 21, wherein performing a series of analysis processes includes identifying data points of values for individual data elements based on ranges of two or more parameters that define the individual data element within the database.

### Claim 23 (depends on 22)

The method of claim 22, wherein the two or more parameters correspond to a first parameter identifying a row of the individual data element, and a second parameter identifying a column of the individual data element.

### Claim 24 (depends on 10)

The method of claim 10, wherein performing a series of analysis processes includes comparing a result of one or more of the series of analysis processes to a previous result from performing the one or more series of analysis processes on a set of data elements identified from the database at a previous time period.

### Claim 25 (depends on 10)

The method of claim 10, wherein performing a series of analysis processes includes comparing a result of one or more of the series of analysis processes to a designated set of results.

### Claim 26 (depends on 10)

The method of claim 10, further comprising automatically signaling a notification if potentially anomalous data is identified.

### Claim 27 (depends on 26)

The method of claim 26, wherein signaling a notification includes sending an email to a designated email address.

### Claim 28 (depends on 26)

The method of claim 26, wherein signaling a notification includes paging a designated phone number.

### Claim 29 (depends on 10)

The method of claim 10, further comprising compiling a result of performing the series of analysis processes at one or more instances into a report.

### Claim 30 (depends on 29)

The method of claim 29, further comprising compiling the potentially anomalous data into the report.

### Claim 31 (depends on 10)

The method of claim 10, further comprising associating potentially anomalous data with an event that caused the data to be stored in the database.

### Claim 32 (depends on 31)

The method of claim 31, further comprising archiving a plurality of events that cause anomalous data to be stored in the database.

### Claim 33

A method for monitoring a database system, the method comprising:
identifying, at one or more instances in a designated time period, a set of data elements stored as content within a database of the database system;
identifying trend data for how the set of data elements are modified over the designated time period; and
performing, based on the trend data, one or more analysis operations in order to identify potentially anomalous data within the database.

### Claim 34 (depends on 33)

The method of claim 33, wherein the step of performing one or more analysis operations includes adjusting the one or more analysis operations based on the trend data.

### Claim 35 (depends on 33)

The method of claim 33, wherein the step of performing one or more analysis operations includes selecting the one or more analysis operations based on the trend data.

### Claim 36 (depends on 33)

The method of claim 33, wherein identifying a trend for how the set of data elements are modified includes identifying the trend data over a duration designated by a user.

### Claim 37 (depends on 33)

The method of claim 33, further comprising, once the designated time period is over, repeating the step of identifying a set of data elements, and then performing the one or more analysis operations based on the trend data identified during the designated time period.

### Claim 38 (depends on 33)

The method of claim 33, wherein identifying a set of data elements includes reading the set of data elements from a database of the database system.

### Claim 39 (depends on 33)

The method of claim 33, wherein the step of identifying a set of data elements is repeated at multiple instances over the designated time period, and wherein the step of identifying trend data for how the set of data elements are modified includes updating the trend data after each instance of identifying the set of data elements.

### Claim 40 (depends on 33)

The method of claim 33, further comprising automatically signaling a notification if potentially anomalous data is identified.

### Claim 41 (depends on 40)

The method of claim 40, wherein signaling a notification includes sending an email to a designated email address.

### Claim 42 (depends on 40)

The method of claim 40, wherein signaling a notification includes paging a designated phone number.

### Claim 43 (depends on 33)

The method of claim 33, further comprising compiling a result of performing the one or more analysis operations into a report.

### Claim 44 (depends on 33)

The method of claim 33, further comprising compiling the potentially anomalous data into the report.

### Claim 45 (depends on 33)

The method of claim 33, further comprising associating potentially anomalous data with an event that caused the data to be stored in the database.

### Claim 46 (depends on 45)

The method of claim 45, further comprising archiving a plurality of events that cause anomalous data to be stored in the database.
