KR101499965B1 - Method of verifying and protecting secure information using ticket - Google Patents

Abstract

The method includes receiving security information from a client and storing the security information, generating a first ticket required to extract the security information from the database, transmitting the first ticket to the client, And extracting the security information corresponding to the first ticket if the second ticket is identical to the first ticket by verifying the second ticket.

According to an embodiment of the present invention, only the internal key value can be transmitted through the network while hiding user information internally.

Ticket, Authentication, Privacy, Security, Password

Description

[0001] The present invention relates to a method for authenticating and protecting security information using a ticket,

The present invention relates to a method and apparatus for authenticating and protecting personal information using tickets to prevent security information from being exposed between a client and a server. The method comprising: receiving and storing security information from a client; generating a first ticket required to extract the security information from the database; sending the first ticket to the client; Receiving the ticket and verifying the second ticket and extracting security information corresponding to the first ticket when the second ticket is identical to the first ticket, And more particularly to a method for authenticating and protecting the same.

Data transmitted and received between a server and a client may be transmitted or received without encryption or without encryption. However, regardless of whether data is transmitted or received, the data transmitted and received between the server and the client may be exposed on the Internet. For example, in the case of functions such as finding a password or registering an existing member, important data (social security number, name, phone number, etc.) inputted by the user during the first step is transmitted as parameters, Exposed. It is an environment in which a malicious user can obtain data through packet sniffing.

Take as an example the member's password search function. The user first confirms whether he or she is a member by inputting his / her social security number and name, and confirms the identity with this information. At this time, if the member information is not transmitted in order to use the member information at the next step, it is troublesome to input personal information every time the page change occurs. Therefore, the method used by most of the services using the web is done by passing the parameters by POST or GET method and acquiring the parameters as they are on the next page. Although these parameters are exchanged between the client and the server through the HTTP protocol, personal information may be leaked if communication data is hacked. Also, in order to prevent leakage of such personal information, data is transmitted in a GET or POST manner. However, since the data itself transmitted through the GET / POST method is not secured, security information such as personal information is leaked.

In order to solve the above-described problems, an object of the present invention is to provide a method and apparatus for transmitting and receiving only a minimum amount of information through a network by internally transmitting a unique internal key value representative of the user information, To acquire and process information.

It is another object of the present invention to increase the network load and the processing speed by transmitting and receiving only the key value of the various data generated in the transmission and reception of the user in the cookie without using the cookie or communication parameters.

According to an aspect of the present invention, there is provided a method for transmitting security information, the method comprising: receiving and storing security information from a client; generating a first ticket required to extract the security information from the database; Receiving a second ticket from the client and verifying the second ticket and extracting security information corresponding to the first ticket when the second ticket is identical to the first ticket; .

As described above, according to the embodiment of the present invention, the key information is transmitted / received through the network, and only the key value capable of extracting the corresponding information is transmitted / received. Therefore, the load on the network is reduced, the processing speed is improved, Security can be enhanced.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the drawings, the same reference numerals are used to designate the same or similar components throughout the drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention unclear.

In the embodiment of the present invention, description will be made mainly on the basis of personal information. However, the present invention can be applied to transmission and reception of all information requiring security besides personal information. Since the characteristics of the information do not affect the present invention, the present invention can be applied to all information transmitted and received between the client and the server. Also, in order to reduce the amount of data to be transmitted / received, only the key value may be transmitted / received, and the detailed information may be stored in a database of the server.

1 is a diagram illustrating a process of transmitting and receiving a ticket-based data according to an embodiment of the present invention.

First, a process of transmitting and receiving personal information between a web browser of the client 100 and the member information server 200 and storing a ticket can be seen. The client 100 means a digital device having a function of connecting to an external server via a network including a general computer, a notebook computer, a PDA, and the like. The member information server 200 manages member information, and when receiving personal information, stores the data in a local DB and generates a ticket. The details will be described below.

The client 100 inputs personal information requested by a web page or the like (S110). The personal information may be a name, a resident registration number, or a telephone number, and may be unique information (for example, a user serial number, etc.) charged to an individual user on the Internet service. At this time, the unique information should not be exposed to other people, and usually corresponds to information classified as security information on the Internet.

The personal information input in the step S110 includes a case where the personal information is transmitted and received during the service providing process such as password search, password modification, personal information confirmation, and correction. When the client inputs personal information on the service page, the input information is transmitted to the member information server 200 through the POST or GET method. Although the POST method is more secure than the GET method, it can transmit and receive by the GET method with encryption.

