(19)
(11)EP 2 998 901 B1

(12)EUROPEAN PATENT SPECIFICATION

(45)Mention of the grant of the patent:
17.06.2020 Bulletin 2020/25

(21)Application number: 14819369.1

(22)Date of filing:  19.06.2014
(51)Int. Cl.: 
G06F 21/55  (2013.01)
G06F 21/56  (2013.01)
H04L 29/06  (2006.01)
G06F 21/31  (2013.01)
G06F 21/62  (2013.01)
(86)International application number:
PCT/JP2014/066272
(87)International publication number:
WO 2015/001969 (08.01.2015 Gazette  2015/01)

(54)

UNAUTHORIZED-ACCESS DETECTION SYSTEM AND UNAUTHORIZED-ACCESS DETECTION METHOD

SYSTEM ZUR DETEKTION VON NICHTAUTHORISIERTEM ZUGRIFF UND VERFAHREN ZUR DETEKTION VON NICHTAUTHORISIERTEM ZUGRIFF

SYSTÈME ET PROCÉDÉ DE DÉTECTION D'ACCÈS NON AUTORISÉ


(84)Designated Contracting States:
AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

(30)Priority: 05.07.2013 JP 2013141770
05.07.2013 JP 2013141772

(43)Date of publication of application:
23.03.2016 Bulletin 2016/12

(73)Proprietor: Nippon Telegraph and Telephone Corporation
Tokyo 100-8116 (JP)

(72)Inventors:
  • AKIYAMA, Mitsuaki
    Musashino-shi Tokyo 180-8585 (JP)
  • YAGI, Takeshi
    Musashino-shi Tokyo 180-8585 (JP)

(74)Representative: Hoffmann Eitle 
Patent- und Rechtsanwälte PartmbB Arabellastraße 30
81925 München
81925 München (DE)


(56)References cited: : 
WO-A1-2009/032379
JP-A- 2006 099 590
JP-A- 2014 110 046
US-A1- 2009 328 216
JP-A- H10 124 457
JP-A- 2012 083 849
US-A1- 2007 261 112
  
  • MITSUAKI AKIYAMA ET AL: "Scalable and Performance-Efficient Client Honeypot on High Interaction System", APPLICATIONS AND THE INTERNET (SAINT), 2012 IEEE/IPSJ 12TH INTERNATIONAL SYMPOSIUM ON, IEEE, 16 July 2012 (2012-07-16), pages 40-50, XP032240389, DOI: 10.1109/SAINT.2012.15 ISBN: 978-1-4673-2001-6
  • TAKESHI YAGI ET AL: "Life-cycle monitoring scheme of malware download sites for websites", SERVICE-ORIENTED COMPUTING AND APPLICATIONS (SOCA), 2010 IEEE INTERNATIONAL CONFERENCE ON, IEEE, 13 December 2010 (2010-12-13), pages 1-6, XP031898675, DOI: 10.1109/SOCA.2010.5707153 ISBN: 978-1-4244-9802-4
  • TAKESHI YAGI: 'Design of an FTP Honeypot for Expanding the Search Scope in Attack Space' CSS2012 COMPUTER SECURITY SYMPOSIUM 2012 RONBUNSHU vol. 2012, no. 3, 23 October 2012, pages 823 - 827, XP055295833
  • TAKESHI YAGI: 'Analysis of Website Infections using Malware' IEICE TECHNICAL REPORT vol. 111, no. 82, 09 June 2011, pages 75 - 80, XP008181265
  
Note: Within nine months from the publication of the mention of the grant of the European patent, any person may give notice to the European Patent Office of opposition to the European patent granted. Notice of opposition shall be filed in a written reasoned statement. It shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention).


Description

Field



[0001] The present invention relates to an unauthorized access detecting system and an unauthorized access detecting method.

Background



[0002] In recent years, by a computer terminal or a server (hereinafter, referred to as "host" without distinguishment between them) becoming infected with malware, which is malicious software, destruction of information inside the host and cases where the host itself is abused as a stepping stone to new attacks have been occurring. Further, the malware is also able to leak out information in the host to outside without permission. Since not only personal information, but also confidential information of a company, a government, a military organization, or the like may be leaked out, information leakage by malware infection has been a problem.

[0003] Infection means through various infection routes have been confirmed for malware, including, for example: infection by a user clicking and installing malware appearing as a file attached to an e-mail; malware appearing as general software distributed on a Web site; malware appearing as a P2P file; infection by malware being automatically downloaded and installed when a Web site including an attack code is browsed with a Web browser having vulnerability; and the like.

[0004] Further, there has been unauthorized access to various services provided on the Internet. Much of the unauthorized access is performed by breaking thorough authentication information (for example, an account name and a password) by brute force (login attempted by an attacker using all possible combinations of account names and passwords) or performed by using genuine authentication information stolen by some means from a user in advance. Since logins are continuously executed when authentication information is broken through by brute force, based on a threshold of the number of login trials per unit time, the detection and protection are possible by an intrusion prevention system (IPS) or the like (see, for example, Non-Patent Literature 1).

[0005] Further, against such malware infection, antivirus vendors generate signatures of malware to prevent hosts from being infected with malware. However, for these signatures, detailed analysis of malware is required, and thus signature generation is costly time-wise.

[0006] Many conventional measures against information leakage prevent leakage of confidential data by setting access rights with respect to information for users. These do not cover a case in which a user having an access right intentionally leaks out information to outside. Further, if that user copies the information, protection with respect to the copied data is not covered.

[0007] A technique called data loss prevention or data leak prevention (DLP) has been recently used as a method of preventing information leakage by control focused on information (see, for example, Non-Patent Literatures 2 to 4). In DLP, access to or transmission of information having confidentiality is monitored, and in particular, the transmission to outside is prevented. This may be achieved by a method of controlling information on a host, or by a method of performing control by monitoring contents of communication on a network.

[0008] As the former method of controlling information on a host, a method of monitoring access to confidential information by using an agent program installed on a host used by a user has been known. For example, if confidential information is attempted to be downloaded from a file server and to be copied into an external storage, such as a USB memory, protection is performed by a warning sentence or the like being displayed on a screen. If the confidential information is attempted to be transmitted to outside as a file attached to an e-mail, protection is performed by a similar process.

[0009] As the latter method of monitoring contents of communication on a network, a method of monitoring contents of communication on a network by using an appliance that analyzes the communication on the network has been known. For example, if confidential information is attempted to be transmitted to outside as a file attached to an e-mail, the appliance checks contents of the communication and blocks the transmission.

Citation List


Non-Patent Literature



[0010] 

Non-Patent Literature 1: "Suricata Downloads" [online], [retrieved on May 15, 2013] from the Internet: <URL: http://www.openinfosecfoundation.org/index.php/download-suricata>

Non-Patent Literature 2: "Trend Micro Data Loss Prevention" [online],[retrieved on May 1, 2013] from the Internet: <URL: http://jp.trendmicro.com/jp/products/enterprise/tmdlp/>

Non-Patent Literature 3:"RSA DLP (Data Loss Prevention) Suite" [online], [retrieved on May 1, 2013] from the Internet: <URL: http://japan.rsa.com/node.aspx?id=3426>

