JP4145365B2 - File access control device - Google Patents

Description

[0001]
[Industrial application fields]
The present invention relates to an apparatus and method for controlling access to a program or data file to prevent destruction of the program or data due to malfunction or execution of an illegal program, or large-scale data destruction due to virus infection. In particular, file access that defines users and programs (hereinafter referred to as application software or simply applications) that can access each program or data file, thereby preventing large-scale data corruption due to chained execution of applications. The present invention relates to a control device and a control method thereof.
[0002]
[Prior art]
Generally, software includes a plurality of programs and data files in one software, and these programs (applications) are executed while being switched.
[0003]
An example of this is game software. In the game software, new screens are developed one after another from the first screen, and the developed new screens are configured to perform an operation along the screen and enjoy one game as a whole. Such a method is not limited to game software but is currently widely used in various software.
[0004]
In the software as described above, applications are related to each other in a complicated manner, and one application can be read or executed by a plurality of other applications. May be rewritten or erased by the application.
[0005]
In such a software structure, an irrelevant program or data file (a file that is not originally accessed by the execution of the application) may be destroyed or chained due to an operation error or execution of an application having a malfunctioning part. There is a risk of irrelevant files being destroyed and causing serious data corruption overall.
[0006]
In particular, virus infection, which has recently become a problem, intentionally targets the above phenomenon, and causes a wide range of data destruction in a chain by executing a program that conceals data destruction.
[0007]
On the other hand, an apparatus and a method for controlling access to a program or data file by an application have been proposed. This conventional file access control apparatus and method loads a non-writable program and data and a writable program and data into an access-prohibited area and an access-permitted area on the memory, respectively, and accesses and transmits an access instruction source The previous programs and data are managed by the addresses on the memory, thereby controlling access to the files (see Japanese Patent Application Laid-Open No. 57-71597).
[0008]
On the other hand, there has conventionally been an apparatus and method for permitting or prohibiting access to a program or data file by a user. This is intended to protect the software by giving access rights to the file only to users who intend to use it normally. Specifically, by confirming the user identification information, access to the file is permitted or prohibited in units of users or in units of user groups.
[0009]
[Problems to be solved by the invention]
However, the conventional method of loading the program and data files into the accessible area and the access-prohibited area of the memory and managing them by the address on the memory has many restrictions on the software configuration. That is, in the case of complex software, a certain program or data file is a write-protected file for access from a predetermined program or the like, and a writable file for access from another program or the like. It needs to be finely configured. On the other hand, such a detailed setting cannot be performed by the above-described conventional method of distinguishing between writable and write-inhibited depending on the area on the memory.
[0010]
In addition, once writable / writable settings have been set, it has not been possible to flexibly change them depending on the software execution conditions. Furthermore, it has been impossible for a user to permit or prohibit access to a predetermined file.
[0011]
On the other hand, the conventional method of permitting or prohibiting access to an application by checking the user authentication information described above allows the user to access any file in the software once the user is recognized as a legitimate user. It becomes. As a result, if the execution instruction of a legitimate user is an operation mistake or there is a problem with the program to be executed, the chained data destruction of the application may occur.
[0012]
In particular, virus-infected software hides a defective program and allows a legitimate user to execute it. Therefore, the conventional method described above cannot prevent extensive data destruction due to viruses.
[0013]
SUMMARY OF THE INVENTION Therefore, an object of the present invention is to solve the above-mentioned problems of the prior art, and to effectively prevent a wide range of data destruction due to malfunction of software composed of a plurality of application software and execution of a faulty program, and It is in providing the control method.
[0014]
[Means for Solving the Problems]
  In order to achieve the above object, a file access control device according to the present invention provides:
  A file attribute management table that defines combinations of users and programs that can be accessed and types of processing that can be executed by the combinations, for each program and data file that constitutes the software;
  User information storage means for storing information of a user currently executing the software;
  Application information management means for registering information on the currently running program;
  When an access command for a predetermined file is issued, the user information storage means is referred to obtain information on the currently executing user, and the application information management means is referred to for information on the currently executing program. File access control means for acquiring and determining whether or not the processing of the access command can be executed by a combination of the currently executing user and the program with reference to the file attribute management table, and permitting or prohibiting the access command And equipped with,
  In the file attribute management table, each file has a user, a user group, and an application ID as attributes, and the type of processing permitted when accessed from the same user as a user management and accessed from the same user group Types of processing permitted in the case, types of processing permitted when accessed from users and user groups other than the same user and user group, and types of processing permitted when accessed from applications having the same application ID Defines the types of processing allowed when accessed from applications other than the same application ID.It is characterized by that.
[0015]
  The present invention can comprise a file attribute management table setting means capable of setting a user and a program that can read, write, execute, and delete each file on a computer screen.
