JP2005293196A - Database access control device and control method, customer information database system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To control access to a customer database in which access authority for accessing a customer database can be set from both user attributes and customer data attributes, and such user access authority can be easily managed. A method or apparatus is provided.
An access permission table and an access prohibition table are used instead of setting an access authority for each user group divided according to user attributes. The access permission and prohibition table creates a record using a user ID as a key. By doing so, the access authority for each user is determined. Further, the access permission table and the access prohibition table set whether or not the user can access the data depending on whether or not various data recorded in the database falls within a specific value range.
[Selection] Figure 4

Description

  The present invention relates to a database access control device and an access control method. In particular, this technique is useful for a system that requires fine-grained access management in a database system that needs to maintain high security, such as a database system that manages customer information.

  With the development of IT technology, various information is accumulated as digital data in various fields and used for computers. In order to improve customer service and promote sales, a customer information database that records and manages customer personal information, purchase (transaction) history information, etc. is constructed and recorded in this database from many client devices via the network. Companies that use systems that can access customer information are not uncommon. Such a customer information database system is a typical information system that handles personal information, and it is particularly required to maintain security. However, not only external security but also security for insiders (inside companies) is important. is there. In order to ensure the latter at a certain level, one of the important functions of the database system is an access authority management function.

  Here, the access authority refers to whether or not the user is permitted to read, rewrite, newly register, and delete the data recorded in the record for each record to be accessed, constituting the database. Or it is the information that defines it.

It is desirable that such an access authority management function can be managed efficiently and flexibly for each user. Here, “user” generally means a user who can access the database. However, in the case of a customer information database system, the officer / employee, employee, or part-time worker of a company (company) that manages the customer information database. It becomes the meaning of the person according to it. Patent Document 1 discloses a data management apparatus or database system provided with a mechanism capable of managing an access authority management function efficiently and flexibly for each user.
Japanese Patent Laying-Open No. 2003-30029 (FIGS. 1-4)

  In the case of a customer information database system, for example, when access control to data on a database is performed according to user attributes (affiliation, job title, business content, etc.), if the data management device described in Patent Document 1 is applied. For example, a group is formed for each user attribute, an access authority is provided for each group, and access control to a database of users belonging to the group is performed.

  FIG. 1 shows the configuration of such a conventional database system 1. The database system 1 is a system described in Patent Document 1, and includes a customer information database 20, an access control device 10, an access terminal 30 used by a user, and an authority setting terminal 40 used by a database administrator.

  The access control apparatus 10 includes a user table 12 that manages user information and group information, a group authority table 13 that manages access authority for each group, a table setting unit 14 that manages both tables, and data requests from users. The access control unit 11 searches the database in consideration of the access authority and returns the result. The access control device 10 is composed of, for example, a server type computer. The user table 12 and the group authority table 13 are configured on a storage device built in such a server computer. An example of the user table 12 and the group authority table 13 in the database system 1 is shown in FIGS. The access control unit 11 and the table setting unit 14 are application programs that run on the server computer. The access control unit 11 refers to the user table 12 and the group authority table 13 and actually issues an SQL command to the customer information database 20.

  Assume a customer information database 20 that manages customer data using a customer table 21 and a transaction status table 22 as shown in FIG. The user table 12 and group authority table 13 for users accessing the database are as shown in FIG. 3, for example. A user ID that uniquely determines a user is assigned to the user, and a group ID that uniquely determines the group is assigned to each group. The user must belong to one of the groups, and the group ID of the group to which the user belongs is registered in the user table record. For example, the user 9003 in FIG. 3 has a group ID “B” according to the user table 12, and therefore, among the data registered in the customer information database according to the description of the group ID “B” in the group authority table 13, Only the information of customers who are located in Kanagawa can be accessed.

Next, the processing operation of the database system 1 according to the prior art will be briefly described with reference to FIG.

