KR101919488B1 - Method for implementing security system based on file management and data encryption and security system based on file management and data encryption - Google Patents

Abstract

A security system based on file management and data encryption and a security system based on file management and data encryption are disclosed. A method of implementing a security system based on file management and data encryption includes the steps of a security system management server receiving security information on a file and the file from a security client, File, and the step of the security system management server transmitting the security target file to the security client.

Description

A security system based on file management and data encryption, a security system based on file management and data encryption, and a security system based on file management and data encryption }

The present invention relates to a security system, and more particularly, to a security system based on file management and data encryption, and a security system based on file management and data encryption.

The business environment of enterprises is undergoing rapid change with the development of information technology (IT) technology. In other words, the IT environment that individuals can access through the rapid expansion of the Internet, the increase of the network speed, and the improvement of the performance of the personal computer are becoming universal and convenient.

The development of IT technology can bring relative security vulnerability at the same time as bringing convenience of business. Large-scale information leakage events such as member information of financial institutions and hacking of Nate which caused the leakage of personal information of 35 million, which is 70% of the population of the country, occurred, and a voice phishing attempt using this personal information and a spam , And loan attempts are taking place.

Therefore, the threats to the security of information systems such as hacking, viruses, leakage of personal financial information, abuse of e-mail, mass distribution of unhealthy information, and personal privacy and e-commerce, It is necessary to have an information protection system that can resolve and securely exchange information.

KR 10-2005-0098364

One aspect of the invention provides a method of implementing a security system based on file management and data encryption.

Another aspect of the present invention provides a security system based on file management and data encryption.

According to an aspect of the present invention, there is provided a method of implementing a security system based on file management and data encryption, the security system management server receiving security information on a file and the file from a security client, Converting the file into a security object file based on the security information, and transmitting the security object file to the security client by the security system management server.

The security information may include lifecycle information of the file to be protected and file deletion information of the file to be protected, and the lifecycle information may include an expiration date for the file to be protected Wherein the file deletion information is information on a specific action performed on the file to be protected for deleting the file to be protected, and the specific action is information on reading, updating, copying, moving The lifecycle information and the file deletion information may be accumulated and managed according to movement and copying of the security object file to another security client.

Also, the security system management server can directly delete the security object file on the security client and the other security client, with the right to delete the security object file directly.

Also, the security system management server manages the first identification information of the security client and the second identification information of the other security client, and the security system management server stores the first identification information and / or the second identification information And the tracking and management information is generated by performing tracking and management of the security object file stored in the security client and / or the other security client based on the tracking and management information, . ≪ / RTI >

Each of the security client and the other security target clients determines whether or not the first identification information and the second identification information are transmitted to the security system management server to the security system management server before receiving or cloning the security object file, It is possible to determine whether to delegate deletion of the security object file.

According to another aspect of the present invention, a security system implemented based on file management and data encryption includes a security system management server, the security system management server receives security information on a file and the file from a security client, Convert the file into a security object file based on the security information, and transmit the security object file to the security client.

The security information may include lifecycle information of the file to be protected and file deletion information of the file to be protected, and the lifecycle information may include an expiration date for the file to be protected Wherein the file deletion information is information on a specific action performed on the file to be protected for deleting the file to be protected, and the specific action is information on reading, updating, copying, moving The lifecycle information and the file deletion information may be accumulated and managed according to movement and copying of the security object file to another security client.

In addition, the security system management server may be configured to have a direct delete right on the security target file, and to directly delete the security target file on the security client and the other security client.

Also, the security system management server manages the first identification information of the security client and the second identification information of the other security client, and based on the first identification information and / or the second identification information, And / or to track and manage the security object file stored in the other security client to generate tracking and management information, and the direct deletion is performed based on the tracking and management information on the security object file .

Each of the security client and the other security target clients determines whether or not the first identification information and the second identification information are transmitted to the security system management server to the security system management server before receiving or cloning the security object file, It is possible to determine whether to delegate deletion of the security object file.

According to the method for implementing the security system based on the file management and the data encryption according to the embodiment of the present invention and the security system based on the file management and the data encryption, in addition to the existing access control method, The history of the steps and actions of the file is managed as data, so that the data leakage is prevented in advance and the transmission route can be immediately grasped even in the case of normal file transmission. In addition, it is possible to directly delete a file through a delete command of a server administrator, thereby preventing leakage of the file or illegal use of the file itself. In addition, a complete deletion function is implemented as a software, so that data can be prevented from being leaked by restoring the deleted file after deleting the file. In addition to this, data transmitted / received between financial institution servers can be encrypted in XML / JSON format, thereby protecting against information leakage and hacking, and the transmission speed can be drastically reduced.