[0018]
[Action]
  The file access control device of the present invention defines and registers in advance in the file attribute management table the user and application that can access the software and the type of processing for the file for each file constituting the software, and the software is stored in the user information storage means. Stores information on the user being executed, stores information on the application software currently being executed in the application information management means, and when there is an instruction to access the file, from the user information storage means and the application information management means The user and application that issued the access command can be detected, and the access command can be permitted or prohibited according to the file attribute management table.
[0019]
As a result, the file access control device and control method of the present invention described above allow users and applications that can access each file constituting the software, and types of processing for the file (for example, read, write, execute, erase, etc.). Can be specified, and the processing by the correct operation of the application constituting the software can be guaranteed, and the chained data destruction of the file due to the malfunction or the execution of the faulty program can be prevented.
[0020]
  Also, the file access control device of the present invention can define user and application software that can read, write, execute and erase each file constituting the software on the computer screen. Depending on the conditions used, the access conditions for each file can be changed at any time. Further, a file access control device and a control method applicable to various software can be obtained by the freedom to arbitrarily define access conditions for such files.
[0021]
【Example】
An embodiment of a file access control apparatus and control method according to the present invention will be described below with reference to the accompanying drawings.
[0022]
FIG. 1 shows a configuration of an embodiment of a file access control apparatus according to the present invention and a flow of processing thereof.
[0023]
The file access control apparatus 1 of the present embodiment can be configured by hardware different from the computer that executes the software, but is preferably a processing device, a storage device, and an input / output device of the computer that executes each software by the software Etc. are used.
[0024]
As shown in FIG. 1, the file access control apparatus 1 according to the present embodiment includes a file attribute management table 2 that defines users, user groups, and application software that can access each file of software to be executed. A file attribute management table setting unit 3 for setting the contents of the file attribute management table 2, a user information storage unit 4 for storing information about a user who is currently executing the software, and an application software which is currently executing a command. When there is an application information management unit 5 that recognizes whether the command is an application command, the application information management unit 5, an application information initial setting unit 6 that performs initial setting of the application information management unit 5, and an access command to a file Before Made from the user information storage unit 4 and the application information management unit 5 and the file attribute management table 2 and with reference to allow or prevent access to a file the file access control unit 7.
[0025]
Next, the operation of the file access control device 1 during software execution based on the above configuration will be described.
[0026]
Assuming that the file attribute management table 2 has already been set, a computer start signal is input to the application information initial setting unit 6 when the computer is first started up, thereby setting the application information to the initial state. Normally, the application information management unit 5 is returned to a state in which no application software is registered by the operation of the application information initial setting unit 6.
[0027]
When the computer starts up, the user information is requested to be input immediately. This is to temporarily remove unauthorized users before executing the software.
[0028]
The user information can be acquired by a known method such as requesting the user to input a user ID or requesting collation using an IC card.
[0029]
When the acquired user information is that of a legitimate user, the user is permitted to use the software, and the obtained user information is stored in the user information storage unit 4.
[0030]
In this way, the user who is permitted to use the software executes the software and performs various processes. These processes include an input / output process for a large number of files constituting the software (there are a program file and a data file).
[0031]
In the file access control apparatus 1 according to the present embodiment, the input / output processing command for the file is once input to the file access control unit 7, and the access control unit 7 determines whether to permit or prohibit the access. Configured to access the file. Types of input / output processing for this file include program execution, file write, file read, and file erase.
[0032]
When the file access control unit 7 receives an input / output processing command for a file, the file access control unit 7 registers the new program name in the application information management unit 5 when the command is a command to read and execute a new program. As a result, the latest information regarding the currently running application can be held.
[0033]
On the other hand, when the input / output processing command for the file is a command for changing or deleting the contents of a predetermined file, the file access control unit 7 includes the user information storage unit 4, the application information management unit 5, and the file attribute management table. Referring to the contents of 2, whether or not the command is a command of the user and application software authorized to access the target file, and the type of processing by the command is permitted It is determined whether or not the instruction is executed, and execution or prohibition of the instruction is permitted.
[0034]
Next, the contents of the file attribute management table serving as a reference for the above determination will be described.
[0035]
FIG. 2 shows an example of a screen for setting the contents of the file attribute management table 2 by the file attribute management table setting unit 3.
[0036]
In FIG. 2, the upper part of the screen is a part for setting search conditions of the setting screen, and by inputting at least one of a file name, a user name, a user group name, a type, and a file ID, a file attribute management table setting unit 3 displays a setting screen of the file attribute management table of the file that matches the search condition.
[0037]
Below the portion for inputting the setting screen search condition is a screen for setting the contents of the file attribute management table.
[0038]
The left part of the screen for setting the contents of the file attribute management table shows the name of the file to be accessed (in this case main.exe, image.dat, sub.exe, hiscore.dat), and the user (α) who performs the access , A user group (β), and an ID (XXX) as an application assigned to each file.
[0039]
On the right side of the screen for setting files, users, etc., there is a screen for setting application access conditions for each file. This access condition setting screen is roughly divided into a user management setting screen and an application management setting screen.
[0040]
The user management setting screen is divided into access permission conditions other than the user, the user group, the user, and the user group. This classification is merely an example, and if necessary, more detailed designation, for example, access permission conditions for each user can be set.
[0041]
Below the user management section, a screen for setting a condition to be permitted or prohibited for each type of processing (read, write, execute, erase) for the target file is displayed.
[0042]
Similarly, the application management setting screen is divided into access from the same application ID and access from different application IDs, and conditions for permitting or prohibiting access from each application for each type of processing. Can be set. In this case as well, finer designation, for example, access conditions for each application ID can be set as required.
[0043]
In the setting example of FIG. 2, the file main.exe can be read only by people other than the user / user group, and the regular user α and the user group β can be executed. Further, the user α can rewrite or delete the file main.exe. The file main.exe can be started and executed by all other application software.
[0044]
On the other hand, the file image.dat can be referred to and rewritten only by the application having the same ID, and only the user α can rewrite.
[0045]
The file sub.exe is executed only by the user α and the user group β through main.exe (same ID). The user α can delete the file sub.exe, but cannot rewrite it to prevent erroneous operation.
[0046]
Finally, the file hiscore.dat can be referred to and rewritten only by the user α and the user group β through the file main.exe or sub.exe. Only the user α can be deleted.
[0047]
As described above, according to the present invention, by setting user management, application management, and permitted processing types in the file attribute management table 2, it is possible to freely set users, applications, and processing types that can access each file. Can do. Since the file attribute management table 2 can be set by the file attribute management table setting unit 3 when necessary, software execution conditions, for example, users who can access files can be added or changed, or software design can be performed. Applications that can access each file can be added or changed by changing the specification. Further, the file access control apparatus and control method of the present invention are highly versatile and applicable to various software by freely setting the access conditions for the file.
[0048]
Next, access control in the file access control unit 7 will be described in accordance with specific application operations.
[0049]
FIG. 3 shows an example of control by the file access control unit 7 in time series. The software illustrated in FIG. 3 includes a plurality of application software, and these application software are configured to be activated and executed one after another according to a user command in a certain procedure.
[0050]
FIG. 3 shows a case where the main application PRG-A is activated and the file FLLE-A is rewritten by the main application PRG-A.
[0051]
In this case, in the file attribute management table 2, the user α can directly start the main application PRG-A, can start the sub application PRG-B through the main application PRG-A, and can pass through the sub application PRG-B. Is set in advance so that the data file FILE-A can be rewritten.
[0052]
In FIG. 3, if a user ID α is acquired after the computer is started up, it is determined whether or not the user ID α is that of a regular user. If the user ID α is that of a regular user, the user ID α is stored in the user information storage unit 4. (Step 100).
[0053]
The stored user ID α remains valid unless a new user ID is acquired, that is, unless the software is stopped and the computer is restarted.
[0054]
Although not shown in FIG. 3, as described in FIG. 1, when the computer is started, the application information management unit 5 is returned to the initial state, that is, the state where nothing is registered.
[0055]
Next, if a command for executing the main application PRG-A is input, information on access to the PRG-A is detected by the file access control unit 7, and the file access control unit 7 tries to execute PRG-A. The user and application to be detected are detected by the user information storage unit 4 and the application information management unit 5, respectively (step 110).
[0056]
In this case, although the user information α is obtained from the user information storage unit 4, since the application information management unit 5 is in an unregistered state, it can be seen that this is a direct PRG-A read command by the user α. Here, the main application PRG-A is defined in the file attribute management table 2 so that the user α can directly read out the main application PRG-A. Therefore, the main application PRG-A is executed and at the same time, the application currently being executed. Is registered as PRG-A in the application information management unit 5 (step 120).
[0057]
The application information (PRG-A) registered in the application information management unit 5 remains valid in the application information management unit 5 until the execution of PRG-A is completed.
[0058]
Next, it is assumed that the execution instruction of the sub application PRG-B is issued by the PRG-A during software execution. The access command for the sub application PRG-B is detected by the file access control unit 7, and the file access control unit 7 sets the user and application that are the source of the execution command for the sub application PRG-B to the user information storage unit 4. An inquiry is made to the application information management unit 5 (step 130).
[0059]
As a result, it is understood that the execution instruction of this PRG-B is performed by the user α through the main application PRG-A, and the file access control unit 7 determines that the sub application PRG is based on the setting condition of the file attribute management table 2. -B execution instruction is allowed.
[0060]
When the sub application PRG-B is executed, the file access control unit 7 additionally registers in the application information management unit 5 that the currently executing application is the sub application PRG-B (step 140).
[0061]
Next, it is assumed that a write command for the data file FILE-A is issued by executing the sub application PRG-B. The file access control unit 7 inquires of the user information storage unit 4 and the application information management unit 5 about the user and application that issued the write command for the data file FILE-A. As a result, it is determined that the user α rewrites the contents of the data file FILE-A through the sub application PRG-B, and this write command is prohibited according to the setting condition of the file attribute management table 2 (step 150).
[0062]
Next, a case where the execution of the sub application PRG-B is completed will be described. When the execution of the sub application PRG-B is completed, the file access control unit 7 detects this and deletes the sub application PRG-B registered in the application information management unit 5 (step 160).
[0063]
When the execution of the sub application PRG-B is completed, the interrupted main application PRG-A is executed. In this state, a write command for the data file FILE-A is issued by executing the main application PRG-A. Suppose that In this case, the file access control unit 7 determines that the data file FILE-A is to be rewritten through the user α or the main application PRG-A, and the data file FILE-A is set according to the setting condition of the file attribute management unit 2 Rewriting is permitted (step 170).
[0064]
4 and 5 illustrate control patterns by the file access control apparatus and control method according to the present invention.
[0065]
FIG. 4 shows a case where control is performed so that a predetermined user X can update / delete the file 1 only by the operation of a specific program A, focusing on user management.
[0066]
FIG. 4A shows file processing performed by the user X or the program A, and any of reading, writing, erasing, and execution can be performed.
[0067]
On the other hand, FIG. 4B shows file processing performed by the user X through a program B other than the designation. In this case, only reading is possible to prevent data destruction due to malfunction.
[0068]
FIG. 4C shows file processing that can be performed by a user (Y) other than the user X. In this case, only the program A can read data.
[0069]
FIG. 5 shows a case where control is performed so that the file 2 can be executed only by the operation of a specific program B, centering on application management.
[0070]
FIG. 5A shows that any user X, Y can read and execute the file 2 only through the program B. On the other hand, as shown in FIG. 5B, any user X, Y cannot read, write, erase, or execute the file 2 through the program A.
[0071]
In this way, by combining access to files centered on user management and access to files centered on application management, it is possible to control various file accesses, and thereby, between applications constituting software The relationship can be defined in detail.
[0072]
Thereby, for example, when a program having a defective part is erroneously executed, data destruction by the defective program is limited to a very limited file. As a result, it is possible to substantially prevent a wide range of data destruction caused by a malfunctioning or malfunctioning application software or a virus infection.
[0073]
【The invention's effect】
As is apparent from the above description, the file access control apparatus and control method according to claims 1 and 3 of the present application include a file attribute management table, application information management means, user information storage means, and file access control means. As a result, users and applications that can access a given file can be restricted, and file processing by the user and application can be restricted to a specific type. Therefore, the file can be executed by executing an unrelated program (application). Can be prevented from being rewritten or erased, so that extensive and serious data destruction due to execution of malfunctioning or malfunctioning programs or virus infection can be substantially prevented.
[Brief description of the drawings]
FIG. 1 is a diagram schematically showing the configuration of a file access control device according to an embodiment of the present invention and the flow of information between the components.
FIG. 2 is a diagram showing an example of a setting screen for a file attribute management table according to the present invention.
FIG. 3 is a flowchart showing the operation of the file access control unit of the present invention in time series using a specific application.
FIG. 4 is a diagram showing an aspect of access to a predetermined file centered on user management.
FIG. 5 is a diagram showing an aspect of access to a predetermined file centering on application software management.
[Explanation of symbols]
1 File access control device
2 File attribute management table
3 File attribute management table setting section
4 User information storage
5 Application Information Management Department
6 Application information initial setting part
7 File access controller

Claims (2)

A file attribute management table that defines combinations of users and programs that can be accessed and types of processing that can be executed by the combinations, for each program and data file that constitutes the software;
User information storage means for storing information of a user currently executing the software;
Application information management means for registering information on the currently running program;
When an access command for a predetermined file is issued, the user information storage means is referred to obtain information on the currently executing user, and the application information management means is referred to for information on the currently executing program. File access control means for acquiring and determining whether or not the processing of the access command can be executed by a combination of the currently executing user and the program with reference to the file attribute management table, and permitting or prohibiting the access command and, with a,
In the file attribute management table, each file has a user, a user group, and an application ID as attributes, and the type of processing permitted when accessed from the same user as a user management and accessed from the same user group Types of processing permitted in the case, types of processing permitted when accessed from users and user groups other than the same user and user group, and types of processing permitted when accessed from applications having the same application ID And a file access control apparatus that defines a type of processing permitted when accessed from an application other than the same application ID .   2. The file access control apparatus according to claim 1, further comprising a file attribute management table setting unit capable of setting a user and a program capable of reading, writing, executing and erasing each file on a computer screen. .

Images