JPH07295876A - Access right controlling device - Google Patents

Abstract

PURPOSE:To comprehensively control an access right in the access right controlling device of a file system. CONSTITUTION:An access right judging part 16 compares information related to the attribute value of a file controlled by an access right control part 13, the access right investigated by an access right investigating part 14 with the attribute value of the file read by an attribute reading part 15, and judges whether or not the attribute value appendant to the object file to be accessed or the access right of a user is included in the information related to the attribute value of the file read from the access right control part 13, and when the attribute value or the access right is included in the information related to the attribute value, it is judged that there is no access right for the file, and the part 16 informs an access instruction receiving part 12 of that the user having issued an access instruction has no access right.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an access right management device for managing security of a file system.

In this specification, access includes various operation operations on a file.

[0003]

2. Description of the Related Art In a conventional file system, access control to a file is judged by attributes such as an access right and a password set for each file.

In Unix, for example, as shown in FIG. 10, Read right, Write right, and Exec right for each file.
There are three access rights of the ute right, and it is possible to set permission / inhibition of access for each of the three users, “self”, “own group”, and “other”. In FIG. 10, all access rights are set for the file manager (self), only the Read right is assigned to the belonging group, and all access rights are restricted to others.

In addition, in password-based access control, a password is set in advance in a file,
When an access request is made to a file, the password set in the file is requested to be input, and access is permitted only when the password is correct.

[0006]

By the way, since the information about the access right is set in each file,
When you want to restrict access to the entire file, for example, access control such as "everyone cannot access the file created on or after 1993", or "all users do not have access to the file with title A". When doing, the access right must be set for each file, which requires a lot of trouble and time.

An object of the present invention is to provide an access right management device capable of comprehensively managing access rights.

[0008]

In order to solve the above-mentioned problems, an access right management device according to the present invention includes an attribute value holding means for holding information on an attribute value of a file which is a target of access control, and a user access. Attribute value determining means for determining whether or not the attribute value associated with the file that is the target of the command is included in the attribute value or the range of attribute values of the file held by the attribute value holding means; It is characterized by comprising an access right decision means for deciding whether or not there is an access right to the file with reference to the result of the decision by the means.

The attribute values associated with the file include, for example, creation date / time, creator, title name, and the like. The information about the attribute value of the file to be access-controlled means the value such as the creation date and time and the creator, or the range of the value.

[0010]

When the access command is issued by the user, the attribute value determination means reads the attribute value associated with the file targeted by the user's access command from the file, and the attribute value holding means targets the access command. Read the information about the attribute value of the file. Then, it is determined whether or not the attribute value associated with the file that is the target of the user's access command is included in the attribute value or the range of attribute values of the file read from the attribute value holding unit. As a result of the judgment by the attribute value judging means, when the attribute value attached to the file is included in the attribute value of the file or the range of the attribute value, the user who issued the access command accesses the file. It is determined that there is no right (or access right).

According to this, by setting a specific value or a range of values for the attribute value associated with the file as information relating to the attribute value of the file, access to the file is made by date of creation, creator, title. Since it can be controlled by the attribute such as the name, it is possible to comprehensively manage the access right of the entire file.

[0012]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of a file management system to which an access right management device according to the present invention is applied will be described below with reference to the drawings.

FIG. 1 is a block diagram showing the functional configuration of the file management system 1 in this embodiment. In the figure, 11 is a file system, 12 is an access command receiving unit, 13 is an access right management unit, 14 is an access right examining unit, 15 is an attribute reading unit, and 16 is an access right judging unit. Of these, the access right management unit 13, the access right inspection unit 14, the attribute reading unit 15, and the access right determination unit 16 constitute the access right management apparatus 10.

The file system 11 manages a plurality of files according to a file management process. The file stored in the file system 11 is composed of a file content part such as text data and image data, and an attribute part of the file such as creation date and time, creator, and title name. When the user who has issued the access command has the access right, the access command of the user is passed from the access command receiving unit 12 to the file system 11, and thereafter, the file access by the user is performed via the operation executing unit (not shown). .

The access command receiving unit 12 receives an access command to the file system 11 from the user, and passes this access command to the access right management device 10 once. When the access right management device 10 receives a determination that the user who issued the access command has the access right, the access command from the user is passed to the file system 11. When the user receives the determination that he does not have the access right, the access instruction from the user is not passed to the file system 11.

