KR20220039193A - File history tracking system in collaboration tools through steganography and method of the same - Google Patents

Abstract

Disclosed are file history tracking system in collaboration tools using steganography, which implements efficient collaboration and easy security accident handling and includes a version management function to increase work efficiency when files are operated through collaboration tools, and a method thereof. According to one embodiment of the present invention, the file history tracking system comprises: a tracking ID generation module configured to generate a file history tracking ID for a file generated from an original file through a collaboration tool; a steganography insertion module configured to insert file history tracking data including the file history tracking ID into the file by using steganography; and a tracking ID database in which the file history tracking data is stored.

Description

File history tracking system in collaboration tools through steganography and method of the same}

The present invention relates to a file history tracking system and method in a collaboration tool using steganography.

Watermarks are used for file security in personal messengers, corporate messengers, or various systems that exchange files for collaboration. For example, when transferring files between users for collaboration of documents or digital content, watermarking such as writing the name of the recipient in the background of the document or recording the name of the recipient when recording There are cases.

However, this conventional file security method using a watermark is inconvenient in that the file sender has to manually execute the watermark, and there is a problem in that work efficiency is lowered due to the watermark on the file receiver side as well. In addition, there is a problem that the existing watermarking method is provided in a form that can be recognized by humans and the location of the watermark can be understood. In addition, the conventional watermark-type file security management technology does not provide a file version management function, so there is a limit in work efficiency.

The present invention enables efficient collaboration and easy security incident management, and can provide a version management function, so that the file history in a collaboration tool using steganography can increase work efficiency when working with files through the collaboration tool To provide a tracking system and method therefor.

In addition, according to the present invention, the file sender does not have to waste time to insert a watermark when sending a file every time, and on the file receiver side, the file history tracking in a collaboration tool using steganography can not be interrupted by the watermark. To provide a system and a method therefor.

In addition, the present invention is to provide a file history tracking system and method in a collaboration tool using steganography that does not cause problems such as watermark damage attempts because file history tracking is performed in a form that is difficult for a user to recognize. .

In addition, the present invention is a collaboration tool using steganography that can effectively detect in which path the file leak occurred through steganography analysis of the leaked file and directed acyclic graph data analysis when a security incident such as a file leak occurs. To provide a file history tracking system and method in

A file history tracking system in a collaboration tool using steganography according to an embodiment of the present invention includes: a tracking ID generation module configured to generate a file history tracking ID for a file generated from an original file through the collaboration tool; a steganography insertion module configured to insert file history tracking data including a file history tracking ID into the file using steganography; and a tracking ID database in which the file history tracking data is stored.

The tracking ID generation module may include: a file history tracking data generator configured to generate file history tracking data including the file history tracking ID for the file; a directed acyclic data generation unit configured to generate directed acyclic graph data for the file based on the file history tracking ID; and a data storage unit configured to store the file history tracking ID and the directed acyclic graph data in the tracking ID database.

The directed acyclic graph data may include data on a direction-derived path from the original file to the file.

The file history tracking data may include the file history tracking ID, file original hash data, current version file hash data, user ID, current version storage time, and current version last view time.

A file history tracking system in a collaboration tool using steganography according to an embodiment of the present invention includes: a steganography tracking module configured to perform a security check by steganography analysis from a tracking target file that is a target of file history tracking may include more.

The steganography tracking module includes: a steganography extraction unit configured to extract a file history tracking ID and current version file hash data from the tracking target file by steganography analysis; a first identification unit configured to query the file history tracking ID in the tracking ID database to identify a first file related to the tracking target file; and a second identification unit configured to identify a second file corresponding to an upper path of the first file based on the directed acyclic graph data.

A file history tracking system in a collaboration tool using steganography according to an embodiment of the present invention further includes: a file format analysis module configured to analyze a first file format of the file and a second file format of the file to be tracked may include

The steganography insertion module may be configured to insert a file history tracking ID into the file based on steganography according to the first file format. The steganography extraction unit may be configured to extract a file history tracking ID from the tracking target file according to the second file format.

A file history tracking method in a collaboration tool using steganography according to an embodiment of the present invention includes: generating, by a tracking ID generation module, a file history tracking ID for a file generated from an original file through the collaboration tool; inserting, by the steganography insertion module, file history tracking data including a file history tracking ID into the file using steganography; and storing the file history tracking data in a tracking ID database.