<Access Control Unit> The user inputs his / her user ID and search conditions for information to be accessed from the access terminal 30. The access control unit 11 searches for the user's group ID from the user table 12 based on the user ID, acquires the access authority specified in the group authority table 13 based on the group ID, and sets the search condition entered by the user. Further, an SQL command is issued to the customer information database 20 under a search condition to which a search condition indicating a range matching the access authority is added. Therefore, after all, only the data to which the access authority is given is displayed on the access terminal 30 among the data hit by the search condition input by the user.

<Table Setting Unit> The table setting unit 14 is operated by the authority setting person from the authority setting terminal 40, changes user information including user addition / deletion / affiliation group ID change to the user table 12, and access authority to the group authority table 13. Add / delete / change groups and add / delete / change authority information.

  In the case of a general database system, such as when a product manufacturer, distributor, printing company, etc. accumulates data for product catalogs, the user attributes (the buyer of the product, the person in charge of purchasing materials, the person in charge of manufacturing) If the authority to access the stored data is determined by the person in charge of the person in charge, sales department staff, etc., the purpose of ensuring security is generally achieved. Therefore, the database management requirement specification for such a database system is satisfied by the method of access authority management of the database system 1 in which a group of users is defined and an access authority is set for each group. Alternatively, as described in FIG. 4 of Patent Document 1, the required specifications are satisfied by setting the access authority for each type of data included in the database by determining the type of operation permitted for the data. Is done.

  However, in the access control to the customer information database that handles personal information such as customer name and address information, the access authority setting for each group of users (in this case, the insider of the company) and the data type for each data type Permission settings that determine the types of operations allowed on data may not be sufficient. This is because personal information such as a telephone number may cause a significant disadvantage to the individual once it is leaked, and may require more detailed access restrictions.

  However, in the method of performing access control to the database for each user group, if the user wants to perform fine and flexible access control, a large number of groups with a small number of affiliated users are created. There is a problem that the management load such as control and group authority setting change increases.

In addition, as a potential problem of access control method for each group,
1) When the user and group information are additionally changed, it is necessary to modify two locations of the user table 12 and the group authority table 13;
2) Two other problems are that the user needs to make decisions during the authority setting process and the authority setting process cannot be fully automated. The reason why the automation of the process 2) is hindered is that when adding and changing user and group information, it is checked whether there is already a group having the same authority as the access authority to be added to the user. This is because it is necessary for the user to determine whether to use or create a new group. Further, when such a check is not performed, there is a problem that a plurality of groups having the same access authority appear and the group authority table becomes redundant.

The present invention was invented in view of such problems of the prior art,
Access control device for customer information database which can set access authority for both user attribute and customer data attribute when accessing customer information database, and can easily manage such user access authority Another object is to provide an access control method.

  In the present invention, the access authority is set and managed not by dividing the users into groups but managing the access authority for each group, but by assigning the access authority to each user individually. Instead of the group authority table, an access permission table and an access prohibition table are used, and the access permission and prohibition table determines the access authority for each user, for example, by creating a record using the user ID as a key. Further, the access permission table and the access prohibition table allow the user to set whether or not the data can be accessed depending on whether or not various data recorded in the database falls within a specific value range.

That is, the first invention of the present application for solving the above-described problems is
A user table for managing information on users accessing the database, an access permission table for managing user access permission information for the database, an access prohibition table for managing user access prohibition information for the database, and database management A table setting unit that accepts input from the user and manages these tables;
A data search request is received from a user, and the data search request is data within a range that matches the search condition and is permitted to be accessed by the user according to the designation of the access permission table, and An access control unit comprising: an access control unit that returns a result to the user as a search result of the database only for data that is not in a range in which the user is prohibited from accessing by designation of the access prohibition table.

  Here, in the database access control device, the access permission table includes information for identifying a registered user who can access the database and one or more specific fields of any of the access target records constituting the database. And the correspondence between the field value and the value that specifies the range of the field data value that permits access to the access target record in terms of the field.

  Further, in the database access control apparatus, the access prohibition table includes, as fields, information for identifying a registered user who can access the database, and one or more specific fields of any access target record constituting the database. And the correspondence between the field value and the value that specifies the range of the field data value that prohibits access to the access target record in terms of the field.

 The second invention of the present application that solves the above problem connects a customer information database, an access terminal used by a user, an authority setting terminal used by a database administrator, and a database access control device according to the first invention. This is a customer information database system configured as described above.

