US5751949A - Data security system and method - Google Patents

Data security system and method Download PDF

Info

Publication number
US5751949A
US5751949A US08/447,650 US44765095A US5751949A US 5751949 A US5751949 A US 5751949A US 44765095 A US44765095 A US 44765095A US 5751949 A US5751949 A US 5751949A
Authority
US
United States
Prior art keywords
server
user
security
access
row
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Lifetime
Application number
US08/447,650
Inventor
Robert David Thomson
Roger Geiwitz
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
MCI Corp
OL Security LLC
Original Assignee
MCI Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by MCI Corp filed Critical MCI Corp
Priority to US08/447,650 priority Critical patent/US5751949A/en
Assigned to MCI COMMUNICATIONS CORPORATION reassignment MCI COMMUNICATIONS CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: GEIWITZ, ROGER, THOMSON, ROBERT
Application granted granted Critical
Publication of US5751949A publication Critical patent/US5751949A/en
Assigned to VERIZON PATENT AND LICENSING INC. reassignment VERIZON PATENT AND LICENSING INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MCI COMMUNICATIONS CORPORATION
Assigned to TEKLA PEHR LLC reassignment TEKLA PEHR LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: VERIZON PATENT AND LICENSING INC.
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60Protecting data
    • G06F21/62Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G06F21/6227Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database where protection concerns the structure of data, e.g. records, types, queries