The generating of the file history tracking ID may include: generating file history tracking data including the file history tracking ID for the file; generating directed acyclic graph data for the file based on the file history tracking ID; and storing the directed acyclic graph data in the tracking ID database.

A file history tracking method in a collaboration tool using steganography according to an embodiment of the present invention is: by a steganography tracking module, performing a security check by steganography analysis from a tracking target file that is a target of file history tracking It may include further steps.

The step of performing the security check by steganography analysis includes: extracting a file history tracking ID and current version file hash data from the tracking target file by steganography analysis; querying the file history tracking ID in the tracking ID database to identify a first file related to the tracking target file; and identifying a second file corresponding to an upper path of the first file based on the directed acyclic graph data.

According to an embodiment of the present invention, there is provided a computer-readable recording medium in which a program for executing the file history tracking method in the collaboration tool using the steganography is recorded.

According to an embodiment of the present invention, efficient collaboration and easy security incident management are possible, and a version management function can be provided, so collaboration using steganography can increase work efficiency when working with files through a collaboration tool. A system and method for tracking file history in a tool are provided.

In addition, according to an embodiment of the present invention, the file sender does not have to waste time to insert a watermark when sending a file every time, and the file receiver side is a collaboration tool using steganography that can not interfere with work due to the watermark A file history tracking system and method are provided.

In addition, according to an embodiment of the present invention, file history tracking system and method in a collaboration tool using steganography that does not cause problems such as watermark damage attempts because file history tracking is performed in a form that is difficult for a user to recognize this is provided

In addition, according to an embodiment of the present invention, when a security incident such as a file leak occurs, it is possible to effectively detect in which path the file leak occurs through steganography analysis of the leaked file and directed acyclic graph data analysis.

1 is a configuration diagram of a file history tracking system in a collaboration tool using steganography according to an embodiment of the present invention.
2 is a block diagram of a tracking ID generation module constituting a file history tracking system in a collaboration tool using steganography according to an embodiment of the present invention.
3 is an exemplary diagram of file history tracking data generated according to an embodiment of the present invention.
4 is a conceptual diagram of directed acyclic graph data generated according to an embodiment of the present invention.
5 is an exemplary diagram of directed acyclic graph data generated according to an embodiment of the present invention.
6 is a block diagram of a steganography tracking module constituting a file history tracking system in a collaboration tool using steganography according to an embodiment of the present invention.
7 is an exemplary diagram for explaining a method of tracking a tracking target file according to an embodiment of the present invention.
8 is a flowchart of a file history tracking method in a collaboration tool using steganography according to an embodiment of the present invention.
9 is a flowchart illustrating a method of tracking an outflow path of a tracking target file based on file history tracking data and directed acyclic graph data according to an embodiment of the present invention.

Advantages and features of the present invention and methods of achieving them will become apparent with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but may be implemented in various different forms, and only these embodiments allow the disclosure of the present invention to be complete, and common knowledge in the art to which the present invention pertains It is provided to fully inform those who have the scope of the invention, and the present invention is only defined by the scope of the claims. Like reference numerals refer to like elements throughout.

In the present specification, when a part "includes" a certain component, it means that other components may be further included, rather than excluding other components, unless otherwise stated. As used herein, '~ unit, ~ module' is a unit that processes at least one function or operation, and may refer to, for example, software, FPGA, or hardware component. The functions provided by '~ unit, ~ module' may be performed separately by a plurality of components, or may be integrated with other additional components. 'Part, ~ module' in this specification is not necessarily limited to software or hardware, and may be configured to be in an addressable storage medium, or may be configured to reproduce one or more processors. Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

1 is a configuration diagram of a file history tracking system in a collaboration tool using steganography according to an embodiment of the present invention. Referring to FIG. 1 , a file history tracking system 10 in a collaboration tool using steganography according to an embodiment of the present invention may include a file management server 100 .

The file management server 100 receives files such as various documents created and uploaded by the user, photos, audio data, and video data from the user terminal 20, stores them, and performs a process for security management of files. can

The user terminal 20 is a terminal used by a user, and may be, for example, a terminal such as a smartphone, a smart pad, a notebook computer, a laptop PC, or a desktop PC, but is not limited thereto.