A third invention of the present application for solving the above-mentioned problem is a database access control method for a database system, and information for identifying a registered user permitted to access a database;
For one or more specific fields of any access target record constituting the database, the value of the field data that permits or prohibits access to the access target record in terms of the field as the value of the field By providing an access condition setting table that records the correspondence with the value that specifies the range, the access authority of the database user is referred to the data recorded in that record by the value of the specific attribute of the record handled by this database, It is a database access control method characterized by determining whether or not to allow an operation type including update, registration, and deletion.

  Here, the access condition setting table is a generic name of an access permission table and an access prohibition table. Alternatively, a value that specifies a range of field data values and a code that indicates whether the range specified by the value is an access-permitted range or an access-prohibited range are recorded as a pair, and accessed in one table. You may comprise so that it may serve as two tables of permission and access prohibition.

  In the database access control method of the database system including the database according to the third invention, the access authority of the database user may be determined for each individual user.

  A fourth invention of the present application that solves the above problem is a computer program that describes a series of instructions for causing a computer to operate as the database access control device according to the first invention by being incorporated in the computer.

A fifth invention of the present application for solving the above problem is a computer-readable recording medium storing a computer program in which a series of instructions for operating a computer as a database access control device according to the first invention by being incorporated in a computer is recorded. is there.

By managing access authority for each user, users can be divided into several groups, and authority can be freely added / deleted without being affected by other users and affiliation information, compared to the conventional method of managing authority for each group. Therefore, it is not necessary to search for an optimal user group, the authority setting process is facilitated, and the authority management load can be reduced. Compared to the conventional access control method that used two primary keys, user table and group authority table, access authority can be acquired / changed / added / deleted with one key, access control and authority setting processing Is simplified. In addition, since the access authority can be controlled by the value of the specific attribute data of the access target record, access to data to be managed strictly can be individually set for each user, so that the security level for the insider can be maintained at a high level.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 4 is an overall configuration diagram of the database system 2 according to an embodiment of the present invention. The database system 2 includes a customer information database 20, an access control device 10, an access terminal 30 used by a user, and an authority setting terminal 40 used by a database administrator. This basic configuration is the same as the database system 1 described in the prior art. The access control device 10 is usually realized by a server computer. The access control device 10 includes a user table 12 that manages user information of users who access the customer information database 20, an access permission table 15 that manages access permission information for each user with respect to the customer information database 20, and a customer information database. 20, an access prohibition table 16 that manages access prohibition information for each user, a table setting unit 14 that manages these tables, and a database search result in consideration of access authority in response to a data search request from a user It is comprised by the access control part 11 which returns.

The authority setter uses the authority setting terminal 40 to add / update / delete records in the user table 12, the access permission table 15, and the access prohibition table 16 via the table setting unit 14, and is given to the user and the user. Set and manage access rights.

A user who browses the customer information database 20 makes a data request to the access control unit 11 from the access terminal 30 and can browse data that can be browsed according to the access authority. In addition, data update, deletion / addition, etc. of the customer information database 20 can be performed according to the access authority.

Here, in order to facilitate understanding of the following explanation, the customer information database 20 manages customer attribute information including a customer ID and personal information / company information for uniquely determining a customer, as shown in FIG. A customer table 210, a transaction information table 220 for managing transaction information and detailed information, a distribution document management table 230 for managing a distribution history when an electronic document is distributed to each company, and the like are assumed. It is assumed that the customer table 210, the transaction information table 220, the distribution document management table 230, and the like have a parent-child relationship and are linked using a customer ID as a key. (In addition, in various general customer information databases, there is a customer information database that includes only the customer table 210 and no child table.)