Definitions

  • the present invention relates generally to computer accessed databases, and, more specifically, to a security system for limiting access to the database to authorized users.
  • Computer accessible databases are well known and typically configure data in tables having rows and columns.
  • a typical server computer system includes a central server computer with many remote terminals operatively joined thereto, with each terminal typically being in the form of a personal computer with its own monitor, keyboard, and central processing unit (CPU).
  • Clients or users utilize the remote terminals to access the server computer for various purposes including accessing databases therein for in turn manipulating the data as desired.
  • the server computer is maintained by one or more administrators who configure and maintain the various databases for use by the various users at the remote terminals. And, the server computer utilizes appropriate software or programs to accomplish this.
  • the server computer includes conventional relational database software stored therein which is used by an administrator for creating and maintaining databases including various server or data tables.
  • An exemplary relational database software is known as standard query language (SQL) Server software and is commercially available from the Sybase Company, of Denver, Colo. for example.
  • SQL standard query language
  • the Sybase SQL Server software is merely representative of existing or developed software having built in capabilities for creating and maintaining databases, and inherent limitations as well.
  • the relational database software is preconfigured for effecting security of the data contained in the various data or server tables thereof in horizontal or vertical manners.
  • a typical server table includes a limited number of data columns in the vertical direction typically limited by the relevant number of pertinent attributes concerning the data.
  • the number of corresponding horizontal rows of the table is usually unlimited, and is typically substantially greater in number than the number of columns. Recognizing the need to provide security to the various data tables as desired, the relational database software is provided with suitable software to limit access to entire server tables to authorized users, as well as limiting access to selected rows or columns of individual tables to authorized users.
  • the relational database software allows an administrator to create using predefined software syntax one or more subsets of the tables known generally as views.
  • views the various users at the remote terminals may only access authorized data columns through predefined views, which is typically implemented by matching a user's log-on (logon) identification (ID) number with a user ID stored in a corresponding system table in the server computer. Since there are a finite, reasonable number of table columns in typical databases, creating a specific view for the corresponding authorized columns is readily accomplished for securing access to these columns.
  • the same security tool requires that an individual view be effected by the administrator for each horizontal slice or row of a given server table. If the number of rows is reasonably small, this security tool is readily implemented.
  • a significant problem occurs when there are a substantial number of horizontal data slices, for example a thousand or more, since the available security method would in turn require the administrator to generate a corresponding number of views, a thousand or more, to implement the row security.
  • the row security parameters require frequent changing, then corresponding views must also be created and entered into the database before the new security can be utilized, which makes the data unavailable for the corresponding time required to implement the security change. It is desirable to improve the ease of effecting security, in particular row security, with a minimum amount of effort and time to implement, and eliminate unavailable down-time for accessing the data in the server tables.
  • a security system and method are provided for securing user access to server tables having data arranged in rows and columns.
  • the server table is contained in a server computer which is accessible by a plurality of user terminals joined thereto.
  • the server computer includes relational database software for creating and maintaining tables, including the server table, and views defining subsets of the tables.
  • a security table is stored in the computer for identifying authorized user access to preselected rows of the server table for pre-identified users.
  • An access view is stored in the computer for automatically joining the security and server tables to limit user access to the server table to the preselected rows thereof based on the security table.
  • a single security table may therefore be used and is readily updated by merely deleting, adding, or updating entries.
  • FIG. 1 is a schematic representation of a plurality of remote user terminals operatively joined to a server computer containing a database with a plurality of server tables having data arranged in rows and columns.
  • FIG. 2 is an exemplary server table containing data arranged in rows and columns stored within the server computer illustrated in FIG. 1.
  • FIG. 3 is a flow chart representation of a user request for data sent to the server computer illustrated in FIG. 1 showing access to a plurality of server tables like the one illustrated in FIG. 2 through a corresponding plurality of access views and a common security table.
  • FIG. 4 is an exemplary embodiment of the security table illustrated in FIG. 3 containing rows of user ID's and authorized row access to the server tables illustrated In FIG. 3.
  • FIG. 5 is an exemplary view of software syntax for joining the security table of FIG. 4 to the first server table illustrated in FIGS. 2 and 3 to effect row security thereof.
  • FIG. 6 is an exemplary second view of software syntax for joining the security table of FIG. 4 with the second server table of FIG. 3 to effect row security based on another row label.
  • FIG. 7 is a table of sample Standard Query Language (SQL) queries provided to the server computer in FIG. 1 through the various remote terminals, with the corresponding query results therefor.
  • SQL Standard Query Language
  • FIG. 1 Illustrated schematically in FIG. 1 is an exemplary database server system 10 which includes a central server computer 12 and a plurality of conventional remote user input/output terminals 14 operatively joined thereto in a conventionally known manner for providing access thereto.
  • the server computer 12 may take any conventional form and includes a digital, programmable central processing unit (CPU) and one or more conventional memory or storage devices.
  • the user terminals 14 may also take any conventional form such as a personal computer including an output monitor, an input keyboard, its own CPU, and its own memory storage device as required.
  • the server computer 12 is conventionally configured with a preexisting relational database software suitably stored in the computer 12.
  • An exemplary relational database software is conventionally known as the Sybase SQL Server software which is a commercially available product from the Sybase Company of Denver, Colo. for example.
  • the relational database software is stored in the server computer 12 and is conventionally operable by an administrator for creating and maintaining a database including tables, with an exemplary table being referred to as a data or server table having data prearranged in horizontal rows and vertical columns.
  • the relational database software also includes conventional views which define subsets of one or more of these server tables, which views are implemented using a preexisting software syntax for the corresponding relational database software. Since various relational database software is available, various syntax is associated therewith, with the corresponding views nevertheless being definable by the administrator to define data subsets as desired.
  • a preexisting security system is provided therein.
  • the security system may be configured by the administrator to limit user access to entire tables or portions thereof based on a suitable user identification (ID) such as a single, multi-digit number (e.g. 12345) for example.
  • ID a single, multi-digit number
  • the administrator creates a specific view for each such data partition giving access thereto to specified users by their corresponding user ID's.
  • a server table includes a reasonably small number of columns, and providing vertical for one or more of the columns is readily accomplished by creating the corresponding views.
  • the number of rows in an exemplary server table is substantially greater than the number of columns and may for example be up to three or more orders of magnitude greater, with the corresponding number of data partitions being equally as large.
  • the number of rows in an exemplary server table is substantially greater than the number of columns and may for example be up to three or more orders of magnitude greater, with the corresponding number of data partitions being equally as large.
  • up to one thousand views would be required to implement horizontal row security using the preexisting relational database software.
  • new views need to be created by the administrator and entered into the database before the new security can be effected, which then prevents the data from being available by the users for the time required to implement the security.
  • the existing relational database software may be used in a new manner to substantially simplify the creation of row security in the server tables thereof.
  • the improved security system in accordance with the present invention includes the existing server computer 12 shown in FIG. 1, the existing relational database software contained therein, and the existing user terminals 14.
  • An exemplary first server TABLE1 stored in the database of the server computer 12 illustrated in FIG. 1 is illustrated in FIG. 2.
  • This exemplary server table includes data arranged in rows and columns of any desired length, with the number of rows typically being substantially larger than the number of columns, for example three or more orders of magnitude greater.
  • each of the various rows has a corresponding row label, which in this exemplary embodiment identifies various departments (Dept's) by a corresponding multiple digit number.
  • each of the row labels there are one or more columns of useful data indicated generically by various combinations of the letters X and Y, with the data taking any suitable form as desired such as alphabetic, numeric, or alphanumeric .
  • the data contained in the various columns might represent sensitive financial data for the corresponding departments, with it being desired to limit user access to the data in TABLE1 on a selected need-to-know basis.
  • a single Security TABLE-S is created by the administrator and stored in the server computer 12 for Identifying authorized user access to preselected rows of the server TABLE1 for pre-identified users as illustrated in FIG. 3.
  • a suitable access view such as first VIEW1 is created by the administrator and is also stored in the server computer 12 for automatically joining the Security TABLE-S and the corresponding server table such as TABLE1 to limit user access to the server table to solely preselected rows thereof based on the Security TABLE-S.
  • an exemplary Security TABLE-S is illustrated and includes a first column of preselected user ID's and one or more corresponding columns of authorized-access row labels for the respective user ID's.
  • each of the users is given a corresponding user ID which may take any suitable form including the multi digit numbers illustrated in FIG. 4.
  • the user ID When a user logs on to one of the remote terminals illustrated in FIG. 1, the user ID must be entered and is conventionally stored in a system table 16 in the server computer 12 in a conventionally known manner. In this way a preselected user ID is associated with a given user.
  • a row label e.g. Dept.number
  • the Security TABLE-S is therefore used to join given or identified users as identified by their ID's to the authorized row labels in the server TABLE1.
  • the Security TABLE-S may include as many row entries as desired for linking user ID's to desired row labels, such as the Dept. numbers found in TABLE1. As indicated for example in Security TABLE-S, one or more user ID rows may be provided for a given user ID to correspond with one or more authorized row labels such as Dept. number.
  • User ID 11111 is listed in the Security TABLE-S as having authorized access to Dept. Nos. 001, 010, and 020 for example.
  • User ID 22222 is authorized for access to Dept. Nos. 001 and 002.
  • the Security TABLE-S provides a simple security list based on user ID's and row labels which is implemented in accordance with the present invention using one or more predefined views having suitable relational database syntax for allowing access to the server TABLE1 by the user solely through the access view itself and based on the Security TABLE-S.
  • FIG. 5 illustrates an exemplary first VIEW1 in conventional Sybase relational database server syntax which creates a subset from TABLE1 based on the Security TABLE-S to allow user access to authorized rows of the server TABLE1 based on the user ID's and row labels.
  • the first access VIEW1 illustrated in FIG. 5 provides the syntax configuration to allow row access to the server TABLE1 where both an authorized-access row label and user ID is contained in the Security TABLE-S for the given user.
  • a user operating a remote terminal 14 in FIG. 1 will be allowed access to the first server TABLE1 through the first VIEW1 which selects from the TABLE1 where the Security TABLE-S user ID is equal to the user name as represented by the user logon ID, in conjunction with the Security TABLE-S row label such as Dept. number where it is equal to the server TABLE1 row label.
  • the first VIEW1 operates with the server TABLE1 to allow access to each row label number 001, 010, and 020 entry and its corresponding data columns found therein.
  • the Security TABLE-S need only include a single record per row label per user ID which results in a relatively simple security table.
  • the Security TABLE-S may therefore simply include duplicate or multiple user ID's as shown in FIG. 4 with different row labels therefor, respectively.
  • the Security TABLE-S may be readily or dynamically updated by the administrator by simply changing, adding, or deleting rows therein containing the user ID and respective row label entry or record. In this way, the various users at the remote terminals 14 may continue to access the various server tables such as TABLE1 with minimal or no interruption, since updating of the Security TABLE-S merely involves simple row by row entries Into that existing table.
  • a typical user request for data is represented in flow chart form for obtaining access to authorized rows in various ones of server tables contained in the server computer 12 of FIG. 1.
  • server tables there are a plurality of different server tables as illustrated in FIG. 3, with each server table containing data in row and column form in a manner identical to the first server TABLE1 illustrated in FIG. 2.
  • the various server tables may be conventionally configured to have different column data for similar row labels, or different row labels and corresponding column entries.
  • column data is provided for a given row label representing different departments (Dept.).
  • the second server TABLE2 illustrated in FIG. 3 is substantially identical to the server TABLE1 illustrated in FIG. 2 except that the row labels thereof are different and indicate for example a different classification such as one of the U.S. States. Since the state row label associated with server TABLE2 is different than the Dept. row label associated with server TABLE1, a correspondingly different second VIEW2 is created therefor.
  • a common, single Security TABLE-S may correspondingly be used to provide secured access to the various server tables by having a corresponding number of data columns therein for the different row labels of server TABLE1 and TABLE2 corresponding to respective user ID's. AS shown in FIG.
  • user ID 11111 has authorized access to the specified departments, and authorized access to data in server TABLE2 for the exemplary states indicated by the two letter abbreviation CA, TX, and NY.
  • a corresponding VIEW2 is required for joining the security TABLE-S with the corresponding server TABLE2 and is illustrated in FIG. 6 with an exemplary syntax.
  • the second VIEW2 illustrates in FIG. 6 is substantially identical to the first VIEW1 illustrated in FIG. 1 except that the row label in VIEW2 is the "state" as identified by the two letter abbreviation, whereas the row label utilized in the first VIEW1 is the "Dept" indicated by its corresponding reference number.
  • a plurality of different server tables are indicated, along with a respective plurality of the views allowing row access to each of the server tables based on a respective one of the views configured specifically therefor.
  • the first VIEW1 is specifically configured for the Dept. TABLE1
  • the second VIEW2 is specifically configured for the state TABLE2.
  • the corresponding views allow indirect access to the corresponding server tables for the authorized row therein which provides simple and effective security using standard tools which preexist in the relational database software contained in the server computer 12. No program changes are required in the relational database software itself, but improved and simplified security is nevertheless available.
  • the relational database software contained in the server computer 12 is conventionally configured to allow direct user read access solely to the various views and the Security TABLE-S, with no direct user access to the server tables themselves, which are maintained by the administrator. Access to the server tables is provided solely through the various views and therefore row security is easily and effectively implemented without major work or modification of the preexisting relational database software itself.
  • the security system of the present invention is effected by an administrator using the available tools in the existing relational database software in the server computer 12.
  • AS is conventionally known, the clients or users at the remote terminals 14 have limited access to the tools available in the relational database software in the server computer 12.
  • Various electronic spreadsheet software and/or report generation software is typically used in the various remote terminals 14 to actually access and manipulate the various databases in the server computer 12 in a conventional fashion and are conventionally compatible with the relational database software itself. Since the remote terminals 14 access data from the server computer 12 using conventional tables and views allowed in the relational database software, the security system of the present invention is effectively invisible to the end user.
  • FIG. 7 illustrates sample relational database (SQL) queries which may be made from any one of the remote terminals 14 by an end user or client. These sample queries are associated with the exemplary first TABLE1 illustrated in FIG. 2.
  • the first query in suitable syntax requests column I data from VIEW1, with the user access to the first server TABLE1 being processed through the flow chart illustrated In FIG. 3 to return the data record in all departments that the user has access based on the Security TABLE-S authorization.
  • the user requests column 1 and 2 records from the first VIEW1 for a specific department such as "001.” Both columns will be returned to the remote terminal 14 for records in Dept. "001” if the user has a record in the Security TABLE-S authorizing the use of Dept. "001.” And in the third query illustrated in FIG. 7, the user requests data records from the first VIEW1 for Depts. "001" and "002.” All records will be returned for these two Depts. if the user has authorization for both Depts. in the Security TABLE-S. If the user is authorized only for one of the two Depts., the access will be limited to that single authorized Dept.
  • the security system and method disclosed above therefore provide improved row security with a single Security TABLE-S, with a single view per serving table for providing access thereto.
  • This substantially simplifies existing security procedures available in the existing relational database software, and correspondingly reduces administration efforts while allowing dynamic and quick changes in the Security TABLE-S for minimizing or preventing interruption or downtime in the various databases contained in the server computer 12.
  • column security is also desired, the standard or existing procedure for effecting column security available in the relational database software may be utilized for creating corresponding views in a conventional manner. In this way both row and column security may be implemented using existing relational database software tools If desired.

Abstract

A security system and method are provided for securing user access to server tables having data arranged in rows and columns. The server table is contained in a server computer which is accessible by a plurality of user terminals joined thereto. The server computer includes relational database software for creating and maintaining tables, including the server table, and views defining subsets of the tables. A security table is stored in the computer for identifying authorized user access to preselected rows of the server table for pre-identified users. An access view is stored in the computer for automatically joining the security and server tables to limit user access to the server table to the preselected rows thereof based on the security table. A single security table may therefore be used and is readily updated by merely deleting, adding, or updating entries.

Description

BACKGROUND OF THE INVENTION
The present invention relates generally to computer accessed databases, and, more specifically, to a security system for limiting access to the database to authorized users.
Computer accessible databases are well known and typically configure data in tables having rows and columns. A typical server computer system includes a central server computer with many remote terminals operatively joined thereto, with each terminal typically being in the form of a personal computer with its own monitor, keyboard, and central processing unit (CPU). Clients or users utilize the remote terminals to access the server computer for various purposes including accessing databases therein for in turn manipulating the data as desired. The server computer is maintained by one or more administrators who configure and maintain the various databases for use by the various users at the remote terminals. And, the server computer utilizes appropriate software or programs to accomplish this.
In one exemplary embodiment, the server computer includes conventional relational database software stored therein which is used by an administrator for creating and maintaining databases including various server or data tables. An exemplary relational database software is known as standard query language (SQL) Server software and is commercially available from the Sybase Company, of Denver, Colo. for example. The Sybase SQL Server software is merely representative of existing or developed software having built in capabilities for creating and maintaining databases, and inherent limitations as well.
For example, the relational database software is preconfigured for effecting security of the data contained in the various data or server tables thereof in horizontal or vertical manners. A typical server table includes a limited number of data columns in the vertical direction typically limited by the relevant number of pertinent attributes concerning the data. The number of corresponding horizontal rows of the table is usually unlimited, and is typically substantially greater in number than the number of columns. Recognizing the need to provide security to the various data tables as desired, the relational database software is provided with suitable software to limit access to entire server tables to authorized users, as well as limiting access to selected rows or columns of individual tables to authorized users.
In order to limit user access to one or more of the table columns, the relational database software allows an administrator to create using predefined software syntax one or more subsets of the tables known generally as views. In this way, the various users at the remote terminals may only access authorized data columns through predefined views, which is typically implemented by matching a user's log-on (logon) identification (ID) number with a user ID stored in a corresponding system table in the server computer. Since there are a finite, reasonable number of table columns in typical databases, creating a specific view for the corresponding authorized columns is readily accomplished for securing access to these columns.
However, in order to effect horizontal or row security in the server tables, the same security tool requires that an individual view be effected by the administrator for each horizontal slice or row of a given server table. If the number of rows is reasonably small, this security tool is readily implemented. A significant problem occurs when there are a substantial number of horizontal data slices, for example a thousand or more, since the available security method would in turn require the administrator to generate a corresponding number of views, a thousand or more, to implement the row security. Furthermore, if the row security parameters require frequent changing, then corresponding views must also be created and entered into the database before the new security can be utilized, which makes the data unavailable for the corresponding time required to implement the security change. It is desirable to improve the ease of effecting security, in particular row security, with a minimum amount of effort and time to implement, and eliminate unavailable down-time for accessing the data in the server tables.
SUMMARY OF THE INVENTION
A security system and method are provided for securing user access to server tables having data arranged in rows and columns. The server table is contained in a server computer which is accessible by a plurality of user terminals joined thereto. The server computer includes relational database software for creating and maintaining tables, including the server table, and views defining subsets of the tables. A security table is stored in the computer for identifying authorized user access to preselected rows of the server table for pre-identified users. An access view is stored in the computer for automatically joining the security and server tables to limit user access to the server table to the preselected rows thereof based on the security table. A single security table may therefore be used and is readily updated by merely deleting, adding, or updating entries.
BRIEF DESCRIPTION OF THE DRAWINGS
The invention, in accordance with preferred and exemplary embodiments, together with further objects and advantages thereof, is more particularly described in the following detailed description taken in conjunction with the accompanying drawings in which:
FIG. 1 is a schematic representation of a plurality of remote user terminals operatively joined to a server computer containing a database with a plurality of server tables having data arranged in rows and columns.
FIG. 2 is an exemplary server table containing data arranged in rows and columns stored within the server computer illustrated in FIG. 1.
FIG. 3 is a flow chart representation of a user request for data sent to the server computer illustrated in FIG. 1 showing access to a plurality of server tables like the one illustrated in FIG. 2 through a corresponding plurality of access views and a common security table.
FIG. 4 is an exemplary embodiment of the security table illustrated in FIG. 3 containing rows of user ID's and authorized row access to the server tables illustrated In FIG. 3.
FIG. 5 is an exemplary view of software syntax for joining the security table of FIG. 4 to the first server table illustrated in FIGS. 2 and 3 to effect row security thereof.
FIG. 6 is an exemplary second view of software syntax for joining the security table of FIG. 4 with the second server table of FIG. 3 to effect row security based on another row label.
FIG. 7 is a table of sample Standard Query Language (SQL) queries provided to the server computer in FIG. 1 through the various remote terminals, with the corresponding query results therefor.
DESCRIPTION OF THE PREFERRED EMBODIMENT(S)
Illustrated schematically in FIG. 1 is an exemplary database server system 10 which includes a central server computer 12 and a plurality of conventional remote user input/output terminals 14 operatively joined thereto in a conventionally known manner for providing access thereto. The server computer 12 may take any conventional form and includes a digital, programmable central processing unit (CPU) and one or more conventional memory or storage devices. The user terminals 14 may also take any conventional form such as a personal computer including an output monitor, an input keyboard, its own CPU, and its own memory storage device as required.
The server computer 12 is conventionally configured with a preexisting relational database software suitably stored in the computer 12. An exemplary relational database software is conventionally known as the Sybase SQL Server software which is a commercially available product from the Sybase Company of Denver, Colo. for example. The relational database software is stored in the server computer 12 and is conventionally operable by an administrator for creating and maintaining a database including tables, with an exemplary table being referred to as a data or server table having data prearranged in horizontal rows and vertical columns. The relational database software also includes conventional views which define subsets of one or more of these server tables, which views are implemented using a preexisting software syntax for the corresponding relational database software. Since various relational database software is available, various syntax is associated therewith, with the corresponding views nevertheless being definable by the administrator to define data subsets as desired.
In the exemplary Sybase SQL Server software, a preexisting security system is provided therein. The security system may be configured by the administrator to limit user access to entire tables or portions thereof based on a suitable user identification (ID) such as a single, multi-digit number (e.g. 12345) for example. In order to create security for a given data partition such as one or more rows or columns of a given server table, the administrator creates a specific view for each such data partition giving access thereto to specified users by their corresponding user ID's. In a practical application, a server table includes a reasonably small number of columns, and providing vertical for one or more of the columns is readily accomplished by creating the corresponding views.
However, the number of rows in an exemplary server table is substantially greater than the number of columns and may for example be up to three or more orders of magnitude greater, with the corresponding number of data partitions being equally as large. For a one thousand row server table, up to one thousand views would be required to implement horizontal row security using the preexisting relational database software. However this presents an administrative burden and is time consuming. Furthermore, if the row security needs to change frequently, then new views need to be created by the administrator and entered into the database before the new security can be effected, which then prevents the data from being available by the users for the time required to implement the security.
In accordance with the present invention, the existing relational database software may be used in a new manner to substantially simplify the creation of row security in the server tables thereof. The improved security system in accordance with the present invention includes the existing server computer 12 shown in FIG. 1, the existing relational database software contained therein, and the existing user terminals 14. An exemplary first server TABLE1 stored in the database of the server computer 12 illustrated in FIG. 1 is illustrated in FIG. 2. This exemplary server table includes data arranged in rows and columns of any desired length, with the number of rows typically being substantially larger than the number of columns, for example three or more orders of magnitude greater. In TABLE1 each of the various rows has a corresponding row label, which in this exemplary embodiment identifies various departments (Dept's) by a corresponding multiple digit number. For each of the row labels, there are one or more columns of useful data indicated generically by various combinations of the letters X and Y, with the data taking any suitable form as desired such as alphabetic, numeric, or alphanumeric . For example, the data contained in the various columns might represent sensitive financial data for the corresponding departments, with it being desired to limit user access to the data in TABLE1 on a selected need-to-know basis.
Accordingly, in order to readily implement row security of the TABLE1 a single Security TABLE-S is created by the administrator and stored in the server computer 12 for Identifying authorized user access to preselected rows of the server TABLE1 for pre-identified users as illustrated in FIG. 3. In addition, a suitable access view, such as first VIEW1 is created by the administrator and is also stored in the server computer 12 for automatically joining the Security TABLE-S and the corresponding server table such as TABLE1 to limit user access to the server table to solely preselected rows thereof based on the Security TABLE-S.
Referring firstly to FIG. 4, an exemplary Security TABLE-S is illustrated and includes a first column of preselected user ID's and one or more corresponding columns of authorized-access row labels for the respective user ID's. For example, each of the users is given a corresponding user ID which may take any suitable form including the multi digit numbers illustrated in FIG. 4. When a user logs on to one of the remote terminals illustrated in FIG. 1, the user ID must be entered and is conventionally stored in a system table 16 in the server computer 12 in a conventionally known manner. In this way a preselected user ID is associated with a given user. And, as shown in FIG. 2, a row label (e.g. Dept.number) is associated with or defines each row of the server TABLE1. The Security TABLE-S is therefore used to join given or identified users as identified by their ID's to the authorized row labels in the server TABLE1.
The Security TABLE-S may include as many row entries as desired for linking user ID's to desired row labels, such as the Dept. numbers found in TABLE1. As indicated for example in Security TABLE-S, one or more user ID rows may be provided for a given user ID to correspond with one or more authorized row labels such as Dept. number. User ID 11111 is listed in the Security TABLE-S as having authorized access to Dept. Nos. 001, 010, and 020 for example. User ID 22222 is authorized for access to Dept. Nos. 001 and 002.
The Security TABLE-S provides a simple security list based on user ID's and row labels which is implemented in accordance with the present invention using one or more predefined views having suitable relational database syntax for allowing access to the server TABLE1 by the user solely through the access view itself and based on the Security TABLE-S. FIG. 5 illustrates an exemplary first VIEW1 in conventional Sybase relational database server syntax which creates a subset from TABLE1 based on the Security TABLE-S to allow user access to authorized rows of the server TABLE1 based on the user ID's and row labels. The first access VIEW1 illustrated in FIG. 5 provides the syntax configuration to allow row access to the server TABLE1 where both an authorized-access row label and user ID is contained in the Security TABLE-S for the given user. Paraphrasing the syntax of the first VIEW1, a user operating a remote terminal 14 in FIG. 1 will be allowed access to the first server TABLE1 through the first VIEW1 which selects from the TABLE1 where the Security TABLE-S user ID is equal to the user name as represented by the user logon ID, in conjunction with the Security TABLE-S row label such as Dept. number where it is equal to the server TABLE1 row label. For example, since the TABLE-S allows access to Dept. Nos. 001, 010, and 020, to user ID 11111, the first VIEW1 operates with the server TABLE1 to allow access to each row label number 001, 010, and 020 entry and its corresponding data columns found therein. The Security TABLE-S need only include a single record per row label per user ID which results in a relatively simple security table. The Security TABLE-S may therefore simply include duplicate or multiple user ID's as shown in FIG. 4 with different row labels therefor, respectively. The Security TABLE-S may be readily or dynamically updated by the administrator by simply changing, adding, or deleting rows therein containing the user ID and respective row label entry or record. In this way, the various users at the remote terminals 14 may continue to access the various server tables such as TABLE1 with minimal or no interruption, since updating of the Security TABLE-S merely involves simple row by row entries Into that existing table.
Referring again to FIG. 3, a typical user request for data is represented in flow chart form for obtaining access to authorized rows in various ones of server tables contained in the server computer 12 of FIG. 1. In a practical application, there are a plurality of different server tables as illustrated in FIG. 3, with each server table containing data in row and column form in a manner identical to the first server TABLE1 illustrated in FIG. 2. The various server tables may be conventionally configured to have different column data for similar row labels, or different row labels and corresponding column entries. In the exemplary first TABLE1 illustrated in FIG. 2, column data is provided for a given row label representing different departments (Dept.).
The second server TABLE2 illustrated in FIG. 3 is substantially identical to the server TABLE1 illustrated in FIG. 2 except that the row labels thereof are different and indicate for example a different classification such as one of the U.S. States. Since the state row label associated with server TABLE2 is different than the Dept. row label associated with server TABLE1, a correspondingly different second VIEW2 is created therefor. A common, single Security TABLE-S may correspondingly be used to provide secured access to the various server tables by having a corresponding number of data columns therein for the different row labels of server TABLE1 and TABLE2 corresponding to respective user ID's. AS shown in FIG. 4 for example, user ID 11111 has authorized access to the specified departments, and authorized access to data in server TABLE2 for the exemplary states indicated by the two letter abbreviation CA, TX, and NY. A corresponding VIEW2 is required for joining the security TABLE-S with the corresponding server TABLE2 and is illustrated in FIG. 6 with an exemplary syntax. The second VIEW2 illustrates in FIG. 6 is substantially identical to the first VIEW1 illustrated in FIG. 1 except that the row label in VIEW2 is the "state" as identified by the two letter abbreviation, whereas the row label utilized in the first VIEW1 is the "Dept" indicated by its corresponding reference number.
As shown in FIG. 3, a plurality of different server tables are indicated, along with a respective plurality of the views allowing row access to each of the server tables based on a respective one of the views configured specifically therefor. In the exemplary embodiment illustrated in FIG. 3, the first VIEW1 is specifically configured for the Dept. TABLE1, and the second VIEW2 is specifically configured for the state TABLE2. Upon matching of a user's log-on ID with the stored user ID's contained in the Security TABLE-S, the corresponding views allow indirect access to the corresponding server tables for the authorized row therein which provides simple and effective security using standard tools which preexist in the relational database software contained in the server computer 12. No program changes are required in the relational database software itself, but improved and simplified security is nevertheless available.
The relational database software contained in the server computer 12 is conventionally configured to allow direct user read access solely to the various views and the Security TABLE-S, with no direct user access to the server tables themselves, which are maintained by the administrator. Access to the server tables is provided solely through the various views and therefore row security is easily and effectively implemented without major work or modification of the preexisting relational database software itself.
The security system of the present invention is effected by an administrator using the available tools in the existing relational database software in the server computer 12. AS is conventionally known, the clients or users at the remote terminals 14 have limited access to the tools available in the relational database software in the server computer 12. Various electronic spreadsheet software and/or report generation software is typically used in the various remote terminals 14 to actually access and manipulate the various databases in the server computer 12 in a conventional fashion and are conventionally compatible with the relational database software itself. Since the remote terminals 14 access data from the server computer 12 using conventional tables and views allowed in the relational database software, the security system of the present invention is effectively invisible to the end user.
FIG. 7 illustrates sample relational database (SQL) queries which may be made from any one of the remote terminals 14 by an end user or client. These sample queries are associated with the exemplary first TABLE1 illustrated in FIG. 2. In conventional fashion, the first query in suitable syntax requests column I data from VIEW1, with the user access to the first server TABLE1 being processed through the flow chart illustrated In FIG. 3 to return the data record in all departments that the user has access based on the Security TABLE-S authorization.
In the second query illustrated in FIG. 7, the user requests column 1 and 2 records from the first VIEW1 for a specific department such as "001." Both columns will be returned to the remote terminal 14 for records in Dept. "001" if the user has a record in the Security TABLE-S authorizing the use of Dept. "001." And in the third query illustrated in FIG. 7, the user requests data records from the first VIEW1 for Depts. "001" and "002." All records will be returned for these two Depts. if the user has authorization for both Depts. in the Security TABLE-S. If the user is authorized only for one of the two Depts., the access will be limited to that single authorized Dept.
The security system and method disclosed above therefore provide improved row security with a single Security TABLE-S, with a single view per serving table for providing access thereto. This substantially simplifies existing security procedures available in the existing relational database software, and correspondingly reduces administration efforts while allowing dynamic and quick changes in the Security TABLE-S for minimizing or preventing interruption or downtime in the various databases contained in the server computer 12. If column security is also desired, the standard or existing procedure for effecting column security available in the relational database software may be utilized for creating corresponding views in a conventional manner. In this way both row and column security may be implemented using existing relational database software tools If desired.
While there have been described herein what are considered to be preferred and exemplary embodiments of the present invention, other modifications of the invention shall be apparent to those skilled in the art from the teachings herein, and it is, therefore, desired to be secured in the appended claims all such modifications as fall within the true spirit and scope of the invention.
Accordingly, what is desired to be secured by Letters Patent of the United States is the invention as defined and differentiated in the following claims:

Claims (13)

We claim:
1. A security system for providing user authorized access to a server table having data arranged in rows and columns comprising:
a server computer for storing said server table;
a plurality of user terminals operatively joined to said computer for providing access to said server table;
relational database software stored in said computer and operable by an administrator for creating and maintaining tables, including said server table, and views defining subsets of said tables;
a security table stored in said computer for identifying authorized user access to preselected rows of said server table for pre-identified users; and
an access view stored in said computer for joining said security and server tables to limit user access to said server table to said preselected rows thereof based on said security table.
2. A security system according to claim 1 further comprising:
a preselected user identification ID associated with a given user;
a row label associated with each row of said server table; and wherein:
said security table includes a column of preselected user ID's and a corresponding column of authorized-access row labels for said user ID's, respectively; and
said access view is configured to allow user access to authorized rows of said server table based on said user ID's and row labels.
3. A security system according to claim 2 further comprising a plurality of said server tables and a respective plurality of said views for allowing row access to each of said server tables based on a respective one of said views configured therefor.
4. A security system according to claim 3 wherein:
said server tables have different row labels;
said security table includes a plurality of columns for said different row labels corresponding to said user ID's; and
said views are configured for respective ones of said row labels.
5. A security system according to claim 3 wherein said security table includes a single record per row label per user ID.
6. A security system according to claim 5 wherein said security table includes duplicate user ID's with different row labels, respectively.
7. A security system according to claim 3 wherein said relational database software is configured to allow user read access solely to said views and said security table, and no direct access to said server tables.
8. A method of securing access to a server table having data arranged in rows and columns and stored in a server computer configured with relational database software for creating and maintaining tables, including said server table, and views defining subsets of said tables, said method comprising:
creating a security table in said computer for authorizing user access to preselected rows of said server table for pre-identified users; and
creating an access view in said computer for automatically joining said security table and said server table to limit user access to said server table to preselected rows thereof based on said security table.
9. A method according to claim 8 further comprising allowing user access to said server table solely through said access view.
10. A method according to claim 9 further comprising:
providing a preselected user ID associated with a given user;
providing a row label associated with each row of said server table;
providing in said server table a column of preselected user ID's and a corresponding column of authorized-access row labels for said user ID's, respectively; and
providing in said access view authorization to allow user access to authorized rows of said server table based on said user ID's and row labels.
11. A method according to claim 10 wherein said security table includes a single record per row label per user ID.
12. A method according to claim 11 wherein said security table includes duplicate user ID's with different row labels, respectively.
13. A method according to claim 12 further comprising updating said security table by adding or deleting user ID and respective row label entries therein.
US08/447,650 1995-05-23 1995-05-23 Data security system and method Expired - Lifetime US5751949A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US08/447,650 US5751949A (en) 1995-05-23 1995-05-23 Data security system and method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US08/447,650 US5751949A (en) 1995-05-23 1995-05-23 Data security system and method

Publications (1)

Publication Number Publication Date
US5751949A true US5751949A (en) 1998-05-12

Family

ID=23777194

Family Applications (1)

Application Number Title Priority Date Filing Date
US08/447,650 Expired - Lifetime US5751949A (en) 1995-05-23 1995-05-23 Data security system and method

Country Status (1)

Country Link
US (1) US5751949A (en)

Cited By (84)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5944825A (en) * 1997-05-30 1999-08-31 Oracle Corporation Security and password mechanisms in a database system
EP0965929A2 (en) * 1998-06-15 1999-12-22 Matsushita Electric Industrial Co., Ltd. Image data management system and method thereof
EP0991005A2 (en) * 1998-10-02 2000-04-05 Ncr International Inc. Privacy-enhanced database
EP0990972A1 (en) * 1998-10-02 2000-04-05 Ncr International Inc. System and method for managing data privacy in a database management system
EP1089196A2 (en) * 1999-10-01 2001-04-04 Ncr International Inc. System and method for managing data privacy in a database management system including a dependently connected privacy data mart
JP2001188804A (en) * 1999-10-01 2001-07-10 Ncr Internatl Inc Management method for data base containing privacy information and device therefor
US6339768B1 (en) 1998-08-13 2002-01-15 International Business Machines Corporation Exploitation of subsumption in optimizing scalar subqueries
WO2002029577A2 (en) * 2000-10-06 2002-04-11 Oracle Corporation Method and apparatus for automatic database encryption
WO2002031686A1 (en) * 2000-10-13 2002-04-18 Axon Information Technology Pty Ltd A multi-user database for computer-based information
US20020174352A1 (en) * 1996-06-20 2002-11-21 Anonymity Protection In Sweden Ab Data security system for a database
US20030061482A1 (en) * 2001-08-23 2003-03-27 Efunds Corporation Software security control system and method
US6578037B1 (en) * 1998-10-05 2003-06-10 Oracle Corporation Partitioned access control to a database
US6587854B1 (en) * 1998-10-05 2003-07-01 Oracle Corporation Virtually partitioning user data in a database system
US6606627B1 (en) * 2001-05-08 2003-08-12 Oracle Corporation Techniques for managing resources for multiple exclusive groups
US6631371B1 (en) 1998-10-05 2003-10-07 Oracle International Corporation Database fine-grained access control
US20030208457A1 (en) * 2002-04-16 2003-11-06 International Business Machines Corporation System and method for transforming data to preserve privacy
US20040039962A1 (en) * 1996-03-19 2004-02-26 Amit Ganesh Method and apparatus for making available data that was locked by a dead transaction before rolling back the entire dead transaction
US20040044655A1 (en) * 2002-09-04 2004-03-04 International Business Machines Corporation Row-level security in a relational database management system
US20040049683A1 (en) * 2002-07-18 2004-03-11 Klaus Abraham-Fuchs Method and system for evaluation of sensitive data
US20040068661A1 (en) * 2002-10-03 2004-04-08 International Business Machines Corporation Intelligent use of user data to pre-emptively prevent execution of a query violating access controls
US6768985B1 (en) * 1999-08-30 2004-07-27 Unisys Corporation Method and apparatus for administration of database partitions
US6813617B2 (en) 1998-10-05 2004-11-02 Oracle International Corporation Dynamic generation of optimizer hints
US6820082B1 (en) * 2000-04-03 2004-11-16 Allegis Corporation Rule based database security system and method
US20040250098A1 (en) * 2003-04-30 2004-12-09 International Business Machines Corporation Desktop database data administration tool with row level security
US20050038783A1 (en) * 1998-10-05 2005-02-17 Lei Chon Hei Database fine-grained access control
US20050144176A1 (en) * 2003-12-24 2005-06-30 Oracle International Corporation Column masking of tables
US20060136479A1 (en) * 2004-12-22 2006-06-22 Microsoft Corporation Secured views for a CRM database
WO2006111515A1 (en) * 2005-04-21 2006-10-26 Amadeus S.A.S. A customer centric travel system
US7133875B1 (en) * 2002-04-12 2006-11-07 Oracle International Corporation Method and apparatus for redefining a group of related objects in a relational database system
US20060259950A1 (en) * 2005-02-18 2006-11-16 Ulf Mattsson Multi-layer system for privacy enforcement and monitoring of suspicious data access behavior
EP1207443A3 (en) * 2000-11-16 2006-11-22 Protegrity Research & Development Encryption of databases based on a combination of hardware and software
US20060271529A1 (en) * 2005-05-31 2006-11-30 Jitendra Dhamija Query generator
US20070027880A1 (en) * 2005-07-28 2007-02-01 International Business Machines Corporation System and method for restricting access to sensitive data
US20070027871A1 (en) * 2005-07-26 2007-02-01 International Business Machines Corporation Self discovering adaptive security system and method
US20070067637A1 (en) * 2000-11-29 2007-03-22 Protegrity, A Swedish Corporation Method and a system for preventing impersonation of a database user
US20070083928A1 (en) * 2001-11-23 2007-04-12 Ulf Mattsson Data security and intrusion detection
US20070124276A1 (en) * 2003-09-23 2007-05-31 Salesforce.Com, Inc. Method of improving a query to a database system
US7228300B2 (en) 1998-10-05 2007-06-05 Oracle International Corporation Caching the results of security policy functions
US20070156375A1 (en) * 2005-12-29 2007-07-05 Microsoft Corporation Performance engineering and the application life cycle
US20070157311A1 (en) * 2005-12-29 2007-07-05 Microsoft Corporation Security modeling and the application life cycle
US20070174271A1 (en) * 2005-02-18 2007-07-26 Ulf Mattsson Database system with second preprocessor and method for accessing a database
US20070199050A1 (en) * 2006-02-14 2007-08-23 Microsoft Corporation Web application security frame
US20070198545A1 (en) * 2006-02-22 2007-08-23 Fei Ge Efficient processing of path related operations on data organized hierarchically in an RDBMS
US20070204346A1 (en) * 2006-02-27 2007-08-30 Microsoft Corporation Server security schema
US20070208745A1 (en) * 2006-03-01 2007-09-06 Oracle International Corporation Self-Service Sources for Secure Search
US20070208734A1 (en) * 2006-03-01 2007-09-06 Oracle International Corporation Link Analysis for Enterprise Environment
US20070208713A1 (en) * 2006-03-01 2007-09-06 Oracle International Corporation Auto Generation of Suggested Links in a Search System
US20070208746A1 (en) * 2006-03-01 2007-09-06 Oracle International Corporation Secure Search Performance Improvement
US20070208714A1 (en) * 2006-03-01 2007-09-06 Oracle International Corporation Method for Suggesting Web Links and Alternate Terms for Matching Search Queries
US20070209080A1 (en) * 2006-03-01 2007-09-06 Oracle International Corporation Search Hit URL Modification for Secure Application Integration
US20070208755A1 (en) * 2006-03-01 2007-09-06 Oracle International Corporation Suggested Content with Attribute Parameterization
US20070208744A1 (en) * 2006-03-01 2007-09-06 Oracle International Corporation Flexible Authentication Framework
US20070214129A1 (en) * 2006-03-01 2007-09-13 Oracle International Corporation Flexible Authorization Model for Secure Search
US20070220268A1 (en) * 2006-03-01 2007-09-20 Oracle International Corporation Propagating User Identities In A Secure Federated Search System
US20070283425A1 (en) * 2006-03-01 2007-12-06 Oracle International Corporation Minimum Lifespan Credentials for Crawling Data Repositories
US20080052291A1 (en) * 2006-08-22 2008-02-28 Michael Bender Database entitlement
US20080082540A1 (en) * 2006-10-03 2008-04-03 Salesforce.Com, Inc. Methods and systems for controlling access to custom objects in a database
US20080097954A1 (en) * 2006-10-20 2008-04-24 Microsoft Corporation Ranged lookups
US20080140620A1 (en) * 2006-12-08 2008-06-12 Michael Bender Method for altering database views dependent on rules
US20090006359A1 (en) * 2007-06-28 2009-01-01 Oracle International Corporation Automatically finding acronyms and synonyms in a corpus
US20090006356A1 (en) * 2007-06-27 2009-01-01 Oracle International Corporation Changing ranking algorithms based on customer settings
US20090024570A1 (en) * 2007-07-20 2009-01-22 Oracle Internatonal Corporation User defined query rewrite mechanism
US20090089591A1 (en) * 2007-09-27 2009-04-02 Protegrity Corporation Data security in a disconnected environment
US7664753B2 (en) 1996-02-17 2010-02-16 Private Access, Inc. Standing order database search system and method for internet and intranet application
US7676453B2 (en) 2004-04-22 2010-03-09 Oracle International Corporation Partial query caching
US7730032B2 (en) 2006-01-12 2010-06-01 Oracle International Corporation Efficient queriability of version histories in a repository
US20100241641A1 (en) * 2009-03-20 2010-09-23 Oracle International Corporation View mechanism for data security, privacy and utilization
EP1616252A4 (en) * 2004-03-29 2010-12-29 Microsoft Corp Systems and methods for fine grained access control of data stored in relational databases
US20110004551A1 (en) * 2001-06-27 2011-01-06 American Express Travel Related Services Company, Inc. Consolidated payment account system and method
US7873660B1 (en) 2003-02-27 2011-01-18 Oracle International Corporation Enforcing data privacy aggregations
US20110093917A1 (en) * 2008-06-13 2011-04-21 Byron A Alcorn Hierarchical Policy Management
US20110106778A1 (en) * 2009-11-05 2011-05-05 Oracle International Corporation Lock manager on disk
US8316051B1 (en) * 2001-11-30 2012-11-20 Oralce International Corporation Techniques for adding multiple security policies to a database system
US8423535B2 (en) 2003-09-23 2013-04-16 Salesforce.Com, Inc. Query optimization in a multi-tenant database system
US8443426B2 (en) 2007-06-11 2013-05-14 Protegrity Corporation Method and system for preventing impersonation of a computer system user
US20130340043A1 (en) * 2012-06-13 2013-12-19 Mehrdad (John) Zarei Distribution of dynamic structured content
CN104050223A (en) * 2013-03-15 2014-09-17 国际商业机器公司 Pivot facets for text mining and search
EP1446737B1 (en) * 2001-09-28 2016-04-27 Oracle International Corporation An efficient index structure to access hierarchical data in a relational database system
US10277561B2 (en) * 2016-07-22 2019-04-30 International Business Machines Corporation Database management system shared ledger support
US10339336B2 (en) 2003-06-11 2019-07-02 Oracle International Corporation Method and apparatus for encrypting database columns
US10652248B2 (en) 2016-07-28 2020-05-12 Molecula Corp. Systems and methods of managing data rights and selective data sharing
US20210350031A1 (en) * 2017-04-17 2021-11-11 EMC IP Holding Company LLC Method and device for managing storage system
US11232226B2 (en) * 2017-08-07 2022-01-25 Chengdu Qianniucao Information Technology Co., Ltd. Column value-based separate authorization method for statistical list operations
US11368466B2 (en) 2019-09-18 2022-06-21 David Michael Vigna Data classification of columns for web reports and widgets

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5021995A (en) * 1985-12-17 1991-06-04 Wang Laboratories, Inc. Data exchange apparatus and methods
US5058162A (en) * 1990-08-09 1991-10-15 Hewlett-Packard Company Method of distributing computer data files
US5065429A (en) * 1989-04-03 1991-11-12 Lang Gerald S Method and apparatus for protecting material on storage media
US5182705A (en) * 1989-08-11 1993-01-26 Itt Corporation Computer system and method for work management
US5272628A (en) * 1990-04-16 1993-12-21 Microsoft Corporation Method and system for aggregating tables having dissimilar formats
US5345549A (en) * 1992-10-30 1994-09-06 International Business Machines Corporation Multimedia based security systems
US5421001A (en) * 1992-05-01 1995-05-30 Wang Laboratories, Inc. Computer method and apparatus for a table driven file interface
US5440735A (en) * 1993-10-08 1995-08-08 International Business Machines Corporation Simplified relational data base snapshot copying
US5483596A (en) * 1994-01-24 1996-01-09 Paralon Technologies, Inc. Apparatus and method for controlling access to and interconnection of computer system resources

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5021995A (en) * 1985-12-17 1991-06-04 Wang Laboratories, Inc. Data exchange apparatus and methods
US5065429A (en) * 1989-04-03 1991-11-12 Lang Gerald S Method and apparatus for protecting material on storage media
US5182705A (en) * 1989-08-11 1993-01-26 Itt Corporation Computer system and method for work management
US5272628A (en) * 1990-04-16 1993-12-21 Microsoft Corporation Method and system for aggregating tables having dissimilar formats
US5058162A (en) * 1990-08-09 1991-10-15 Hewlett-Packard Company Method of distributing computer data files
US5421001A (en) * 1992-05-01 1995-05-30 Wang Laboratories, Inc. Computer method and apparatus for a table driven file interface
US5345549A (en) * 1992-10-30 1994-09-06 International Business Machines Corporation Multimedia based security systems
US5440735A (en) * 1993-10-08 1995-08-08 International Business Machines Corporation Simplified relational data base snapshot copying
US5483596A (en) * 1994-01-24 1996-01-09 Paralon Technologies, Inc. Apparatus and method for controlling access to and interconnection of computer system resources

Cited By (190)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7664753B2 (en) 1996-02-17 2010-02-16 Private Access, Inc. Standing order database search system and method for internet and intranet application
US9047487B2 (en) 1996-02-17 2015-06-02 Robert H. Shelton Standing order database search system and method for internet and intranet application
US7237147B2 (en) 1996-03-19 2007-06-26 Oracle International Corporation Method and apparatus for making available data that was locked by a dead transaction before rolling back the entire dead transaction
US20040039962A1 (en) * 1996-03-19 2004-02-26 Amit Ganesh Method and apparatus for making available data that was locked by a dead transaction before rolling back the entire dead transaction
US20110246788A1 (en) * 1996-06-20 2011-10-06 Protegrity Corporation Data security system for a database
US8402281B2 (en) * 1996-06-20 2013-03-19 Protegrity Corporation Data security system for a database
US20020174352A1 (en) * 1996-06-20 2002-11-21 Anonymity Protection In Sweden Ab Data security system for a database
US20070180240A1 (en) * 1996-06-20 2007-08-02 Ulf Dahl Data security system for a database
US5944825A (en) * 1997-05-30 1999-08-31 Oracle Corporation Security and password mechanisms in a database system
US6515765B1 (en) 1998-06-15 2003-02-04 Matsushita Electric Industrial Co., Ltd. Image data management system and method thereof
EP0965929A2 (en) * 1998-06-15 1999-12-22 Matsushita Electric Industrial Co., Ltd. Image data management system and method thereof
EP0965929A3 (en) * 1998-06-15 2000-03-22 Matsushita Electric Industrial Co., Ltd. Image data management system and method thereof
US6339768B1 (en) 1998-08-13 2002-01-15 International Business Machines Corporation Exploitation of subsumption in optimizing scalar subqueries
JP4588142B2 (en) * 1998-10-02 2010-11-24 エヌシーアール インターナショナル インコーポレイテッド Data management apparatus and method with improved privacy protection function
US6480850B1 (en) * 1998-10-02 2002-11-12 Ncr Corporation System and method for managing data privacy in a database management system including a dependently connected privacy data mart
JP2000112796A (en) * 1998-10-02 2000-04-21 Ncr Internatl Inc Method and system for managing data privacy in database management system
JP2000293421A (en) * 1998-10-02 2000-10-20 Ncr Internatl Inc Device and method for data management with improved privacy protecting function
EP0990972A1 (en) * 1998-10-02 2000-04-05 Ncr International Inc. System and method for managing data privacy in a database management system
US6275824B1 (en) 1998-10-02 2001-08-14 Ncr Corporation System and method for managing data privacy in a database management system
JP4590048B2 (en) * 1998-10-02 2010-12-01 テラデータ ユーエス インク Database system
EP0991005A3 (en) * 1998-10-02 2003-12-17 Ncr International Inc. Privacy-enhanced database
EP0991005A2 (en) * 1998-10-02 2000-04-05 Ncr International Inc. Privacy-enhanced database
US6813617B2 (en) 1998-10-05 2004-11-02 Oracle International Corporation Dynamic generation of optimizer hints
US6631371B1 (en) 1998-10-05 2003-10-07 Oracle International Corporation Database fine-grained access control
US7228300B2 (en) 1998-10-05 2007-06-05 Oracle International Corporation Caching the results of security policy functions
US20050038783A1 (en) * 1998-10-05 2005-02-17 Lei Chon Hei Database fine-grained access control
US6587854B1 (en) * 1998-10-05 2003-07-01 Oracle Corporation Virtually partitioning user data in a database system
US6578037B1 (en) * 1998-10-05 2003-06-10 Oracle Corporation Partitioned access control to a database
US7281003B2 (en) 1998-10-05 2007-10-09 Oracle International Corporation Database fine-grained access control
US6768985B1 (en) * 1999-08-30 2004-07-27 Unisys Corporation Method and apparatus for administration of database partitions
JP4507147B2 (en) * 1999-10-01 2010-07-21 テラデータ ユーエス インク Data management system in database management system
EP1089196A3 (en) * 1999-10-01 2004-07-21 Ncr International Inc. System and method for managing data privacy in a database management system including a dependently connected privacy data mart
JP2001188804A (en) * 1999-10-01 2001-07-10 Ncr Internatl Inc Management method for data base containing privacy information and device therefor
JP2001154917A (en) * 1999-10-01 2001-06-08 Ncr Internatl Inc Data management system in data base management system
EP1089196A2 (en) * 1999-10-01 2001-04-04 Ncr International Inc. System and method for managing data privacy in a database management system including a dependently connected privacy data mart
US6820082B1 (en) * 2000-04-03 2004-11-16 Allegis Corporation Rule based database security system and method
WO2002029577A3 (en) * 2000-10-06 2003-09-18 Oracle Corp Method and apparatus for automatic database encryption
US7111005B1 (en) 2000-10-06 2006-09-19 Oracle International Corporation Method and apparatus for automatic database encryption
WO2002029577A2 (en) * 2000-10-06 2002-04-11 Oracle Corporation Method and apparatus for automatic database encryption
US20030177135A1 (en) * 2000-10-13 2003-09-18 Axon Information Technology Pty Ltd. Multi-user database for computer-based information
WO2002031686A1 (en) * 2000-10-13 2002-04-18 Axon Information Technology Pty Ltd A multi-user database for computer-based information
EP1207443A3 (en) * 2000-11-16 2006-11-22 Protegrity Research & Development Encryption of databases based on a combination of hardware and software
US20070067637A1 (en) * 2000-11-29 2007-03-22 Protegrity, A Swedish Corporation Method and a system for preventing impersonation of a database user
US6606627B1 (en) * 2001-05-08 2003-08-12 Oracle Corporation Techniques for managing resources for multiple exclusive groups
US20110004551A1 (en) * 2001-06-27 2011-01-06 American Express Travel Related Services Company, Inc. Consolidated payment account system and method
US8504474B2 (en) * 2001-06-27 2013-08-06 American Express Travel Related Services Company, Inc. Consolidated payment account system and method
US20030061482A1 (en) * 2001-08-23 2003-03-27 Efunds Corporation Software security control system and method
EP1446737B1 (en) * 2001-09-28 2016-04-27 Oracle International Corporation An efficient index structure to access hierarchical data in a relational database system
US7594266B2 (en) 2001-11-23 2009-09-22 Protegrity Corporation Data security and intrusion detection
US20070083928A1 (en) * 2001-11-23 2007-04-12 Ulf Mattsson Data security and intrusion detection
US8316051B1 (en) * 2001-11-30 2012-11-20 Oralce International Corporation Techniques for adding multiple security policies to a database system
US7133875B1 (en) * 2002-04-12 2006-11-07 Oracle International Corporation Method and apparatus for redefining a group of related objects in a relational database system
US20030208457A1 (en) * 2002-04-16 2003-11-06 International Business Machines Corporation System and method for transforming data to preserve privacy
US7024409B2 (en) * 2002-04-16 2006-04-04 International Business Machines Corporation System and method for transforming data to preserve privacy where the data transform module suppresses the subset of the collection of data according to the privacy constraint
US20040049683A1 (en) * 2002-07-18 2004-03-11 Klaus Abraham-Fuchs Method and system for evaluation of sensitive data
US8478713B2 (en) 2002-09-04 2013-07-02 International Business Machines Corporation Row-level security in a relational database management system
US20090030907A1 (en) * 2002-09-04 2009-01-29 International Business Machines Corporation Row-level security in a relational database management system
US9870483B2 (en) * 2002-09-04 2018-01-16 International Business Machines Corporation Row-level security in a relational database management system
US20070244898A1 (en) * 2002-09-04 2007-10-18 International Business Machines Corporation Row-level security in a relational database management system
US20040044655A1 (en) * 2002-09-04 2004-03-04 International Business Machines Corporation Row-level security in a relational database management system
US20170053133A1 (en) * 2002-09-04 2017-02-23 International Business Machines Corporation Row-level security in a relational database management system
US9514328B2 (en) * 2002-09-04 2016-12-06 International Business Machines Corporation Row-level security in a relational database management system
US7240046B2 (en) * 2002-09-04 2007-07-03 International Business Machines Corporation Row-level security in a relational database management system
US7464080B2 (en) 2002-09-04 2008-12-09 International Business Machines Corporation Row-level security in a relational database management system
US20090043775A1 (en) * 2002-09-04 2009-02-12 International Business Machines Corporation Row-level security in a relational database management system
US20040068661A1 (en) * 2002-10-03 2004-04-08 International Business Machines Corporation Intelligent use of user data to pre-emptively prevent execution of a query violating access controls
EP1550038A4 (en) * 2002-10-03 2009-04-01 Ibm Intelligent use of user data to pre-emptively prevent execution of a query violating access controls
EP1550038A2 (en) * 2002-10-03 2005-07-06 International Business Machines Corporation Intelligent use of user data to pre-emptively prevent execution of a query violating access controls
US7698441B2 (en) 2002-10-03 2010-04-13 International Business Machines Corporation Intelligent use of user data to pre-emptively prevent execution of a query violating access controls
US7873660B1 (en) 2003-02-27 2011-01-18 Oracle International Corporation Enforcing data privacy aggregations
US7155612B2 (en) 2003-04-30 2006-12-26 International Business Machines Corporation Desktop database data administration tool with row level security
US20040250098A1 (en) * 2003-04-30 2004-12-09 International Business Machines Corporation Desktop database data administration tool with row level security
US10339336B2 (en) 2003-06-11 2019-07-02 Oracle International Corporation Method and apparatus for encrypting database columns
US8543566B2 (en) * 2003-09-23 2013-09-24 Salesforce.Com, Inc. System and methods of improving a multi-tenant database query using contextual knowledge about non-homogeneously distributed tenant data
US8732157B2 (en) 2003-09-23 2014-05-20 Salesforce.Com, Inc. Query optimization in a multi-tenant database system
US8423535B2 (en) 2003-09-23 2013-04-16 Salesforce.Com, Inc. Query optimization in a multi-tenant database system
US10152508B2 (en) 2003-09-23 2018-12-11 Salesforce.Com, Inc. Improving a multi-tenant database query using contextual knowledge about tenant data
US20070124276A1 (en) * 2003-09-23 2007-05-31 Salesforce.Com, Inc. Method of improving a query to a database system
US8620954B2 (en) 2003-09-23 2013-12-31 Salesforce.Com, Inc. Query optimization in a multi-tenant database system
US7310647B2 (en) 2003-12-24 2007-12-18 Oracle International Corporation Column masking of tables
US20050144176A1 (en) * 2003-12-24 2005-06-30 Oracle International Corporation Column masking of tables
EP1616252A4 (en) * 2004-03-29 2010-12-29 Microsoft Corp Systems and methods for fine grained access control of data stored in relational databases
US7676453B2 (en) 2004-04-22 2010-03-09 Oracle International Corporation Partial query caching
EP1675030A1 (en) * 2004-12-22 2006-06-28 Microsoft Corporation Secured views for a CRM database
AU2005237168B2 (en) * 2004-12-22 2010-11-04 Microsoft Corporation Secured views for a CRM database
CN1794232B (en) * 2004-12-22 2010-09-29 微软公司 Method for establishing secured views for a database
KR101224822B1 (en) 2004-12-22 2013-01-21 마이크로소프트 코포레이션 Secured views for a crm database
US20060136479A1 (en) * 2004-12-22 2006-06-22 Microsoft Corporation Secured views for a CRM database
US7562092B2 (en) * 2004-12-22 2009-07-14 Microsoft Corporation Secured views for a CRM database
AU2005237168A2 (en) * 2004-12-22 2010-06-03 Microsoft Corporation Secured views for a CRM database
US8935787B2 (en) 2005-02-18 2015-01-13 Protegrity Corporation Multi-layer system for privacy enforcement and monitoring of suspicious data access behavior
US20070174271A1 (en) * 2005-02-18 2007-07-26 Ulf Mattsson Database system with second preprocessor and method for accessing a database
US20060259950A1 (en) * 2005-02-18 2006-11-16 Ulf Mattsson Multi-layer system for privacy enforcement and monitoring of suspicious data access behavior
US10552622B2 (en) 2005-02-18 2020-02-04 Protegrity Corporation Multi-layer system for privacy enforcement and monitoring of suspicious data access behavior
WO2006111515A1 (en) * 2005-04-21 2006-10-26 Amadeus S.A.S. A customer centric travel system
US20060271529A1 (en) * 2005-05-31 2006-11-30 Jitendra Dhamija Query generator
US7814090B2 (en) * 2005-05-31 2010-10-12 Oracle International Corporation Query generator
US7676470B2 (en) * 2005-07-26 2010-03-09 International Business Machines Corporation Self discovering adaptive security system and method
US20070027871A1 (en) * 2005-07-26 2007-02-01 International Business Machines Corporation Self discovering adaptive security system and method
US20070027880A1 (en) * 2005-07-28 2007-02-01 International Business Machines Corporation System and method for restricting access to sensitive data
US8321387B2 (en) 2005-07-28 2012-11-27 International Business Machines Corporation Restricting access to sensitive data
US20070157311A1 (en) * 2005-12-29 2007-07-05 Microsoft Corporation Security modeling and the application life cycle
US7890315B2 (en) 2005-12-29 2011-02-15 Microsoft Corporation Performance engineering and the application life cycle
US20070156375A1 (en) * 2005-12-29 2007-07-05 Microsoft Corporation Performance engineering and the application life cycle
US7730032B2 (en) 2006-01-12 2010-06-01 Oracle International Corporation Efficient queriability of version histories in a repository
US20070199050A1 (en) * 2006-02-14 2007-08-23 Microsoft Corporation Web application security frame
US7818788B2 (en) 2006-02-14 2010-10-19 Microsoft Corporation Web application security frame
US20070198545A1 (en) * 2006-02-22 2007-08-23 Fei Ge Efficient processing of path related operations on data organized hierarchically in an RDBMS
US9229967B2 (en) 2006-02-22 2016-01-05 Oracle International Corporation Efficient processing of path related operations on data organized hierarchically in an RDBMS
US20070204346A1 (en) * 2006-02-27 2007-08-30 Microsoft Corporation Server security schema
US7712137B2 (en) 2006-02-27 2010-05-04 Microsoft Corporation Configuring and organizing server security information
US8601028B2 (en) 2006-03-01 2013-12-03 Oracle International Corporation Crawling secure data sources
US20070208755A1 (en) * 2006-03-01 2007-09-06 Oracle International Corporation Suggested Content with Attribute Parameterization
US11038867B2 (en) 2006-03-01 2021-06-15 Oracle International Corporation Flexible framework for secure search
US7725465B2 (en) 2006-03-01 2010-05-25 Oracle International Corporation Document date as a ranking factor for crawling
US7941419B2 (en) 2006-03-01 2011-05-10 Oracle International Corporation Suggested content with attribute parameterization
US20160055209A1 (en) * 2006-03-01 2016-02-25 Oracle International Corporation Flexible authentication framework
US8005816B2 (en) 2006-03-01 2011-08-23 Oracle International Corporation Auto generation of suggested links in a search system
US8027982B2 (en) 2006-03-01 2011-09-27 Oracle International Corporation Self-service sources for secure search
US20070283425A1 (en) * 2006-03-01 2007-12-06 Oracle International Corporation Minimum Lifespan Credentials for Crawling Data Repositories
US9177124B2 (en) 2006-03-01 2015-11-03 Oracle International Corporation Flexible authentication framework
US8214394B2 (en) * 2006-03-01 2012-07-03 Oracle International Corporation Propagating user identities in a secure federated search system
US8239414B2 (en) 2006-03-01 2012-08-07 Oracle International Corporation Re-ranking search results from an enterprise system
US10382421B2 (en) * 2006-03-01 2019-08-13 Oracle International Corporation Flexible framework for secure search
US20070250486A1 (en) * 2006-03-01 2007-10-25 Oracle International Corporation Document date as a ranking factor for crawling
US20100185611A1 (en) * 2006-03-01 2010-07-22 Oracle International Corporation Re-ranking search results from an enterprise system
US20160119321A1 (en) * 2006-03-01 2016-04-28 Oracle International Corporation Flexible authentication framework
US8332430B2 (en) 2006-03-01 2012-12-11 Oracle International Corporation Secure search performance improvement
US8352475B2 (en) 2006-03-01 2013-01-08 Oracle International Corporation Suggested content with attribute parameterization
US20070220268A1 (en) * 2006-03-01 2007-09-20 Oracle International Corporation Propagating User Identities In A Secure Federated Search System
US9081816B2 (en) 2006-03-01 2015-07-14 Oracle International Corporation Propagating user identities in a secure federated search system
US20070214129A1 (en) * 2006-03-01 2007-09-13 Oracle International Corporation Flexible Authorization Model for Secure Search
US20180124031A1 (en) * 2006-03-01 2018-05-03 Oracle International Corporation Flexible framework for secure search
US20070208744A1 (en) * 2006-03-01 2007-09-06 Oracle International Corporation Flexible Authentication Framework
US8433712B2 (en) 2006-03-01 2013-04-30 Oracle International Corporation Link analysis for enterprise environment
US9853962B2 (en) * 2006-03-01 2017-12-26 Oracle International Corporation Flexible authentication framework
US9251364B2 (en) 2006-03-01 2016-02-02 Oracle International Corporation Search hit URL modification for secure application integration
US20070209080A1 (en) * 2006-03-01 2007-09-06 Oracle International Corporation Search Hit URL Modification for Secure Application Integration
US20070208745A1 (en) * 2006-03-01 2007-09-06 Oracle International Corporation Self-Service Sources for Secure Search
US20170039282A1 (en) * 2006-03-01 2017-02-09 Oracle International Corporation Flexible authentication framework
US20070208714A1 (en) * 2006-03-01 2007-09-06 Oracle International Corporation Method for Suggesting Web Links and Alternate Terms for Matching Search Queries
US8595255B2 (en) 2006-03-01 2013-11-26 Oracle International Corporation Propagating user identities in a secure federated search system
US20070208734A1 (en) * 2006-03-01 2007-09-06 Oracle International Corporation Link Analysis for Enterprise Environment
US9479494B2 (en) * 2006-03-01 2016-10-25 Oracle International Corporation Flexible authentication framework
US20070208746A1 (en) * 2006-03-01 2007-09-06 Oracle International Corporation Secure Search Performance Improvement
US8626794B2 (en) 2006-03-01 2014-01-07 Oracle International Corporation Indexing secure enterprise documents using generic references
US8875249B2 (en) 2006-03-01 2014-10-28 Oracle International Corporation Minimum lifespan credentials for crawling data repositories
US8707451B2 (en) 2006-03-01 2014-04-22 Oracle International Corporation Search hit URL modification for secure application integration
US8725770B2 (en) 2006-03-01 2014-05-13 Oracle International Corporation Secure search performance improvement
US20070208713A1 (en) * 2006-03-01 2007-09-06 Oracle International Corporation Auto Generation of Suggested Links in a Search System
US9467437B2 (en) * 2006-03-01 2016-10-11 Oracle International Corporation Flexible authentication framework
US8868540B2 (en) 2006-03-01 2014-10-21 Oracle International Corporation Method for suggesting web links and alternate terms for matching search queries
US8676845B2 (en) * 2006-08-22 2014-03-18 International Business Machines Corporation Database entitlement
US20080052291A1 (en) * 2006-08-22 2008-02-28 Michael Bender Database entitlement
US9705670B2 (en) 2006-08-25 2017-07-11 Protegrity Corporation Data security in a disconnected environment
US9378392B2 (en) 2006-10-03 2016-06-28 Salesforce.Com, Inc. Methods and systems for controlling access to custom objects in a database
US20080082540A1 (en) * 2006-10-03 2008-04-03 Salesforce.Com, Inc. Methods and systems for controlling access to custom objects in a database
US8095531B2 (en) 2006-10-03 2012-01-10 Salesforce.Com, Inc. Methods and systems for controlling access to custom objects in a database
US10410013B2 (en) 2006-10-03 2019-09-10 Salesforce.Com, Inc. Methods and systems for controlling access to custom objects in a database
US20080097954A1 (en) * 2006-10-20 2008-04-24 Microsoft Corporation Ranged lookups
US8402017B2 (en) * 2006-12-08 2013-03-19 International Business Machines Corporation Method for altering database views dependent on rules
US20080140620A1 (en) * 2006-12-08 2008-06-12 Michael Bender Method for altering database views dependent on rules
US8443426B2 (en) 2007-06-11 2013-05-14 Protegrity Corporation Method and system for preventing impersonation of a computer system user
US7996392B2 (en) 2007-06-27 2011-08-09 Oracle International Corporation Changing ranking algorithms based on customer settings
US20090006356A1 (en) * 2007-06-27 2009-01-01 Oracle International Corporation Changing ranking algorithms based on customer settings
US8412717B2 (en) 2007-06-27 2013-04-02 Oracle International Corporation Changing ranking algorithms based on customer settings
US20090006359A1 (en) * 2007-06-28 2009-01-01 Oracle International Corporation Automatically finding acronyms and synonyms in a corpus
US8316007B2 (en) 2007-06-28 2012-11-20 Oracle International Corporation Automatically finding acronyms and synonyms in a corpus
US20090024570A1 (en) * 2007-07-20 2009-01-22 Oracle Internatonal Corporation User defined query rewrite mechanism
US20090089591A1 (en) * 2007-09-27 2009-04-02 Protegrity Corporation Data security in a disconnected environment
US8826449B2 (en) 2007-09-27 2014-09-02 Protegrity Corporation Data security in a disconnected environment
US8533775B2 (en) * 2008-06-13 2013-09-10 Hewlett-Packard Development Company, L.P. Hierarchical policy management
US20110093917A1 (en) * 2008-06-13 2011-04-21 Byron A Alcorn Hierarchical Policy Management
US8239396B2 (en) 2009-03-20 2012-08-07 Oracle International Corporation View mechanism for data security, privacy and utilization
US20100241641A1 (en) * 2009-03-20 2010-09-23 Oracle International Corporation View mechanism for data security, privacy and utilization
US8510334B2 (en) 2009-11-05 2013-08-13 Oracle International Corporation Lock manager on disk
US20110106778A1 (en) * 2009-11-05 2011-05-05 Oracle International Corporation Lock manager on disk
US9165125B2 (en) * 2012-06-13 2015-10-20 Mobilextension Inc. Distribution of dynamic structured content
US20130340043A1 (en) * 2012-06-13 2013-12-19 Mehrdad (John) Zarei Distribution of dynamic structured content
CN104050223A (en) * 2013-03-15 2014-09-17 国际商业机器公司 Pivot facets for text mining and search
CN104050223B (en) * 2013-03-15 2017-10-31 国际商业机器公司 Pivot face for text mining and search
US10180984B2 (en) 2013-03-15 2019-01-15 International Business Machines Corporation Pivot facets for text mining and search
US10277561B2 (en) * 2016-07-22 2019-04-30 International Business Machines Corporation Database management system shared ledger support
US10826878B2 (en) 2016-07-22 2020-11-03 International Business Machines Corporation Database management system shared ledger support
US10652248B2 (en) 2016-07-28 2020-05-12 Molecula Corp. Systems and methods of managing data rights and selective data sharing
US11425136B2 (en) 2016-07-28 2022-08-23 Molecula Corp. Systems and methods of managing data rights and selective data sharing
US20210350031A1 (en) * 2017-04-17 2021-11-11 EMC IP Holding Company LLC Method and device for managing storage system
US11907410B2 (en) * 2017-04-17 2024-02-20 EMC IP Holding Company LLC Method and device for managing storage system
US11232226B2 (en) * 2017-08-07 2022-01-25 Chengdu Qianniucao Information Technology Co., Ltd. Column value-based separate authorization method for statistical list operations
US11368466B2 (en) 2019-09-18 2022-06-21 David Michael Vigna Data classification of columns for web reports and widgets

Similar Documents

Publication Publication Date Title
US5751949A (en) Data security system and method
AU757061B2 (en) System and method for selectively defining access to application features
US7720894B2 (en) Internal security system for a relational database system
US7174345B2 (en) Methods and systems for auto-partitioning of schema objects
JP2634117B2 (en) Method and system for determining user access privileges for database objects
US6275825B1 (en) Data access control apparatus for limiting data access in accordance with user attribute
JP3851493B2 (en) Database search method, database search system, and computer-readable recording medium recording database search program
US20020093857A1 (en) System and method for managing information objects
US20030065673A1 (en) Method and device for marking and filtering data elements in a database
JP2006277756A (en) Method and apparatus for controlling access to database
US7933922B2 (en) Systems, methods and computer program products for automating retrieval of data from a DB2 database
Dinter et al. The OLAP market: state of the art and research issues
EP1450274A2 (en) Dimension-based partitioned cube
US8645313B1 (en) Systems and methods for enhanced SQL indices for duplicate row entries
US7555786B2 (en) Method for providing security mechanisms for data warehousing and analysis
US6810399B2 (en) Property extensions
JPH08185349A (en) Data security device
US7047234B2 (en) System and method for managing database access
US20020129037A1 (en) Method for accessing a database
US7177856B1 (en) Method for correlating data from external databases
Francett Decisions, decisions: users take stock of data warehouse shelves
Baier et al. Data management in a knowledge-based system for marketing research
JP2000187665A (en) Information deriving method and its system in data base system and storage medium
JPH06348562A (en) Data base control information management system
WO2004031989A1 (en) A database provider system

Legal Events

Date Code Title Description
AS Assignment

Owner name: MCI COMMUNICATIONS CORPORATION, DISTRICT OF COLUMB

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:THOMSON, ROBERT;GEIWITZ, ROGER;REEL/FRAME:007710/0160;SIGNING DATES FROM 19950926 TO 19951102

STCF Information on status: patent grant

Free format text: PATENTED CASE

FPAY Fee payment

Year of fee payment: 4

REMI Maintenance fee reminder mailed
FPAY Fee payment

Year of fee payment: 8

SULP Surcharge for late payment

Year of fee payment: 7

FPAY Fee payment

Year of fee payment: 12

FEPP Fee payment procedure

Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

AS Assignment

Owner name: VERIZON PATENT AND LICENSING INC., NEW JERSEY

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MCI COMMUNICATIONS CORPORATION;REEL/FRAME:028969/0416

Effective date: 20120917

AS Assignment

Owner name: TEKLA PEHR LLC, DELAWARE

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:VERIZON PATENT AND LICENSING INC.;REEL/FRAME:029368/0460

Effective date: 20120918