The member information server 200 receives the personal information and stores it in the DB (S120). This is for storing the data for transmission when requesting confirmation or transmission of personal information from the client in the future. A database can be used as a storage medium, but it is not limited to a database, and various media such as a memory, a file, and a pipe can be used. After storing the personal information, a ticket is generated based on the personal information (S125). The created ticket is stored together with the personal information in the area where the personal information is stored in step S120. The process of generating a ticket based on the personal information and the process of storing the personal information and the ticket in the database will be described later. In order to transmit the generated ticket to the client, the ticket is added to the HTTP Request object as an attribute value and transmitted (S130). The value included in the HTTP Request is transmitted to the client 100 by the HTTP protocol. In the service page received by the HTTP protocol, the client 100 extracts a ticket (S140). The extraction of the ticket can be extracted from the HTTP Request object that transmitted the service page.

The client 100 receiving the ticket can use the ticket to request a service page requiring personal information. Therefore, in order to request a service page requiring personal information, a process of confirming that the client is a valid client is performed through a ticket. And requests ticket validation (S145). When the ticket is transmitted to the member information server 200, the server checks the validity of the received ticket value (S150). The validity of the ticket value can be confirmed by extracting the ticket value from the database in which the personal information is stored in steps S120 and S125. If the extracted ticket is present, since the client having the ticket is a valid client, the process of notifying that the ticket is valid is performed (S155). If it is determined that the client 100 is a valid client, the client requests personal information (S160). The requesting process can be deployed through the process of sending a ticket. Upon receiving the request for personal information, the member information server 200 extracts personal information corresponding to the ticket value from the database (S170). The extracted personal information is added to the HTTP Request object (S175), which is transmitted to the client (100) so as to utilize the personal information (S180).

2 is a diagram illustrating storage of personal information according to an embodiment of the present invention.

210 and 220 show examples in which data is stored in a database in which data is stored. The process of storing the personal information in the DB in steps S120 and S125 of FIG. 1 and the process of generating a ticket based on the personal information.

The member information server 200 can store 210 the personal information transmitted from the client 100 in the database. At this time, the information to be stored may be service information (member information), name, and storage time. This is information that is usually used for personal information. When storing personal information for the first time, a ticket is not created and the ticket portion is blank.

Then, the member information server 200 combines personal information to generate a ticket. The way to create a ticket is to have a hash in MD5 encryption algorithm and store it as a ticket. Of course, you can create and store tickets in a non-MD5 fashion. Also, after storing personal information such as 210 and 220, it is possible to generate a ticket, but it is possible to store the ticket in the database immediately after creating the ticket through personal information.

When the ticket is stored, when the ticket is received from the client in the future, the personal information related to the ticket can be extracted from the database and confirmed and transmitted. At this time, the personal information is stored in the database together with the ticket, so that unnecessary transmission / reception between the services is prevented and it is confirmed through the ticket.

FIG. 3 is a diagram illustrating an interaction between a client and a server according to an exemplary embodiment of the present invention. Referring to FIG.

The client 100 includes a device in which a client program for enabling network or Internet access is installed. The client 100 may operate as a server, but in the drawings of the present invention, it acts as a client in relation to an authentication server. The server 200 mainly includes an authentication unit or an authentication server 310 and a database 320. There may be a plurality of authentication units or authentication servers, and the server 200 may physically include one server as well as a plurality of servers.

The client 100 sends the personal information to the server 200 (S310). The transmitted personal information is transmitted to the authentication unit 310 of the server 200, and the authentication unit 310 stores the personal information in the member DB 320 (S320). Then, a ticket 350 to be transmitted to the client 100 is generated (S330). The ticket may be a key value for searching personal information stored in the member database 320, and may be a value converted by a method of hashing or encrypting the key value. The generated ticket 350 is transmitted again to the client 100 (S340).

The client 100 transmits a query for requesting personal information together with the received ticket 350 to the server 200 (S350). The ticket and the query transmitted to the server are transmitted to the authentication unit 310. The authentication unit 310 verifies the validity of the ticket and transmits personal information (S370). The validity of the ticket can be confirmed through the ticket issuance time, whether or not the key value extracted from the ticket information is a valid value, and the like.

The validity management of a ticket used in an embodiment of the present invention is possible as follows. A ticket is a unique key that can not be decrypted (one-way encryption algorithm, MD5). Even if a ticket transmitted between a client and a server is leaked to another person by hacking or the like, private information can not be exposed through a ticket. Some information used to create a ticket is not exposed.