Non-Patent Literature 4: "McAfee Data Loss Prevention Endpoint" [online, [retrieved on May 1, 2013] from the Internet <URL: http://www.mcafee.com/japan/products/data_loss_prevention.asp >



[0011] WO 2009/032379 A1 refers to providing trap-based defenses in a computing environment. Decoy information is generated and a beacon is embedded into the decoy information. The decoy information is then inserted into a computing environment and the beacon provides an indication that the decoy information has been accessed by an attacker. In an example decoy information can be an email login or a system login that functions like an actual login. A server such as a web server may identify failed login attempts using the decoy username and password and may obtain the IP address or other identifying information of the attacker.

[0012] US 2009/328216 A1 describes a personalized honeypot for detecting information leaks and security breaches. Resources in a computing environment are associated with a honeypot. Unique identifiers with respective ones of the honeypotted resources are provided to a honeypot monitoring functionality for monitoring use of the honeypotted resources. A honeypotted fake user account may be established in an enterprise network. As no legitimate user would enter the resource, any attempt to enter the resource can be identified to be malicious. According to another example, a password file may be honeypotted so that a user can directly change the passwords if it is detected that the password file was accessed.

[0013] MITSUAKI AKIYAMA ET AL: "Scalable and Performance-Efficient Client Honeypot on High Interaction System", APPLICATIONS AND THE INTERNET (SAINT), [...], 16 July 2012, refers to a client honeypot on a high interaction system. A honeypot as a decoy system functioning as a vulnerable host can be used to observe the internal situation of a victim host on an equivalent environment as an actual victim host.

[0014] TAKESHI YAGI ET AL: "Life-cycle monitoring scheme of malware download sites for websites", SERVICE-ORIENTED COMPUTING AND APPLICATIONS (SOCA), [...], 13 December 2010, refers to a life-cycle monitoring scheme of malware download sites for websites. A system for automatically updating a filtering configuration on download sites is described, based on a dynamic malware analysis using attack re-creation by coupling the attack collection function, attack analysis function, and filter management function.

Summary


Technical Problem



[0015] However, the conventional techniques have a problem that identification of unauthorized access, or identification of a program that performs the unauthorized access may not be possible.

[0016] For example, if unauthorized access is performed by use of genuine authentication information stolen by some means from a user, an attacker will perform login by using the genuine authentication information, and thus distinction between access by the authorized user and access by the attacker is difficult. Thus, it has been a problem to properly perform detection of unauthorized access that uses leaked authentication information.

[0017] Further, for example, in the above described method of controlling information on a host by using an agent program, if the host is infected with malware, operation may be performed with this agent program being stopped. Therefore, complete protection against information leakage operation on a host is difficult.

[0018] Further, for example, in the above described method of monitoring contents of communication on a network, if malware encrypts the contents of communication, it is difficult to identify what kind of information is actually being transmitted just by the contents of communication.

[0019] Further, for example, various programs exist on the Internet, and in order to determine whether such a program is malware that leaks out information, detailed analysis of the program is required. However, since malware generally has analysis-resistant functions, such as a code obfuscation function and an anti-debugging function, and the contents of communication themselves are often encrypted, it is difficult to determine whether information leakage is performed.

[0020] Therefore, an object of this invention is to properly identify unauthorized access, or identify a program that performs the unauthorized access.

Solution to Problem



[0021] This object of the invention is solved by the subject matter of the independent claims. Advantageous embodiments of the invention are disclosed in the dependent claims.

[0022] An unauthorized access detecting system includes: a generating unit that generates authentication information to be leaked outside; an operating unit that sets the authentication information generated by the generating unit on a host and causes a program to be analyzed to operate on the host; a detecting unit that detects access to a content using the authentication information; and an identifying unit that identifies, if access using the authentication information is detected by the detecting unit, the access as unauthorized access.

[0023] Further, an unauthorized access detecting method executed by an unauthorized access detecting system, the unauthorized access detecting method includes: a generating step of generating authentication information to be leaked outside; an operating step of setting the authentication information generated by the generating step on a host and causing a program to be analyzed to operate on the host; a detecting step of detecting access to a content using the authentication information; and an identifying step of identifying, if access using the authentication information is detected by the detecting step, the access as unauthorized access.

[0024] Further, an unauthorized access detecting system includes: a generating unit that generates authentication information; an operating unit that sets the authentication information generated by the generating unit on a host and causes a program to be analyzed to operate on the host; a detecting unit that detects unauthorized access to a content using the authentication information; and an identifying unit that identifies, as a program that leaks out information, a program that operates on the host set with the authentication information if unauthorized access using the authentication information has been detected by the detecting unit.

[0025] Further, an unauthorized access detecting method executed by an unauthorized access detecting system, the unauthorized access detecting method includes: a generating step of generating authentication information; an operating step of setting the authentication information generated by the generating step on a host and causing a program to be analyzed to operate on the host; a detecting step of detecting unauthorized access to a content using the authentication information; and an identifying step of identifying, if unauthorized access using the authentication information is detected by the detecting step, a program that operates on the host set with the authentication information, as a program that leaks out information.

Advantageous Effects of Invention



[0026] An unauthorized access detecting system and an unauthorized access detecting method disclosed in this application are able to properly identify unauthorized access or identify a program that performs the unauthorized access.

Brief Description of Drawings



[0027] 

FIG. 1 is a diagram illustrating an example of a configuration of an unauthorized access detecting system according to a first embodiment.

FIG. 2 is a diagram illustrating a process of leaking out analysis authentication information and a process of monitoring unauthorized access in a service set with the analysis authentication information, in the unauthorized access detecting system according to the first embodiment.

FIG. 3 is a block diagram illustrating a configuration of an authentication information management device according to the first embodiment.

FIG. 4 is a block diagram illustrating a configuration of an analyzing host according to the first embodiment.

FIG. 5 is a block diagram illustrating a configuration of a server according to the first embodiment.

FIG. 6 is a diagram illustrating an information leakage detecting process using authentication information in the unauthorized access detecting system according to the first embodiment.

FIG. 7 is a block diagram illustrating a configuration of an unauthorized access information management device according to the first embodiment.

FIG. 8 is a diagram illustrating a process upon filtering a host of an attacker performing unauthorized access in the unauthorized access detecting system according to the first embodiment.

FIG. 9 is a diagram illustrating a process of preventing unauthorized access in the unauthorized access detecting system according to the first embodiment.

FIG. 10 is a flow chart illustrating a flow of an unauthorized access detecting process in the server of the unauthorized access detecting system according to the first embodiment.

FIG. 11 is a diagram illustrating an example of a configuration of an unauthorized access detecting system according to a second embodiment.

FIG. 12 is a diagram illustrating a process of leaking out analysis authentication information and a process of monitoring unauthorized access in a service set with the analysis authentication information, in the unauthorized access detecting system according to the second embodiment.

FIG. 13 is a block diagram illustrating a configuration of an authentication information management device according to the second embodiment.

FIG. 14 is a diagram illustrating an example of a table stored in an analysis authentication information storage unit.

FIG. 15 is a block diagram illustrating a configuration of an analyzing host according to the second embodiment.

FIG. 16 is a diagram illustrating an analyzing process using a single type and plural types of authentication information.

FIG. 17 is a block diagram illustrating a configuration of a server according to the second embodiment.

FIG. 18 is a diagram illustrating an information leakage detecting process using authentication information in the unauthorized access detecting system according to the second embodiment.

FIG. 19 is a diagram illustrating a process of identifying malware that leaks out information, in the unauthorized access detecting system according to the second embodiment.

FIG. 20 is a flow chart illustrating a flow of an unauthorized access detecting process in the server of the unauthorized access detecting system according to the second embodiment.

FIG. 21 is a diagram illustrating a computer that executes an unauthorized access detecting program. Description of Embodiments



[0028] Hereinafter, with reference to the drawings, embodiments of an unauthorized access detecting system and an unauthorized access detecting method according to this invention will be described in detail. The invention is not limited by these embodiments.

[First Embodiment]



[0029] Hereinafter, flows of processes by an unauthorized access detecting system and an unauthorized access detecting method according to a first embodiment will be described in sequence, and lastly, effects by the first embodiment will be described.

[Configuration of System]



[0030] First of all, an example of a configuration of an unauthorized access detecting system 100 according to the first embodiment will be described. FIG. 1 is a diagram illustrating the example of the configuration of the unauthorized access detecting system according to the first embodiment. As illustrated in FIG. 1, the unauthorized access detecting system 100 has an authentication information management device 10, an analyzing host 20, a group of servers 30A to 30C, and an unauthorized access information management device 40. Further, in the unauthorized access detecting system 100, the authentication information management device 10, the analyzing host 20, and the group of servers 30A to 30C are connected to one another via the Internet 50. As for the group of servers 30A to 30C, if one of the servers is described without any particular distinction among them, that server will be referred to as "server 30".

[0031] The authentication information management device 10 generates authentication information for analysis and manages correspondence between the generated authentication information and a program set with the authentication information. Further, the authentication information management device 10 performs transmission to the analyzing host 20. The generated authentication information corresponds respectively to the servers 30A and 30C and as the authentication information, site information of a service, an account name, and a password are generated. The site information of a service is information on a server that provides a service for monitoring unauthorized access using authentication information for analysis, and is, for example, an IP address or FQDN of the group of servers 30A to 30C. Further, the account name and password are randomly generated, and those, which are not being actually used, are generated.

[0032] The analyzing host 20 sets authentication information of a particular service that is on the analyzing host 20 and causes a program to be analyzed to operate. The analyzing host 20 is connected to the Internet 50 in advance. If the program is malware that leaks out information, the program will secretly leak out authentication information to an outside attacker without consent of a user.

[0033] The group of servers 30A to 30C are servers that manage contents of a Web site, and are servers for causing an attacker to fraudulently make access with the authentication information intentionally leaked out. For example, if there is access using the leaked authentication information, the group of servers 30A to 30C identify the access as unauthorized access, obtains host information (for example, an IP address) of the attacker that has made the unauthorized access, and transmits the host information to the unauthorized access information management device 40.

[0034] The unauthorized access information management device 40 manages the host information of the attacker that has made the unauthorized access, and transmits the host information to the group of servers 30A to 30C. Thereby, the host of the attacker that has made the unauthorized access with respect to the group of servers 30A to 30C becomes a target to be filtered in various services.

[0035] In the unauthorized access detecting system 100, as a premise, a process of intentionally causing authentication information for analysis to be leaked out and monitoring unauthorized access is performed. By use of FIG. 2, a process of leaking out analysis authentication information and a process of monitoring unauthorized access in a service set with the analysis authentication information will be described. FIG. 2 is a diagram illustrating a process of leaking out analysis authentication information and a process of monitoring unauthorized access in a service set with the analysis authentication information, in the unauthorized access detecting system according to the first embodiment.

[0036] As illustrated in FIG. 2, first, the analyzing host 20 sets, as authentication information of a particular service on the analyzing host, authentication information generated by the authentication information management device 10, and if a program to be analyzed is malware that leaks out information, the analyzing host 20 accesses a file or a registry, in which the above described authentication information is stored (see (1) in FIG. 2). The analyzing host 20 then secretly leaks out the authentication information without the user's consent to an outside attacker (see (2) in FIG. 2).

[0037] Next, while the group of servers 30A to 30C providing a particular service are being operated, login is observed. If login by the attacker using the leaked authentication information is performed (see (3) in FIG. 2), the group of servers 30A to 30C determine that the login is unauthorized access (see (4) in FIG. 2).

[0038] As described above, by intentionally causing authentication information for analysis to be leaked out, as the same leaked authentication information is used, the use is able to be identified as unauthorized access. By obtaining host information of the attacker that has made the unauthorized access, and filtering the host information in various services, unauthorized access is able to be detected and prevented.

[Configuration of Authentication Information Management Device]



[0039] Next, a configuration of the authentication information management device 10 illustrated in FIG. 3 will be described. FIG. 3 is a block diagram illustrating a configuration of the authentication information management device according to the first embodiment. As illustrated in FIG. 3, the authentication information management device 10 has a communication processing unit 11, a control unit 12, and a storage unit 13.

[0040] The communication processing unit 11 controls communication related to various types of information exchanged with the analyzing host 20, the group of servers 30A to 30C, and the like, which are connected thereto. For example, the communication processing unit 11 transmits the generated authentication information to the analyzing host 20. Further, for example, the communication processing unit 11 receives authentication information used in unauthorized access, from the group of servers 30A to 30C.

[0041] The storage unit 13 has, as illustrated in FIG. 3, an analysis authentication information storage unit 13a. The storage unit 13 is, for example: a semiconductor memory element, such as a random access memory (RAM) or a flash memory; or a storage device, such as a hard disk or an optical disk.

[0042] The analysis authentication information storage unit 13a stores therein a table in which correspondence between authentication information for analysis generated by a generating unit 12a described later and a program set with the authentication information is prescribed.

[0043] For example, as the authentication information used in analysis, the analysis authentication information storage unit 13a stores therein site information of a service, an account name, a password, and the like. The site information of a service is, for example, information related to the group of servers 30A to 30C that provide a service for monitoring unauthorized access using authentication information for analysis, and is, for example, an IP address or a fully qualified domain name (FQDN).

[0044] Further, the analysis authentication information storage unit 13a stores therein, as the account name, for example, one which is not being used in real services. Further, the analysis authentication information storage unit 13a stores therein, as the password, a character string, which is difficult to be guessed and sufficiently complex. This is for discriminating a login from a login attack by brute force when whether the password is the leaked information is identified upon the login.

[0045] Returning to FIG. 3, the control unit 12 has the generating unit 12a and a management unit 12b. The control unit 12 is an electronic circuit, such as a central processing unit (CPU) or a micro processing unit (MPU), or an integrated circuit, such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA).

