JP6851758B2 - Label management support method, system - Google Patents

Description

The present invention relates to a technique for collecting various information, combining the information, and generating new information as new knowledge when analyzing the current state and future prospects of corporate trends, social conditions, and the like.

In Patent Document 1, when the file 1 and the file 2 are opened at the same time, the system that inherits the attribute 1 of the file 1 and the attribute 2 of the file 2 without inconsistency between the attributes when opening and closing each file is provided. It is disclosed. If attribute 1 is lower than attribute 2, (1) do not open file 2 after opening file 1, (2) close file 1 and then open file 2, (3) read file 1. Let the user select either to open the file 2 after setting it to the dedicated mode. If the level of attribute 1 is higher than that of attribute 2, after opening file 1, (1) file 2 is not opened, (2) the attribute of file 2 is changed to attribute 1, and (3) file. Let the user choose to open 2 in read-only mode. In response to the user's selection, the system executes file opening / closing and read-only mode, and even if files with different attributes are opened at the same time, the attributes that match the contents of each file are inherited when each file is saved. be able to. Also, as before, when attribute 1 has a higher level than attribute 2, copying the contents of file 1 to the shared memory and then pasting it into file 2 is the same as before (1) File. The contents of each file by either disallowing pasting to 2 or (2) permitting pasting after changing the attribute of file 2 to attribute 1, or (3) opening file 2 in read-only mode. It is possible to inherit the attributes that match.

Japanese Unexamined Patent Publication No. 2009-266034

With the method described in Patent Document 1, it is possible to inherit the attributes (labels) of the currently open file (or the file whose contents are copied to the shared memory) to another file, but the label of the file opened in the past. Cannot be carried over to another file currently being edited.

In order to solve the above problem, the information accessed by the user when the newly created information is created is collected as an access log, the data shown in this access log, the label indicating the file attribute is collected, and the access log is collected. And the label are displayed and presented to the user.

The labels of the data and files referenced in the past are inherited when editing another data or file, preventing the management of incorrect labels.

A conceptual diagram showing an outline of label management support. System configuration diagram of the label management support system. Data structure diagram of access log management memory. Data structure diagram of the label management database. Data structure diagram of the label management database. Data structure diagram of the label judgment rule database. Data structure diagram of the label judgment rule database. Data structure diagram of the label judgment rule database. Processing flow diagram of registration of expected information. Information creation and labeling process flow chart. Label approval, label audit processing flow diagram. Process flow diagram of changing the display range of the access log. Expected information setting screen. Schedule label registration screen. Access log list display screen.

Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings.

Before explaining the details of the embodiment, the outline of the present embodiment will be described first. In this embodiment, when analyzing the current situation and future prospects of corporate trends, social conditions, etc., various information is collected, and the information is combined to generate new information as new knowledge. , Manage the labels of the generated information.

Here, labels can be broadly divided into levels and categories. The level indicates the confidentiality of information. For example, the US government ranks it into four levels: TOP SECRET, SECRET, CONFIDENTIAL, and UNCLASSIFIDE. A category limits the scope of disclosure by indicating a group in which information can be disclosed, and indicates a group such as a work group, a department, or a project.

In order to properly manage labels, when a user starts creating information, the label management support system accepts a label (scheduled label) to be given to the information from the user. Next, regarding various information collected by the user (database server data, file server file, etc.), the user's access log and the label of the information on the access log are acquired and compared with the schedule label. Emphasize the display of access logs for data and files with labels that are more stringent than the schedule label (highly confidential, different / narrow disclosure range). This prompts the user to confirm that the level and category of the appointment label are correct.

In addition, before starting the creation of information, the management user sets the information (expected information) expected to be created in the future in advance, and when the user finishes creating the information, the created information and the expected information are set. Compare. If both match and the expected information label is stricter than the scheduled label (highly confidential, different / narrow disclosure range), the user is warned that the created information label is incorrect. .. Further, when the warning is given, the display is emphasized when displaying the access log for data or files that partially match the expected information. This prompts the user to confirm that the level and category of the appointment label are correct.