The manager terminal 30 is a terminal used by an administrator who manages the file management server 100, and may be, for example, a terminal such as a smartphone, a smart pad, a notebook computer, a laptop PC, or a desktop PC, but is limited thereto. not.

The file management server 100 may automatically insert a file history tracking ID into the file requested by the user to download the file by using steganography and transmit it to the user terminal 20 when the user requests the file download. .

In addition, the file management server 100 inserts a new file history tracking ID into the file every time a file is downloaded for version management of one or more files sequentially generated from the original file through the collaboration tool, and can be transmitted to the user terminal 20. there is.

The manager terminal 30 can upload the tracking target file 40 that is the target of file history tracking to the file management server 100 in order to track the user who leaked the tracking target file 40 to an unauthorized third party. there is.

The file management server 100 may extract the steganography of the tracking target file 40 to analyze the file history tracking ID, and track the user who leaked the tracking target file 40 therefrom.

In addition, the file management server 100 may track a file corresponding to an original file generated before the tracking target file 40 and a higher path of the tracking target file 40 generated from the original file.

In an embodiment, the file management server 100 includes a file format analysis module 110 , a steganography analysis module 120 , a file database 130 , a tracking ID generation module 140 , and a steganography insertion module 150 . , a tracking ID database 160 and a steganography tracking module 170 .

The file format analysis module 110 may analyze the file format of the file uploaded by the user terminal 20 and/or the manager terminal 30 .

The file format analysis module 110 may analyze whether the file is in, for example, a PDF format, an MP3 format, or other file format. The file format analyzed by the file format analysis module 110 is not limited thereto, and may be variously changed.

The steganography analysis module 120 may perform steganography analysis according to the file format analyzed by the file format analysis module 110 .

For example, when the file format is a PDF document, steganography analysis may be performed using in-band signaling that is hidden in self-explosion, inter-character spacing, and leading ratio.

As another example, when the file format is an MP3 file or other audio file, steganographic analysis may be performed by analyzing the spread-spectrum phase-shift data after the audio data.

The file database 130 may store a file uploaded by a user. When the uploaded file includes the file history tracking ID, the file is stored in the file database 130 as it is in the state including the file history tracking ID.

The tracking ID generation module 140 may generate a file history tracking ID for a file generated from an original file through a collaboration tool.

The steganography insertion module 150 extracts the download requested file from the file database 130 when the user requests a file download, and uses steganography on the file to track file history data including the file history tracking ID. can be inserted.

In this case, a new file history tracking ID different from the file history tracking ID inserted in the previous version of the file may be inserted into the download-requested file.

The steganography insertion module 150 may insert the file history tracking ID into the file based on the steganography according to the first file format of the file analyzed by the file format analysis module 110 .

For example, if the file requested to be downloaded is a PDF document, the file history tracking data including the file history tracking ID is encoded with self-explosion, kerning, and leading ratio, and then the file history is inserted by moving the PDF object in a steganography method. You can insert file history tracking data that includes the tracking ID.

Table 1 below illustrates the insertion of a file history tracking ID into a PDF document by steganography.

Steganography insertion module 150, for example, by adjusting the spacing in the PDF document in units of 1 mm, encoding 1 for short spacing than other characters, and encoding the spacing with normal length as 0 Stegano File history tracking IDs can be inserted into PDF documents by graphy.

In addition, in order to read the hidden information from the inter-character data and to increase the confidentiality of the data added through the steganography technique, it is possible to insert the file history tracking ID after encoding it using the Manchester code. Through such an additional encoding process, a false positive rate of file history tracking ID recognition can be reduced, and variations between characters can be implemented less conspicuously.

When embedding encoded data in a PDF document, embedding can be performed by scattering the encoded data in various places throughout the document rather than in a designated location. This increases the probability of data discovery and increases the probability that the watermark will survive even if a part of the document is edited.

As another example, if the file requested to be downloaded is an MP3 file or other audio file, the file history tracking ID is obtained in a steganographic manner that encodes spread-spectrum phase-shift data and blends it into the audio file content. Included file history tracking data can be inserted.

The tracking ID database 160 may store file history tracking data including the file history tracking ID generated by the tracking ID generation module 140 and directed acyclic graph data to be described later.

Steganography tracking module 170, based on the file history tracking data stored in the tracking ID database 160 and directed acyclic graph data to be described later, performs a security check by steganography analysis from the tracking target file 40 can do.

