# US 2010/0306826 A1 · Methods and systems for implementing a self defending/repairing database

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

- Number: US 2010/0306826 A1
- Document ID: US20100306826A1
- Status: Published application
- Kind: A1
- Application number: 12/475,171
- Filed: 2009-05-29
- Published: 2010-12-02
- Earliest claimed: 2009-05-29
- Assignees: Oracle International Corporation
- Inventors: Peter Kestner; Kurt Lysy
- Web page: https://patentgrep.com/patent/US20100306826A1

## CPC

- G06F 11/1448: {Management of the data involved in backup or backup restore}
- G06F 21/554: {involving event detection and direct action}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

This disclosure describes, generally, methods and systems for self defending and repairing a database. The method includes monitoring, at a database server, code modifications to a database management application. The database management application is configured to maintain the database. The method further includes determining that a code modification has occurred to the database management application. The method further includes checking the code modification for the presence of an authorization key, and in response to an invalid or non-existent authorization key, determining that the code modification is unauthorized. Further, the method includes quarantining the modified code in a secure storage location, and automatically accessing original code of the database management application and replacing the modified code with code from the original code of the database management application.

## Claims

### Claim 1

A method of self defending and repairing a database, the method comprising:
monitoring, at a database server, code modifications to a database management application, wherein the database management application is configured to maintain the database;
determining that a code modification has occurred to the database management application;
checking the code modification for the presence of an authorization key;
in response to an invalid or non-existent authorization key, determining that the code modification is unauthorized;
quarantining the modified code in a secure storage location; and
automatically accessing original code of the database management application and replacing the modified code with code from the original code of the database management application.

### Claim 2 (depends on 1)

The method of claim 1, further comprising identifying a code structure associated with the code modification.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
determining if an auditing mode for the database is engaged; and
in response to the auditing mode being engaged, allowing the code modification to occur in order to track the intruder's actions.

### Claim 4 (depends on 1)

The method of claim 1, further comprising storing a secure mirror copy of the original source code.

### Claim 5 (depends on 4)

The method of claim 4, wherein the secure mirror copy and the secure storage location are stored using a high security storage mechanism.

### Claim 6 (depends on 4)

The method of claim 4, wherein the original source code is accessed at the secure mirror copy.

### Claim 7 (depends on 1)

The method of claim 1, wherein, in response to a valid authorization key, the code modification is allowed to remain.

### Claim 8 (depends on 7)

The method of claim 7, wherein the code modification is determined to be an authorized update and/or patch to the database management application.

### Claim 9 (depends on 1)

The method of claim 1, further comprising:
logging code modification activities; and
storing the logged activities in an instruction log file.

### Claim 10 (depends on 1)

The method of claim 1, further comprising installing, at the database server, a database security component.

### Claim 11 (depends on 10)

The method of claim 10, initializing the database security component.

### Claim 12 (depends on 11)

The method of claim 11, wherein the initializing of the database security component comprises storing a secure mirror copy of the original source code.

### Claim 13 (depends on 12)

The method of claim 12, wherein the database security component is configured to monitor the code modifications and replace the modified code with the original code.

### Claim 14

A system for self defending and repairing a database, the system comprising:
a database configured to store data;
a secure storage location; and
a database server coupled with the database and the secure storage location, the database server including a security component, wherein the security component is configured to monitor code modifications to a database management application, wherein the database management application is configured to maintain the database, determine that a code modification has occurred to the database management application, check the code modification for the presence of an authorization key, in response to an invalid or non-existent authorization key, determine that the code modification is unauthorized, quarantining the modified code in the secure storage location, and automatically access original code of the database management application and replace the modified code with code from the original code of the database management application.

### Claim 15 (depends on 14)

The system of claim 14, further comprising a safe mirror copy storage location coupled with the database server, wherein the safe mirror copy is configured to store a secure mirror copy of the original source code.

### Claim 16

A machine-readable medium having sets of instructions stored thereon for self defending and repairing a database which, when executed by a machine, cause the machine to:
monitor, at a database server, code modifications to a database management application, wherein the database management application is configured to maintain the database;
determine that a code modification has occurred to the database management application;
check the code modification for the presence of an authorization key;
in response to an invalid or non-existent authorization key, determine that the code modification is unauthorized;
quarantine the modified code in a secure storage location; and
automatically access original code of the database management application and replace the modified code with code from the original code of the database management application.

### Claim 17 (depends on 16)

The machine-readable medium of claim 16, wherein the sets of instructions, when further executed by the machine, cause the machine to identify a code structure associated with the code modification.

### Claim 18 (depends on 16)

The machine-readable medium of claim 16, wherein the sets of instructions, when further executed by the machine, cause the machine to:
determine if an auditing mode for the database is engaged; and
in response to the auditing mode being engaged, allow the code modification to occur in order to track the intruder's actions.

### Claim 19 (depends on 19)

The machine-readable medium of claim 19, wherein the sets of instructions, when further executed by the machine, cause the machine to store a secure mirror copy of the original source code.

### Claim 20 (depends on 19)

The machine-readable medium of claim 19, wherein the secure mirror copy and the secure storage location are stored using a high security storage mechanism.