For the highlighted access log data and file, the user can (1) specify to exclude items unrelated to information creation (exclusion specification), (2) access log data and information on the sensitive contents of the file. Specify that it is not reflected in the creation and does not affect the labeling (no effect is specified). The system accepts exclusion specifications and no impact specifications from users. The user reviews the label as needed and accepts label registration in the system.

In addition, the same access log as before, including highlighting and warning display, is displayed at the time of approval by the label approving user or at the time of auditing by the auditing user.

Furthermore, the management user accepts the setting of the access log display range (for example, from one week ago to one month ago). After that, the display range is automatically changed in order to prevent the label assignment error by using the history when the label is determined to be an error from the approval result and the audit result after the user has assigned the label in the past. If errors occur frequently in the information attributes, change the display range according to the information attributes (when there are many errors, when there are many times, when there are many errors after the event occurs, when each time matches. Set the display range longer, etc.). If errors occur frequently in the user's attributes, change the display range according to the user's attributes (for individuals with many errors, many departments, many areas, set the display range longer, etc.). By performing such processing, the label management support system can manage labels.

Next, the details of this embodiment will be described with reference to FIGS. 1 to 12. However, the present invention is not limited to this embodiment, and the present invention can be applied in any situation where labels of information are managed.

FIG. 1 is a conceptual diagram showing an overall picture of a process for appropriately managing labels when various information is collected, combined, and new information is generated as new knowledge in the first embodiment.

The information management server 243 of the data management system 240 stores various information such as file I101, file II102, and data III103. The user operates the input / output device 232 of the label management support system 200, refers to the various information described above via the communication line 260, and creates new information 104 (file IV).

Before creating the new information 104, information (expected information) expected to be created in the future is set in advance. When the user creates the new information 104 and assigns a label, the label (scheduled label) to be assigned at the start of creating the new information 104 is registered in the label management support system 200, and the label management support system 200 registers the label (scheduled label). , Refer to the user's access log to the data management system 240, and emphasize the display of the access log of data and files with labels with stricter conditions than the scheduled label (highly confidential, different / narrow disclosure range). In addition, the label of the expected information has stricter conditions than the schedule label, and emphasizes the display of access logs of data and files whose contents partially match the expected information. The highlighting of the display prompts the user to confirm that the level and category of the appointment label are correct. As a result, the user cancels the registration of the new information 104 in the information management server 243, reviews the label, or declares that the corresponding access log is not related to the creation of the new information 104.

As the communication line 260, various networks such as LAN (Local Area Network), dedicated line, WAN (Wide Area Network), power line network, wireless network, public line network, mobile phone network, satellite communication line, etc. are adopted. can do.

FIG. 2 shows an example of the system configuration. The label management support system 200 connects to the data management system 240 and the big data analysis system 250 via the communication line 260. The data management system 240, the big data analysis system 250, and the label management support system 200 are general computers, and include a central control device 230, a main storage device 210, an auxiliary storage device 220, a communication device 231 and an input / output device 232. .. These are connected to each other by a bus.

The auxiliary storage device 220 stores the label management database 222 and the label determination rule database 223.

The main storage device 210 stores the access log management memory 221 and the program. The access log collection unit 211, the label determination unit 212, the access log display unit 213, the user operation reception unit 214, and the label audit unit 215 are programs. After that, when the main body is described as "○○ part", the central control device 230 reads each program from the auxiliary storage device 220, loads each program into the main storage device 210, and then functions of each program (details will be described later). Shall be realized.

Further, the data management system 240 is a system that controls access based on the label given by the label management support system 200 and provides an access log to the label management system 200. The communication device 241 and the access control unit 242 and information. It is composed of a management server 243. The communication device 241 connects to the communication line 260 to communicate with the label management system 200, the access control 242 determines the access request to the information stored in the information management server 243, and the access availability is determined based on the determination result. Run. The big data analysis system analyzes whether there was an error in the past labeling, and if there is an error, it analyzes the cause and expands the display range of the access log to prevent the labeling error. Make improvements.