2 is a block diagram of a tracking ID generation module constituting a file history tracking system in a collaboration tool using steganography according to an embodiment of the present invention. 3 is an exemplary diagram of file history tracking data generated according to an embodiment of the present invention.

1 and 2 , the tracking ID generation module 140 may include a file history tracking data generation unit 142 , a directional acyclic data generation unit 144 , and a data storage unit 146 .

The file history tracking data generating unit 142 may generate file history tracking data including a file history tracking ID for a file requested to be downloaded by the user terminal 20 .

3 is an exemplary diagram of file history tracking data generated according to an embodiment of the present invention. 1 to 3 , the file history tracking data generation unit 142 includes a file history tracking ID, file original hash data, current version file hash data, user ID, current version storage time, and current version final viewing time It is possible to create a file history tracking data (50).

This file history tracking data 50 may be inserted into a file requested to be downloaded by the user by steganography. The file into which the file history tracking data 50 is inserted may be transmitted to the user terminal 20 requesting the download of the file.

The directed acyclic data generation unit 144 generates directed acyclic graph data based on the file history tracking ID generated by the file history tracking data generation unit 142 for the file requested to be downloaded by the user terminal 20 . can

4 is a conceptual diagram of directed acyclic graph data generated according to an embodiment of the present invention. 5 is an exemplary diagram of directed acyclic graph data generated according to an embodiment of the present invention.

Referring to FIGS. 1, 2, 4 and 5 , the directed acyclic graph data 60 and 70 may include data on a direction-derived path from an original file to a file requested to be downloaded.

The directed acyclic graph data 60 and 70 are infinite directed graphs without directional circulation, and this data structure may be used for version management of files.

The directed acyclic data generation unit 144 may check the file history tracking ID of the previous file through the file history tracking data extracted by steganography from the previous version of the file, and based on the version relationship, the directed acyclic graph data (60 , 70) can be created.

In the examples of FIGS. 4 and 5 , uppercase letters A to G indicate files that are sequentially downloaded and updated by various users from the original file in the order of version.

In the examples shown in FIGS. 4 and 5 , a capital letter A of the alphabet indicates an original file created by the user A and uploaded to the server, and indicates that the user B and the user D have downloaded the original file A from the server, respectively.

In the example of FIG. 5 , file history tracking IDs indicating previous versions of files are listed in vertical fields, and file history tracking IDs indicating new versions of files are listed in horizontal fields.

In the example of FIG. 4, since the original file A was downloaded from the server by the user B and the user D, respectively, the field values of the 'B' column and the 'D' column of the row corresponding to the original file A in FIG. 5 are recorded as '1'. has been

In addition, in the example of FIG. 4 , since file B was downloaded from the server by user C, the field value of column 'C' of the row corresponding to file B in FIG. 5 is recorded as '1'.

From the directed acyclic graph data 60 and 70, it is possible to grasp the history of downloading files sequentially from the original file, and accordingly, the version management of the file is possible.

The data storage unit 146 tracks the file history tracking data including the file history tracking ID generated by the file history tracking data generation unit 142 and the directed acyclic graph data generated by the directed acyclic data generation unit 144 . It may be stored in the ID database 160 .

6 is a block diagram of a steganography tracking module constituting a file history tracking system in a collaboration tool using steganography according to an embodiment of the present invention.

1 and 6 , the steganography tracking module 170 may include a steganography extraction unit 172 , a first identification unit 174 , and a second identification unit 176 .

The steganography extraction unit 172 may extract the file history tracking ID and the current version file hash data from the tracking target file 40 by steganography analysis.

At this time, the steganography extraction unit 172 analyzes the file format of the tracking target file 40, and extracts the file history tracking ID from the tracking target file 40 by steganography according to the analyzed file format. there is.

Since the file history tracking data generated when it is downloaded from the server is inserted into the tracking target file 40 by steganography, the file history tracking ID and the current version file hash data can be extracted therefrom.

The first identification unit 174 may identify the first file related to the tracking target file 40 by inquiring the file history tracking ID extracted by the steganography extraction unit 172 to the tracking ID database 160 . .

The second identification unit 176 may identify the second file corresponding to the upper path of the first file based on the directed acyclic graph data.

7 is an exemplary diagram for explaining a method of tracking a tracking target file according to an embodiment of the present invention. A case in which the file E is the leaked tracking target file 40 in FIG. 4 will be described as an example.