[0046] The generating unit 12a generates authentication information to be leaked outside. For example, the generating unit 12a generates, as the authentication information for analysis to be intentionally leaked out to an attacker, a set of: an IP address or FQDN of the group of servers 30A to 30C; and an account name and a password that are randomly generated. The generated authentication information may correspond to various types of services, for example, those of Secure Shell (SSH), File Transfer Protocol (FTP), Post Office Protocol (POP), and the like.

[0047] In order to accurately distinguish between login by brute force (login attempted by an attacker using all possible combinations of account names and passwords) and login using the leaked authentication information, with respect to a service in the server 30 that provides the service, the generated analysis authentication information is desirably a character string, which is randomly generated, sufficiently long, and unique.

[0048] The management unit 12b transmits the authentication information generated by the generating unit 12a, to the analyzing host 20. The transmitted authentication information is set on the analyzing host 20 and a program to be analyzed is executed. Further, the management unit 12b receives a set of authentication information corresponding to the program executed by the analyzing host 20 and stores the program correspondingly with the set of authentication information corresponding to the program into the analysis authentication information storage unit 13a.

[Configuration of Analyzing Host]



[0049] Next, a configuration of the analyzing host 20 illustrated in FIG. 4 will be described. FIG. 4 is a block diagram illustrating the configuration of the analyzing host according to the first embodiment. As illustrated in FIG. 4, the analyzing host 20 has a communication processing unit 21, a control unit 22, and a storage unit 23.

[0050] The communication processing unit 21 controls communication related to various types of information exchanged with the authentication information management device 10, the group of servers 30A to 30C, and the like, which are connected thereto. For example, the communication processing unit 21 receives authentication information from the authentication information management device 10. Further, for example, the communication processing unit 21 transmits authentication information to an outside attacker. If authentication information is received from the authentication information management device 10, the received authentication information is stored in an analysis authentication information storage unit 23a described later.

[0051] The storage unit 23 has, as illustrated in FIG. 4, the analysis authentication information storage unit 23a. The storage unit 23 is, for example: a semiconductor memory element, such as a random access memory (RAM) or a flash memory; or a storage device, such as a hard disk or an optical disk.

[0052] The analysis authentication information storage unit 23a stores therein the above described authentication information for analysis generated by the authentication information management device 10. For example, the analysis authentication information storage unit 23a stores therein, as the authentication information used in analysis, site information of a service, an account name, a password, and the like. The site information of a service is, for example, information related to the group of servers 30A to 30C that provide a service for monitoring unauthorized access using the authentication information for analysis, and is, for example, an IP address or a fully qualified domain name (FQDN).

[0053] Further, the analysis authentication information storage unit 23a stores therein, as the account name, one that is not being used in real services, for example. Further, the analysis authentication information storage unit 23a stores therein, as the password, a character string, which is difficult to be guessed and sufficiently complex. This is for discriminating a login from a login attack by brute force when whether the password is the leaked information is identified upon the login.

[0054] Returning to FIG. 4, the control unit 22 has a setting unit 22a and an operating unit 22b. The control unit 22 is an electronic circuit, such as a central processing unit (CPU) or a micro processing unit (MPU), or an integrated circuit, such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA).

[0055] The setting unit 22a sets, as authentication information of a particular service, the authentication information generated by the generating unit 12a of the authentication information management device 10. For example, the setting unit 22a obtains authentication information from the analysis authentication information storage unit 23a and sets the obtained authentication information as the authentication information of the particular service.

[0056] The operating unit 22b causes a client application (of SSH, FTP, POP, or the like) of a service to operate on the analyzing host 20 set with the authentication information by the setting unit 22a, as a program to be analyzed. The operating unit 22b performs notification of the set of authentication information corresponding to the executed program. If the operated program is malware that leaks out information, the program will secretly leak out authentication information to an outside attacker without consent of a user. The authentication information to be leaked out may be of any type of service as long as whether there has been a login with the authentication information leaked by the server 30 providing the service is able to be checked. Further, the service may be prepared for the analysis, or a real service may be used.

[Configuration of Server]



[0057] Next, a configuration of the server 30 illustrated in FIG. 5 will be described. FIG. 5 is a block diagram illustrating the configuration of the server according to the first embodiment. As illustrated in FIG. 5, the server 30 has a communication processing unit 31, a control unit 32, and a storage unit 33.

[0058] The communication processing unit 31 controls communication related to various types of information exchanged with the authentication information management device 10, the analyzing host 20, and the like, which are connected thereto. For example, the communication processing unit 31 transmits, to the authentication information management device 10, authentication information used in unauthorized access. Further, the communication processing unit 31 receives analysis authentication information from the authentication information management device 10. The received analysis authentication information is stored in an analysis authentication information storage unit 33a.

[0059] The storage unit 33 has, as illustrated in FIG. 5, the analysis authentication information storage unit 33a and a malicious host information storage unit 33b. The storage unit 33 is, for example: a semiconductor memory element, such as a random access memory (RAM) or a flash memory; or a storage device, such as a hard disk or an optical disk.

[0060] The analysis authentication information storage unit 33a stores therein a list of authentication information for analysis generated by the above described authentication information management device 10. The list of authentication information stored in the analysis authentication information storage unit 33a is used by a detecting unit 32a, which will be described later, for determining whether or not a login is unauthorized access.

[0061] For example, the analysis authentication information storage unit 33a stores therein, as the authentication information used in analysis, site information of a service, an account name, a password, and the like. The site information of a service is, for example, information related to the server 30 that provides a service for monitoring unauthorized access using the authentication information for analysis, and is, for example, an IP address or a fully qualified domain name (FQDN).

[0062] Further, the analysis authentication information storage unit 33a stores therein, as the account name, one which is not being used in real services, for example. Further, the analysis authentication information storage unit 33a stores therein, as the password, a character string, which is difficult to be guessed and sufficiently complex. This is for discriminating a login from a login attack by brute force when whether the password is the leaked information is identified upon the login.

[0063] The malicious host information storage unit 33b stores therein information on a host that has performed unauthorized access. For example, the malicious host information storage unit 33b stores therein, as the information on a host that has performed unauthorized access, the IP address.

[0064] Returning to FIG. 5, the control unit 32 has the detecting unit 32a, an identifying unit 32b, a storing unit 32c, and an access preventing unit 32d. The control unit 32 is an electronic circuit, such as a central processing unit (CPU) or a micro processing unit (MPU), or an integrated circuit, such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA).

[0065] The detecting unit 32a detects access to a content using the authentication information generated by the generating unit 12a of the authentication information management device 10. Specifically, the detecting unit 32a determines whether the authentication information used in the access to the content coincides with the authentication information stored in the analysis authentication information storage unit 33a.

[0066] If access using the authentication information is detected by the detecting unit 32a, the identifying unit 32b identifies the access as unauthorized access. For example, if a login event occurs with respect to a content, for which an analysis account corresponding to the analysis authentication information has been prepared, the identifying unit 32b determines whether the authentication information used in the login is included in the analysis authentication information stored in the analysis authentication information storage unit 33a.

[0067] As a result, if the authentication information used in the login is included in the list of analysis authentication information stored in the analysis authentication information storage unit 33a, the identifying unit 32b identifies the login as unauthorized access and transmits the authentication information used in the unauthorized access to the authentication information management device 10.

[0068] The storing unit 32c obtains information on a host that has performed the access identified as the unauthorized access by the identifying unit 32b and stores the information into the malicious host information storage unit 33b. Further, the storing unit 32c transmits the obtained information on the host to the unauthorized access information management device 40.

[0069] The access preventing unit 32d detects access from the host identified by the information on the host stored in the malicious host information storage unit 33b and prevents access from the host. For example, the access preventing unit 32d determines whether or not the host attempting a login is included in attacker host information, and if as a result of the determination, the host is included in the attacker host information, the access preventing unit 32d determines the login to be a login by an attacker and blocks the login.

[0070] By use of FIG. 6, an information leakage detecting process using authentication information in the unauthorized access detecting system 100 according to the first embodiment will be described. FIG. 6 is a diagram illustrating the information leakage detecting process using authentication information in the unauthorized access detecting system according to the first embodiment. As illustrated in FIG. 6, the authentication information management device 10 of the unauthorized access detecting system 100 generates, every time a program is analyzed, unique analysis authentication information (a set of a server name that provides a service, an account name, and password information) (see (1) in FIG. 6).

[0071] The generated analysis authentication information is set on the analyzing host 20 that executes the program (see (2) in FIG. 6) and the program to be analyzed is executed (see (3) in FIG. 6). Further, the analyzing host 20 notifies the authentication information management device 10 of the set of authentication information corresponding to the executed program (see (4) in FIG. 6). The authentication information management device 10 notifies the server 30 that provides a service, of the generated analysis authentication information (see (5) in FIG. 6).

[0072] Thereafter, after the program to be analyzed is executed, the analyzing host 20 transmits the set analysis authentication information to an attacker, if the program is malware that leaks out information (see (6) in FIG. 6). There is no need to identify whether the program has leaked out information at this point. The attacker performs unauthorized access to the service by using the leaked authentication information and attempts login (see (7) in FIG. 6). The server 30 that provides the service identifies whether the login is login using the analysis authentication information, and if the login is the login using the analysis authentication information, the login is detected as unauthorized access (see (8) in FIG. 6). By obtaining and storing information on a host that has performed the unauthorized access, the information on the host is made a target to be filtered in various services.