Although the label management support system 200 is supposed to perform input / output independently in FIG. 2, it may be connected to another terminal by a communication line 260 and information is input / output by the input / output device of the terminal. ..

FIG. 3 shows an example of the access log management memory 221.

The accelerator log management memory 221 stores a partial copy of the access log to the data management system 240 acquired from the data management system 240, only a part necessary for display.

The access log list 300 includes user ID 301, date 302, time 303, folder / database 304, file / table 305, created user ID 306, label: confidentiality 307, and label: disclosure range 308. It is composed. The keys for identifying each record are the user ID 301, the date 302, and the time 303. The user ID 301 is an identifier for uniquely identifying the accessing user. The date 302 indicates the date of access. Time 303 indicates the time of access. The folder / database 304 indicates a folder of the file server that has been accessed, or a database of the database server. File / table 305 shows the file of the accessed file server or the table of the database server. The creation user ID 306 is an identifier for uniquely identifying the user who created the information to be accessed. Label: Confidentiality 307 indicates the level of label (confidentiality). Label: Confidentiality 308 indicates the label category (public scope).

4A and 4B show an example of the label management database 222. In the label management database 222, the display range of the access log and the history of erroneous labeling by the user are stored.

The label management database 222 is composed of a display range table 400 (FIG. 4A) and a label assignment error history table 410 (FIG. 4B).

In the display range table 400, the range for displaying the access log is stored for each user.

The display range table 400 is composed of a user ID 401 and a display range 402. The key for identifying each record is the user ID 401. The user ID 401 is an identifier for uniquely identifying the user. The display range 402 indicates the display range of the access log, and is composed of the latest 403 and the oldest 404. The latest 403 indicates the latest limit of the access log to be displayed. The oldest 404 indicates the oldest limit of the access log to be displayed.

In the label assignment error history table 410, when the approving user or the audit user later determines that the label assigned by the user is an incorrect label, it is considered that there was an error in the label assignment, and the history is stored. ing.

The label assignment error history table 410 is composed of a user ID 411, a folder / database 412, a file / table 413, a label: confidentiality 414, a label: disclosure range 415, and a label assignment date and time 416. The keys for identifying each record are the user ID 411, the folder / database 412, the file / table 413, and the label assignment date and time 416. The user ID 411 is an identifier for uniquely identifying a user who has incorrectly assigned a label. The folder / database 412 indicates a file server folder or a database of a database server, which is a storage location for labeled information. The file / table 413 indicates a file of a file server or a table of a database server that stores information that has been incorrectly labeled. Label: Confidentiality 414 indicates the level (confidentiality) of the given label. Label: Confidentiality 415 indicates the category (publication range) of the given label. The label giving date and time 416 indicates the date and time when the label was given.

5A to 5C show an example of the label determination rule database 223.

In the label judgment rule database 223, the label judgment rule at the time of information creation regarding the information (expected information) expected to be created in the future and the label judgment rule at the time of auditing the already created information (existing information) are stored. There is.

The label determination rule database 223 is composed of a logical expression table 500 (FIG. 5A), a keyword table 510 (FIG. 5B), and a label table 520 (FIG. 5C).

In the logical expression table 500, as one of the rules for determining the label, a logical expression combining the keywords stored in the keyword table 510 is stored.

The formula table 500 is composed of a formula ID 501, a formula 502, and a type 503. The key for identifying each record is the logical expression ID 501.

The logical expression ID 501 is an identifier for uniquely identifying the logical expression. The logical expression 502 indicates an expression (logical expression) in which the keywords stored in the keyword table 510 are combined with logical symbols such as an AND condition and an OR condition. Type 503 indicates whether the formula is related to expected information or existing information, and the type thereof.

In the keyword table 510, the keywords used in the logical formula 502 of the logical formula table 500 are stored as one of the rules for determining the label.

The keyword table 510 is composed of a logical expression ID 511, a keyword ID 512, and a type 513. The keys for identifying each record are the logical expression ID 511 and the keyword ID 512. The logical expression ID 511 is an identifier for uniquely identifying the logical expression, and indicates in which logical expression the keyword is used. The keyword ID 512 is an identifier for uniquely identifying the keyword in the logical expression 502 of the logical expression ID 511. Keyword 513 indicates a keyword used in a logical expression.

