JP2017156979A - Server, authentication level change method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a technique for keeping a balance between the safety of a financial transaction and the convenience of a user.SOLUTION: An authentication unit 130 provides an authentication screen for performing user authentication. When the user authentication by the authentication unit 130 is successful, a transaction providing unit 150 provides the financial transaction to a user. A history management unit 180 manages the history of the financial transaction. An analysis unit 170 analyzes the timing of the financial transaction managed by the history management unit 180. The authentication unit 130 changes the authentication level of the user authentication on the basis of the timing of the financial transaction.SELECTED DRAWING: Figure 2

Description

  The present invention relates to a server for financial transactions, an authentication level changing method executed by the server, and a program for causing the server to realize an authentication level changing function.

  Regarding the safety of financial transaction services using networks such as ATM and the Internet, for example, in a financial transaction system having an automatic transaction device such as ATM and a host computer that executes the processing, use of the automatic transaction device according to the transaction situation. A technique for limiting is known (see, for example, Patent Document 1). In addition, in various systems that are operated by connecting to a server via a network, a technique for determining an authentication level for performing the user authentication based on user usage tendency information is also known (for example, Patent Documents). 2).

JP 2009-140273 A JP 2007-164661 A

  In order to ensure the safety of transactions in financial transactions using networks, identity verification is essential before transactions. There is a tendency for the confirmation work of the person to become more complicated as the safety is increased, and this is a factor that reduces the convenience of financial transactions using the network. In particular, if financial transactions are restricted too much with an emphasis on safety, the convenience may be lost. For this reason, there is a demand for a technology that achieves both convenience and safety of financial transactions using a network.

  In addition, it is considered that the usage tendency of users differs between a general system connected to a server via a network and a system specialized for financial transactions. It is difficult to improve the convenience of users in financial transactions using a network simply by diverting it to a system. For this reason, there is a demand for a technology that achieves both convenience and safety of financial transactions using a network.

  The present invention has been made in view of these points, and an object thereof is to provide a technique for maintaining a balance between the safety of financial transactions and the convenience of the user.

  The financial transaction server according to the first aspect of the present invention includes an authentication unit that provides an authentication screen for user authentication, and a transaction providing unit that provides a user with a financial transaction when the user authentication by the authentication unit is successful And a history management unit that manages the history of the financial transaction, and an analysis unit that analyzes the timing of the financial transaction managed by the history management unit, wherein the authentication unit is based on the analysis result of the analysis unit The authentication level of the user authentication is changed.

  When the financial transaction has periodicity, the authentication unit may lower the authentication level of the user authentication to an authentication level at the time when the financial transaction is requested.

  The authentication unit may further comprise an authentication information management unit that manages user authentication information to be confirmed when executing the financial transaction, and a change reception unit that receives a change of the authentication information from the user, The authentication unit may change the authentication level based on a timing at which the change receiving unit receives a change in the authentication information.

  The authentication unit may lower an authentication level of a user whose predetermined period has not elapsed since the authentication information was changed.

  The authentication unit may increase the authentication level of the user authentication step by step as the time elapsed after the change of the authentication information becomes longer.

  The analysis unit performs user authentication by the authentication unit before executing the financial transaction based on the contents of the financial transaction provided by the transaction providing unit and the history of the financial transaction managed by the history management unit. It may be determined whether or not to do so.

  The authentication unit may provide the user with a screen with information indicating the current authentication level of the user and information indicating a condition for changing the authentication level.

  In the authentication level changing method according to the second aspect of the present invention, a step of providing an authentication screen for performing user authentication, a step of providing a financial transaction to a user when the user authentication is successful, and the financial transaction And a step of changing the authentication level of the user authentication based on the analysis result of the financial transaction timing.

  A program according to a third aspect of the present invention includes a function for providing a computer with an authentication screen for user authentication, a function for providing a financial transaction to a user when user authentication is successful, and a function of the financial transaction. A function of analyzing the timing and a function of changing the authentication level of the user authentication based on the analysis result of the timing of the financial transaction are realized.

  This program may be provided as part of the firmware incorporated in the device to perform basic control of the financial transaction server. This firmware is stored in a semiconductor memory such as a ROM (Read Only Memory) or a flash memory in the device, for example. In order to provide the firmware or to update a part of the firmware, a computer-readable recording medium storing the program may be provided, and the program may be transmitted through a communication line.

  It should be noted that any combination of the above-described constituent elements and the expression of the present invention converted between a method, an apparatus, a system, a computer program, a data structure, a recording medium, and the like are also effective as an aspect of the present invention.

  ADVANTAGE OF THE INVENTION According to this invention, the technique for keeping the balance of the safety | security of a financial transaction and a user's convenience can be provided.

