Internal security system for a relational database system

• US 7,720,894 B2
• Filed: 09/12/2006
• Issued: 05/18/2010
• Est. Priority Date: 07/27/2001
• Status: Active Grant

• Current Assignee: Patrice P. Parent
• Original Assignee: Patrice P. Parent
• Inventors: Parent, Patrice P.
• Primary Examiner(s): Ehichioya; Fred I
• Application Number:
  US11/519,377
• Publication Number:
  US 20070094298A1
• Time in Patent Office: 1,344 Days
• Field of Search: 707/999.003, 707/999.004, 707/999.009, 707/999.1, 707/999.102, 707/999.2, 707/999.201
• US Class Current: 707/781
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 2221/2141 Access rights, e.g. capability lists, access control lists, access tables, access matrices
• CPC Class Codes: Y10S 707/954 Relational
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation
• CPC Class Codes: Y10S 707/99939 Privileged access
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

An internal security method for use with a relational database system is disclosed. The method is incorporated into a database system such that there is no need for security coding be layered on top of the system application software to prevent unauthorized access to restricted database information. The method of the present invention includes at least two embodiments and at least one of the embodiments has a “down the tree view” structure.

Claims

1. An internal security method for a relational database system, comprising one or more processors implementing the steps of:

(a) determining which data information from the total amount of data information stored in system databases is restricted data information that shall not be accessible by each and every 1 to N system users, where N is an integer greater than 1;

(b) determining for each individual specific system user the restricted data information that such a system user shall have access;

(c) creating at least one relational access table with each specific system user having at least one record in the relational access table and using a foreign key in the table created at step (c) that is linked to a primary key associated with a specific system user'"'"'s table of the relational database system for controlling that specific system user'"'"'s access to the restricted data information that was determined at step (b) and preventing downstream and upstream access to unauthorized restricted data information through the use of the foreign key and primary key link, such that a first specific system user will have one or more records in the relational access table that will permit the first specific system user'"'"'s access to restricted data information that is determined for the first specific system user to be joined with a second specific system user'"'"'s access to restricted data information that is determined for the second specific system user, and the specific second system user will have one or more records in the relational access table that will permit the second specific system user'"'"'s access to restricted data information that is determined for the second specific system user; and

(d) each specific system user accessing restricted data information stored in the system databases according to the relational access table created at step (c) and specific one way joining links to restricted data information stored in the system databases of other system users according to step (c).

2. The method as recited in claim 1, wherein the relational database is a structured query language database.

3. The method as recited in claim 1, wherein each relational access table has a foreign key that relates to a primary key of only one specific system user.

4. The method as recited in claim 1, wherein each relational access table created at step (c) may have access to additional restricted data information added to it by updating the relational access table after it is created.

5. The method as recited in claim 1, wherein each relational access table created at step (c) may have access to certain restricted data information deleted from it by updating the relational access table after it is created.

6. The method as recited in claim 1, wherein the relational database system that incorporates the internal security method includes a star schema configuration.

7. The method as recited in claim 6, wherein the relational database system that incorporates the internal security method includes a full star schema configuration.