The access right management unit 13 has an attribute identifier for identifying an attribute, an attribute value of the attribute identifier or a range of attribute values, and the attribute value or attribute as information about the attribute value of the file to be access controlled. It manages access rights to the range of values and the target user name. The basic configuration of the table managed by the access right management unit 13 is shown in FIG. Each record that makes up the table includes an "attribute name" that represents an attribute identifier, an "attribute value" corresponding to this, a "user name" of the target user, and an "access right" that represents a denied access right. have. In the table of FIG. 2, the attribute specified in the "attribute name" column is specified in the "user name" column for a file having the attribute value specified in the "attribute value" column. It indicates that the user cannot have the access right specified in the “access right” column. Information about the attribute values of these files can be written, added, corrected, and changed through the user interface.

If at least the attribute identifier and the attribute value, or the range of the attribute identifier and the attribute value is registered in the access right management unit 13, the function as the access right management device can be realized. For example, if the attribute identifier is the creation date and time and the creation year (year) is set as the attribute value, it is possible to perform access control such as "a file whose creation date is 1993 or later cannot be accessed by anyone". .

The access right examining unit 14 interprets the access command received by the access command receiving unit 12 and detects the access right necessary for executing the access command. The detected access right is passed to the access right determination unit 16.

The attribute reading unit 15 reads the attribute value associated with the file that is the target of the access command from the file system 11. As described above, the file has the attribute part of the file such as the creation date and time, the creator, and the title name. Therefore, the necessary attribute value is read from this attribute part. The read attribute value is passed to the access right determination unit 16.

The access right judging unit 16 stores information about the attribute value of the file managed by the access right management unit 13, the access right checked by the access right checking unit 14, and the attribute value of the file read by the attribute reading unit 15. Are compared to determine whether the attribute value associated with the file to be accessed or the user's access right is included in the information about the attribute value of the file read from the access right management unit 13.
As a result of this determination, when the attribute value or the access right is included in the information about the attribute value of the file, it is determined that there is no access right to the file, and the access instruction receiving unit 12 accesses the user who issued the access instruction. Notify that there is no right. When the attribute value and the access right are not included in the information about the attribute value of the file, it is determined that the file has the access right, and the user who issued the access command is notified of the access right.

By changing the description of the table (FIG. 2) of the access right management unit 13, there is an access right to the file when the attribute value related to the access command or the access right is included in the information such as the attribute value of the file. , If it is not included, it is possible to determine that there is no access right to the file.

FIG. 3 shows a specific example for realizing the file management system 1 shown in FIG. 1, and shows the hardware configuration of a computer system functioning as a file server.

The CRT 21 is a user interface having a display screen, and displays text data, graphics, etc. on the screen. These image displays are controlled by a CRT controller (not shown).

The keyboard (KB) 22 is a user interface for inputting data such as commands and character strings, and is connected to a mouse (not shown) for selecting instructions on the screen. Various data and instructions input from the keyboard 22 are sent to the processor 25 through a keyboard / mouse control unit (not shown).

The disk device 23 is composed of a mass storage device such as a magnetic disk, and stores various data in a file format. Input / output of data in the disk device 23 is managed by a disk device controller (not shown).

The main memory 24 is a buffer memory composed of a memory device such as a RAM, and temporarily stores various programs and various data and commands input from the keyboard 22. The programs and data required by the processor 25 are copied from the secondary storage device such as the disk device 23 to the main memory 24 in part or in whole.

The processor 25 is a central processing unit composed of a CPU and its peripheral circuits, manages the operation of each of the above-mentioned parts according to a control program, and executes arithmetic processing for predetermined data.

The communication control unit 26 is connected to a network (not shown) and controls data transmission / reception to / from a user machine operated by a user who uses the file system, such as a personal computer or a workstation, or another server. To do.

An access command is issued to the file server shown in FIG. 3 via a network from a remote user machine. In this case, the remote user machine needs to have at least the function of the communication control unit 26. Needless to say, the file server can be accessed locally.

Next, in the file management system 1 described above, the basic processing flow when the file system access command is received from the user will be described with reference to the flowchart of FIG.