1 is a conceptual diagram illustrating a security method for a file in a security system according to an embodiment of the present invention.
2 is a conceptual diagram illustrating a security system according to an embodiment of the present invention.
3 is a conceptual diagram illustrating an operation for file security in a file management system according to an embodiment of the present invention.
4 is a conceptual diagram illustrating an encryption processing method for data in a security system according to an embodiment of the present invention.
5 is a conceptual diagram illustrating communication of encrypted data between financial institution servers according to an embodiment of the present invention.
FIG. 6 is a conceptual diagram illustrating a method of setting file life cycle information for a file according to an embodiment of the present invention.
7 is a conceptual diagram illustrating a file tracking method according to an embodiment of the present invention.

The following detailed description of the invention refers to the accompanying drawings, which illustrate, by way of illustration, specific embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention. It should be understood that the various embodiments of the present invention are different, but need not be mutually exclusive. For example, certain features, structures, and characteristics described herein may be implemented in other embodiments without departing from the spirit and scope of the invention in connection with an embodiment. It is also to be understood that the position or arrangement of the individual components within each disclosed embodiment may be varied without departing from the spirit and scope of the invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is to be limited only by the appended claims, along with the full scope of equivalents to which such claims are entitled, if properly explained. In the drawings, like reference numerals refer to the same or similar functions throughout the several views.

Hereinafter, preferred embodiments of the present invention will be described in more detail with reference to the drawings.

Currently, there exists a file encryption system and an access authority management system as a system for security. Most of the current information leakage incidents are caused by carelessness of the authorized administrator or manager's intention. In many systems that require security, there are files that are not encrypted, and even encrypted files are public key, which means there is always the possibility that encryption of the files is released.

That is, if a file is leaked in the present security system, the file may be an unencrypted file or a file that can be easily decrypted, and there is always a possibility of damage due to leakage of such a file. For example, files that require security such as the current bank association / NICE / KCB CB end-of-date information files exist in the form of a TEXT file on the server. That is, it is possible for a user other than the person in charge to view or download a file that requires security within the current security system without any special encryption.

Information leakage from three existing card companies is an accident caused by the leakage of such a file, which is caused by the inability to control copy or download of the file.

A security setting method and apparatus for a file according to an embodiment of the present invention discloses a method of setting a deletion period, a deletion time setting method, and a file deletion condition of a file stored in a security system. Also, in the security setting method and apparatus for a file according to an embodiment of the present invention, a user can check a file using only a dedicated tool and decrypt an encrypted file.

1 is a conceptual diagram illustrating a security method for a file in a security system according to an embodiment of the present invention.

In Fig. 1, a newly defined file format and a security function for a file for file security are disclosed.

Referring to FIG. 1, in a security system according to an embodiment of the present invention, a file format including life cycle information may be defined. Specifically, the file format including the life cycle information may include file life cycle information 100 and file information. In addition, a file format that further includes information on a file deletion condition (hereinafter, file deletion condition information 120) as well as life cycle information may be defined.

The lifecycle information 100 may include information on a time period and a time period during which deletion of a file is performed after the file is created.

The file deletion condition information 120 may include information on a specific condition for deleting a file after creation of the file.

Hereinafter, in the embodiment of the present invention, the file format including the lifecycle information 100 and the file deletion condition information 120 is expressed as a security target file format, the file generated based on the security target file format is referred to as security It is represented by the term target file. For example, the lifecycle information 100 and the file deletion condition information 120 may be included as header information of a security object file.

In the security system according to the embodiment of the present invention, the security object file format can be utilized as a file format.

The security object file can be deleted based on the life cycle information 100 included in the security object file. As described above, the life cycle information 100 may include information on a period / time (or time / time when a file is activated) for deleting a file, and a file to be secured may be included in the life cycle information 100 And may be deleted based on information on the period / time. For example, if 30 days is set to the life cycle of a file to be protected, after 30 days, the file to be protected may be deleted or deactivated.