It is a figure which shows typically the schematic structure of the financial transaction system which concerns on embodiment. It is a figure which shows typically the function structure of the financial transaction server which concerns on embodiment. It is a figure which shows an example of the web page on which the authentication screen at the time of the login which the authentication part which concerns on embodiment provides to a client terminal was displayed. It is a figure which shows an example of the timing of a user's financial transaction typically. It is a figure for demonstrating the change of the authentication level based on progress of the time which the authentication information management part which concerns on embodiment performs. It is a figure which shows typically an example of the timing of a certain user's financial transaction. It is a figure which shows an example of the screen of the user authentication at the time of login which the authentication part which concerns on embodiment provides. It is a flowchart which shows the flow of the authentication level change process which the financial transaction server which concerns on embodiment performs. It is a figure which shows typically an example of the fluctuation | variation of the authentication level of a certain user.

<Outline of the embodiment>
First, the outline of the embodiment of the present invention will be described with reference to FIG.
FIG. 1 is a diagram schematically showing a schematic configuration of a financial transaction system 1 according to an embodiment. In the example shown in FIG. 1, the first client terminal 10a used by the first user U1, the second client terminal 10b used by the second user U2, and the third client terminal 10c used by the third user U3 are the Internet or the like. Are connected to the financial transaction server 100 and the sales transaction server 30 via the network 20. In the example shown in FIG. 1, the first client terminal 10a and the second client terminal 10b are notebook PCs (Personal Computers) possessed by the first user U1 and the second user U2, respectively, and the third client terminal 10c is , ATM.

In the following description, the term “client terminal 10” is used unless the first client terminal 10a, the second client terminal 10b, and the third client terminal 10c are distinguished. Similarly, “user U” is described except when the first user U1, the second user U2, and the third user U3 are distinguished.
In FIG. 1, three client terminals 10, that is, a first client terminal 10 a, a second client terminal 10 b, and a third client terminal 10 c are illustrated, but the number of client terminals 10 is not limited to three. Further, in FIG. 1, only one sales transaction server 30 is shown, but two or more sales transaction servers 30 may be provided.

  The financial transaction server 100 provides various financial transaction services to the user U who has logged into the financial transaction server 100 using the client terminal 10, such as transfer, transfer, payment, account settlement such as online shop, purchase of financial products, and the like. . For this reason, an account of each user U is created in advance in the financial transaction server 100. According to the financial transaction history of each user U, the financial transaction server 100 according to the embodiment changes the authentication level required when the user U performs a financial transaction.

  Here, “financial transaction” includes the above-described actions such as transfer, payment, settlement, etc., that is, the action of changing the balance of the account of the user U. In addition, the “financial transaction” in this specification includes account balance inquiry, change of information used for user authentication such as password, change of personal information registered in the financial transaction server 100 such as address and e-mail address, etc. Also included is an action that the user U causes the financial transaction server 100 to execute using the client terminal 10 without affecting the balance of the account. Furthermore, the login transaction (including authentication in ATM) that attempts to access the financial transaction server 100 as a premise for executing these actions and the authentication that is imposed on the user before actually moving the money in the account are also included in the financial transaction.

  For this reason, “history of financial transaction” means a history of an action for the user U to access the financial transaction server 100 using the client terminal 10 and an action performed by accessing the financial transaction server 100. The history of financial transactions is assigned to the access environment (for example, the access area of the client terminal 10 to be used, the operating system installed in the client terminal 10, and the client terminal 10) when the client terminal 10 accesses the financial transaction server 100. IP (Internet Protocol) address, MAC (Media Access Control) address, store name where ATM is installed, ATM identification number, and the like.

  The “authentication level required when performing a financial transaction” represents the strength of security required before each action performed by the user U on the financial transaction server 100. For example, when the authentication level when logging in to the financial transaction server 100 is high, the user U is required to enter a user name and a password, and to require a security code and image authentication. Further, when the user U performs a transfer or the like, a one-time password is further requested. On the other hand, when the authentication level is low, the user U can log in to the financial transaction server 100 with only the password, or can check the balance without requiring any authentication.

  The “authentication” in the financial transaction is generally performed in order to confirm whether or not the user U who wants to receive a financial transaction service from the financial transaction server 100 is the owner of the account. Here, for example, the transfer of rent, the transfer of living expenses to a family, etc. are financial transactions carried out by the user U periodically. For this reason, it can be said that a login that matches the periodicity of past financial transactions has a high probability of being the owner of the account. If it is determined that the password at the time of login is complicated and difficult to guess by others, it is highly likely that the person who knows the password is the person himself / herself. In particular, immediately after the user U changes the password, it can be said that the probability that the password is leaked to others is low.

  Therefore, the financial transaction server 100 according to the embodiment stores the history of financial transactions of each user U, and analyzes the timing of the financial transactions, thereby obtaining the authentication level required when performing financial transactions for each user U. change. For example, in the case of login timing that matches a transaction cycle of a certain user U, the financial transaction server 100 lowers the authentication level at the time of login for that user U. Immediately after a user U changes a password for authentication to a complex password, the authentication level required for the user U is lowered. If a long time has elapsed since the password change, the user U is requested to do so. Increase the authentication level.

  As described above, since the financial transaction server 100 according to the embodiment changes the authentication level required of the user U according to the history of the financial transaction of the user U, the safety of the financial transaction and the convenience of the user U Can keep the balance.