Upon receiving an access command to the file system 11 from the user, the access command receiving unit 12 requests the access right management device 10 to determine whether the user who issued the access command has the access right ( Step 101, step 102). The access right management device 10 determines the access right according to the flowchart of FIG. 5 described later, and passes the determination result to the access command receiving unit 12 (step 103). Access command receiver 1
2 interprets the received determination result and checks whether the user who issued the access command has the access right (step 104). When the user has the access right, an access command is passed to the file system 11 (step 105). If the user does not have access,
No access command is passed to the file system 11 (step 106).

If the user does not have the access right,
For example, processing such as returning an error to the user may be performed via the communication control unit 26 (FIG. 3).

Next, the flow of processing in the access right management device 10 when the access command receiving unit 12 requests the determination as to whether or not the user has the access right will be described with reference to the flowchart of FIG.

First, the access right judging unit 16 requests the access right examining unit 14 to examine the access right necessary for executing the access instruction requested by the access instruction receiving unit 12. The access right examining unit 14 interprets the requested access instruction and detects the access right necessary for executing the access instruction (step 201). The detected access right is passed to the access right determination unit 16. The access right determination unit 16 reads information about the attribute value of the file to be access controlled from the access right management unit 13 (step 202). Then, the attribute reading unit 15 reads the attribute value of the file to be accessed (step 203). The access right determination unit 16 compares the access right checked by the access right checking unit 14, the information about the attribute value of the file read from the access right management unit, and the attribute value of the file read by the attribute reading unit,
It is determined whether the attribute value associated with the file to be accessed or the user's access right is included in the information about the attribute value of the file read from the access right management unit 13 (steps 204 and 205). here,
When the attribute value associated with the file to be accessed or the user's access right is included in the information about the attribute value of the file, it is determined that the user does not have the access right, and the access command receiving unit 12 determines that the user has the access right. Notify that there is not (step 206). If the attribute value associated with the file to be accessed or the user's access right is not included in the information about the attribute value of the file, it is determined that the user has the access right, and the access command receiving unit 12 is notified to the user. Notify that you have access rights (step 207).

6 to 8 show an example of a table managed by the access right management unit 13. Next, a specific example of processing in the access right determination unit 16 described above for determining whether or not the attribute value associated with the file to be accessed and the access right of the user are included in the information regarding the attribute value of the file is shown in FIG. A description will be given together with a table example.

In the table shown in FIG. 6, the date and time when the file is created is used as a control target (attribute value), and the attribute "CreateDateAndTi" that stores the creation date and time.
access is controlled by "me". Further, the attribute value is represented by a time range consisting of the maximum value (the beginning of the period) and the minimum value (the end of the period). The following contents are set in this table.

"From 0:00:00 on January 1, 1992,
User A does not have the Read right for the file created between 00:00 and 1 January 1, 1993. "From 00:00, 00:00 October 10, 1989, 1990
User B does not have the Read right to the file created between 00:00 and 00:00 on October 10, 2014. With such information stored in the table,
Consider a case where a read access command is issued from the user A to a file created on October 10, 1992.

First, the access right examining unit 14 interprets the access command requested by the access right judging unit 16 and detects the access right necessary for executing the access command.
As a result, Read (right) is obtained. Next, the access right determination unit 16 reads information about the attribute value of the file to be access controlled as shown in FIG. 6 from the access right management unit 13. Then, the access right determination unit 16 reads the attribute value (creation date and time in this example) of the file to be accessed from the attribute reading unit 15. As a result, the conditions for determining the access right of the user A are complete.

Here, FIG. 9 shows the flow of processing for determining whether the attribute value associated with the file or the user's access right is included in the information on the attribute value of the file read from the access right management unit 13. The flowchart will be described.

First, it is checked whether or not there is a user name on the table that matches the user name that issued the access command (step 301). The name matching the user A is in the user name item of the first record in FIG. Next, it is checked whether or not there is an access right matching the access right required to execute the access instruction for the first record (step 302). Read that matches the access right required to execute the access instruction is in the item of the access right of the record. Then, it is checked whether the creation date and time of the access target file is included in the range of the attribute value of the file (step 303). The file creation date and time, October 10, 1992, is in the range of the attribute value of the file "January 1, 1992 0:00:00 to 199".
"January 1, 3rd 0:00:00" (step 303 "Y"). Therefore, the access right determination unit 16
Determines that the user who issued the access command does not have the access right (step 304). If there is no matching condition in steps 301 to 303, it is determined that the user who issued the access command has the access right (step 305).