[Configuration of Unauthorized Access Information Management Device]



[0073] Next, a configuration of the unauthorized access information management device 40 illustrated in FIG. 7 will be described. FIG. 7 is a block diagram illustrating a configuration of the unauthorized access information management device according to the first embodiment. As illustrated in FIG. 7, the unauthorized access information management device 40 has a communication processing unit 41, a control unit 42, and a storage unit 43.

[0074] The communication processing unit 41 controls communication related to various types of information exchanged with the authentication information management device 10, the analyzing host 20, the server 30, and the like, which are connected thereto. For example, the communication processing unit 31 receives, from the server, information on a host that has performed unauthorized access. Further, the communication processing unit 41 transmits the information on a host that has performed unauthorized access, to the group of servers 30A to 30C.

[0075] The storage unit 43, has, as illustrated in FIG. 7, a malicious host information storage unit 43a and a server information storage unit 43b. The storage unit 43 is, for example: a semiconductor memory element, such as a random access memory (RAM) or a flash memory; or a storage device, such as a hard disk or an optical disk.

[0076] The malicious host information storage unit 43a stores therein a list of information on hosts that have performed unauthorized access (which may, hereinafter, be referred to as "attacker host information list"). For example, the malicious host information storage unit 43a stores therein, as the list of information on hosts that have performed unauthorized access, the IP addresses. The information stored therein is a list of host information collected from the group of servers 30A to 30C.

[0077] The server information storage unit 43b stores therein address information or the like of a server to be notified of the information on a host that has performed unauthorized access. The information stored therein is referred to by a transmitting unit 42b, which will be described later, when the transmitting unit 42b transmits the information on a host that has performed unauthorized access, to the server 30.

[0078] Returning to FIG. 7, the control unit 42 has a storing unit 42a and the transmitting unit 42b. The control unit 42 is an electronic circuit, such as a central processing unit (CPU) or a micro processing unit (MPU), or an integrated circuit, such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA).

[0079] The storing unit 42a receives the information on a host that has made unauthorized access, the information being transmitted from the server 30, and stores the information on the host that has made unauthorized access, into the malicious host information storage unit 43a. For example, as the information on a host that has made unauthorized access, the storing unit 42a stores the IP address into the malicious host information storage unit 43a and updates the attacker host information list.

[0080] The attacker host information list, which is able to be collected when unauthorized access is identified in a service by use of analysis authentication information, is applicable to real services using various types of authentication information. For an intracompany system or a service with limited users, by limiting IP addresses or the like of hosts, unauthorized access due to account information leakage is able to be prevented to a certain extent. For example, in an intracompany system, protection is possible by allowing only login from intracompany IP addresses. However, since a vast number of hosts that perform login exist for a service used by an unspecified large number of users and the IP addresses are scattered, measures by limiting the IP addresses of the users beforehand are unable to be taken. This embodiment may be applied to the latter service used by an unspecified large number of users, for example, a mail service, an internet shopping service, a social network service, a blog service, or the like.

[0081] The transmitting unit 42b transmits, to the respective servers 30A to 30C, the information on a host that has made unauthorized access. For example, the transmitting unit 42b refers to the address information of the server 30 stored in the server information storage unit 43b and transmits the information on the host that has made unauthorized access to the respective servers 30A to 30C.

[0082] By use of FIG. 8, a process upon filtering a host of an attacker that performs unauthorized access will be described. FIG. 8 is a diagram illustrating the process upon filtering a host of an attacker that performs unauthorized access in the unauthorized access detecting system according to the first embodiment. As illustrated in FIG. 8, when the server 30A that provides a service detects unauthorized access using analysis authentication information (see (1) in FIG. 8), the host information of that attacker is transmitted to the unauthorized access information management device 40 (see (2) in FIG. 8).

[0083] The unauthorized access information management device 40 transmits, to the other servers (the server 30B and the server 30C), the host information of the attacker that performs unauthorized access (see (3) in FIG. 8). When unauthorized access is received (see (4) in FIG. 8), each of the servers 30A to 30C that have received the information on the attacker identifies the host of the attacker by comparison with the host information upon the login based on that information and prevents the unauthorized access (see (5) in FIG. 8). Plural types of the servers 30 that provide services may be present, or the server 30 may be a single server.

[0084] By use of FIG. 9, a process of preventing unauthorized access in the unauthorized access detecting system 100 according to the first embodiment will be described. FIG. 9 is a diagram illustrating the process of preventing unauthorized access in the unauthorized access detecting system according to the first embodiment.

[0085] As illustrated in FIG. 9, the analyzing host 20 sets, as authentication information of a particular service on the analyzing host 20, the authentication information generated by the authentication information management device 10, and when a program is caused to operate, if the program to be analyzed is malware that leaks out information, the analyzing host 20 accesses the file or registry, in which the above described authentication information is stored (see (1) in FIG. 9). The analyzing host 20 then secretly leaks out the authentication information without the user's consent to an outside attacker (see (2) in FIG. 9).

[0086] Next, while the server 30 that provides a particular service is being operated, login is observed. When login by the attacker using the leaked authentication information is performed (see (3) in FIG. 9), the server 30 determines that the login is unauthorized access (see (4) in FIG. 9). By utilizing the information on the host that has made the unauthorized access in access filtering of other services, unauthorized access is able to be prevented.

[Process by Server]



[0087] Next, by use of FIG. 10, a process by the server 30 according to the first embodiment will be described. FIG. 10 is a flow chart illustrating a flow of an unauthorized access detecting process in the server of the unauthorized access detecting system according to the first embodiment.

[0088] As illustrated in FIG. 10, the communication processing unit 31 of the server 30 determines whether analysis authentication information has been received from the authentication information management device 10 (Step S101). As a result, if the analysis authentication information has not been received from the authentication information management device 10 (Step S101: No), the process is advanced to processing of Step S103. Further, if the analysis authentication information has been received from the authentication information management device 10 (Step S101: Yes), the communication processing unit 31 updates a list of analysis authentication information for comparison stored in the analysis authentication information storage unit 33a (Step S102).

[0089] The storing unit 32c then determines whether host information of an attacker has been received from the unauthorized access information management device 40 (Step S103). As a result, if the host information on an attacker has not been received from the unauthorized access information management device 40 (Step S103: No), the process is advanced to processing of Step S105. Further, if the host information of an attacker has been received from the unauthorized access information management device 40 (Step S103: Yes), the storing unit 32c updates the attacker host information list for comparison by storing the host information into the malicious host information storage unit 33b (Step S104).

[0090] The detecting unit 32a then determines whether or not a login event has occurred with respect to a content, for which an analysis account corresponding to the analysis authentication information has been prepared (Step S105). As a result, if no login event has occurred (Step S105: No), the process is returned to the processing of Step S101. Further, if a login event has occurred (Step S105: Yes), the detecting unit 32a determines whether the authentication information used in the login is included in the analysis authentication information stored in the analysis authentication information storage unit 33a (Step S106).

[0091] As a result, if the authentication information used in the login is included in the analysis authentication information stored in the analysis authentication information storage unit 33a (Step S106: Yes), the identifying unit 32b determines the login to be of unauthorized access (Step S107). Subsequently, the identifying unit 32b notifies the authentication information management device 10 of the authentication information used in the unauthorized access (Step S108), and the process is advanced to processing of Step S112.

[0092] Further, at Step S106, if the authentication information used in the login is not included in the analysis authentication information stored in the analysis authentication information storage unit 33a (Step S106: No), the access preventing unit 32d determines whether the host attempting the login is included in the attacker host information (Step S109). As a result, if it is determined that the host attempting the login is not included in the attacker host information (Step S109: No), the login is determined to be of normal access (Step S110) and the process is advanced to processing of Step S112. If it is determined that the host attempting the login is included in the attacker host information (Step S109: Yes), the access preventing unit 32d determines the login to be login by an attacker and blocks the login (Step Sill), and the process is advanced to processing of Step S112.

[0093] At Step S112, the detecting unit 32a determines whether or not monitoring of unauthorized access is to be continued (Step S112). As a result, if it is determined that the monitoring of unauthorized access is to be continued (Step S112: Yes), the process is returned to Step S101. Further, if the detecting unit 32a determines that the monitoring of unauthorized access is not to be continued (Step S112: No), the process is ended.

[Effects of First Embodiment]



[0094] As described above, in the unauthorized access detecting system 100 according to the first embodiment, authentication information to be leaked outside is generated, the generated authentication information is set on a host, and a program to be analyzed is operated on the host. In the unauthorized access detecting system 100, access to a content using the authentication information is detected, and if the access using the authentication information is detected, the access is identified as unauthorized access. Therefore, detection and protection from unauthorized access using leaked authentication information are able to be performed properly.

[0095] Further, distinction between an authorized user and an attacker has been difficult in an invasion detection system when the attacker has performed unauthorized access to various services using authentication information obtained by information leakage, but in the unauthorized access detecting system 100, since the leaked information itself is for analysis and will not be used by general users, as the leaked information is used, the use is identifiable as unauthorized access, and a host of the attacker that has made that unauthorized access is able to be identified. Since the host of this attacker is likely to be making unauthorized access to other various services, by filtering information on this host (for example, the IP address) in other various services, unauthorized access is able to be detected and prevented.

[Second Embodiment]



[0096] Although the case, in which unauthorized access using leaked authentication information is detected, has been described in the first embodiment, the embodiment is not limited to this case. For example, malware that leaks out information may be identified. Therefore, hereinafter, as a second embodiment, an example of a case, in which an unauthorized access detecting system detects unauthorized access to a content using authentication information, and identifies, if unauthorized access using the authentication information is detected, a program operating on a host set with the authentication information as a program that leaks out information, will be described.

[Configuration of System]