<Functional configuration of financial transaction server>
Next, the financial transaction server 100 according to the embodiment will be described in more detail.
FIG. 2 is a diagram schematically illustrating a functional configuration of the financial transaction server 100 according to the embodiment. The financial transaction server 100 includes a communication unit 110, a change receiving unit 120, an authentication unit 130, a transaction receiving unit 140, a transaction providing unit 150, an authentication information management unit 160, an analysis unit 170, a history management unit 180, and a storage unit 190. .

  FIG. 2 shows a functional configuration for realizing the financial transaction server 100 according to the embodiment, and other configurations are omitted. In FIG. 2, each element described as a functional block for performing various processes is configured by a CPU (Central Processing Unit) of the financial transaction server 100, a main memory, and other LSI (Large Scale Integration) in terms of hardware. can do. In terms of software, it is realized by a program loaded in the main memory. Accordingly, it is understood by those skilled in the art that these functional blocks can be realized in various forms depending on the calculation resource of the financial transaction server 100, and is not limited to any one. Although not limited, as an example, the financial transaction server 100 can be realized by using a known mainframe or cloud server.

[Basic configuration]
The communication unit 110 is a communication interface for each part of the financial transaction server 100 to exchange information with an external device via the network 20. The communication unit 110 can be realized by using, for example, a known LAN (Local Area Network) card.

  The transaction receiving unit 140 receives a request for a financial transaction from the user U to the financial transaction server 100 via the network 20 from the client terminal 10. Hereinafter, in the present specification, when the user U accesses the financial transaction server 100, it is assumed that the user U accesses via the network 20 using the client terminal 10 and simply “from the client terminal 10 to the financial transaction server 100. It may be described as "Access".

For example, the transaction receiving unit 140 receives a login request from the client terminal 10 to the financial transaction server 100. The authentication unit 130 provides an authentication screen for user authentication. For example, the authentication unit 130 provides the client terminal 10 with a web page for user authentication.
FIG. 3 is a diagram illustrating an example of a web page on which an authentication screen at the time of login provided to the client terminal 10 by the authentication unit 130 according to the embodiment is displayed. In the example illustrated in FIG. 3, when the user U inputs a user name that is a user identifier and a password that is authentication information at a predetermined position on the authentication screen, the authentication unit 130 determines whether the user name and the password match. To do. In this sense, the act of the user U attempting to log in to the financial transaction server 100 is also an example of the financial transaction service that the user U provides the financial transaction server 100.

  The authentication information management unit 160 manages the authentication information of the user U confirmed when the authentication unit 130 executes a financial transaction. More specifically, the authentication information management unit 160 associates each user identifier of the user U with information used for user authentication such as a password, a security code, and an image for image authentication in the storage unit 190. I remember it. The authentication information management unit 160 also generates temporary information for use in user authentication such as a one-time password. The authentication unit 130 acquires information used for user authentication from the authentication information management unit 160 and executes user authentication.