In the label table 520, what kind of label is given to the expected information (a logical expression expressed by combining the logical expression table 500 and the keyword table 510) as one of the rules for determining the label. It is remembered.

The label table 520 is composed of a logical expression ID 521, a label: confidentiality 522, and a label: disclosure range 523. The key for identifying each record is the logical expression ID 521. The logical expression ID 521 is an identifier for uniquely identifying the logical expression. Label: Confidentiality 522 indicates the level of label (confidentiality). Label: Disclosure range 523 indicates a label category (publication range).

Subsequently, a series of processes for label management in the present embodiment will be described.

Figure 7 shows the process of creating information and assigning labels. FIG. 9 shows a process of automatically changing and improving the display range of the access log referred to at that time by using the history of erroneous labeling in the past. Further, FIG. 7 shows a registration process of expected information (information expected to be created) for comparing whether or not there is an error in the label when the label is given. Further, FIG. 8 shows a process of approving the label or auditing the label after assigning the label to check for an error in the label.

FIG. 6 shows a processing flow in which, among the information to be created, the information required for the top management of the organization to make a decision, that is, the information expected to be created in the future is set as the expected information. Note that FIG. 10 is an image of the setting screen.

In the process S600, the central control device 230 of the label management support system 200 starts the process flow of setting the expected information. After that, the user operation reception unit 214 processes. Proceed to process S601.

In the process S601, as input information of the expected information from the user, the input / output device 232 receives one or a plurality of keywords constituting the expected information and a logical expression in which the keywords are combined under the AND condition, the OR condition, and the like. Proceed to process S602.

In the process S602, the input / output device 232 receives the label to be given to the expected information from the user. Proceed to process S603.

In the process S603, the input / output device 232 accepts registration of the keywords and logical expressions input in the process S601 and the labels input in the process S602. Keywords, logical expressions, and labels are registered in the label determination rule database 223. The logical formula ID is automatically assigned by the system so that there is no duplication, and the assigned number is stored as the same number in the logical formula ID 501, the logical formula ID 511, and the logical formula ID 521. "Expectation" is stored in the type 503. Other items store information (keywords, logical expressions, labels) received by the input / output device 232. Proceed to process S604.

In the process S604, the central processing unit 230 ends the process flow for setting the expected information.

FIG. 7 is a diagram showing a processing flow of information creation and labeling.

In the process S700, the central control device 230 starts the process flow of information creation and labeling. Proceed to process S701.

In process S701, the user operation reception unit 214 receives from the user the start of information creation and the label (scheduled label) to be given to the created information. An example of the reception screen is shown in FIG. Proceed to process S702.

In process S702, the access log collection unit 211 collects the user's access log and the labels of the data and files indicated in the access log from the data management system 240 and holds them in the access log management memory 221. The user ID for collecting the access log may be specified by using the user's login information to the label management support system 200, or the user may be explicitly input with the user information to specify the user ID. It may be used as the user ID. Further, the target time for collecting the access log is specified as the date and time in the range of the display range 402 set in the display range table 400 of the label management database 222. Furthermore, the log at the time of creating the file or data shown in the access log (access log log) is also collected in parallel with the access log collection. The user ID specified when collecting the access log is specified by the access log creation user ID 306 and collected. In other words, it collects the logs that were accessed by the creator user when the files and data shown in the access log were created. Proceed to process S703.

In process S703, the label determination unit 212 compares the created information with the access log to determine the label. The data and file labels shown in the access log: confidentiality 307 and label: disclosure range 308 are compared with the confidentiality and disclosure range of the scheduled label to determine which is stricter. If the labels of the data and files shown in the access log are stricter than the schedule label (higher than the confidentiality of the schedule label, or different from the disclosure range of the schedule label / narrower than the disclosure range of the schedule label), process S704 If not, the process proceeds to process S709.