[0097] First, an example of a configuration of an unauthorized access detecting system 200 according to the second embodiment will be described. FIG. 11 is a diagram illustrating the example of the configuration of the unauthorized access detecting system according to the second embodiment. As illustrated in FIG. 11, the unauthorized access detecting system 200 has an authentication information management device 210, an analyzing host 220, and a group of servers 230A to 230C. Further, in the unauthorized access detecting system 200, the authentication information management device 210, the analyzing host 220, and the group of servers 230A to 230C are connected to one another via the Internet 240. As for the group of servers 230A to 230C, if one of the servers is described without any particular distinction among them, that server will be referred to as "server 230".

[0098] The authentication information management device 210 generates authentication information for analysis and manages correspondence between the generated authentication information and a program to be set with the authentication information. Further, the authentication information management device 210 performs transmission to the analyzing host 220. The generated authentication information corresponds to each of the servers 30A and 30C and as the authentication information, site information of a service, an account name, and a password are generated. The site information of a service is information on a server that provides a service for monitoring unauthorized access using authentication information for analysis, and is, for example, an IP address or FQDN of the group of servers 30A to 30C. Further, the account name and password are randomly generated, and those that are not being actually used are generated.

[0099] Further, if authentication information used in unauthorized access is received from the group of servers 230A to 230C, the authentication information management device 210 identifies a program corresponding to the received authentication information to be a program that leaks out information.

[0100] The analyzing host 220 sets authentication information of a particular service on the analyzing host 220 and operates a program to be analyzed. The analyzing host 220 is connected to the Internet 240 in advance. If the program is malware that leaks out information, the program will secretly leak out authentication information to an outside attacker without consent of a user.

[0101] The group of servers 230A to 230C are servers that manage contents of a Web site and are servers for causing an attacker to fraudulently make access with the authentication information intentionally leaked out. For example, if there is access in which the leaked authentication information is used, the group of servers 230A to 230C identify that access to be unauthorized access, and notify the authentication information management device 210 of the used authentication information.

[0102] In the unauthorized access detecting system 200, as a premise, a process of monitoring unauthorized access is performed by causing authentication information for analysis to be intentionally leaked out. By use of FIG. 12, a process of leaking out analysis authentication information and a process of monitoring unauthorized access in a service set with the analysis authentication information will be described. FIG. 12 is a diagram illustrating a process of leaking out analysis authentication information and a process of monitoring unauthorized access in a service set with the analysis authentication information, in the unauthorized access detecting system according to the second embodiment.

[0103] First, as illustrated in FIG. 12, the analyzing host 220 sets, as authentication information of a particular service on the analyzing host, the authentication information generated by the authentication information management device 210, and when a program is operated, if the program to be analyzed is malware that leaks out information, the analyzing host 220 accesses a file or a registry, in which the above described authentication information has been stored (see (1) in FIG. 12). The analyzing host 220 then secretly leaks out the authentication information without the user's consent to an outside attacker (see (2) in FIG. 12).

[0104] Next, while the group of servers 230A to 230C providing a particular service are being operated, login is observed. If login by the attacker using the leaked authentication information is made (see (3) in FIG. 12), the group of servers 230A to 230C determine that the login is of unauthorized access (see (4) in FIG. 12).

[0105] Accordingly, by intentionally leaking out authentication information for analysis, as the same leaked authentication information is used, that use is able to be identified as unauthorized access. A program corresponding to the authentication information used in the unauthorized access is then identified as a program that leaks out information.

[Configuration of Authentication Information Management Device]



[0106] Next, a configuration of the authentication information management device 210 illustrated in FIG. 13 will be described. FIG. 13 is a block diagram illustrating the configuration of the authentication information management device according to the second embodiment. As illustrated in FIG. 13, the authentication information management device 210 has a communication processing unit 211, a control unit 212, and a storage unit 213.

[0107] The communication processing unit 211 controls communication related to various types of information exchanged with the analyzing host 220, the group of servers 230A to 230C, and the like, which are connected thereto. For example, the communication processing unit 211 transmits the generated authentication information to the analyzing host 220. Further, for example, the communication processing unit 211 receives authentication information used in unauthorized access, from the group of servers 230A to 230C.

[0108] The storage unit 213, has, as illustrated in FIG. 13, an analysis authentication information storage unit 213a and a malicious program storage unit 213b. The storage unit 213 is, for example: a semiconductor memory element, such as a random access memory (RAM) or a flash memory; or a storage device, such as a hard disk or an optical disk.

[0109] The analysis authentication information storage unit 213a stores therein a table prescribing correspondence between authentication information for analysis generated by a generating unit 212a, which will be described later, and a program set with the authentication information. For example, the analysis authentication information storage unit 213a stores therein, as exemplified in FIG. 14, "Analyzed Program", which is information identifying a program to be analyzed, "Client Application", which indicates a type of application operated on the analyzing host 220, and "Authentication Information", which is information identifying the generated authentication information, in association with one another.

[0110] For example, as the authentication information used in analysis, the analysis authentication information storage unit 213a stores therein site information of a service, an account name, a password, and the like. The site information of a service is, for example, information related to the group of servers 230A to 230C that provide a service for monitoring unauthorized access using the authentication information for analysis, and is, for example, an IP address or a fully qualified domain name (FQDN).

[0111] Further, the analysis authentication information storage unit 213a stores therein, as the account name, for example, one that is not being used in real services. Further, the analysis authentication information storage unit 213a stores therein, as the password, a character string, which is difficult to be guessed and sufficiently complex. This is for discriminating a login from a login attack by brute force when whether the password is the leaked information is identified upon the login.

[0112] The malicious program storage unit 213b stores therein information identifying a malicious program that leaks out information. Specifically, the malicious program storage unit 213b stores therein information identifying the malicious program identified by an identifying unit 212c described later.

[0113] Returning to FIG. 13, the control unit 212 has the generating unit 212a, a management unit 212b, the identifying unit 212c, and a collecting unit 212d. The control unit 212 is an electronic circuit, such as a central processing unit (CPU) or a micro processing unit (MPU), or an integrated circuit, such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA).

[0114] The generating unit 212a generates authentication information to be leaked outside. For example, the generating unit 212a generates, as the authentication information for analysis to be intentionally leaked out to an attacker, a set of: an IP address or FQDN of the group of servers 230A to 330C; and an account name and a password that are randomly generated. The generated authentication information may correspond to various types of services, for example, those of Secure Shell (SSH), File Transfer Protocol (FTP), Post Office Protocol (POP), and the like.

[0115] In order to accurately distinguish between brute force login (login attempted by an attacker using all possible combinations of account names and passwords) and login using the leaked authentication information, with respect to the service in the server 230 providing the service, the generated analysis authentication information is desirably a character string, which is randomly generated, sufficiently long, and unique.

[0116] The management unit 212b transmits the authentication information generated by the generating unit 212a to the analyzing host 220. The transmitted authentication information is set on the analyzing host 220 and a program to be analyzed is executed. Further, the management unit 212b receives a set of authentication information corresponding to the program executed by the analyzing host 220 and stores the program correspondingly with the set of authentication information corresponding to the program, into the analysis authentication information storage unit 213a.

[0117] If unauthorized access using the authentication information is detected by a later described detecting unit 232a of the server 230, the identifying unit 212c identifies the program operating on the analyzing host 220 set with the authentication information to be a program that leaks out information. For example, when the authentication information used in the unauthorized access is received from the group of servers 230A to 230C, the identifying unit 212c refers to the table stored in an analysis authentication information storage unit 233a, obtains a program corresponding to the authentication information, and identifies the program to be a program that leaks out information.

[0118] The collecting unit 212d collects the same program as the program identified by the identifying unit 212c from a Web space. For example, the collecting unit 212d may perform the collection by using a Web client honeypot of an existing technique and patrolling the Web space. A Web client honeypot is, not only able to collect programs automatically downloaded and installed by vulnerability of a Web browser being attacked, but even also able to collect programs, for which a user needs to click dialogs in pop-ups or the like to download and install the programs, by imitating user interaction. In particular, such programs, for which a user needs to click dialogs to download and install the programs, include both genuine and malicious programs, and thus based on whether information is leaked, whether a program is malware is able to be identified.

[Configuration of Analyzing Host]



[0119] Next, a configuration of the analyzing host 220 illustrated in FIG. 15 will be described. FIG. 15 is a block diagram illustrating the configuration of the analyzing host according to the second embodiment. As illustrated in FIG. 15, the analyzing host 220 has a communication processing unit 221, a control unit 222, and a storage unit 223.

[0120] The communication processing unit 221 controls communication related to various types of information exchanged with the authentication information management device 210, the group of servers 230A to 230C, and the like, which are connected thereto. For example, the communication processing unit 221 receives authentication information from the authentication information management device 210. Further, for example, the communication processing unit 221 transmits authentication information to an outside attacker. If authentication information is received from the authentication information management device 210, the received authentication information is stored in an analysis authentication information storage unit 223a described later.

[0121] A storage unit 233 has, as illustrated in FIG. 15, the analysis authentication information storage unit 223a. The storage unit 223 is, for example: a semiconductor memory element, such as a random access memory (RAM) or a flash memory; or a storage device, such as a hard disk or an optical disk.

[0122] The analysis authentication information storage unit 223a stores therein the above described authentication information for analysis generated by the authentication information management device 210. For example, the analysis authentication information storage unit 223a stores therein, as the authentication information used in analysis, site information of a service, an account name, a password, and the like. The site information of a service is, for example, information related to the group of servers 230A to 230C that provide a service for monitoring unauthorized access using the authentication information for analysis, and is, for example, an IP address or a fully qualified domain name (FQDN).

[0123] Further, the analysis authentication information storage unit 223a stores therein, as the account name, one that is not being used in real services, for example. Further, the analysis authentication information storage unit 223a stores therein, as the password, a character string, which is difficult to be guessed and sufficiently complex. This is for discriminating a login from a login attack by brute force when whether the password is the leaked information is identified upon the login.

[0124] Returning to FIG. 15, the control unit 222 has a setting unit 222a and an operating unit 222b. The control unit 222 is an electronic circuit, such as a central processing unit (CPU) or a micro processing unit (MPU), or an integrated circuit, such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA).

[0125] The setting unit 222a sets, as authentication information of a particular service, the authentication information generated by the generating unit 212a of the authentication information management device 210. For example, the setting unit 222a obtains authentication information from the analysis authentication information storage unit 223a and sets the obtained authentication information as the authentication information of the particular service.