When the user authentication by the authentication unit 130 is successful, the transaction providing unit 150 provides the user U with the financial transaction requested by the transaction receiving unit 140 from the client terminal 10. For example, the transaction providing unit 150 performs settlement of a transaction performed by the user U on the sales transaction server 30 that is an Internet shopping server.
The history management unit 180 manages the history of financial transactions provided by the transaction providing unit 150 in association with the user identifier of the user U. The storage unit 190 is a known large-capacity storage device such as an HDD (Hard Disk Drive) or an SSD (Solid State Drive). The history management unit 180 stores the history of financial transactions in the storage unit 190, and the transaction providing unit 150 Update financial transaction history when providing financial transactions.

The analysis unit 170 analyzes the timing of the financial transaction managed by the history management unit 180.
FIGS. 4A and 4B are diagrams schematically illustrating an example of timing of the financial transaction of the user U. FIG. Specifically, FIG. 4 (a) is a diagram showing the timing of financial transactions from January to August of a certain year by the first user U1, and FIG. 4 (b) is a period of synchronization by the second user U2. It is a figure which shows the timing of the financial transaction in. In order to avoid complications, not all are labeled, but a black rectangle denoted by reference numeral 192 in FIGS. 4A to 4B indicates the financial transaction timing of the user U. That is, FIG. 4 (a) shows that the first user U1 has executed a financial transaction once a month at approximately the same cycle. FIG. 4B shows that the timing of the financial transaction by the second user U2 is less periodic than the timing of the financial transaction by the first user U1.

  The analysis unit 170 refers to the history management unit 180, acquires the history of financial transactions for each user U, and analyzes the periodicity of the timing of financial transactions. The analysis unit 170 can acquire the periodicity of the timing of the financial transaction by performing frequency analysis on the time series data of the timing of the financial transaction, for example. The frequency analysis can be realized using, for example, a known FFT (Fast Fourier Transform).

  The authentication unit 130 changes the authentication level of the user authentication for each client terminal 10, that is, for each user U, based on the analysis result of the financial transaction timing by the analysis unit 170. More specifically, the authentication unit 130 lowers the authentication level of user authentication when the timing of executing the financial transaction is periodic than when there is no periodicity. In the example illustrated in FIG. 4, the authentication unit 130 sets the authentication level of the first user U1 to be lower than the authentication level of the second user U2. This can be realized by the authentication information management unit 160 obtaining the analysis result of the financial transaction timing by the analysis unit 170 and changing the authentication level for each user U.

  As described above, it is considered that a financial transaction request that matches the period of the financial transaction timing specified from the history of past financial transactions is highly likely to be a request by the principal. On the other hand, when there is no periodicity in the timing of financial transactions, it is difficult to distinguish whether a certain financial transaction request is made by the principal or by a third party. The authentication unit 130 changes the authentication level based on the analysis result of the financial transaction timing, thereby reducing the complexity of user authentication in the financial transaction and improving the convenience of the user U, while also ensuring the safety of the financial transaction. Can be secured.

  The change receiving unit 120 receives a change in authentication information such as a password and a security code from the user U. Here, it is considered that the user U who periodically changes the authentication information is highly interested in security and is likely to be appropriately managed. Accordingly, the authentication unit 130 changes the authentication level based on the timing at which the change receiving unit 120 receives a change in authentication information.

  More specifically, the authentication information management unit 160 causes the analysis unit 170 to analyze the change timing of the authentication information made via the change reception unit 120 and determines whether or not the timing has periodicity. The authentication information management unit 160 lowers the authentication level of the user authentication when the timing of changing the authentication information has periodicity than when it is not. Thereby, about the user U who updates authentication information regularly, the complexity in user authentication can be reduced and the convenience can be improved. Further, for the user U who does not regularly update the password, the security level can be increased by raising the authentication level of user authentication.

[Initial value of authentication level]
The initial value of the authentication level will be described.
The initial value of the authentication level set for each user U is set by the authentication information management unit 160. The authentication information management unit 160 also manages the personal information of each user U, and the authentication level of each user U is initially set based on this personal information. Moreover, the authentication information management part 160 sets an authentication level separately for every financial transaction. For example, when a certain user U has successfully logged in, the authentication information management unit 160 does not request user authentication for balance reference, but sets user authentication for remittance.