In the process S704, the label determination unit 212 holds the access log data and files determined to be strict in the process S703 as a log to be highlighted in the main storage device. Proceed to process S705.

In process S705, the label determination unit 212 compares the created information with the expected information to determine the label. If the content of the created information matches any expected information (logical expression 502 using the keyword 513), the label of the expected information: confidentiality 522 and the label: disclosure range 523, and the confidentiality and disclosure range of the scheduled label are displayed. Compare and determine which is stricter. If the label of the expected information is stricter than the schedule label (higher than the confidentiality of the schedule label, or different from the disclosure range of the schedule label / narrower than the disclosure range of the schedule label), the process proceeds to S706, and if not, the process proceeds to S706. Proceed to process S709.

In the process S706, the label determination unit 212 determines that the expected information is stricter than the scheduled label in the process S705. Therefore, the validity of the scheduled label is suspected. Hold in main memory. Proceed to process S707.

In process S707, the label determination unit 212 partially matches the access log data, the contents of the file, and the expected information (logical expression 502 using the keyword 513) (whether a part of the logical expression matches). ) Judgment, if they match, the process proceeds to process S708, and if not, the process proceeds to process S709.

In the process S708, the label determination unit 212 holds the partially matched access log data and files in the process S707 in the main storage device as a log to be highlighted. Proceed to process S709.

In process S709, the input / output device 232 displays the access log acquired in process S702. At the time of display, if the highlighting of the process S704, the warning display of the process S706, and the highlighting of S708 are held in the main storage device, these are also displayed. An example of the display screen is shown in FIG. Proceed to process S710.

In process S710, the user operation reception unit 214 specifies (1) to exclude data and files of the highlighted access log that are not related to information creation (exclusion designation), and (2) access log. The user accepts that the indicated data and file contents do not affect the labeling of information (no effect is specified). After the designation, if the highlighting remains, the user changes the label as necessary, registers the information, registers the label, and the user operation reception unit 214 accepts the registration of the label. Proceed to process S711.

In process S711, the central processing unit 230 ends the process flow of information creation and labeling.

FIG. 8 is a diagram showing a processing flow of label approval and label audit processing.

In the process S800, the central control device 230 starts the process flow of label approval and label audit. Proceed to process S801.

In process S801, the label audit unit 215 acquires the approval target list or the audit target list from the access log management memory 221 and displays the list. Proceed to process S802.

In process S802, the access log collection unit 211 uses the user's access log and the data and file labels shown in the access log that are insufficient in the data held in the access log management memory 221. , Collected from the data management system 240 and stored in the access log management memory 221. The user ID 301 held in the access log management memory 221 is used to specify the user ID for collecting the access log. After that, as in the process of process S702, the target time of the access log is specified, and the log at the time of creating the file or data indicated by the access log (access log log) is collected. Proceed to process S803.

In the process S803, the user operation reception unit 214 receives the selection of the information to be approved and the information to be audited from the approval target list or the audit target list from the user at the input / output device 232. Proceed to process S804.

In the process S804, the label determination unit 212 displays the access log on the input / output device 232 together with the highlighting and the warning display in the same process as the processes S703 to S709. An example of the display screen is FIG. 12 as in the process S709. Proceed to process S805.

In process S805, the user operation reception unit 214 receives the approval result and the audit result for the label from the approval user or the audit user at the input / output device 232.

In process S806, the user operation reception unit 214 determines whether or not the label is judged to be valid based on the approval result and the audit result. If it is valid, the process proceeds to process S808, and if it is not valid, the process proceeds to process S807.

In process S807, the label audit unit 215 corrects the label determined to be invalid according to the approval result or the audit result, and transmits the label to the data management system 240 as a correct label. In addition, the label change is notified to the user who has the access log that has accessed the information in the past. Further, the access log at the time of information creation is stored in the user ID 411, the folder / database 412, and the file / table 413 in the label assignment error history table, and the label information before modification is labeled as label: confidentiality 414 and label: disclosure range 415. Then, it is stored in the label assignment date and time 416, and the process proceeds to process S808.