[0126] The operating unit 222b operates a client application (of SSH, FTP, POP, or the like) of a service, as a program to be analyzed, on the analyzing host 220 set with the authentication information by the setting unit 222a. The operating unit 222b performs notification of the set of authentication information corresponding to the executed program. If the operated program is malware that leaks out information, the program will secretly leak out the authentication information to an outside attacker without consent of a user. The authentication information to be leaked out may be of any type of service as long as whether there has been a login with the authentication information leaked out by the server 230 providing the service is able to be checked. Further, the service may be prepared for the analysis, or a real service may be used.

[0127] Further, if a client application of a service operates on the analyzing host 220, it is supposed that the client application will write authentication information into a file or a registry. The stored path and format for this setup file or registry by each client application are determined beforehand, and thus authentication information is written into the file or registry according thereto.

[0128] If a program to be analyzed is malware that leaks out information, the program will access the file or registry, in which the above described authentication information has been stored, and transmit that information to outside. The authentication information may be set in a file or registry of a single particular client application for each host, or may be set in files or registries of plural client applications simultaneously. If analysis information is simultaneously set for plural client applications, analysis authentication information corresponding to the number of types of the set client applications need to be generated.

[0129] For example, as exemplified in FIG. 16, in an example of setting authentication information in a file or registry of a single particular client application, the analyzing host 220 sets "Analysis Authentication Information A" in "Setup File of SSH Client Application" and causes "Program 1" to operate. Or, a different analyzing host 220 sets "Analysis Authentication Information B" in "Setup File of FTP Client Application", and causes "Program 2" to operate.

[0130] Further, as exemplified in FIG. 16, in an example of simultaneously setting analysis authentication information in files or registries of plural client applications, the analyzing host 220 sets: "Analysis Authentication Information C" in "Setup File of SSH Client Application"; "Analysis Authentication Information D" in "Setup File of FTP Client Application"; and "Analysis Authentication Information E" in "Setup Registry of POP Client Application", and causes "Program 3" to operate.

[Configuration of Server]



[0131] Next, a configuration of the server 230 illustrated in FIG. 17 will be described. FIG. 17 is a block diagram illustrating the configuration of the server according to the second embodiment. As illustrated in FIG. 17, the server 230 has a communication processing unit 231, a control unit 232, and a storage unit 233.

[0132] The communication processing unit 231 controls communication related to various types of information exchanged with the authentication information management device 210, the analyzing host 220, and the like, which are connected thereto. For example, the communication processing unit 231 transmits, to the authentication information management device 210, authentication information used in unauthorized access. Further, the communication processing unit 231 receives analysis authentication information from the authentication information management device 210. The received analysis authentication information is stored in the analysis authentication information storage unit 233a.

[0133] The storage unit 233 has, as illustrated in FIG. 17, an analysis authentication information storage unit 233a. The storage unit 233 is, for example: a semiconductor memory element, such as a random access memory (RAM) or a flash memory; or a storage device, such as a hard disk or an optical disk.

[0134] The analysis authentication information storage unit 233a stores therein a list of authentication information for analysis generated by the above described authentication information management device 210. The list of authentication information stored in the analysis authentication information storage unit 233a is used by a detecting unit 232a, which will be described later, for determining whether or not a login is of unauthorized access.

[0135] For example, the analysis authentication information storage unit 223a stores therein, as the authentication information used in analysis, site information of a service, an account name, a password, and the like. The site information of a service is, for example, information related to the server 230 that provides a service for monitoring unauthorized access using the authentication information for analysis, and is, for example, an IP address or a fully qualified domain name (FQDN).

[0136] Further, the analysis authentication information storage unit 233a stores therein, as the account name, one that is not being used in real services, for example. Further, the analysis authentication information storage unit 233a stores therein, as the password, a character string, which is difficult to be guessed and sufficiently complex. This is for discriminating a login from a login attack by brute force when whether the password is the leaked information is identified upon the login.

[0137] Returning to FIG. 17, the control unit 232 has a detecting unit 232a and a deleting unit 232b. The control unit 232 is an electronic circuit, such as a central processing unit (CPU) or a micro processing unit (MPU), or an integrated circuit, such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA).

[0138] The detecting unit 232a detects unauthorized access to a content using the authentication information generated by the generating unit 212a of the authentication information management device 210. Specifically, the detecting unit 232a determines whether the authentication information used in the access to the content coincides with the authentication information stored in the analysis authentication information storage unit 233a, and if they coincide with each other, the detecting unit 232a detects the access as unauthorized access.

[0139] For example, if a login event occurs with respect to a content, for which an analysis account corresponding to analysis authentication information has been prepared, the detecting unit 232a determines whether the authentication information used in the login is included in the analysis authentication information stored in the analysis authentication information storage unit 233a.

[0140] As a result, if the authentication information used in the login is included in the list of analysis authentication information stored in the analysis authentication information storage unit 233a, the detecting unit 232a determines the login to be of unauthorized access and transmits the authentication information used in the unauthorized access to the authentication information management device 210. Further, if the authentication information used in the login is not included in the list of analysis authentication information stored in the analysis authentication information storage unit 233a, the detecting unit 232a determines the login to be of normal access.

[0141] The deleting unit 232b detects a program identified by the identifying unit 212c of the authentication information management device 210 and if the program is detected, the deleting unit 232b deletes the program. Further, for example, if information identifying a program that leaks out information is received from the authentication information management device 210, the deleting unit 232b is able to prohibit execution of the program on the host, as a method of protecting the actual host from damage of information leakage by the program that leaks out information. The program is registered as a file signature of a host-based invasion detection system or antivirus software, and if the file is present on the host or if the file is attempted to be executed, prohibition and deletion thereof are performed.

[0142] Further, as a method of preventing an actual host from damage of information leakage, downloading of the program from the network may be prohibited. Monitoring is performed by a network-based invasion detection system, a Web proxy, a mail server, or the like, a file downloaded from an external network is examined, and if the program is included therein, downloading thereof is prohibited.

[0143] By use of FIG. 18, an information leakage detecting process using authentication information in the unauthorized access detecting system 200 according to the second embodiment will be described. FIG. 18 is a diagram illustrating the information leakage detecting process using authentication information in the unauthorized access detecting system according to the second embodiment. As illustrated in FIG. 18, the authentication information management device 210 of the unauthorized access detecting system 200 generates, every time a program is analyzed, unique analysis authentication information (a set of a server name that provides a service, an account name, and password information), and performs notification thereof (see (1) in FIG. 18).

[0144] The generated analysis authentication information is set on the analyzing host 220 that executes a program (see (2) in FIG. 18) and the program to be analyzed is executed (see (3) in FIG. 18). Further, the analyzing host 220 notifies the authentication information management device 210 of the set of authentication information corresponding to the executed program (see (4) in FIG. 18). The authentication information management device 210 then delete notifies the server 230 that provides a service, of the generated analysis authentication information (see (5) in FIG. 18).

[0145] Thereafter, after executing the program to be analyzed, if the program is malware that leaks out information, the analyzing host 220 transmits the set analysis authentication information to the attacker (see (6) in FIG. 18). There is no need to determine whether the program has leaked out information at this point. The attacker makes unauthorized access with respect to the service and attempts login, by using the leaked authentication information (see (7) in FIG. 18). The server 230 that provides the service identifies whether the login in login using the analysis authentication information, and if the login is login using the analysis authentication information, the login is detected as unauthorized access (see (8) in FIG. 18). Since the analyzed program is able to be identified from the analysis authentication information used in the login, the program is able to be identified as a program that leaks out information.

[0146] By use of FIG. 19, a process of identifying malware that leaks out information in the unauthorized access detecting system 200 according to the second embodiment will be described. FIG. 19 is a diagram illustrating the process of identifying malware that leaks out information, in the unauthorized access detecting system according to the second embodiment.

[0147] As illustrated in FIG. 19, the analyzing host 220 sets, as authentication information of a particular service on the analyzing host 220, the authentication information generated by the authentication information management device 210, and when a program is operated, if the program to be analyzed is malware that leaks out information, the analyzing host 220 accesses a file or registry, in which the above described authentication information has been stored (see (1) in FIG. 19). The analyzing host 220 then secretly leaks out the authentication information without the user's consent to an outside attacker (see (2) in FIG. 19) .

[0148] Next, while the server 230 that provides a particular service is being operated, login is observed. If login by the attacker using the leaked authentication information is performed (see (3) in FIG. 19), the server 230 determines that the login is of unauthorized access (see (4) in FIG. 19). From the authentication information used in the unauthorized access, the program that has been set with the authentication information and analyzed is able to be identified, and further, it is able to be concluded that this program has leaked out information. Therefore, malware that leaks out information is able to be identified accurately.

[Process by Server]



[0149] Next, by use of FIG. 20, a process by the server 230 according to the second embodiment will be described. FIG. 20 is a flow chart illustrating a flow of an unauthorized access detecting process in the server of the unauthorized access detecting system according to the second embodiment.

[0150] As illustrated in FIG. 20, the communication processing unit 231 of the server 230 determines whether analysis authentication information has been received from the authentication information management device 210 (Step S201). As a result, if the communication processing unit 231 has not received the analysis authentication information from the authentication information management device 210 (Step S201: No), the process is advanced to processing of Step S203. Further, if the analysis authentication information has been received from the authentication information management device 210 (Step S201: Yes), the communication processing unit 231 updates the list of analysis authentication information for comparison stored in the analysis authentication information storage unit 233a (Step S202).

[0151] The detecting unit 232a then determines whether or not a login event has occurred with respect to a content, for which an analysis account corresponding to the analysis authentication information has been prepared (Step S203). As a result, if the login event has not occurred (Step S203: No), the process is returned to the processing of Step S201. Further, if a login event has occurred (Step S203: Yes), the detecting unit 232a determines whether the authentication information used in the login is included in the analysis authentication information stored in the analysis authentication information storage unit 233a (Step S204) .