In the following description of the embodiment, the user table 12, the access permission table 15, and the access prohibition table 16 are described as being configured as one database. In the following description, a database that implements the user table 12, the access permission table 15, and the access prohibition table 16 is referred to as a “user management database”.
FIG. 6 is a diagram illustrating a schema example of the user table 12, the access permission table 15, and the access prohibition table 16. In the user table 12, in addition to a user ID for uniquely identifying a user, attribute information such as a user name, a department, and a post is registered. In the access permission table 15, user permission and access permission information indicating conditions of customer information accessible to each user are registered. In the access permission information, the field name of the customer information database is designated as the field name, and the condition for accessing the field value is designated. The meaning of access permission conditions varies depending on the data type of the field. If the field is a character string type, a partial match comparison is performed between the actual data and the value specified as the access permission condition. If the field matches, the access to the data is permitted. If the field is a numeric type, the value specified as the access permission condition means the lower limit value of the accessible numeric range. In the case of the date type, the value specified as the access permission condition means the start value of the access permission period.

  In the access prohibition table 16, access prohibition information indicating a user ID and access prohibition conditions for each user is registered. In the access prohibition information, the field name of the customer information database is specified as the field name, and the access prohibition condition is specified as the field value. Access prohibition conditions differ depending on the data type of the field. If the field is a character string type, partial match comparison is made between the actual data and the value specified as the access prohibition condition. Forbidden. If the field is a numeric type, the value specified as the access prohibition condition means the lower limit value of the numerical range for which access is prohibited. In the case of the date type, the value specified as the access prohibition condition means the start value of the access prohibition period. If both tables have empty values, there are no access permission / prohibition conditions for that field.

  Next, the operation of the access control unit 11 and the control of access permission / prohibition conditions will be described. For example, the access permission condition of the user 9001 in FIG. 6 is a customer whose “location” is “Tokyo”, and the access prohibition condition is a customer whose “average transaction amount” is “500,000 yen or more”. Yes. The user can access customer information that satisfies the access permission condition and does not correspond to the access prohibition condition. Therefore, the user 9001 can access only the information of customers with customer IDs 0002, 0003, and 0006. Customer IDs 0001, 0004, and 0005 cannot be accessed because the average transaction amount is 500,000 yen or more.

  Next, access control when both the access permission condition and the access prohibition condition are specified will be described. For example, the access permission condition of the user 9002 in the figure is a customer whose “location” is “Tokyo”, and the access prohibition condition is that “document type” is “contract”. In this case, the user 9002 can access the information in the customer table 210 and the transaction table 220 of the customers whose customer IDs are 0001 to 0006, but the document type of each record in the distribution document management table 230 is “contract”. The records that are related to the customers with IDs 0001 to 0006 cannot be accessed.

  Next, operations of the access control unit 11 and the table setting unit 14 will be described. In order to use the access control apparatus 10, authentication using a user ID, a password, or the like can be considered, but here, the authentication procedure is not particularly described because only a well-known procedure is used.

  FIG. 7 is a block diagram illustrating the operation flow of the access control unit 11. First, the user inputs his / her user ID and search conditions for information he / she wants to browse and transmits it to the access control unit (S10). Then, the access control unit 11 accepts a data request from the user sent from the access terminal 30 (S12). Next, the access control unit 11 refers to the access permission table 15 and the access prohibition table 16 using the received user ID as a key, and acquires the access authority of the user (S14). The access control unit 11 searches the customer information database 20 in accordance with the request data search condition received in step S12, and further acquires data corresponding to the access authority of the user acquired in step S14 from the extracted data, that is, an access permission table. In step S16, data that is permitted to be accessed in step S1 and that does not correspond to the access prohibited data is selected from the access prohibited table. The access control unit 11 displays the final selection result on the access terminal 30 as a search result for the accepted search request. If there is no data corresponding to the search condition and there is no corresponding data in the final selection result, the fact is displayed on the access terminal (S18).

In step S16, the SQL statement issued from the access control unit 11 to the customer information database 20 is as follows.
Slect * from Search target table
where Search criteria entered by the user
and user permission conditions
If it is not necessary to describe the logical negation of “and (user access prohibition condition)” or the above “search condition input by the user”, it is as follows.
Slect * from Search target table
where user permission conditions
Logical negation of and (user access prohibition condition)