More specifically, the authentication information management unit 160 sets the authentication level based on, for example, the following personal information.
a) E-mail address registration b) E-mail address security c) Password security strength d) Age e) Telephone number registration

  The authentication information management unit 160 sets the initial value of the authentication level lower for the user U whose email address is registered than for the user U whose email address is not registered. This is because the user U whose mail address is registered can be additionally authenticated by contact using the mail address. The authentication information management unit 160 also sets the initial value of the authentication level lower when the registered email address is more secure than when it is lower. The authentication information management unit 160 can determine the safety of the email address based on the domain of the email address, for example. Specifically, the authentication information management unit 160 sets the initial value of the authentication level higher when the registered email address is a so-called free email address than when it is not.

  The authentication information management unit 160 sets the initial value of the authentication level lower when the strength of the registered password is stronger than when it is weaker. The authentication information management unit 160 can calculate the security strength of the password based on, for example, a character string used in the password (such as using a plurality of numbers, uppercase letters, lowercase letters, and symbols). Further, when the age of the user U exceeds a predetermined age (for example, 65 years old), the authentication information management unit 160 sets the initial value of the authentication level higher as the age increases. The authentication information management unit 160 also sets the initial value of the authentication level lower when the telephone number is registered as personal information than when it is not. This is because additional authentication by telephone is possible.

[Change authentication level over time]
Next, the change of the authentication level based on the passage of time will be described.
It is considered that the probability that the authentication information is leaked to others is lower when the time elapsed since the user U changed the authentication information is shorter than when the time has elapsed. Therefore, the authentication unit 130 lowers the authentication level of user authentication for the user U whose predetermined period has not elapsed since the change of the authentication information. More specifically, when there is a change in the authentication information, the authentication information management unit 160 lowers the authentication level of the user authentication of the user U who has changed the authentication information until a predetermined period elapses.

  Here, the “predetermined period” is a period in which the authentication information management unit 160 reduces the authentication level in accordance with the change of the authentication information, and refers to “authentication level management” that is referred to when determining whether to increase the authentication level. Reference period ". The length of the predetermined period may be determined by experiment in consideration of the contents of financial transactions, the safety strength of authentication information, and the like. The authentication information management unit 160 sets the authentication level low immediately after the change of the authentication information by the user U, thereby reducing the complexity at the time of user authentication by the authentication unit 130 and the user U at the time of user authentication in the financial transaction. Convenience can be improved.

  The authentication unit 130 increases the authentication level at the time of user authentication after a predetermined period has elapsed. Here, the authentication unit 130 increases the authentication level of the user authentication step by step as the time elapsed after the change of the authentication information becomes longer. More specifically, the authentication information management unit 160 increases the authentication level of the user authentication stepwise as the time elapsed since the authentication information was changed by the user U becomes longer. As a result, the authentication level at the time of user authentication provided to the client terminal 10 by the authentication unit 130 is also increased.

  FIGS. 5A and 5B are diagrams for explaining the change of the authentication level based on the passage of time executed by the authentication information management unit 160 according to the embodiment. 5A and 5B, the vertical axis represents the authentication level of user authentication, and the horizontal axis represents the passage of time. In the example shown in FIGS. 5A and 5B, the authentication level is represented by numbers from 1 to 4, and the larger the number, the higher the authentication level. That is, the authentication level 1 indicates that the authentication level is the lowest, and the authentication level 4 indicates that the authentication level is the highest.

  In FIG. 5A, it is assumed that the authentication information is changed when the elapsed time is “0”. In this case, the period from 0 to T1 is the authentication level management reference period, which is the “predetermined period” described above. The authentication information management unit 160 changes the authentication level from 1 to 2 after the time T1 has elapsed. The authentication information management unit 160 changes the authentication level from 2 to 3 at T2 when the same time as the authentication level management reference period has elapsed from T1. Similarly, the authentication information management unit 160 changes the authentication level from 3 to 4 at T3 when the same time as the authentication level management reference period has elapsed from T2. After T3 time elapses, the authentication information management unit 160 maintains the authentication level at 4 until the authentication information is changed again.

  FIG. 5B is a diagram showing an authentication level change pattern different from that in FIG. More specifically, in the change pattern shown in FIG. 5B, the period during which the authentication level is maintained differs depending on the authentication level. In FIG. 5B, the period from 0 to T4 is the authentication level management reference period, which is shorter than the authentication level management reference period in FIG. In the change pattern shown in FIG. 5 (b), the period during which the state where the authentication level is the lowest is maintained is shorter than that in the change pattern shown in FIG. 5 (a). I can say that.