[0152] As a result, if the authentication information used in the login is not included in the analysis authentication information stored in the analysis authentication information storage unit 233a (Step S204: No), the detecting unit 232a determines the login to be of normal access (Step S206) and executes processing of later described Step S208. Further, if the authentication information used in the login is included in the analysis authentication information stored in the analysis authentication information storage unit 233a (Step S204: Yes), the detecting unit 232a determines the login to be of unauthorized access (Step S205).

[0153] Subsequently, the detecting unit 232a notifies the authentication information management device 210 of the authentication information used in the unauthorized access (Step S207), and determines whether or not monitoring of unauthorized access is to be continued (Step S208). As a result, if it is determined that the monitoring of unauthorized access is to be continued (Step S208: Yes), the process is returned to Step S201. Further, if the detecting unit 232a determines that the monitoring of unauthorized access is not to be continued (Step S208: No), the process is ended.

[Effects of Second Embodiment]



[0154] As described above, in the unauthorized access detecting system 200 according to the second embodiment, authentication information is generated, the generated authentication information is set on the analyzing host 220, and a program to be analyzed is operated on the analyzing host 220. Unauthorized access to a content using the authentication information is detected, and if unauthorized access using the authentication information is detected, the program operating on the analyzing host 220 set with the authentication information is identified as a program that leaks out information. Therefore, malware that leaks out information is able to be identified accurately.

[0155] Further, in the unauthorized access detecting system 200, a program, in particular, malware, has analysis-resistant functions, and thus analysis of program codes, analysis of behaviors, and analysis of contents of communication are generally difficult. In this embodiment, without identifying a code that executes information leakage and analyzing behaviors of the program or contents of communication that the program transmits outside, the program that leaks out information (malware) is able to be accurately identified.

[System Configuration and the like]



[0156] Further, each component of the respective devices in the drawings is functionally and conceptionally illustrated, and is not necessarily physically configured as illustrated in the drawings. That is, specific modes of distribution and integration of the respective devices are not limited to those illustrated in the drawings, and depending on various loads and use situations, all or some of the devices may be configured to be functionally or physically distributed or integrated in arbitrary units. For example, the generating unit 12a and the management unit 12b may be integrated with each other. Further, all or any part of the processing functions executed by the respective devices may be realized by a CPU and a program analyzed and executed by the CPU, or may be implemented as hardware by wired logic.

[0157] Further, of the respective processes described in the embodiments, all or a part of the processes described as being executed automatically may be manually executed, or all or a part of the processes described as being executed manually may be automatically executed by a known method. In addition, the procedural sequences, control sequences, specific names, and information including various data and parameters described above and illustrated in the drawings may be arbitrarily modified unless otherwise particularly stated.

[Program]



[0158] Further, programs, which describe, in a language executable by a computer, the processes executed by the respective devices in the unauthorized access detecting systems 100 and 200 described in the embodiments, may be generated. For example, an unauthorized access detecting program, which describes, in a language executable by a computer, the process executed by each of the devices in the unauthorized access detecting system 100 according to the first embodiment or the unauthorized access detecting system 200 according to the second embodiment, may be generated. In this case, by the computer executing the unauthorized access detecting program, effects that are the same as those of the above embodiments are able to be obtained. Further, by recording that unauthorized access detecting program in a computer readable recording medium and causing the computer to load the unauthorized access detecting program recorded in this recording medium to execute the unauthorized access detecting program, processing that is the same as that of the first embodiment or the second embodiment may be realized.

[0159] FIG. 21 is a diagram illustrating a computer 1000 that executes the unauthorized access detecting program. As exemplified in FIG. 21, the computer 1000 has, for example, a memory 1010, a CPU 1020, a hard disk drive interface 1030, a disk drive interface 1040, a serial port interface 1050, a video adapter 1060, and a network interface 1070, and these are connected to one another by a bus 1080.

[0160] The memory 1010 includes, as exemplified in FIG. 21, a read only memory (ROM) 1011 and a RAM 1012. The ROM 1011 stores therein a boot program, such as a basic input output system (BIOS), for example. The hard disk drive interface 1030 is, as exemplified in FIG. 21, connected to a hard disk drive 1031. The disk drive interface 1040 is, as exemplified in FIG. 21, connected to a disk drive 1041. An attachable and detachable storage medium, such as a magnetic disk or an optical disk, for example, is inserted into the disk drive 1041. The serial port interface 1050 is, as exemplified in FIG. 21, connected to, for example, a mouse 1051 and a keyboard 1052. The video adapter 1060 is, as exemplified in FIG. 21, connected to, for example, a display 1061.

[0161] As exemplified in FIG. 21, the hard disk drive 1031 stores therein, for example, an OS 1091, an application program 1092, a program module 1093, and program data 1094. That is, the above described unauthorized access detecting program is stored, as a program module in which commands executed by the computer 1000 are described, in the hard disk drive 1031, for example.

[0162] Further, the various data described in the embodiments are stored in, for example, the memory 1010 or the hard disk drive 1031, as program data. The CPU 1020 reads, as necessary, the program module 1093 and program data 1094 stored in the memory 1010 or hard disk drive 1031 out to the RAM 1012, and executes various procedures.

[0163] The program module 1093 and program data 1094 related to the unauthorized access detecting program are not necessarily stored in the hard disk drive 1031, and may be stored in an attachable and detachable storage medium to be read out by the CPU 1020 via the disk drive or the like, for example. Or, the program module 1093 or program data 1094 related to the unauthorized access detecting program may be stored in another computer connected via a network (a local area network (LAN), a wide area network (WAN), or the like) and read out via the network interface 1070 by the CPU 1020.

Reference Signs List



[0164] 

10, 210 AUTHENTICATION INFORMATION MANAGEMENT DEVICE

11, 21, 31, 41, 211, 221, 231 COMMUNICATION PROCESSING UNIT

12, 22, 32, 42, 212, 222, 232 CONTROL UNIT

12a, 212a GENERATING UNIT

12b, 212b MANAGEMENT UNIT

13, 23, 33, 43, 213, 223, 233 STORAGE UNIT

13a, 23a, 33a, 213a, 223a, 233a ANALYSIS AUTHENTICATION INFORMATION STORAGE UNIT

20, 220 ANALYZING HOST

22a, 222a SETTING UNIT

22b, 222b OPERATING UNIT

30, 230 SERVER

32a, 232a DETECTING UNIT

32b IDENTIFYING UNIT

32c, 42a STORING UNIT

32d ACCESS PREVENTING UNIT

33b, 43a MALICIOUS HOST INFORMATION STORAGE UNIT

40 UNAUTHORIZED ACCESS INFORMATION MANAGEMENT DEVICE

42b TRANSMITTING UNIT

43b SERVER INFORMATION STORAGE UNIT

50, 240 THE INTERNET

100, 200 UNAUTHORIZED ACCESS DETECTING SYSTEM

212c IDENTIFYING UNIT

212d COLLECTING UNIT

213b MALICIOUS PROGRAM STORAGE UNIT

232b DELETING UNIT




Claims

1. An unauthorized access detecting system (200), comprising:

a management device (210) including a generating unit (212a) operable to generate authentication information;

an analyzing host (220) including an operating unit (222b) operable to set the authentication information generated by the generating unit (212a) on the analyzing host and to cause a program to be analyzed to operate on the analyzing host;

a service providing server (230) including a detecting unit (232a) operable to detect unauthorized access to a content by an outside attacker host using the authentication information; and

an identifying unit (212c) operable to obtain a program corresponding to the authentication information by referring to a table stored in an analysis authentication information storage unit (233a), the table prescribing correspondence between the authentication information and the obtained program, and to identify the obtained program as the program that operates on the analyzing host set with the authentication information as a program that leaks out the authentication information to the outside attacker host without consent of a user, if unauthorized access using the authentication information has been detected by the detecting unit (232a).


 
2. The unauthorized access detecting system according to claim 1, further comprising a storage unit (223a) operable to store therein the authentication information generated by the generating unit (212a), wherein
the detecting unit (232a) is further operable to determine whether authentication information used in access to the content coincides with the authentication information stored in the storage unit (223a), and if there is coincidence, to detect the access as unauthorized access.
 
3. The unauthorized access detecting system according to claim 1 or 2, further comprising a deleting unit (232b) operable to detect the program identified by the identifying unit (212c) and to delete the program if the program is detected.
 
4. The unauthorized access detecting system according to claim 1 or 2, further comprising a collecting unit operable to collect the same program as the program identified by the identifying unit (212c) from a Web space.
 
5. An unauthorized access detecting method executed by an unauthorized access detecting system (200), the unauthorized access detecting method including:

a generating step of generating authentication information;

an operating step of setting the authentication information generated by the generating step on an analyzing host and causing a program to be analyzed to operate on the analyzing host;

a detecting step of detecting unauthorized access to a content on a service providing server by an outside attacker host using the authentication information; and

an identifying step of obtaining a program corresponding to the authentication information by referring to a table stored in an analysis authentication information storage unit (233a), the table prescribing correspondence between the authentication information and the obtained program and of identifying the obtained program as the program that operates on the analyzing host set with the authentication information, as a program that leaks out the authentication information to an outside attacker host without consent of a user, if unauthorized access using the authentication information is detected by the detecting step.


 
6. The unauthorized access detecting method according to claim 5, further including a storing step of storing the authentication information generated by the generating step into a storage unit (223a), wherein
in the detecting step, whether authentication information used in access to the content coincides with the authentication information stored in the storage unit (223a) is determined, and if there is coincidence, the access is detected as unauthorized access.
 
7. The unauthorized access detecting method according to claim 5 or 6, further including a deleting step of detecting the program identified by the identifying step, and deleting the program if the program is detected.
 
8. The unauthorized access detecting method according to claim 5 or 6, further including a collecting step of collecting the same program as the program identified by the identifying step from a Web space.
 


Ansprüche

1. System (200) zur Detektion von nichtautorisiertem Zugriff, umfassend:

eine Verwaltungsvorrichtung (210), beinhaltend eine Erzeugungseinheit (212a), die betreibbar ist, Authentifizierungsinformationen zu erzeugen;