In addition, the personal information used in the ticket is not the important personal information but only the role of the key which combines the information elements satisfying the uniqueness such as the ID and the connection time, so that the exposure of the ticket does not cause any separate information leakage. Also, even if another person creates a ticket arbitrarily, information about the ticket is not stored in the member database of the server, or if the expiration date of the ticket expires, any information can not be accessed through the ticket.

In order to further enhance security, the service may include the identity verification function of an auxiliary means such as a cellular phone, a landline telephone, or an authorized certificate. If the validity of the corresponding value is incorrect 3 times, a process of invalidating the ticket may be added have.

If the current use of a specific service is terminated (membership completion, password search completion, logout, etc.), the ticket can be set to expire at the expiration time so that the ticket can no longer be used. In the case of Hong Kil-dong in Table 1 below, it can be seen that the validity of the key has expired (valid value N) due to the above situation, and the corresponding ticket can not be used.

ticket Profile Membership Data storage time Effective value e12fdbd99435 55135234 Hong Gil Dong 07/04/2008 12:26:54 Y f26713d5e9e 54313443 Hong Gil Soon 07/04/2008 12:27:21 N

In Table 2, the ticket validity time is managed by adding the time at which the ticket was issued to the same table. Through this, it is possible to check the time that a ticket is validly used in one service, and expire as soon as this time passes, so that the constraint can be maintained only for a certain period of time.

For example, when one ticket has been generated for one minute, it is determined that there is no validity of the ticket, and personal information extraction is not permitted. The background of this method is that it assumes that the process of transmitting personal information through one service can be processed within one minute. In the table below, the key issued to Hong Gyun Soon on July 4, 2007 at 12:26:54 may be determined to be a key that can not be reused when it is after 12:27:54 on July 4, 2007.

ticket Profile Member ID Membership Data storage time e12fdbd99435 55135234 hks@n.com Hong Gil Soon 07/04/2008 12:26:54 f26713d5e9e 54313443 hkd@n.com Hong Gil Dong 07/04/2008 12:27:21

Further, when issuing a ticket, the client IP can be recorded in the service requesting the issuance. Client IP will be able to enhance the ability of IP filtering to compare where the ticket is issued and where it is requested. In other words, if another person hacked and used it within the validity period of the ticket, it is possible to transmit the ticket from the computer of the IP other than the corresponding IP. To prevent this, the ticket can be protected by storing the IP number in the member database as shown in Table 3.

ticket Profile Membership IP Effective value e12fdbd9435 55135234 Hong Gil Soon 1.1.1.2 Y f26713d5e9e 54313443 Hong Gil Dong 1.1.2.113 N

Meanwhile, the update management of the ticket can be performed. That is, the time point at which the ticket is re-issued is when the validity time has expired (in the case of Table 2) or the number of times of confirmation exceeded a limited number of times in the identity verification process of the auxiliary means. Except in this case, since the ticket is a simple unique key that has no meaning in itself, it does not need to be updated frequently, so it can perform updates rather than regeneration.

The ticket may not be re-used as the first key issued to the service after the user first enters his / her own information.

4 is a flowchart illustrating a flow of a server-side process according to an embodiment of the present invention.

The server receives and stores the security information from the client (S410). Storage can usually be done in the database, but memories and files can be used. Also, when the server is composed of a plurality of servers, distributed memory can be used, and a distributed database can be used. Next, a first ticket necessary for extracting the security information from the database is generated (S420). The first ticket can be extracted using a specific value of the security information, and can be generated using the database unique key value. The creation process can use encryption methods such as MD5, data hashing, and the like. When the generation of the ticket is completed, the first ticket is transmitted to the client (S430). Then, the second ticket and the identifier of the requested service are received from the client (S440). It is confirmed whether the received second ticket is the first ticket that has been generated (S450). If it is not the first ticket, the security information generating the first ticket can not be transmitted, and the process ends. If it is the first ticket, it is checked whether it is within the validity period of the first ticket (S460). If the validity period has elapsed, the corresponding ticket can not be used, so it is also terminated.

If the ticket is valid, the security information corresponding to the ticket is extracted (S470). Then, the security information and the information of the requested service are transmitted to the client (S480). Optionally, only the information of the requested service may be transmitted and the security information may not be transmitted.

5 is a configuration of a service to which an integrated authentication ticket according to an embodiment of the present invention is applied.