The second identification unit 176 may inquire a row having a field value of '1' in the column CE corresponding to the file history tracking ID ID1 of the file E in the directed acyclic graph data.

In the example of FIGS. 4 and 7 , since the field value is '1' in the line corresponding to the file history tracking ID (ID2) of the file D corresponding to the previous version of the file E, which is the first file, the corresponding file D is the file E It may be determined as the second file corresponding to the upper path of .

In addition, the file corresponding to the upper path of the file D can be determined by inquiring the row in which the field value is '1' in the column (CD) corresponding to the file history tracking ID (ID2) of the file D.

In the examples of FIGS. 4 and 7 , since the file corresponding to the upper path of the file D is the original file A, the original file A may also be determined as the second file corresponding to the upper path of the file E which is the first file. On the other hand, since files B, C, F, and G do not correspond to a higher path of file E, they are not determined as the second file.

In addition, the steganography tracking module 170 includes the file history tracking ID (ID1) of the first file corresponding to the tracking target file 40, and the file history tracking IDs (ID2) of the second files corresponding to the upper path. , ID3) by inquiring the tracking ID database 160 , it is possible to recognize one or more users related to the leakage of the tracking target file 40 through the user ID related to the first file and the second file.

In addition, the steganography tracking module 170 extracts hash data from the file history tracking data analyzed by steganography analysis from the tracking target file 40 , and it matches the hash data stored in the tracking ID database 160 . It can be compared whether or not the tracking target file 40 is manipulated.

8 is a flowchart of a file history tracking method in a collaboration tool using steganography according to an embodiment of the present invention. 1 and 8 , when a file download request is made from the user terminal 20 , the tracking ID generation module 140 traces the file history including the file history tracking ID for the file generated from the original file through the collaboration tool. Data can be generated (S110).

The steganography insertion module 150 extracts the download requested file from the file database 130 when the user requests a file download, and uses steganography on the file to track file history data including the file history tracking ID. can be automatically inserted (S120).

The file history tracking data may include a file history tracking ID, a file original hash data, a current version file hash data, a user ID, a current version storage time, and a current version last view time.

A new file history tracking ID different from the file history tracking ID inserted in the file of the previous version may be inserted into the file requested to be downloaded by the user terminal 20 .

The steganography insertion module 150 may insert the file history tracking ID into the file based on the steganography according to the first file format of the file analyzed by the file format analysis module 110 .

In the embodiment, when the file requested to be downloaded is a PDF document, the file history tracking data including the file history tracking ID is encoded with self-explosion, kerning, and leading ratio, and then the PDF object is moved and inserted in a steganography method. You can insert file history tracking data including the history tracking ID.

Steganography insertion module 150, for example, by adjusting the spacing in the PDF document in units of 1 mm, encoding 1 for short spacing than other characters, and encoding the spacing with normal length as 0 Stegano File history tracking IDs can be inserted into PDF documents by graphy.

As another example, if the file requested to be downloaded is an MP3 file or other audio file, the file history tracking ID is obtained in a steganographic manner that encodes spread-spectrum phase-shift data and blends it into the audio file content. Included file history tracking data can be inserted.

Such file history tracking data may be inserted into a file requested for download by the user by steganography. The file into which the file history tracking data is inserted may be transmitted to the user terminal 20 requesting the download of the file.

The tracking ID generation module 140 may generate directed acyclic graph data based on the file history tracking ID for the file requested to be downloaded by the user terminal 20 ( S130 ).

The directed acyclic graph data may include data on a direction-derived path from an original file to a file requested to be downloaded. Directed acyclic graph data is an infinite directed graph without directed circulation, and this data structure can be used for version control of files.

The tracking ID generation module 140 may check the file history tracking ID of the previous file through the file history tracking data extracted by steganography from the file of the previous version, and generate directed acyclic graph data based on the version relationship. can

From this directed acyclic graph data, it is possible to determine the history of downloading files sequentially from the original file, and accordingly, file version management is possible.

The tracking ID generation module 140 records the file history tracking data including the file history tracking ID and the directed acyclic graph data to the tracking ID database 160 to determine the outflow path of the tracking target file 40 corresponding to the outflow file. can be saved

9 is a flowchart illustrating a method of tracking an outflow path of a tracking target file based on file history tracking data and directed acyclic graph data according to an embodiment of the present invention.