For example, when the user 9001 in FIG. 6 obtains all records in the transaction status table whose transaction year field value is 2001,
Slect * from Trading Status Table
where trading status table, trading year = '2001'
and customer table.Location = 'Tokyo'
and customer table, average transaction amount <500000
The following SQL statement is issued.

For example, when the user 9002 in FIG. 6 acquires all the records of the distribution document management table,
Slect * from Distribution document management table
where customer table, where = 'Tokyo'
and Distribution document management table.Document type <>'Contract'
The following SQL statement is issued. <> Means not equal.

  Next, the table setting unit 14 will be described. The table setting unit 14 adds / deletes / changes attribute information to / from the user table 12 and adds / changes / deletes access authority to the access permission table 15 / access prohibition table 16. This process is performed from the authority setting terminal 40 by the authority setting person. In particular, since there is no group-based access authority management, the authority setter need not consider what access authority is assigned to the user's group or existing group. Therefore, unlike the conventional method in which decision making by the user is necessary during the table setting process, the authority setting process is almost automated and the load on the user can be reduced.

  As operations of the table setting unit, user addition, user access authority change, and multiple user access authority batch change are taken as an example, and the processing flow is shown in FIGS. 8 to 10, respectively. For reference, FIGS. 15 to 17 show examples of processing flows when the same operation is performed by the conventional method.

  The user addition process will be described with reference to FIG. The authority setting person inputs user information and access permission / prohibition information of the user to be added from the authority setting terminal 40 (S20). The table setting unit 14 receives the input user information / access permission / prohibition information (S22). The table setting unit 14 checks the contents of the received data, and confirms whether there is any data deficiency or operation error (S24). For example, it is checked whether the data type and the range of the specified value are appropriate for the type of field (record attribute item) specified for access restriction. When it is determined in step S22 that the input data is correct, the table setting unit 14 adds a record to each table (S26).

For example, when adding a new user 9003 to the table of FIG. 6, the authority setting person inputs the following information from the authority setting terminal 40 in step S20.
User table User ID: 9003
Last name: Takahashi
Affiliation: Employee access permission table User ID: 9003
Location: Kanagawa Access Prohibited Table User ID: 9003
Average transaction amount: 500,000

Then, in step S26, the table setting unit 14 issues the following three SQL statements to the user management database.
Insert into user table (user ID, surname, affiliation) value ('9003', 'Takahashi', 'Employee')
Insert into access permission table (user ID, location) value ('9003', 'Kanagawa')
Insert into access prohibition table (user ID, average transaction amount, document type)
value ('9003', 500000, NULL)

  FIG. 15 is a flowchart for explaining user addition processing similar to that in FIG. 8 in the configuration of the database system 1 of the prior art shown in FIG. 1 for comparison.

In FIG. 15, first, the authority setting person inputs user information and access authority information of the user to be added from the authority setting terminal 40 (S30). The table setting unit 14 receives the input user information / access authority information (S32). The table setting unit 14 checks the contents of the received data, and confirms whether there is a data deficiency or an operation error (S34).
The access authority information in this case refers to reference, rewrite, new registration, and deletion for each type of data handled by a database such as material data, bibliographic data, or correction instruction data as described in FIG. It is characterized from the viewpoint of whether or not it can be performed.
Next, the table setting unit 14 refers to the group authority table 13 as shown in FIG. 3 of Patent Document 1 to determine whether there is an existing user group having the same access authority as the designated access authority information. A search is made (S36). If such an existing group exists, the user is notified of the group. If not, a notification to that effect is sent (S38). If there is an existing group, the user selects one of the user groups (S40). Then, the information on the selected user group is updated in the user table, and the user group record itself is also updated (S52). If there is no existing group, the user requests registration of a new group (S42). Upon receiving a new group registration request from the user, the table setting unit 14 checks for duplicate group names and authority (S44, S46). If there is no problem, the new group name is registered and the new group is assigned group authority. It is additionally registered in the table (S48, S50). The table setting unit 14 updates the information on the newly established user group to the user table (S52).

  Comparing FIG. 8 and FIG. 15, it can be seen that the process in the database system 2 can simply perform the user addition process.

  Next, the process of changing the user authority will be described with reference to FIG. The authority setter inputs the user ID of the user to be changed and the changed authority information from the authority setting terminal 40 (S60). The table setting unit 14 receives the input target user ID and access permission / prohibition information (S62). The table setting unit 14 checks the contents of the received data and confirms whether there is any data deficiency or operation error (S64). When it is determined in step S62 that the input data is correct, the table setting unit 14 changes the corresponding record in the access permission table 15 and the access prohibition table 16 (S66).

