JPH02143349A - Preventing system for file misuse - Google Patents

Abstract

PURPOSE:To prevent the misuse of a file by giving plural names to each file handled with a data processing system and having an attribute at every name. CONSTITUTION:A file operation processing part 11 uses a file name specified by a user and requests an inspection whether or not a requested operation can be executed to a file name control part 13. The file name control part 13 retrieves a file name managing table 15 and inspects whether or not a specified operation is allowed to the file name. The file operation processing part 11 operates a requested file only when the execution of a file operation is allowed as the result of the inspection. Thus, the misuse of the file can be prevented without changing the operation authorization of the user.

Description

[Detailed Description of the Invention] [Summary] By allowing multiple names to be assigned to each file handled by a data processing system and by assigning attributes to each name, misuse of the file can be prevented. Concerning the method for preventing file 1.

The purpose is to prevent operations such as erroneous deletion and erroneous access to files.

A file name management book that stores correspondence information between file names and files and authority information that can be obtained using the file names; a file name management section that manages file operations and file access authority based on file names; It is equipped with a file usage rights management register that stores information on the rights that users can perform on files, and a file usage rights management section that manages file operations and file access that users can perform on files. is I
The system is configured to perform an authority check for each file name for files that may be given M numbers.

[Industrial application field]

The present invention enables each file handled by a data processing system to be given multiple names and has an attribute for each name, thereby preventing the misuse of files by using different file names. Misuse prevention processing system In a data processing system using a computer, a collection of data is managed as a file, but a means is required to prevent necessary data from being lost due to misuse of the file.

[Background Art] File operations in a data processing system include file operations such as file creation and deletion, and file access such as file reference and update.

In the 1 file system, what can be done with regard to file operations or file access qualification checks is managed depending on the relationship between the file user and the file. That is, various operating authorities and access JFE limits were managed for each file name and user.

By the way, in a normal file system, only one file name can be assigned to one file entity. However, some systems allow you to alias files. In such systems, a file's real name and alias are distinguished, and a single name allows both file operations and file access, while a alias allows file access, but not the file itself. Only the name can be manipulated. Furthermore, even in systems where multiple names can be assigned to a file, what can be done regarding file operations and file access is determined arbitrarily depending on the relationship between the refile user and the file. was.

(Problems to be Solved by the Invention) According to the conventional method described above, it is possible to check the qualifications for the user's ability to create and access a file, but the user can only access the file once. , it was not possible to prevent incorrect operations or accesses.

FIG. 5 shows an example of a conventional file system that allows files to be aliased.

The file name management unit 53 manages file names, file locations: n, etc. using a file name management list 55. In this example, the file name “X, Y, INPIJT” is an alias for the file “X, Y, υPDATE”, and when there is an access request for “X, Y, INr”UT”, the file name The management unit 53 converts the name into one real name "@X, Y, IIPDATE".

The file usage right management unit 54 handles each file individually.

What kind of printing authority and access authority a user has is managed by a file usage right management list 56.

The user ID, which is the user's identification information, is "tlsER1"
A user mistakenly specified the input and output files in reverse order, as shown in FIG.

Assume that a program P that accesses a file is started.

In that program P, 1 should originally be the input side "X, Y"
, INI'UT'' in the update mode. Upon receiving the 0PEN request, the file access processing unit 52 relies on the file name management unit 53 to check the file name.

On the other hand, the file name management unit 53 stores the file capillary F.
See Il Book 55'c, ``X, Y, l1fPII
T'no zero name °x.