The flowchart of FIG. 9 is for explaining the basic flow of the judgment processing, and does not show the procedure of the actual judgment processing.

As shown in the example of FIG. 6, "CreateDat
The access control by "eAndTime" is, for example, "1.
Files created after 993 contain the latest data and should not be published, so read only by specific people. This is convenient when performing control such as ".

In the table shown in FIG. 7, the user name of the file last changed is used as an attribute value, and the attribute "LastModifiedB" is an attribute for storing the last updater name.
The access is controlled by "y". The following contents are set in this table.

"Anyone other than the user A has the Write right for the file last modified by the user A""Read for the file last modified by the user B"
No right other than user B has the right. "As in the example of FIG. 7," LastModifiedBy "
In the case of access control by, for example, "A person is the person who finally checks the contents of the file, and after this person checks and changes the contents, no other person should change it." Or, "Person B evaluates the contents of the file and writes confidential information, so after this person checks and changes the contents, other people cannot see this file." It is convenient for controlling.

In the table shown in FIG. 8, the title name of the file is used as an attribute value, and access is controlled by "Title" which is an attribute for storing the title name. The following contents are set in this table.

"Everyone does not have all access rights to a file whose title is" confidential * "(* is an arbitrary character string). A person other than A does not have all access rights to a file whose title is “* (Aonly)” (eg, “technical data (Aonly)”). As in the example of FIG. 8, the access control by “Title” is convenient when the access right is controlled by the meaning of the file name. As the attribute value, path names such as / A / B / C and / A / B / D used in the directory may be used.

Also in the access control of FIGS. 7 and 8, whether the attribute value associated with the file to be accessed or the user's access right is included in the information about the attribute value of the file read from the access right management unit 13. The processing procedure for determining whether or not it can be realized by the flowchart according to FIG.

In the above-described embodiment, the attribute values such as the date and time of creation, the creator, and the title name attached to the file are used to determine the access right. However, these attribute values are not limited to one but other It may be set in combination with the attribute value. It is also possible to add a special attribute value to the file and use this attribute value for determining the access right.

[0049]

As described above, in the access right management device according to the present invention, the information about the attribute value of the file to be the access control is held and is attached to the file to which the user's access command is issued. Whether or not the access right to the file is determined depending on whether or not the attribute value is included in the attribute value of the file to be held or the range of the attribute value. Therefore, the creation date and time of the file, the creator, the title name, etc. By manipulating the attribute value of, it becomes possible to comprehensively manage the access right of the entire file.

[Brief description of drawings]

FIG. 1 is a block diagram showing a functional configuration of a file management system.

FIG. 2 is a diagram showing a basic configuration of a table managed by an access right management unit.

FIG. 3 is a diagram showing a hardware configuration of a computer system.

FIG. 4 is a flowchart showing a processing flow of the file management system.

FIG. 5 is a flowchart showing a processing flow of the access right management device.

FIG. 6 is a diagram showing an example of a table having a creation date and time as an attribute value.

FIG. 7 is a diagram showing an example of a table having a creator as an attribute value.

FIG. 8 is a diagram showing an example of a table having a title name as an attribute value.

FIG. 9 is a flowchart showing a processing flow of an access right determination unit.

FIG. 10 is a diagram showing the relationship between access rights and target users.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 1 ... File management system, 10 ... Access right management device, 11 ... File system, 12 ... Access command reception part, 13 ... Access right management part, 14 ... Access right inspection part, 15 ... Attribute reading part, 16 ... Access right judgment Department

Claims (1)

[Claims] 1. An attribute value holding means for holding information on an attribute value of a file to be an access control target, and an attribute value attached to a file to be an access target are attributes of a file held by the attribute value holding means. An attribute value determining means for determining whether the value or the attribute value is included in a range of attribute values, an access right determining means for determining whether or not there is an access right to a file to be accessed by referring to a result of the determination, An access right management device characterized by comprising.