On the other hand, the period in which the authentication level 3 is maintained in the change pattern shown in FIG. 5B is longer than the period in which the authentication level 3 is maintained in the change pattern shown in FIG. This can be said to be a setting that places emphasis on reducing the complexity of user authentication because safety is ensured even if the period is extended if the security at authentication level 3 is sufficiently high.
In this manner, how to set the authentication level change pattern may be determined by experiment in consideration of the contents of the financial transaction provided by the financial transaction server 100.

[Set authentication level for each financial transaction]
The authentication unit 130 according to the embodiment can individually change the authentication level for each financial transaction provided to the user U. For example, the element group described below is compared with the history of financial transactions, and the authentication level is changed depending on the degree of deviation.
a) Transaction details (remittance destination and remittance amount, etc.)
b) Transaction time or time zone and transaction date c) Access environment

  In order to realize this, the analysis unit 170 receives the financial transaction request from the user U from the user U and provides the content of the financial transaction provided by the transaction providing unit 150 and the financial transaction managed by the history management unit 180. Based on the history, before the transaction providing unit 150 executes the financial transaction, it is determined whether or not the authentication unit 130 performs user authentication. For example, when there is a remittance request from a certain user U, the analysis unit 170 requires user authentication before executing the financial transaction if at least one of the remittance destination and the remittance amount is different from the history of the financial transaction. judge. When the analysis unit 170 determines that user authentication is necessary, the authentication information management unit 160 sets an authentication level higher than the authentication level set by the authentication information management unit 160 for the financial transaction. Thereby, the safety | security of a financial transaction can be improved more.

The analysis unit 170 also determines that user authentication is necessary before the execution of the financial transaction when the transaction time or time zone and the transaction date are different from the history of the financial transaction.
FIGS. 6A to 6B are diagrams schematically illustrating an example of a financial transaction timing of a certain user U. FIG. Specifically, FIG. 6A is a diagram illustrating the timing of financial transactions from January to August of a certain year by the user U, and FIG. 6B is one of another year by the same user U. It is a figure which shows the timing of the financial transaction from the month to August. In order to avoid complication, not all symbols are attached, but a black rectangle indicated by reference numeral 192 in FIG. 6A indicates the timing of the financial transaction of the user U. That is, FIG. 6A shows that the user U has executed a financial transaction once a month with substantially the same cycle.

  In FIG. 6B, a white rectangle denoted by reference numeral 194 indicates the timing of the financial transaction of the user U as well as the black rectangle. Unlike the black rectangle, the white rectangle indicates a financial transaction for which periodicity cannot be specified. The analysis unit 170 refers to the history management unit 180, acquires the history of financial transactions for each user U, and analyzes the periodicity of the timing of financial transactions.

  When the financial transaction has periodicity, the analysis unit 170 sets the authentication level of the user authentication to be lower than the authentication level at the time when the financial transaction is requested. Conversely, if the financial transaction has no periodicity, the user authentication level is increased. Specifically, when there is a financial transaction that does not match the period calculated from the history of the financial transaction of a certain user U, the analysis unit 170 determines that user authentication at a higher level is necessary when executing the financial transaction. If the analysis unit 170 determines that high level user authentication is required, the authentication information management unit 160 sets an authentication level higher than the authentication level set by the authentication information management unit 160 for the financial transaction. To do. Thereby, the safety | security of a financial transaction can be improved more.

  Further, when the access environment of the client terminal 10 accessing the financial transaction server 100 is different from the history of the financial transaction, the analysis unit 170 determines that user authentication is necessary before executing the financial transaction. In general, it is considered that a certain user U often accesses the financial transaction server 100 from a limited access environment. Therefore, when the access environment of the client terminal 10 accessing the financial transaction server 100 is different from the history of the financial transaction, it can be said that there is a high probability that the access is not made by the legitimate user U as compared to the case where the access environment is not.

  When the analysis unit 170 determines that user authentication is necessary, the authentication information management unit 160 sets an authentication level higher than the authentication level set by the authentication information management unit 160 for the financial transaction. Thereby, the safety | security of a financial transaction can be improved more.