In the process S808, the central processing unit 230 ends the process flow of the label approval and label audit processes. The contents stored in the access log management memory 221 are released.

FIG. 9 is a diagram showing a processing flow for changing the display range of the access log.

In the process S900, the central control device 230 starts the process flow of changing the display range of the access log.

In process S901, the access log collection unit 211 acquires the set value of the access log display range from the display range table 400 of the label management database 222. Proceed to process S902.

In process S902, the access log collection unit 211 receives the analysis result of the access log from the big data analysis system 250. Based on the analysis result, if there is a bias in the information attribute, the process proceeds to process S903, and if there is a bias in the user attribute, the process proceeds to the process S904, and there is no bias in the label assignment error. In the case, the process proceeds to process S907.

In process S903, the access log collection unit 211 proceeds to process S904 with respect to the information attribute in which the labeling error is biased. If there is no biased information attribute, the process proceeds to process S907.

In process S904, the label audit unit 215 expands the display range of the access log in order to prevent the user from making an error in assigning a label to an information attribute having many errors in assigning a label. It is assumed that the value for expansion is fixed by default. Proceed to process S903.

In process S905, the access log collection unit 211 proceeds to process S906 with respect to the user attribute in which the labeling error is biased. If there is no biased user attribute, the process proceeds to process S907.

In process S906, the label audit unit 215 expands the display range of the access log in order to prevent an error in assigning a label to a user attribute having many errors in assigning a label. It is assumed that the value for expansion is fixed by default. Proceed to process S905.

In process S907, the access log collection unit 211 changes the display range 402 of the display range table 400 based on the enlarged set value. Proceed to process S908.

In the process S908, the central processing unit 230 ends the process flow of the process of changing the display range of the access log.

FIG. 10 shows an example of an expected information setting screen as a setting screen to be displayed in the process of FIG. The expected information setting screen is a screen for setting expected information (information expected to be created), and is displayed on the input / output device 232 of the label management support system 200. The expected information setting screen is composed of a logical formula 1000, a keyword 1010, a label 1020, and an expected information setting button 1030. The logical expression 1000 is the expected information itself that is set by combining keywords, and indicates an expression (logical expression) in which words (input box 1011) registered by the keyword 1010 are combined with logical symbols such as AND condition and OR condition. The keyword 1010 is composed of a word (input box 1011) for registering as a keyword of expected information and a line addition 1012. Item numbers are assigned to the words (input box 1011), and there is a one-to-one correspondence with the item numbers in the formula 1000. To increase the number of words, press the line addition button 1012 to increase the word input box 1011. Item numbers are automatically assigned to the increased input boxes 1011. The label 1020 indicates a label to be given to the expected information, and is composed of the confidentiality 1021 and the disclosure range 1022. Confidentiality 1021 indicates the level (confidentiality) of the label given to the expected information. Disclosure range 1022 indicates the category (disclosure range) of the label given to the expected information. The expected information setting button 1030 is a button for registering information set by the user. As a result, the user accepts the registration of expected information on this screen.

FIG. 11 shows an example of a schedule label registration screen as a reception screen displayed in the process S701 of FIG. 7. The schedule label registration screen receives a declaration of the start of information creation and a label (scheduled label) to be given to the information when the user starts information creation, and is an input / output device of the label management support system 200. It is displayed at 232. The schedule label registration screen is composed of confidentiality 1101, disclosure range 1102, and information creation start button 1110. Confidentiality 1101 indicates the level (confidentiality) of the label (scheduled label) to be given to the information (created information) to be created. Disclosure range 1102 indicates the category (disclosure range) of the schedule label. The information creation start button 1110 is a button for the user to declare the start of information creation and register the schedule label to be given to the information. As a result, this screen accepts the start of information creation and the registration of the schedule label from the user.