Ticket information is applied to send and receive security information. That is, the authentication server stores the security information used by the other service server and transmits the security information only to the client identified through the ticket, or the second security information (for example, Encrypted data to be used) so that the client can access another service server and use the service.

The client 510 is issued a ticket by a method predetermined by the authentication server 521 or by a method proposed by the present invention. The client 510 having received the ticket inputs the ID and the password to the service server 530 to log in. At this time, the input ID and password are transmitted to the authentication server 521 and stored in the authentication server 525. The manner in which they are stored may be stored in a table-based database as in embodiment 527. [

The configuration of the table is composed of a ticket, service server information, security information 1, security information 2, and security information 3. The ticket indicates ticket information to be transmitted to the authentication server 521 for confirmation. The service server portion includes the site address of the service server 530. Or information for identifying various service servers 530. Security information 1, security information 2, and security information 3 all mean security information required for accessing a corresponding service server. In FIG. 5, since www.a.com requires a mail address and a password to access the service, the mail address hks@nate.com is entered in the security information 1 and password 1, which is the password, is stored in the security information 2.

On the other hand, since www.b.com transmits and receives another ticket, which is not an ID and a password, as security information, the ticket value (a30592be092723) is input to the security information 1. It is possible to increase the data input area by using security information 1, security information 2, security information 3, and the like.

Therefore, when connecting to each service server, the client 510 transmits the ticket information held by the client 510 and the information about the service server to be connected to the authentication server 521 without memorizing or inputting the corresponding security information separately And transmits the retrieved security information to the client 510 due to the ticket information. The transmitted security information is transmitted to the service server 530 by the client using the HTTP protocol or various network communication methods, and the service server 530 authenticates the client 510 using the transmitted security information. The client 510 may then use the service server 530.

The security information 1, the security information 2, and the security information 3 can be re-encrypted and stored. At this time, the value to be decoded by the ticket value can be stored.

When the ticket method is applied as in the embodiment of FIG. 5, it can be applied to various authentication services and can hold security information.

Using the ticket of the present invention, one encrypted information can be used to connect to multiple servers.

The foregoing description is merely illustrative of the technical idea of the present invention, and various changes and modifications may be made by those skilled in the art without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are intended to illustrate rather than limit the scope of the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be construed according to the following claims, and all technical ideas within the scope of equivalents should be construed as falling within the scope of the present invention.

The present invention restricts the amount of information transmitted and received in order to protect user information, allows tickets to be transmitted and received between a client and a server, and transmits important security information when authentication is performed through a ticket, thereby enabling protection of information .

1 is a diagram illustrating a process of transmitting and receiving a ticket-based data according to an embodiment of the present invention.

2 is a diagram illustrating storage of personal information according to an embodiment of the present invention.

FIG. 3 is a diagram illustrating an interaction between a client and a server according to an exemplary embodiment of the present invention. Referring to FIG.

4 is a flowchart illustrating a flow of a server-side process according to an embodiment of the present invention.

5 is a configuration of a service to which an integrated authentication ticket according to an embodiment of the present invention is applied.

Claims (7)

Storing the site address of the service server necessary for the authentication server to receive the security information from the client and access the database with the security information; Extracting and encrypting some of the received security information in the database to generate a first ticket, which is a key value necessary for extracting the security information; Storing the first ticket in a database storing the security information; Sending the first ticket to the client; Receiving a second ticket from the client and information about a service server to be accessed; Verifying whether the second ticket is a value stored in the database and extracting security information from the database using the first ticket if the second ticket is identical to the first ticket; And And transmitting the extracted security information to the client, Wherein the client authenticates at the service server using the security information, and wherein the authentication server and the service server are different. The method according to claim 1, Wherein the sending of the first ticket comprises adding a value of the first ticket to a Request object by HTTP protocol. The method according to claim 1, Setting an expiration date of the first ticket; And Stopping the extraction of the security information corresponding to the first ticket when the validity period of the first ticket has expired even if the second ticket is the same as the first ticket, How to authenticate and protect information. delete The method according to claim 1, Wherein the security information includes personal information, wherein the ticket is used to authenticate and protect the security information. The method according to claim 1, Wherein the security information is not computed inversely from the first ticket. ≪ RTI ID = 0.0 > 11. < / RTI > The method according to claim 1, Wherein receiving the second ticket from the client comprises receiving a service identifier requesting the security information, And transmitting service information requested by the service identifier after the step of extracting the security information.

Images