[Display Authentication Level]
In the financial transaction server 100 according to the embodiment, the authentication level in the user authentication varies for each user U and for each content of the financial transaction. Therefore, it is convenient for the user U to check the current authentication level at the time of user authentication.
Therefore, the authentication unit 130 may add information indicating the current authentication level of the user U to a web page for performing user authentication.

  FIG. 7 is a diagram illustrating an example of a screen for user authentication at the time of login provided by the authentication unit 130 according to the embodiment. More specifically, FIG. 7A is a diagram showing an input screen for a user name as a user identifier, and FIG. 7B is a diagram showing an input screen for a password and security code as authentication information.

  As shown in FIG. 7A, on the screen for inputting the user identifier, the user U is only required to input the user name. The authentication information management unit 160 acquires the current authentication level at the time of login of the user U based on the user name of the user U acquired from the authentication unit 130. Based on the authentication level acquired by the authentication information management unit 160, the authentication unit 130 determines authentication information that requires the user U to input. As shown in FIG. 7B, the authentication unit 130 displays that the current authentication level of the user U is “medium”. The authentication unit 130 also displays a screen that prompts input of a password and a security code as authentication information. As a result, the user U can grasp the authentication level of the current authentication at a glance, so that it becomes easy to understand why the input of the two authentication information of the password and the security code is required. Although not shown, the authentication unit 130 may display information indicating a condition for changing the authentication level on the user authentication screen. Specific examples of “conditions for displaying the authentication level” include information indicating how many days later the authentication level will increase, and how many times the user authentication succeeds will result in a decrease in the authentication level. It is information which shows.

<Processing flow>
FIG. 8 is a flowchart showing a flow of authentication level change processing executed by the financial transaction server 100 according to the embodiment. The process in this flowchart starts when the financial transaction server 100 is activated.

  The transaction reception unit 140 acquires a login request for the financial transaction server 100 from the client terminal 10 operated by the user U (S2). When the transaction receiving unit 140 acquires the login request, the authentication unit 130 acquires the authentication level in the user authentication of the user U from the authentication information management unit 160 (S4). The authentication unit 130 provides a web page that displays a login authentication screen on the client terminal 10 via the network 20 (S6).

  While the user authentication is not successful (NO in S8), the authentication unit 130 provides the user U with a user authentication procedure. If the user authentication is successful (YES in S8), the transaction accepting unit 140 acquires a request for a financial transaction desired by the user U (S10). The authentication unit 130 inquires of the authentication information management unit 160 whether or not new user authentication is necessary before executing the financial transaction requested by the user U. When user authentication is required (YES in S12), the authentication unit 130 provides the user U with a screen for user authentication necessary for the financial transaction requested by the user U (S14).

  When user authentication is unnecessary (NO in S12), or when authentication on the authentication screen newly provided by the authentication unit 130 is completed, the transaction providing unit 150 provides a financial transaction to the user U (S16). The history management unit 180 stores the financial transaction executed by the user U in the storage unit 190 and updates the history of the financial transaction (S18).

  The analysis unit 170 analyzes the history of the financial transaction related to the user U updated by the history management unit 180 (S20). As a result of the analysis, if the authentication level of the user U should be changed (YES in S22), the authentication information management unit 160 changes the authentication level associated with the user U (S24). If the authentication information management unit 160 changes the authentication information or if the analysis result does not require changing the authentication level (NO in S22), the processing in this flowchart ends. The financial transaction server 100 updates the authentication level at the time of user authentication in the financial transaction for each user U by repeating the above processing, and manages the authentication level.

  FIG. 9 is a diagram schematically illustrating an example of a change in the authentication level of a certain user U. In the graph shown in FIG. 9, the vertical axis represents the strength of the authentication level, and the horizontal axis represents the flow of time. In the example shown in FIG. 9, the authentication level of the user U started from 1. However, since the user U did not log in to the financial transaction server 100 and the authentication level management reference period T7 passed, the authentication level at the time of T7 is Went up to 2. Thereafter, at time T8, the user U logs in to the financial transaction server 100. Since this is a login at a timing that matches the cycle of the financial transaction of the user U, the authentication level is 1. At time T10, the user U failed to authenticate the user a plurality of times, so the authentication level of the user U increased to 3.

  At time T11, the user U has changed the password, which is authentication information, so the authentication level has dropped to 1. After that, since the user U did not execute the financial transaction on the financial transaction server 100 until the time T15, the authentication level gradually increased at the times T12, T13, and T14. Thereafter, at T15, the user U changed the security code, which is the authentication information, so the authentication level returned to 1.

  As described above, the financial transaction server 100 according to the embodiment changes the strength of the authentication level of the user authentication imposed when the user U executes the financial transaction according to the history of the financial transaction by the user U.