FIG. 12 shows an example of an access log list display screen as a display screen to be displayed in the process S709 of FIG. 7 and the process S804 of FIG. The access log list display screen visualizes the access log when the user accesses the data management system 240 at the time of information creation, and is displayed on the input / output device 232 of the label management support system 200. The access log list display screen is enlarged display of the access log list 1200, the access log 1201, the highlighting 1202, the semi-highlighting 1203, the information image (broken line) 1204, the information image 1205, the magnifying glass icon 1206, and the like. It consists of a pop-up 1207, a schedule label 1208, a warning 1209, and a label registration button 1210.

The access log list 1200 shows a list of user access logs and labels of data and files shown in the access logs. The access log 1201 is a log of a specific user accessing the data management system 240 during the period of the display range 402 of the display range table 400, a label thereof, and is the minimum component of the access log list 1200. When the access log 1201 is clicked, the log (access log log) at the time of creating the file or data shown in the access log 1201 is displayed as another access log list 1200, and is scheduled to match the access log list. Update the values on label 1208 and warning 1209. Highlight 1202 indicates that the label of the access log 1201 is stricter than the schedule label (higher than the confidentiality of the schedule label, or different from the disclosure range of the schedule label / narrower than the disclosure range of the schedule label). It is a display for emphasizing. As a method of emphasizing, a darkening display, a hatching display, a display by checking the highlight column, or the like may be used. Right-click on the highlight to display the exclusion specification and no effect specification menu, and accept the exclusion specification and no effect specification from the user. After accepting exclusion designation and no influence designation, change to semi-highlight 1203. Semi-highlighted 1203, like highlighting 1202, indicates something stricter than the schedule label, and indicates that exclusion designation and no influence designation have already been made. Also, not only the one specified in this operation, but also the one that was specified as exclusion or no influence at the time of the previous information creation, it is assumed that the exclusion is specified or no influence is specified by default in this information creation. , The access log list display screen may be semi-highlighted from the beginning. Information image (broken line) 1204 indicates an image figure of data or a file accessed at the time of information creation. The information image 1205 shows an image figure of the information to be created. The magnifying glass icon 1206 is used to confirm the details of the access log 1201, and the access log is selected by using the magnifying glass icon 1206. The enlarged display pop-up 1207 is a screen for displaying the detailed contents of the access log 1201 selected by the magnifying glass icon 1206 in a pop-up. Schedule label 1208 indicates the schedule label of the creation information. If there is a change in the appointment label, accept the change. Warning 1209 is a column for warning that the label of the expected information is stricter than the schedule label. The label registration button 1210 is a button that becomes effective when there is no problem in label assignment due to exclusion designation, no influence designation, and schedule label change, and is a button for the user to assign a label. As a result, this screen accepts the label of the created information from the user.

In this embodiment, the display range table 400 of the label management database 222 is automatically improved by the system, but the management user may manually reset the display range table 400.

Further, in this embodiment, the audit user manually audits the validity of the label according to the processing flow of FIG. 8, but the system may periodically and automatically determine the validity of the label. In that case, in the situation where highlighting or warning is displayed, it is judged that the label is not appropriate, and the label shall be changed.

Further, in this embodiment, the keyword of the expected information is set on the expected information setting screen of FIG. 10, but for the existing information, the keyword is set on the same setting screen as that of FIG. 10, and the label determination rule database is used. Store in 223. At this time, the type 503 is not "expected" but "existing". The keyword of this existing information may be used to automatically perform an audit based on the keyword.

Further, in this embodiment, it is assumed that the information including the created information is stored in the data management system 240, but the information is downloaded from the data management system 240 to the terminal in the user's hand and new information is created. Later, it may be uploaded to the data management system 240. In this case, the information downloaded to the terminal at hand is compared with the information in the data management system 240, the label of the matching information is interpreted as the label of the information at hand, and access control is performed on the terminal at hand. Alternatively, the access result may be transmitted to the data management system 240 and added to the access log.

Further, in the present embodiment, regarding the label determined to be invalid as a result of the audit in the process S807, the user who has the access log to the information of the label is notified of the label change. , The information may be notified only to the user who has downloaded the information from the data management system 240.