In addition, the security object file can be deleted based on the file deletion condition information 120 included in the security object file. As described above, the file deletion information 120 may include information on a condition for deletion of a file, and the security object file may be deleted based on the file deletion condition information 120. [ For example, when a specific action for a security target file occurs, the security target file can be deleted. A specific action for deleting a security target file is to delete the file for more than 5 times of reading, n times of update, n times of copy, n times of move or n times of download, It may be the specific action performed.

In addition, according to the embodiment of the present invention, the security object file can be viewed only by the exclusive viewer, and the settlement can be obtained by the settlement process upon decryption. The security system can perform an alarm operation in conjunction with an operational risk detection system or an early warning system or transmit short message service (SMS) characters to a person in charge.

In addition, the security system can manage the history of all actions (read, copy, download, etc.) performed on the file. That is, a management server for managing actions for all files may be separately constructed and registered as a management server in order to build a security system.

In addition, the security system management server can support an operating system (OS) such as Windows, UNIX, LINUX, mobile (Android, iOS). The security system management server can perform the deletion procedure for the security file, and the deletion to the file can be a deletion that can not be completely recovered by S / W wiping (overwriting). The security system management server can delete files that are entered by the administrator through the normal root through the remote delete command.

In addition, the security system management server can support MS Office, Hangul, Text, PDF, image file, compressed file and so on. In addition, the security system management server supports the encryption method using the public key recommended by the FSS, and can support a function of only viewing a file by a specific person in charge. In addition, the security system management server can provide an automatic decryption and transmission queue method or a secure file transfer protocol (SFTP) input function for a specific program.

When the security system according to the embodiment of the present invention is used, the history of the steps and actions of the file is managed as data in addition to the existing access control method, the file itself has a life cycle, Even when transferring normal files, it is possible to grasp the transfer route of the file immediately. In addition, the deletion of the file can be directly performed by the deletion command of the administrator of the security system management server, and the leakage of the file or the illegal use of the file itself can be prevented. In addition, a complete deletion function is implemented as a software, so that data can be prevented from being leaked by restoring the deleted file after deleting the file.

2 is a conceptual diagram illustrating a security system according to an embodiment of the present invention.

In Fig. 2, a file management system for security is disclosed.

2, the file management system may include a security system management server (file security management server 200, file creation / processing server 210, communication server 220) and a security client 230.

The security client 230 may be a user device (for example, a notebook PC, a personal computer, a smart phone, or the like) who wants to use a file to be secured. The user device may be a variety of operating systems (e.g., MS WINDOW, LINUX, iOS, ANDROID, etc.). The security client 230 may directly set life cycle information and file deletion condition information of the generated file.

The file security management server 200 can be implemented for security management of files. The file security management server 200 receives lifecycle information and file deletion condition information of the file from the security client 230 and performs security setting on the file when there is a request for file security from the security client 230 can do.

The file creation / processing server 210 can be implemented for generation of a security target file. The file creation / processing server 210 can change the file format to a security target file format. For example, the security target file format may include file life cycle information and file deletion condition information as header information.

The communication server 220 can be implemented for communication with an external file management system.

A plurality of file management systems may exist, and each of the plurality of file management systems may communicate with each other through a communication server to transmit information about the management of a security target file created / managed in each of the plurality of file management systems, .

The lifecycle information and the file deletion information may be accumulated and managed in accordance with movement and copying of the security target file from the security client to the other security client in accordance with the movement of the file.

Alternatively, the security system management server may separately set a lifetime of the security object file in another user apparatus by setting a separate lifecycle when transmitting the security object file to another user apparatus.

3 is a conceptual diagram illustrating an operation for file security in a file management system according to an embodiment of the present invention.

3, communication between the security system management server and the security client for file security is initiated in the file management system.

Referring to FIG. 3, the security client can set various security information for file security. Specifically, the security client can set the lifecycle of the file, the encryption method of the file, the setting of the action that can be performed on the file, the setting of the person having authority to the file, and other settings for the file.

The security client can transmit the set security information and file information to the security server (step S300).

The security system management server may generate a security object file based on the security information and the file information, and may transmit the security object file to the security client (step S310).

In addition, the security client may receive the security object file generated by the security system management server based on the security information, and may perform processing and automatic deleting procedure for the security object file (step S320).

For example, the security client can make access to the security target file available only to a specific person based on the person information included in the security target file. Also, the security client can perform the automatic deleting procedure for the security target file in consideration of the expiration of the lifecycle of the security target file and the satisfaction of the file deletion condition based on the life cycle information and the file deletion condition information.

In addition to this, the security client may receive a separate mandatory delete command for the file from the security system management server, and may perform deletion of the security target file in accordance with the mandatory delete command.

The security system management server can generate header information of the security target file based on the security information and generate the security target file based on the security target file format.

The security system management server can perform file transfer to the security target file, and can perform the file control procedure in the security system management server itself. The file control procedure may be a security clearance procedure for a file based on direct control of the security system management server as a procedure for enforcing a file operation.

In addition, the security system management server can alert and monitor security problems generated in a security object file generated in the security system through alert / warning and occasional monitoring.

That is, the security system management server receives the file and the security information for the file from the security client, and the security system management server can convert the file to the security target file based on the security information. In addition, the security system management server can transmit the security target file to the security client.

Hereinafter, an embodiment of the present invention discloses an encryption procedure for data in a security system.

Currently, the communication with the Federation of Korean Industries, NICE, KCB, and financial institutions (1,2 financial sector, loan department, etc.) is carried out by X.25 or transmission control protocol (TCP) Under the exceptional approval of the Financial Supervisory Service, we are exchanging valuable customer data without encrypting it.

Data (or text) to be transmitted / received in the security system is also subjected to processing of a designated length offset method, and even a CRC (cyclic redundancy check) or check BIT verification is not performed. There is no preparation for error or hacking. Exposed lines will also be exposed to hacking. Moreover, the offset method increases the problem of pushing even one byte of data. Moreover, when a packet unit is 4k (4096) bytes, when the amount of data is large, the transfer speed also becomes very slow due to occurrence of repeated repetition. Also, in the case of a batch professional, it is necessary to always check the perfect match between the provider and the user regarding the definition of the item and the information of the offset, and there may be a problem in changing only one side.

Hereinafter, an embodiment of the present invention discloses an encryption process for data in a security system to solve the above problem. Hereinafter, the data may be interpreted to include a message transmitted between communicable devices.

4 is a conceptual diagram illustrating an encryption processing method for data in a security system according to an embodiment of the present invention.

4 illustrates a method of transmitting encrypted data between financial institution servers in a security system. For example, a financial institution server may be a server such as a CB (Credit Bureau), a financial institution / a CB company / association, a federation / insurance association, and other financial institutions.

Referring to FIG. 4, data transmitted / received between financial institution servers in the security system is generated in XML (extensible markup language) / JSON (JavaScript Object Notation) format instead of offset, and data in XML / And may be transmitted / received between financial institution servers in the security system. By defining only items in the XML / JSON format data, a faster mapping between the provider and the user can be performed. Also, when an encrypted file transfer scheme is used, all of the data can be transferred at once and the degradation in speed due to repeated transmission and reception can be reduced.

When the data is encrypted in the XML / JSON format, it is possible to protect against information leakage and hacking, and the transmission speed can be drastically reduced. In addition, the matching between the provider and the user for the data is terminated only by the item matching, so that the development speed and consistency with respect to the data can be remarkably improved.

An outflow-related problem that arises in the case of a batch file can be solved by using the security system described above in Figures 1-3. Data transmitted and / or received between financial institutions and financial institutions is encrypted in this manner, so that security and consistency of data can be dramatically improved.

5 is a conceptual diagram illustrating communication of encrypted data between financial institution servers according to an embodiment of the present invention.

5, a procedure of transmitting and receiving data between financial institution servers is disclosed.

Referring to FIG. 5, the first financial institution server may generate data in JSON format according to a request of a business unit.

The first financial institution server can encrypt the data in the JSON format and transmit the encrypted data to the second financial institution server (step S510).

The second financial institution server may receive the encrypted data, perform the release procedure for the encrypted data, and then generate the response data for the encrypted data. Response data for the encrypted data can be generated based on the JSON format.

The second financial institution server may encrypt the response data for the encrypted data in the JSON format and transmit the encrypted response data to the first financial institution server (step S520).

The first financial institution server may receive the encrypted response data, perform the release procedure for the encrypted response data, and then perform the business process based on the response data that decrypts the encrypted data at the business end.

FIG. 6 is a conceptual diagram illustrating a method of setting file life cycle information for a file according to an embodiment of the present invention.

6 illustrates a method for a security system management server to set lifecycle information for a file.

Referring to FIG. 6, the security system management server can set a life cycle of a file according to security importance of the file. Setting of the lifecycle of individual files by the user apparatus may be performed, but an automatic lifecycle setting procedure is performed in the security system management server, and the security system management server periodically informs the user whether the life cycle of the file is extended .

Alternatively, the security system management server can determine the life cycle of the file and recommend the life cycle of the file to the user through an algorithm for determining the security necessity of the file.

Specifically, the security system management server determines the security necessity of the file in consideration of the contents information in the file, and can determine the life cycle of the file according to the security necessity of the file. For example, the security system management server can determine whether or not information estimated as the user's personal information is included as internal contents of the file. When the personal information of the user is included as the internal content of the file, the security system management server can determine the file as the security target file and determine the life cycle of the security target file. In addition, the security system management server can determine whether a file security requirement is detected by searching whether the vocabulary associated with security is included as content information in the file.

If the security required level of the file is equal to or greater than a predetermined threshold value, the security system management server can set the lifecycle of the file in consideration of the life cycle set in the file containing the same / similar content as the corresponding file. The comparison of the contents similarity between the files of the security system management server can be performed based on the text included in the contents.

Specifically, when the content of the current file includes personal information (for example, a resident registration number, a telephone number, an address, a name, and the like), a file containing personal information has been previously set as a security target file The life cycle of the current file can be determined by the security system management server in consideration of the life cycle set at the time of creation.

According to another embodiment of the present invention, the security system management server may transmit the lifecycle of the current file determined as described above to the user device (security client) as the recommended lifecycle information 600. The user device (security client) may receive the recommendation lifecycle information 600 and may allow the life cycle of the current file to be set to the recommended life cycle by accepting the recommendation life cycle. Alternatively, the user device (security client) may receive the recommended lifecycle information 600 and change the recommended lifecycle to set the lifecycle of the current file.

According to an embodiment of the present invention, a file deletion condition for a file can also be determined in the same manner.

Specifically, the security system management server determines the security necessity of the file in consideration of the content information in the file, and can determine the file deletion condition of the file according to the security necessity of the file.

If the security required level of the file is equal to or greater than a predetermined threshold, the security system management server can set a file deletion condition of the file in consideration of a file deletion condition set in an existing file containing the same / similar content as the corresponding file. The comparison of the contents similarity between the files of the security system management server can be performed based on the text included in the contents.

The security system management server can transmit the file deletion condition of the current file set as described above to the user device (security client) as recommendation file deletion condition information 620. [ The user device (security client) receives the recommended file deletion condition information 620, accepts the recommended file deletion condition information 620, and sets the file deletion condition of the current file to be the same as the recommended file deletion condition information 620 can do. Alternatively, the user device (security client) may receive the recommended file deletion condition information 620 and change the recommended file deletion condition information 620 to be set as the file deletion condition information of the current file.

7 is a conceptual diagram illustrating a file tracking method according to an embodiment of the present invention.

In FIG. 7, a method is disclosed in which the security system management server tracks the location of a file and proceeds to delete the file in consideration of the location of the tracked file.

Referring to FIG. 7, the location of the security object file generated through the security system management server can be continuously tracked, and information on the current location of the copied file / transferred file is managed through the security system management server .

Specifically, in order to transfer / copy the security object file to / from a specific user device, it is necessary to transfer the security object file to the security system management server in the device identification information (for example, IP (internet protocol) A delivery procedure can be performed.

The security object file can be configured to request the user device to which the security target file is to be transferred or copied to transmit the identification information 700 of the user device to the security system management server and to request the user device to delete additional rights to the file. For example, such a request (request for transmission of identification information, request for deletion permission) based on the header information of the security target file can be performed on the user device.

When the user of the user device accepts the request for transmission and deletion of the identification information 700 of the user apparatus to the security system management server, the identification information 700 of the user apparatus can be transmitted to the security system management server. On the contrary, if the user of the user device does not accept the transmission request or the deletion permission request of the identification information 700 of the user device to the security system management server, copying of the security object file to the user device may not be performed.

When the user of the user device accepts the transmission request and the deletion permission request of the identification information 700 of the user apparatus to the security system management server, the security system management server transmits the identification information 700 of the user apparatus and the security- Based on the delete privilege, the target file can be deleted if necessary.

For example, the first security client and the second security target client respectively determine whether the first identification information and the second identification information are transmitted to the security system management server by the security system management server before receiving or copying the security target file, You can decide whether to delegate file deletion permission.

When the security system management server is delegated authority to delete the identification information and the security target file from each of the first security client and the second security target client, the security system management server transmits the first identification information of the first security client and the first identification information of the second security client The security system management server manages the second identification information, and the security system management server performs tracking and management of the security target file stored in the client and / or the other client based on the first identification information and / or the second identification information, Information can be generated. Direct deletion of the security target file of the security system management server can be performed based on tracking and management information about the security target file.

Such a method of implementing a security system based on file management and data encryption may be implemented in an application or implemented in the form of program instructions that can be executed through various computer components and recorded in a computer-readable recording medium. The computer-readable recording medium may include program commands, data files, data structures, and the like, alone or in combination.

The program instructions recorded on the computer-readable recording medium may be those specially designed and configured for the present invention and may be those known and used by those skilled in the computer software arts.

Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks and magnetic tape, optical recording media such as CD-ROMs and DVDs, magneto-optical media such as floptical disks, media, and hardware devices specifically configured to store and execute program instructions such as ROM, RAM, flash memory, and the like.

Examples of program instructions include machine language code such as those generated by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like. The hardware device may be configured to operate as one or more software modules for performing the processing according to the present invention, and vice versa.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it will be understood by those skilled in the art that various changes and modifications may be made therein without departing from the spirit and scope of the invention as defined in the appended claims. It will be possible.

Claims (10)

A method of implementing a security system based on file management and data encryption,
The security system management server receiving security information on the file and the file from the security client;
The security system management server converting the file into a security target file based on the security information; And
The security system management server transmits the security object file to the security client,
Wherein the security information includes lifecycle information on the security object file and file deletion information on the security object file,
Wherein the lifecycle information is information on an expiration date of the file to be protected for deletion of the file to be protected,
Wherein the file deletion information is information on a specific action performed on the file to be protected for deletion of the file to be protected,
Wherein the specific action includes reading, updating, copying, and moving the security target file,
Wherein the lifecycle information and the file deletion information are accumulated and managed according to movement and duplication of the security object file to another security client. delete The method according to claim 1,
Wherein the security system management server has a direct delete right on the security object file and proceeds to delete the security object file directly on the security client and the other security client. The method of claim 3,
Wherein the security system management server manages first identification information of the security client and second identification information of the other security client,
The security system management server performs tracking and management of the security object file stored in the security client and / or the other security client based on the first identification information and / or the second identification information, Lt; / RTI >
Wherein the direct deletion is performed based on the tracking and management information for the security object file. 5. The method of claim 4,
Wherein each of the security client and the other security target clients determines whether or not the first identification information and the second identification information are transmitted to the security system management server to the security system management server before receiving or duplicating the security object file, The deletion permission of the target file is determined. A security system implemented based on file management and data encryption,
The security system includes a security system management server,
The security system management server receives security information on the file and the file from the security client,
Converting the file into a security object file based on the security information,
And to transmit the secured object file to the secure client,
Wherein the security information includes lifecycle information on the security object file and file deletion information on the security object file,
Wherein the lifecycle information is information on an expiration date of the file to be protected for deletion of the file to be protected,
Wherein the file deletion information is information on a specific action performed on the file to be protected for deletion of the file to be protected,
Wherein the specific action includes reading, updating, copying, and moving the security target file,
Wherein the lifecycle information and the file deletion information are accumulated and managed according to movement and replication of the security object file to another security client. delete The method according to claim 6,
Wherein the security system management server has a direct deletion right for the security object file and performs the direct deletion of the security object file on the security client and the other security client. 9. The method of claim 8,
Wherein the security system management server manages first identification information of the security client and second identification information of the other security client,
And to track and manage the security object file stored in the security client and / or the other security client based on the first identification information and / or the second identification information to generate tracking and management information,
Wherein the direct deletion is performed based on the tracking and management information for the security object file. 10. The method of claim 9,
Wherein each of the security client and the other security target clients determines whether or not the first identification information and the second identification information are transmitted to the security system management server to the security system management server before receiving or duplicating the security object file, And to determine whether to delegate deletion permission of the target file.

Images