As an example, when updating the user information of the user 9002 in the table of FIG. 6, the authority setting person inputs the user ID: 9002 from the authority setting terminal 40 in step S60. Then
User table User ID: 9002
Surname: Suzuki
Affiliation: Employee access permission table User ID: 9002
Location: Tokyo Access Denied Table User ID: 9002
Document type: Contract is displayed on the authority setting terminal 40. Therefore, for example, when adding a condition of an average transaction amount of 500,000 yen (or more) to the access prohibition condition and deleting the access prohibition condition depending on the document type at the same time, in step S60, “ Delete the indication “Document type: Contract” and enter “Average transaction amount: 500000” instead. As a result, in step S66,
Update access prohibition table set Average transaction amount = 500000, Document type = NULL
where user ID = '9002'
Is issued from the table setting unit 14 to the user management database.

  FIG. 16 is a flowchart for explaining a process for changing user authority similar to that in FIG. 9 in the configuration of the database system 1 of the prior art shown in FIG. 1 for comparison.

  First, the authority setter inputs the user ID of the user to be changed and the changed authority information from the authority setting terminal 40 (S70). The table setting unit 14 receives the input user ID / access authority information (S72). Next, the table setting unit 14 searches the group authority table 13 for an existing user group having the same access authority as the access authority information specified to be changed (S74). If such an existing group exists, the user is notified of the group. If not, a notification to that effect is sent (S76). If there is an existing group, the user selects one of the user groups (S78). Then, the information on the selected user group is updated in the user table, and the user group record itself is also updated (S90). If there is no existing group, the user requests registration of a new group (S80). Upon receiving a new group registration request from the user, the table setting unit 14 checks for duplicate group names and authority (S82, S84). If there is no problem, the new group name is registered (S86). Are additionally registered in the group authority table (S88). The table setting unit 14 updates the information on the newly established user group to the user table (S90).

  Comparing FIG. 9 and FIG. 16, it can be seen that the process in the database system 2 can simply perform the user authority change process.

  An advantage of performing access authority management in units of groups in the conventional system (database system 1) is that authority of a plurality of users can be changed at a time. The database system 2 does not perform access authority management by group, but nevertheless, authority changes of a plurality of users can be performed as follows.

  A process for collectively changing the authority of a plurality of users will be described with reference to FIG. The authority setter searches the authority setting terminal 40 for the user to be changed based on the user ID and attribute information (S100). The table setting unit 14 accepts the input user search conditions (S102). The table setting unit 14 searches the user table 12, acquires the corresponding user, and displays the corresponding user list on the authority setting terminal 40 (S104). The authority setter selects the change target user at the authority setting terminal 40 and inputs an access authority change instruction (S106). The table setting unit 14 receives the input change target user and the access authority change instruction (S108). The table setting unit 14 checks the contents of the received data, and confirms whether there is a data deficiency or an operation error (S110). When it is determined in step S110 that the input data is correct, the table setting unit 14 changes the corresponding record in the access permission table 15 and the access prohibition table 16 (S112).

The user addition process and the user authority change process in the database system 2 have been described above in comparison with the database system 1. In the following embodiments, the use of the access control device 10 according to the present invention enables flexible authority settings to be set for each user in the customer information database 20, the access permission table 15, and the access prohibition table 16. A description will be given using a schema as an example.

