The present invention relates to database systems, and more particularly to confidential data encryption in database systems.
Just as computers have become more and more prevalent in everyday life, networks of linked computers have become important in distributing information amongst computer users. Many computer systems are organized according to a client/server metaphor. Generally, in client/server computing, end users are each provided with a desktop computer or terminal known as a “client.” The clients are connected using a network to another computer known as a “server”, because its general function is to serve or fulfill requests submitted by clients. Application programs running on the clients prepare requests and transmit them to the server over the network. A ‘network’ of computers can be any number of computers that are able to exchange information with one another. The computers may be arranged in any configuration and may be located in the same room or in different countries, so long as there is some way to connect them together (for example, by telephone lines or other communication systems) so they can exchange information. Just as computers may be connected together to make up a network, networks may also be connected together through tools known as bridges and gateways. These tools allow a computer in one network to exchange information with a computer in another network.
Of particular interest in today's computing environment are relational database applications. Relational DataBase Management System (RDBMS) software using a Structured Query Language (SQL) interface is well known in the art. The SQL interface has evolved into a standard language for RDBMS software and has been adopted as such by both the American Nationals Standard Organization (ANSI) and the International Standards Organization (ISO).
In RDBMS software, all data is externally structured into tables. The SQL interface allows users to formulate relational operations on the tables either interactively, in batch files, or embedded in host languages such as C, COBOL, etc. Operators are provided in SQL that allow the user to manipulate the data, wherein each operator operates on either one or two tables and produces a new table as a result. The power of SQL lies in its ability to link information from multiple tables or views together to perform complex sets of procedures with a single statement.
The power of being able to gather, store, and relate information in database systems and then operate on that information through SQL allows for an almost limitless range of applications for such technology. Together with computer networks, including the Internet, incredible opportunities exist for people and businesses to communicate and to conduct commerce. Concerns arise with these opportunities, particularly with regard to ensuring confidentiality of personal information, sensitive communications, and financial data.
For example, users sometimes are required to input personal information, such as credit card information, for processing within a website. While security techniques may be used during the transmission of the data, within the database receiving and storing the information, the information remains accessible to the database administrator (DBA). A DBA refers to an individual who is responsible for the design, development, operation, safeguarding, maintenance, and use of a database. Unfortunately, the accessibility of the confidential, personal information of a user creates an opportunity for intruders/malicious DBAs to misuse the information.
Accordingly, a need exists for a technique that provides users with a straightforward and flexible manner of protecting confidential information within a database. The present invention addresses such a need.
The present invention provides aspects for integrating encryption functionality into a database system. The aspects include providing at least two functions to support data encryption in a database system. The at least two functions are utilized within structured query language statements to preserve confidentiality of user-specified data in the database system.
Through the aspects of the present invention, users have better assurance that data private to a database application remains inaccessible to others, such as database administrators. Further, the provision of the encryption functionality of the present invention in an integrated manner with SQL creates a substantially unlimited range of database environments within which the present invention may be used. These and other advantages of the aspects of the present invention will be more fully understood in conjunction with the following detailed description and accompanying drawings.
The present invention relates to protection of confidential data within a database by a user. The following description is presented to enable one of ordinary skill in the art to make and use the invention and is provided in the context of a patent application and its requirements. Thus, the present invention is not intended to be limited to the embodiment shown, but is to be accorded the widest scope consistent with the principles and features is described herein.
As shown in
Computer system 1c has a processor 13 for controlling the overall operation of the computer system 1c, a high speed cache memory 12, a long-term storage device 14 (e.g., hard disk drive), and a database management system 15, e.g., an RDBMS system, such as DB2.
In accordance with the present invention, functions are provided that achieve privacy and user control of access to data in the database system 15, so that only users with the proper access and password can view the data. These functions are integrated into the database system 15 to allow access via SQL statements executed in the database system 15. The integration of the functionality into the database system 15 with the present invention occurs through a straightforward approach that can be utilized as desired with any client application of the database, as described in more detail hereinbelow.
Referring to the diagrams of
By way of example, suppose a table exists for social security numbers (SSN) of employees (EMP) of a company in the database system 15. The following example SQL statements illustrate the use of the encrypt and decrypt functions and encryption password in accordance with the present invention to ensure confidentiality with such a table.
In a further embodiment, the encrypt function 20 may encrypt a password hint, as well. A password hint refers to a phrase that assists data owners in remembering their passwords. With the ability to encapsulate password hints, another function, GETHINT, can be defined that returns an encapsulated password hint.
When the inclusion of a hint for the password is desired, such as the use of the hint “WASHINGTON” for remembering the password of “GEORGE”, the insert statement for the example becomes:
As demonstrated by the example, the encrypt function 20 and decrypt function 22 preferably follow the basic formats:
With the encryption techniques using a password as an encryption key, the present invention provides a straightforward and flexible technique to protect confidential data in a database in a manner that allows integration with well-established, non-proprietary SQL techniques. Accordingly, users have better assurance that data private to a database application remains inaccessible to others, such as database administrators. Further, the provision of the encryption functionality of the present invention in an integrated manner with SQL creates a substantially unlimited range of database environments within which the present invention may be used.
Although the present invention has been described in accordance with the embodiments shown, one of ordinary skill in the art will readily recognize that there could be variations to the embodiments and those variations would be within the spirit and scope of the present invention. Accordingly, many modifications may be made by one of ordinary skill in the art without departing from the spirit and scope of the appended claims.
Number | Name | Date | Kind |
---|---|---|---|
4993069 | Matyas et al. | Feb 1991 | A |
5003597 | Merkle | Mar 1991 | A |
5056142 | Lapointe et al. | Oct 1991 | A |
5301231 | Abraham et al. | Apr 1994 | A |
5425102 | Moy | Jun 1995 | A |
5713018 | Chan | Jan 1998 | A |
5963947 | Ford et al. | Oct 1999 | A |
5966707 | Van Huben et al. | Oct 1999 | A |
5978482 | Dwork et al. | Nov 1999 | A |
6002769 | McGough | Dec 1999 | A |
6038317 | Magliveras et al. | Mar 2000 | A |
6178243 | Pomerantz et al. | Jan 2001 | B1 |
6185681 | Zizzi | Feb 2001 | B1 |
6275939 | Garrison | Aug 2001 | B1 |
6360322 | Grawrock | Mar 2002 | B1 |
6389535 | Thomlinson et al. | May 2002 | B1 |
6421703 | Steinmetz et al. | Jul 2002 | B1 |
6442559 | Martinsen et al. | Aug 2002 | B1 |
6446115 | Powers | Sep 2002 | B2 |
6463418 | Todd | Oct 2002 | B1 |
6502102 | Haswell et al. | Dec 2002 | B1 |
6618806 | Brown et al. | Sep 2003 | B1 |
6633875 | Brady | Oct 2003 | B2 |
6711575 | Applewhite et al. | Mar 2004 | B1 |
6785810 | Lirov et al. | Aug 2004 | B1 |
6874001 | Narang et al. | Mar 2005 | B2 |
7093137 | Sato et al. | Aug 2006 | B1 |
20060053112 | Chitkara et al. | Mar 2006 | A1 |
Number | Date | Country |
---|---|---|
WO0113572 | Feb 2001 | WO |
Number | Date | Country | |
---|---|---|---|
20020129260 A1 | Sep 2002 | US |