Y, UPDAT[! ”, the location VI including volume information is notified.

Next, the file access processing unit 52 informs the file usage rights management unit 54 that the user “USERI” has access to the file “
Request X, Y, and UPD^Tε° to check whether they have update authority. The file usage rights management section 54 refers to the file usage rights management list 56.

Notify that you have permission to update.

Through the above processing, the file name “X, Y, INPU
T” is.

This is an alias for "X, Y, UPDATE" and has the right to update, so the incorrect update mode of 0PEN is allowed. Therefore, if you run the program by specifying the input and output files incorrectly,
The contents of the file will be destroyed.

8For example, there are 4 files, and each file name is '
A, B, C', “6.83 mouths”, 1^, B, E”l
Assume that the following deletion command is input in an attempt to delete the former three files "^, I3.Z".

“DELETE person, B, *’ Here, "*" is a wildcard character.

This means that it applies to any string.

This command allows you to delete the file name "A" that you do not want to delete.
, B, and Z'' files will also be deleted by mistake.

As mentioned above, in the conventional method, it is not possible to give two or more types of permissions to one file at the same time, so files may be destroyed or deleted due to misuse, so this can be avoided. In order to do this, there was a problem in that the user's authority had to be changed every time before or after using the file. Changing permissions is cumbersome, and if you forget to change the permissions, there is a risk of file damage due to misuse.

The present invention aims to solve the above problems, and for files,
The purpose is to prevent errors such as erroneous deletion processing and erroneous access.

[! Means to solve one problem] FIG. 1 shows an example of the configuration of the present invention.

In FIG. 1, IO is a processing device consisting of a CPU, memory, etc., 11 is a file operation processing unit that creates/deletes files, adds/deletes/renames files, etc.;
2 is a file access processing unit that performs data input/output processing for files;

13 is a file name management unit, 14 is a file usage rights management unit, 15 is a file name management list, and 16 is a file usage rights management unit 7y1. ．． 17 is a file management Th'1 that stores attributes such as file organization and extent information for each file;
．． A file 219 18 represents an external storage device such as a magnetic disk device.

The file name management list 15 includes the file name given to the file 18 by the user, the file entity name uniquely given to each file within the system, and the permissions for the types of file operations and file accesses that can be performed using the file name. It stores information etc. A file entity name corresponds to each file on a one-to-one basis.The file name management book 15 allows a plurality of file names to be associated with one file entity name.

The file usage right management list 16 includes file entity names and user IDs that are identifiers for identifying users.

It stores the types of file operations and file accesses that the user can perform on the file.

The file name management unit 13 manages file operations and file access privileges based on file names based on information registered in the file name management directory 15. The file usage rights management unit 14 manages the file access rights and the file operations that the user can perform on the file, based on the information 93 and 2 sent to the file usage rights management board 16.

File hill production processing unit 11. File access processing unit 12
The file name management unit 13 and the file usage unit respond to file operation requests and file access requests, respectively.
By calling the IT management section 14, an authority check based on the file name and a user authority check for file operation or file access are performed in the same manner as in the past.

[Effect]

When executing a request from a user, the file operation processing unit 11 or file access processing unit 12 inputs a file name specified by the user, a user ID that identifies the user, and information about the operation or access that the user is attempting to perform. Based on the type, it is determined whether abuse or access is allowed, and if it is not allowed, an error notification is issued.

This will be explained using file operations as an example. First, the file operation processing section 11 requests the file name management section 13 to check whether the requested operation can be performed using the file name specified by the user.

The file name management unit 13 searches the file name management list 15 and checks whether the specified operation is permitted for the corresponding file name.

If the operation is permitted, the file operation processing unit 11 first checks whether the user is permitted to perform the requested operation on the file using the file usage management unit 1π. Ask I4. In file usage 1, the management unit 14 searches the file usage rights management list 16 and checks whether the user has the authority to manipulate the file.

As a result of the above inspection, the file operation processing unit 11 only performs file substitution if it is permitted.

This will perform the requested file operation.

Misuse of files can be prevented without changing the user's operating authority.

In the case of file access, the file access processing unit 12 starts the file access.

Misuse can be prevented by checking access authority in a similar manner to the file operation example above.

〔Example〕

FIG. 2 shows a processing flow according to an embodiment of the present invention, FIG. 3 shows an example of a file operation according to an embodiment of the present invention, and FIG. 4 shows an example of file access according to an embodiment of the present invention.

When a user (including application programs, etc.) requests a file operation such as creating or deleting a file, the process shown in Figure 2 (
Processes ① to ① shown in b) are performed.

(2) By searching the file name management 'a 15 with the file name, the location of the file such as the file entity name and the location of the file, and the operation authority information allowed for the file name are obtained from the file name management RV 15.

■ Determine whether you have sufficient privileges to operate on the file name. If you do not have operational authority.

Notify the requester of the error.

■ By file entity name or user ID.

By searching the file usage rights management list 16, the usage rights information of the corresponding file granted to the user is obtained from the file usage rights management 7yJ16.

■ Determine whether the user has sufficient privileges for the operation. 1. If you do not have the authority to create a mulberry, send an error notification to the requester.

■ If the operation privileges are sufficient, perform the requested operation on the file and exit.

When there is a file access request such as file reference or update from a user (including application programs, etc.), the second
Processes ① to ② not shown in the figure (b) are performed.

(2) By searching the file name management book 15 using the file name, the location of the file, such as the file entity name and the location of the file, and the access authority information allowed for the file name are obtained from the file name management book 15.

■ Determine whether you have sufficient privileges to access the file name. If there is no access authority, an error notification will be sent to the requester.

(2) By searching for the file usage rights management 't+''J l 6 using the file entity name or user ID, information on the use JfN of the file permitted by the user is obtained from the file usage rights management list 16.

■ Determine whether access privileges are sufficient for the user. If there is no access authority, an error notification will be sent to the requester.

■ If access privileges are sufficient, perform the requested access to the file and exit.

Next, a specific example of file operation will be explained with reference to FIG.

There are four files on the external storage device, and the file names given by the user are “A, [1, C”, “A, B, Mouth””^, B, E”, “A, B, Z ”. Here, it is assumed that the files corresponding to the file names "A, B, and Z" must be saved for a long period of time, so it is necessary to prevent them from being deleted by mistake.

In such a case, files with file names "A, B, Z" are given long aliases that are difficult to use, such as "^, Vv, XX, YY". For the file names "A, B, Z" that are commonly used in 1lli, the operation authority information t9 is registered in the file name management book 15 so that the files themselves are not allowed to be deleted (.

The file name management list 15 has information as shown in FIG. 3 (b), for example. FILEI to FILE4 are file entity names uniquely given to each file by the system, and Vl and V2 are file position information such as volume information. It is assumed that the file usage right management book 16 has the information shown in FIG. 3(c).

In this state, as shown in Figure 3 (a).

The user whose user ID is “USEI?I°”.

When the rDBLETE A, B, *J deletion command is input and a file operation request is made, the file concealment processing unit 11 performs the following processing.

The file operation processing section 11 sends A to the file name management section 13.
, B, *”. The file name management unit 13 searches the file name management list 15 and requests deletion authority for “A, B, *”.
, *” as the file name that corresponds to 8, ” A, B
,C”,“8,B,[l”,”A,[1,pi.

Obtain 4 of °^, B, and Z'. Also: Obtain the relevant file entity name and location information. Here, the previous three file names can be deleted, but the file names "A, B, and Z" cannot be deleted, so information to that effect is sent to the file operation processing unit 11. to notify. The file operation processing unit 11 removes files with file names "A, B, Z' from deletion targets.

Next, the file operation processing unit 11 specifies the file entity name to the file usage rights management unit 14, and inputs “US
Request the user of "ERI" to check the deletion authority.

For the user “USER1”, “^, B, C” “^
, B, D", "11. Since deletion of files with file entity names corresponding to B and E'' is allowed, these files are deleted.

Even if the user himself/herself has the authority to delete the file whose file entity name is "FILE4", the file name is "A, [
1,Z'' cannot be deleted, which can prevent accidental deletion.If you actually need to delete, use other difficult-to-use file names such as ゛^, VV,
It can be deleted by specifying "XX, YY".

Next, a specific example of file access will be explained with reference to FIG.

For a certain file, "If there is a file, it will only be referenced, and in other cases, it will be updated.

In such a case, to prevent misuse, the file itself should be ``9'' e.g.
Y.

1. Add two file names: ``X, Y, INP[IT'' and ``Cannot update'' file names. Register in I5 in advance.

It is assumed that the file name management '71v15 and the file usage rights management book 16 have information as shown in FIG. 4(b) and FIG. 4(c), respectively.

In this state, when the user with the user ID "ll5ER1" runs the program P that performs input/output between files, as shown in FIG. Suppose that ``Y, lN11[IT'' is specified to the output side by mistake.

The file access processing unit 12 has a file name of 'X,
Y, INPUT”, requests the file name management unit 13 to check the access authority based on the file name.File name management unit 13
searches the file name management list 15.

For the file name "X, Y, INPUT", an attribute indicating that the file is not allowed to be updated is obtained, and this is notified to the file access processing unit 12. As a result, the file access processing unit 12 determines that the open is an error.

As described above, even if a user has the authority to update a file, misuse can be prevented by attaching an authority attribute to each file name.

〔Effect of the invention〕

As explained above, according to the present invention, a plurality of file names can be assigned to one file entity.

Since each file name can have a usage right attribute, it is possible to use different file names to prevent operations such as erroneous deletion processing and erroneous access.

[Brief explanation of the drawing]

FIG. 1 shows a configuration example of the present invention. FIG. 2 shows a processing flow according to an embodiment of the present invention. FIG. 3 shows an example of file operations according to an embodiment of the present invention. FIG. 4 is an example of file access according to an embodiment of the present invention. FIG. 5 shows a diagram illustrating problems in the prior art. In the figure, IO is a processing device, 11 is a file operation processing unit, 1
2 is a file access processing unit, 13 is a file name management unit, 14 is a file usage right management unit] 5 is a file name management R
'X, 16 is a file usage rights management list, 17 is a file management list, and 18 is a file. 19 represents an external recording tQ device.

Claims (1)

[Claims] A file operation processing unit (11) that operates files;
File access processing unit (1) that accesses files
2) In a file system that allows multiple names to be assigned to a file, correspondence information between file names and files, the types of file operations that can be performed using the file names, and the types of file accesses that can be performed using the file names. A file name management book (15) that stores information, a file name management unit (13) that manages file operations and file access privileges based on file names based on information registered in the file name management book, and a user. File usage rights management book (16) that stores the types of file operations and file accesses that can be performed on files.
), and the File Usage Rights Management Department (1
4) A processing method for preventing misuse of a file, which is characterized in that an authority check is performed for each file name for files that may have multiple file names.