<Use Example at Customer Center> Consider the authority at the customer center to access the customer information database 20 shown in FIG. It is assumed that there are a plurality of operators (hereinafter referred to as users) in the customer center, and the charge is divided according to the location of the customer company. In addition, it is assumed that access to customer company information is restricted by the user's job title (employee / part-time job). FIG. 11 shows the access permission table 15 and the access prohibition table 16 in such a case. For example, the user 9001 can access information of all customers whose “location” field value in the customer table is “Tokyo”. In addition, in the case of the user 9004, it is possible to access information of a customer whose “location” field is “Tokyo” and whose value of the “transaction amount” field of the transaction status table is “less than 2,000,000 yen”.

<Usage example at a sales office> Consider the access authority in the usage at a sales office that handles business-to-business transactions to the customer information database 20 shown in FIG. FIG. 12 is a diagram showing a schema example of an access permission / prohibition table in a usage method in which a sales person changes depending on a transaction amount with a business partner.

  In FIG. 12, an area where access authority can be assigned is determined for each user. For example, users 9001 to 9003 can access information on customer companies whose “transaction amount” is “5,000,000 yen or more”, and users 9004 and 9005 are prohibited from accessing. Due to the setting of the transaction amount in Table 16, it is not possible to access information of customer companies whose “transaction amount” is “5,000,000 yen or more”. Also, part-time workers (user IDs 9006 to 9007) who work at this sales office cannot access information on customer companies whose “transaction amount” is “2,000,000 yen or more” by setting the transaction amount in the access prohibition table 16. In addition, it is possible to access information of customer companies whose “transaction amount” is “less than 2,000,000 yen”, but among those customer information, information whose “document type” is “contract” cannot be accessed.

In this way, the access authority to the customer information database can be finely controlled in accordance with the user's skill and job title.

<Example of Use at Agents and Sales Offices> Consider the authority to access the customer information database 20 shown in FIG. In the agency or the sales office, since the customer in charge of each sales person is determined, the sales ID in charge is added to the information in the customer table 20. The sales representative ID corresponds to the user ID shown in FIG. 13 and represents that one sales representative is always attached to the customer. The sales person in charge is responsible for a plurality of customers. In the user table of FIG. 13, it can be seen that the agency and the sales office are composed of hierarchical positions.

  When the organization is hierarchical in this way, sales representatives who are general employees need only be able to access the information of their own customers, but the senior manager of the sales representative is informed about the information of the sales representative who is a subordinate. Must be accessible. Even if the hierarchical structure becomes deeper, this access mechanism does not change.

  For example, it is assumed that there is a sales office in each district such as Kanto and Tohoku, and each department in the sales office is in charge of customers in each prefecture in the district. A sales person 9001 whose job title is a general employee can view only the information of customers whose “Sales ID” in the customer table is “9001”. Further, since the section manager 9701 who is the superior of the sales staff 9001 and 9002 needs to browse the information of his subordinates, the contents of the access permission table 15 are as shown in FIG. Then, record two records, “9001” and “9002”.

  Furthermore, in order to enable the managers of each department to view information of all customers in charge of the department, the location field of the customer information table is the name of the prefecture in charge of the department. As for the user 9901, a record written as Tokyo and a record written as Kanagawa are recorded in the location field. As a result, “Takahashi Director” who is the user 9901 can view information of all customers in charge of the sales offices in Tokyo and Kanagawa.

  The access control apparatus according to the present invention has been described in detail above by explaining the database system 2. Also, the access control method according to the present invention has been described through the description of the access control apparatus. In the description of the access permission table 15 and the access prohibition table 16 of the database system 2, the access permission (prohibition) information is “specify the field name of the customer information database in the field name and access the field value (prohibit access). ) Specify the condition.If the field is a numeric type, the value specified as the access permission (prohibition) condition means the lower limit value of the accessible (prohibited access) numeric range. ” The gist of the invention is not limited to the construction and use of the tables 15 and 16 as described above. The idea of the present invention is to allow the user's access authority to be managed by the value of the data recorded in the database itself. For example, the value set for the average transaction amount in the access prohibition table of FIG. The access control unit 11 may be configured to set a pair of an upper limit value and a lower limit value and handle a range determined by these two values as access prohibition.

  Further, only one of the access permission table and the access prohibition table may be provided. In addition, a single table can be accessed by recording a pair of a value specifying a field data value range and a code indicating whether the specified range is an access-permitted range or an access-prohibited range. You may comprise so that it may serve as two tables of permission and access prohibition. Such structural differences do not depart from the spirit of the present invention.