einen analysierenden Host (220), beinhaltend eine Betriebseinheit (222b), die betreibbar ist, die Authentifizierungsinformationen, die von der Erzeugungseinheit (212a) erzeugt werden, auf dem analysierenden Host einzustellen und zu veranlassen, dass ein zu analysierendes Programm auf dem analysierenden Host läuft;

einen Dienst bereitstellenden Server (230), beinhaltend eine Detektionseinheit (232a), die betreibbar ist, nichtautorisierten Zugriff auf einen Inhalt durch einen externen Angreifer-Host unter Verwendung der Authentifizierungsinformationen zu detektieren; und

eine Identifizierungseinheit (212c), die betreibbar ist, ein Programm entsprechend den Authentifizierungsinformationen durch Bezugnahme auf eine Tabelle zu erhalten, die in einer Analyseauthentifizierungsinformationen-Datenspeichereinheit (233a) gespeichert ist, wobei die Tabelle eine Entsprechung zwischen den Authentifizierungsinformationen und dem erhaltenen Programm vorschreibt, und das erhaltene Programm, als das Programm, das auf dem analysierenden Host läuft, auf dem die Authentifizierungsinformationen eingestellt sind, als ein Programm zu identifizieren, das die Authentifizierungsinformationen ohne Zustimmung eines Benutzers zu dem externen Angreifer-Host durchsickern lässt, falls nichtautorisierter Zugriff unter Verwendung der Authentifizierungsinformationen von der Detektionseinheit (232a) detektiert wurde.


 
2. System zur Detektion von nichtautorisiertem Zugriff nach Anspruch 1, weiter umfassend eine Datenspeichereinheit (223a), die betreibbar ist, darin die Authentifizierungsinformationen zu speichern, die durch die Erzeugungseinheit (212a) erzeugt werden, wobei
die Detektionseinheit (232a) weiter betreibbar ist zu bestimmen, ob Authentifizierungsinformationen, die bei Zugriff auf den Inhalt verwendet werden, mit den Authentifizierungsinformationen übereinstimmen, die in der Datenspeichereinheit (223a) gespeichert sind, und falls eine Übereinstimmung vorliegt, den Zugriff als nichtautorisierten Zugriff zu detektieren.
 
3. System zur Detektion von nichtautorisiertem Zugriff nach Anspruch 1 oder 2, weiter umfassend eine Löscheinheit (232b), die betreibbar ist, das Programm zu detektieren, das durch die Identifizierungseinheit (212c) identifiziert wurde, und das Programm zu löschen, falls das Programm detektiert wird.
 
4. System zur Detektion von nichtautorisiertem Zugriff nach Anspruch 1 oder 2, weiter umfassend eine Sammeleinheit, die betreibbar ist, dasselbe Programm wie das Programm, das durch die Identifizierungseinheit (212c) identifiziert wurde, aus einem Webspace zu sammeln.
 
5. Verfahren zur Detektion von nichtautorisiertem Zugriff, das von einem System (200) zur Detektion von nichtautorisiertem Zugriff ausgeführt wird, das Verfahren zur Detektion von nichtautorisiertem Zugriff beinhaltend:

einen Erzeugungsschritt zum Erzeugen von Authentifizierungsinformationen;

einen Betriebsschritt zum Einstellen der Authentifizierungsinformationen, die im Erzeugungsschritt erzeugt werden, auf einem analysierenden Host und Veranlassen, dass ein zu analysierendes Programm auf dem analysierenden Host läuft;

einen Detektionsschritt zum Detektieren von nichtautorisiertem Zugriff auf einen Inhalt auf einem Dienst bereitstellenden Server durch einen externen Angreifer-Host unter Verwendung der Authentifizierungsinformationen; und

einen Identifizierungsschritt zum Erhalten eines Programms entsprechend den Authentifizierungsinformationen durch Bezugnahme auf eine Tabelle, die in einer Analyseauthentifizierungsinformationen-Datenspeichereinheit (233a) gespeichert ist, wobei die Tabelle eine Entsprechung zwischen den Authentifizierungsinformationen und dem erhaltenen Programm vorschreibt, und zum Identifizieren des erhaltenen Programms, als das Programm, das auf dem analysierenden Host läuft, auf dem die Authentifizierungsinformationen eingestellt sind, als ein Programm, das die Authentifizierungsinformationen ohne Zustimmung eines Benutzers zu einem externen Angreifer-Host durchsickern lässt, falls nichtautorisierter Zugriff unter Verwendung der Authentifizierungsinformationen durch den Detektionsschritt detektiert wurde.


 
6. Verfahren zur Detektion von nichtautorisiertem Zugriff nach Anspruch 5, weiter beinhaltend einen Speicherungsschritt zum Speichern der Authentifizierungsinformationen, die durch den Erzeugungsschritt erzeugt werden, in einer Datenspeichereinheit (223a), wobei
im Detektionsschritt bestimmt wird, ob Authentifizierungsinformationen, die beim Zugriff auf den Inhalt verwendet werden, mit den Authentifizierungsinformationen übereinstimmen, die in der Datenspeichereinheit (223a) gespeichert sind, und falls eine Übereinstimmung vorliegt, der Zugriff als nichtautorisierter Zugriff detektiert wird.
 
7. Verfahren zur Detektion von nichtautorisiertem Zugriff nach Anspruch 5 oder 6, weiter beinhaltend einen Löschungsschritt zum Detektieren des Programms, das durch den Identifizierungsschritt identifiziert wurde, und Löschen des Programms, falls das Programm detektiert wird.
 
8. Verfahren zur Detektion von nichtautorisiertem Zugriff nach Anspruch 5 oder 6, weiter beinhaltend einen Sammelschritt zum Sammeln desselben Programms wie das Programm, das durch den Identifizierungsschritt identifiziert wurde, aus einem Webspace.
 


Revendications

1. Système de détection d'accès non autorisé (200), comprenant :

un dispositif de gestion (210) incluant une unité de génération (212a) pouvant fonctionner pour générer des informations d'authentification ;

un hôte d'analyse (220) incluant une unité de fonctionnement (222b) pouvant fonctionner pour définir les informations d'authentification générées par l'unité de génération (212a) sur l'hôte d'analyse et pour amener un programme devant être analysé à fonctionner sur l'hôte d'analyse ;

un serveur fournisseur de service (230) incluant une unité de détection (232a) pouvant fonctionner pour détecter un accès non autorisé à un contenu par un hôte attaquant extérieur en utilisant les informations d'authentification ; et

une unité d'identification (212c) pouvant fonctionner pour obtenir un programme correspondant aux informations d'authentification en consultant un tableau stocké dans une unité de stockage d'informations d'authentification d'analyse (233a), le tableau imposant une correspondance entre les informations d'authentification et le programme obtenu, et pour identifier le programme obtenu comme le programme qui fonctionne sur l'hôte d'analyse défini avec les informations d'authentification comme un programme qui divulgue les informations d'authentification à l'hôte attaquant extérieur sans consentement d'un utilisateur, si un accès non autorisé en utilisant les informations d'authentification a été détecté par l'unité de détection (232a).


 
2. Système de détection d'accès non autorisé selon la revendication 1, comprenant en outre une unité de stockage (223a) pouvant fonctionner pour stocker dans celle-ci les informations d'authentification générées par l'unité de génération (212a), dans lequel
l'unité de détection (232a) peut en outre fonctionner pour déterminer si des informations d'authentification utilisées en accès au contenu coïncident avec les informations d'authentification stockées dans l'unité de stockage (223a), et si elles coïncident, pour détecter l'accès comme accès non autorisé.
 
3. Système de détection d'accès non autorisé selon la revendication 1 ou 2, comprenant en outre une unité de suppression (232b) pouvant fonctionner pour détecter le programme identifié par l'unité d'identification (212c) et pour supprimer le programme si le programme est détecté.
 
4. Système de détection d'accès non autorisé selon la revendication 1 ou 2, comprenant en outre une unité de collecte pouvant fonctionner pour collecter le même programme que le programme identifié par l'unité d'identification (212c) depuis un espace Web.
 
5. Procédé de détection d'accès non autorisé exécuté par un système de détection d'accès non autorisé (200), le procédé de détection d'accès non autorisé incluant :

une étape de génération consistant à générer des informations d'authentification ;

une étape de fonctionnement consistant à définir les informations d'authentification générées par l'étape de génération sur un hôte d'analyse et à amener un programme devant être analysé à fonctionner sur l'hôte d'analyse ;

une étape de détection consistant à détecter un accès non autorisé à un contenu sur un serveur fournisseur de service par un hôte attaquant extérieur en utilisant les informations d'authentification ; et

une étape d'identification consistant à obtenir un programme correspondant aux informations d'authentification en consultant un tableau stocké dans une unité de stockage d'informations d'authentification d'analyse (233a), le tableau imposant une correspondance entre les informations d'authentification et le programme obtenu, et consistant à identifier le programme obtenu comme le programme qui fonctionne sur l'hôte d'analyse défini avec les informations d'authentification, comme un programme qui divulgue les informations d'authentification à un hôte attaquant extérieur sans consentement d'un utilisateur, si un accès non autorisé en utilisant les informations d'authentification a été détecté par l'étape de détection.


 
6. Procédé de détection d'accès non autorisé selon la revendication 5, incluant en outre une étape de stockage consistant à stocker les informations d'authentification générées par l'étape de génération dans une unité de stockage (223a), dans lequel
dans l'étape de détection, il est déterminé si des informations d'authentification utilisées en accès au contenu coïncident avec les informations d'authentification stockées dans l'unité de stockage (223a), et si elles coïncident, l'accès est détecté comme accès non autorisé.
 
7. Procédé de détection d'accès non autorisé selon la revendication 5 ou 6, incluant en outre une étape de suppression consistant à détecter le programme identifié par l'étape d'identification, et supprimer le programme si le programme est détecté.
 
8. Procédé de détection d'accès non autorisé selon la revendication 5 ou 6, incluant en outre une étape de collecte consistant à collecter le même programme que le programme identifié par l'étape d'identification depuis un espace Web.
 




Drawing




























































REFERENCES CITED IN THE DESCRIPTION



This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.

Patent documents cited in the description




Non-patent literature cited in the description