1, 6 and 9, the steganography extraction unit 172 may extract the file history tracking ID and the current version file hash data from the tracking target file 40 by steganography analysis ( S210).

At this time, the steganography extraction unit 172 analyzes the file format of the tracking target file 40, and extracts the file history tracking ID from the tracking target file 40 by steganography according to the analyzed file format. there is.

Since the file history tracking data generated when it is downloaded from the server is inserted into the tracking target file 40 by steganography, the file history tracking ID and the current version file hash data can be extracted therefrom.

The first identification unit 174 may identify the first file related to the tracking target file 40 by inquiring the file history tracking ID extracted by the steganography extraction unit 172 to the tracking ID database 160 . (S220).

The second identification unit 176 may identify the second file corresponding to the upper path of the first file corresponding to the outflow path of the tracking target file 40 based on the directed acyclic graph data (S230).

As such, the steganography tracking module 170 uses the file history tracking ID of the first file corresponding to the tracking target file 40 and the file history tracking IDs of the second files corresponding to the upper path of the tracking ID. By inquiring the database 160, the outflow path of the tracking target file 40 may be traced through the user ID associated with the first file and the second file.

In addition, the steganography tracking module 170 extracts hash data from the file history tracking data analyzed by steganography analysis from the tracking target file 40 , and it matches the hash data stored in the tracking ID database 160 . It is also possible to determine whether the tracking target file 40 has been manipulated by comparing it.

According to the file history tracking method in the collaboration tool using steganography according to the embodiment of the present invention as described above, the file sender does not have to waste time to insert a watermark when sending a file every time, and the file receiver does not have to The advantage is that the work is not interrupted by the watermark.

In addition, unlike the watermark being in a form that can be understood by humans and there is a risk of attempting to damage the watermark, according to the embodiment of the present invention, since file history tracking is performed in a form that is difficult for the user to recognize, the watermark There are no problems such as attempts to tamper with the mark.

In addition, according to the file history tracking method in the collaboration tool using steganography according to an embodiment of the present invention, when a security incident such as a file leak occurs, which It can effectively detect whether a file leak has occurred in the path.

In addition, according to the file history tracking method in the collaboration tool using steganography according to an embodiment of the present invention, efficient collaboration and easy security incident management are possible, and a version management function can be provided, so that the You can increase work efficiency when working with files.

At least some of the configurations of the embodiments described above may be implemented as a hardware component, a software component, and/or a combination of the hardware component and the software component. For example, the apparatus, method, and component described in the embodiments may include, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate (FPGA). Array), a programmable logic unit (PLU), a microprocessor, or any other device capable of executing and responding to instructions, may be implemented using one or more general purpose or special purpose computers.

The processing device may run an operating system and one or more software applications running on the operating system. A processing device may also access, store, manipulate, process, and generate data in response to execution of the software. For convenience of understanding, a processing device is sometimes described as being used, but a person of ordinary skill in the art will recognize that the processing device includes a plurality of processing elements and/or a plurality of types of processing elements. It will be understood that this may include

For example, the processing device may include a plurality of processors or one processor and one controller. Other processing configurations are also possible, such as a Parallel Processor. The software may include a computer program, code, instructions, or a combination of one or more thereof, which configures a processing device to operate as desired or is independently or collectively processed You can command the device.

The software and/or data may be any kind of machine, component, physical device, virtual equipment, computer storage medium or device, to be interpreted by or provide instructions or data to the processing device. , or may be permanently or temporarily embody in a transmitted signal wave. The software may be distributed over networked computer systems and stored or executed in a distributed manner. Software and data may be stored in one or more computer-readable recording media.

The method according to the embodiment may be implemented in the form of program instructions that can be executed through various computer means and recorded in a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, etc. alone or in combination. The program instructions recorded on the medium may be specially designed and configured for the embodiment, or may be known and available to those skilled in the art of computer software.

Examples of the computer-readable recording medium include magnetic media such as hard disks, floppy disks and magnetic tapes, optical media such as CDROMs and DVDs, and ROM, RAM, and flash memory. Hardware devices specially configured to store and execute program instructions, such as, etc. are included. Examples of program instructions include not only machine language codes such as those generated by a compiler, but also high-level language codes that can be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