In addition, as described in the database system 2, the access permission condition and the access prohibition condition for a certain user may be determined for each user by specifying a user ID. For each group of users, it can be defined as a table that defines whether or not access is possible by the value of a specific field of the access target record. Even in the configuration of the database system based on such a definition, one feature of the present invention is realized in which users accessing a record including the data can be limited by the value of the data recorded in the database.

It is a figure which shows the structure of the database system 1 of a general prior art. Customer information database 20 for managing customer data by means of customer table 21 and transaction status table 22 It is a figure which shows the example of a schema of the user table 12 and the group authority table 13. 1 is an overall configuration diagram of a database system 2 according to an embodiment of the present invention. It is a figure which shows the schema example of the customer database. It is a figure which shows the example of a schema of the user table 12, the access permission table 15, and the access prohibition table 16. FIG. 4 is a block diagram for explaining an operation flow of an access control unit 11. It is a figure explaining a user addition process. It is a figure explaining the process which changes a user's authority. It is a figure explaining the process which changes the authority of multiple users collectively. 6 is a diagram illustrating an access permission table 15 and an access prohibition table 16 according to the first embodiment. FIG. It is a figure explaining the access permission table 15 and the access prohibition table 16 in Example 2. FIG. It is a figure explaining the user table in Example 3, and an access permission table. It is a figure explaining the schema of the customer information database 20 in Example 3. FIG. FIG. 9 is a flowchart for explaining user addition processing similar to that in FIG. 8 in the configuration of the database system 1 according to the related art. 10 is a flowchart for explaining processing for changing the authority of a user similar to that in FIG. 9 in the configuration of the database system 1 of the prior art.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Database system 2 Database system 10 Access control apparatus 11 Access control part 12 User table 13 Group authority table 14 Table setting part 15 Access permission table 16 Access prohibition table 20 Customer information database 30 Access terminal 40 Authority setting terminal

Claims (7)

A user table for managing information on users accessing the database, an access permission table for managing user access permission information for the database, an access prohibition table for managing user access prohibition information for the database, and database management A table setting unit that accepts input from the user and manages these tables;
A data search request is received from a user, and the data search request is data within a range that matches the search condition and is permitted to be accessed by the user according to the designation of the access permission table, and An access control unit that returns a result to the user as a search result of the database, only data that is not in a range where the user is prohibited from accessing by specifying the access prohibition table;
A database access control device. The access control apparatus according to claim 1, wherein the access permission table includes information for identifying a registered user who is permitted to access a database.
For one or more specific fields of any access target record constituting the database, a field data value range that allows access to the access target record is specified from the viewpoint of the field as the field value. A database access control device that records the correspondence with values. The access control device according to claim 1, wherein the access prohibition table includes information for identifying a registered user who is permitted to access a database;
For one or more specific fields of any of the access target records constituting the database, a field data value range that prohibits access to the access target record in terms of the field is specified as the field value. A database access control device that records the correspondence between values.  A customer information database, an access terminal used by a user, an authority setting terminal used by a database administrator, and the database access control device according to any one of claims 1 to 3, are connected to each other. Customer information database system. A database access control method for a database system, comprising:
Information identifying registered users authorized to access the database;
For one or more specific fields of any access target record constituting the database, the value of the field data that permits or prohibits access to the access target record in terms of the field as the value of the field By providing an access condition setting table that records the correspondence with the value that specifies the range, the access authority of the database user is referred to the data recorded in that record by the value of the specific attribute of the record handled by this database, A database access control method characterized in that it can be determined whether or not to permit an operation type including update, registration, and deletion.   A computer program in which a series of instructions for causing a computer to operate as the access control device according to any one of claims 1 to 5 is incorporated into the computer. A computer-readable recording medium storing a computer program in which a series of instructions for operating the computer as an access control device according to any one of claims 1 to 5 by being incorporated in the computer is recorded.

Images