As described above, according to the financial transaction server 100 according to the embodiment, it is possible to provide a technique for maintaining a balance between the safety of financial transactions and the convenience of the user U.
In particular, by changing the authentication level based on the presence or absence of the periodicity of the user U's financial transaction, it is possible to reduce the burden of authentication of the user U who executes periodic financial transactions. Further, the burden of authentication can be reduced even for the user U who regularly changes the authentication information.
Furthermore, the security of the financial transaction can be ensured by changing the authentication level according to the time elapsed since the authentication information was changed.

  As mentioned above, although this invention was demonstrated using embodiment, the technical scope of this invention is not limited to the range as described in the said embodiment. It will be apparent to those skilled in the art that various modifications or improvements can be added to the above embodiment. It is apparent from the scope of the claims that the embodiments added with such changes or improvements can be included in the technical scope of the present invention. Such modifications will be described below.

  The authentication information management unit 160 may change the authentication level based on information other than the above. For example, the user U who has a high frequency of financial transactions may have a lower authentication level in user authentication than the user U who has a low frequency of financial transactions. Since the user U with high frequency of financial transactions is considered to be more interested in account fluctuations than the low user U, the convenience of such a user U can be improved.

  Further, the authentication information management unit 160 may make the authentication level of the user U whose account change frequency is high lower than the user U whose account change frequency is low. When the account change frequency is high, the transaction account is more likely to be an account that is currently used than when the account change frequency is low, so the convenience of the user U having such an account is improved. be able to.

  In the above description, the case where the input of a one-time password is requested as an example when the authentication level is high has been described. In addition to this, an authentication method using a random number table may be added, or PKI (Public Key Infrastructure) authentication may be performed using a USB (Universal Serial Bus) terminal or the like distributed to each user U in advance. Good.

DESCRIPTION OF SYMBOLS 10 ... Client terminal 20 ... Network 30 ... Sales transaction server 100 ... Financial transaction server 110 ... Communication part 120 ... Change reception part 130 ... Authentication part 140 ... Transaction reception 150 ... Transaction providing unit 160 ... Authentication information management unit 170 ... Analysis unit 180 ... History management unit 190 ... Storage unit

Claims (9)

An authentication unit that provides an authentication screen for user authentication;
When the user authentication by the authentication unit is successful, a transaction providing unit that provides a financial transaction to the user;
A history management unit for managing the history of the financial transaction;
An analysis unit for analyzing the timing of a financial transaction managed by the history management unit;
With
The authentication unit changes the authentication level of the user authentication based on the analysis result of the analysis unit.
A server characterized by that.   2. The authentication unit according to claim 1, wherein when the financial transaction has periodicity, the authentication unit lowers an authentication level of the user authentication to an authentication level at the time when the financial transaction is requested. server. An authentication information management unit for managing user authentication information to be confirmed when the authentication unit executes the financial transaction;
A change accepting unit that accepts a change in the authentication information from the user;
Further comprising
The server according to claim 1, wherein the authentication unit changes the authentication level based on a timing at which the change receiving unit receives a change in the authentication information.   The server according to claim 3, wherein the authentication unit lowers an authentication level of a user who has not passed a predetermined period after the change of the authentication information.   5. The server according to claim 3, wherein the authentication unit increases the authentication level of the user authentication stepwise as the time elapsed since the change of the authentication information becomes longer.   The analysis unit performs user authentication by the authentication unit before executing the financial transaction based on the contents of the financial transaction provided by the transaction providing unit and the history of the financial transaction managed by the history management unit. 6. The server according to claim 1, wherein it is determined whether or not to perform.   The said authentication part provides the said user with the screen which provided the information which shows the said user's present authentication level, and the information which shows the conditions by which the said authentication level is changed, The said user is characterized by the above-mentioned. The server as described in any one. Providing an authentication screen for user authentication;
Providing the user with a financial transaction if the user authentication is successful;
Analyzing the timing of the financial transaction;
Changing the authentication level of the user authentication based on the analysis result of the timing of the financial transaction;
An authentication level changing method, wherein the processor executes On the computer,
A function to provide an authentication screen for user authentication;
The ability to provide financial transactions to users if user authentication is successful;
A function of analyzing the timing of the financial transaction;
A function of changing an authentication level of the user authentication based on the analysis result of the timing of the financial transaction;
A program characterized by realizing.