As described above, although the embodiments have been described with reference to the limited embodiments and drawings, various modifications and variations are possible from the above description by those skilled in the art. For example, the described techniques are performed in an order different from the described method, and/or the described components of the system, structure, apparatus, circuit, etc. are combined or combined in a different form than the described method, or other components Or substituted or substituted by equivalents may achieve an appropriate result. Therefore, other implementations, other embodiments, and equivalents to the claims are also within the scope of the following claims.

10: File history tracking system in collaboration tools using steganography
20: user terminal
30: administrator terminal
40: Trace target file
50: file history trace data
60, 70: directed acyclic graph data
100: file management server
110: file format analysis module
120: steganography analysis module
130: file database
140: tracking ID generation module
142: file history trace data generation unit
144: directed acyclic data generation unit
146: data storage unit
150: steganography insertion module
160: tracking ID database
170: Steganography tracking module
172: Steganography extraction unit
174: first identification unit
176: second identification unit

Claims (10)

a tracking ID generating module, configured to generate a file history tracking ID for a file generated from the original file via the collaboration tool;
a steganography insertion module configured to insert file history tracking data including a file history tracking ID into the file using steganography; and
A file history tracking system in a collaboration tool using steganography, including a tracking ID database in which the file history tracking data is stored. According to claim 1,
The tracking ID generation module includes:
a file history tracking data generating unit configured to generate file history tracking data including the file history tracking ID for the file;
a directed acyclic data generation unit configured to generate directed acyclic graph data for the file based on the file history tracking ID; and
a data storage configured to store the file history tracking ID and the directed acyclic graph data in the tracking ID database;
The directed acyclic graph data is a file history tracking system in a collaboration tool using steganography, including data on a direction-derived path from the original file to the file. 3. The method of claim 2,
The file history tracking data is a file in a collaboration tool using steganography, including the file history tracking ID, file original hash data, current version file hash data, user ID, current version storage time and current version final viewing time Traceability system. 4. The method of claim 3,
Further comprising a steganography tracking module configured to perform a security check by steganography analysis from the tracking target file that is the target of file history tracking,
The steganographic tracking module includes:
a steganography extraction unit configured to extract a file history tracking ID and current version file hash data from the tracking target file by steganography analysis;
a first identification unit configured to query the file history tracking ID in the tracking ID database to identify a first file related to the tracking target file; and
A file history tracking system in a collaboration tool using steganography, comprising a second identification unit configured to identify a second file corresponding to an upper path of the first file based on the directed acyclic graph data. 5. The method of claim 4,
a file format analysis module, configured to analyze a first file format of the file and a second file format of the tracked file;
the steganography insertion module is configured to insert a file history tracking ID into the file based on steganography according to the first file format;
The file history tracking system in the collaboration tool using steganography, wherein the steganography extraction unit is configured to extract a file history tracking ID from the tracking target file according to the second file format. generating, by the tracking ID generating module, a file history tracking ID for a file generated from an original file through a collaboration tool;
inserting, by the steganography insertion module, file history tracking data including a file history tracking ID into the file using steganography; and
A file history tracking method in a collaboration tool using steganography, comprising the step of storing the file history tracking data in a tracking ID database. 7. The method of claim 6,
The step of generating the file history tracking ID is:
generating file history tracking data including the file history tracking ID for the file; and
generating directed acyclic graph data for the file based on the file history tracking ID; and
storing the directed acyclic graph data in the tracking ID database;
The directed acyclic graph data is a file history tracking method in a collaboration tool using steganography, including data on a direction-derived path from the original file to the file. 8. The method of claim 7,
The file history tracking data is a file in a collaboration tool using steganography, including the file history tracking ID, file original hash data, current version file hash data, user ID, current version storage time and current version final viewing time History tracking method. 9. The method of claim 8,
Further comprising, by the steganography tracking module, performing a security check by steganography analysis from the tracking target file that is the target of file history tracking,
The step of performing the security check by the steganographic analysis is:
extracting a file history tracking ID and current version file hash data from the tracking target file by steganography analysis;
querying the file history tracking ID in the tracking ID database to identify a first file related to the tracking target file; and
A file history tracking method in a collaboration tool using steganography, comprising the step of identifying a second file corresponding to a higher path of the first file based on the directed acyclic graph data. A computer-readable recording medium in which a program for executing the file history tracking method in the collaboration tool using steganography according to any one of claims 6 to 9 is recorded.

Images