Further, in the access log management memory 221 and the label assignment error history table 410, the access log management unit is limited to the file unit and the table unit, but the management unit is finer, that is, the word unit and the table in the file. It may be possible to manage up to the record unit in. In this case, the label comparison in the processing of FIGS. 7 and 8 may be performed by a word-based label or a record-based label.

101 File I
102 File II
103 Data III
104 New Information (File IV)
200 Label management support system 210 Main storage device 211 Access log collection unit 212 Label judgment unit 213 Accelerator log display unit 214 User operation reception unit 215 Label audit unit 221 Access log management memory 220 Auxiliary storage device 222 Label management database 223 Label judgment rule database 230 Central control device 231 Communication device 232 Input / output device 240 Data management system 241 Communication device 242 Access control unit 243 Information management server 250 Big data analysis system 260 Communication line

Claims (3)

A label management support method in which the label management support system supports label management.
The step of collecting the information accessed by the user when the label management support system creates the newly created information as an access log, and
A step in which the label management support system collects labels indicating the data and file attributes shown in the access log, and
The step that the label management support system displays the access log and the label, and
A step of comparing the label given to the newly created information by the label management support system with the data shown in the access log and the label of the file to determine the validity of the label.
A step in which the label management support system presents the result of determining the validity of the label to the user.
With
In the step of determining the validity of the label, the label management support system
It is determined that the access log with the label condition stricter than the given label condition is highlighted and presented to the user.
Access logs with label conditions that are stricter than the label conditions given above, and the data and file contents shown in the specification or access log that exclude those unrelated to information creation do not affect the labeling of information. Semi-highlight the access log specified in and determine that it will be presented to the user.
In the display step, the label management support system
Based on past labeling errors, it is determined whether the amount of errors is biased by the attributes of information or the attributes of the user, and if the errors are biased by the attributes of information, the attributes of the biased information Expand the display range of the access log for information creation, and if there is a bias in the error due to the user's attributes, expand and expand the access log display range for information creation with the biased user's attributes. and stores the display range that is in the database,
The information expected to be created and its label are preset,
The content of the information expected to be created is shown using the logical formula of the keyword.
In the step of determining the validity of the label, the label management support system
Comparing the content of the newly created information with the content of the information expected to be created,
If the contents of both are the same and the label condition of the information expected to be created is stricter than the label condition given to the newly created information, the label of the newly created information is incorrect. Judged to warn the user that there is
A label management support method characterized in that it is determined to emphasize an access log indicating data or a file that partially matches the information expected to be created. In the label management support method according to claim 1,
The label is information indicating confidentiality and openness, and is
A label management support method, characterized in that the label management support system determines that the label conditions are strict when the label management support system has high confidentiality and the disclosure range of openness is narrow or different. A label management support system that supports label management.
Control device and
Including storage and
The control device is
Collect the information accessed by the user when creating the newly created information as an access log,
Collect the data shown in the access log and the label showing the attribute of the file,
Display the access log and the label,
The validity of the label is judged by comparing the label given to the newly created information with the data and file label shown in the access log.
The result of determining the validity of the label is presented to the user, and the result is presented to the user.
The access log of the label condition stricter than the given label condition is highlighted and presented to the user.
Access logs with label conditions that are stricter than the label conditions given above, and the data and file contents shown in the specified or access log that exclude those unrelated to information creation do not affect the labeling of information. Semi-highlight the access log specified in and present it to the user.
Based on past labeling errors, it is determined whether the amount of errors is biased by the attributes of information or the attributes of the user, and if the errors are biased by the attributes of information, the attributes of the biased information Expand the display range of the access log for information creation, and if there is a bias in the error due to the user's attributes, expand and expand the access log display range for information creation with the biased user's attributes. Store the displayed range in the database
The information expected to be created and its label are preset,
The content of the information expected to be created is shown using the logical formula of the keyword.
The control device further
Comparing the content of the newly created information with the content of the expected information,
If the contents of both are the same and the label condition of the information expected to be created is stricter than the label condition given to the newly created information, the label of the newly created information is incorrect. Warn the user that there is
A label management support system that emphasizes access logs that indicate data or files that partially match the information expected to be created.

Images