Source: https://patents.google.com/patent/JP2007004685A/en
Timestamp: 2020-02-17 18:24:27
Document Index: 458358193

Matched Legal Cases: ['art 502', 'art 503', 'art 502', 'art 503', 'art 502', 'art, 402', 'art, 403', 'art, 404']

JP2007004685A - Communication information monitoring device - Google Patents
Communication information monitoring device Download PDF
JP2007004685A
JP2007004685A JP2005186694A JP2005186694A JP2007004685A JP 2007004685 A JP2007004685 A JP 2007004685A JP 2005186694 A JP2005186694 A JP 2005186694A JP 2005186694 A JP2005186694 A JP 2005186694A JP 2007004685 A JP2007004685 A JP 2007004685A
JP2005186694A
弘二郎 中山
2005-06-27 Application filed by Hitachi Ltd, 株式会社日立製作所 filed Critical Hitachi Ltd
2005-06-27 Priority to JP2005186694A priority Critical patent/JP2007004685A/en
2007-01-11 Publication of JP2007004685A publication Critical patent/JP2007004685A/en
<P>PROBLEM TO BE SOLVED: To generate a check rule for ensuring the security of a system. <P>SOLUTION: This communication information monitoring device 201 comprises a pseudo client 501, a monitoring part 502, and an integrating part 503. The pseudo client 501 transmits a request message including a trace value as a parameter to a web application and also analyzes a response message returned from the web application. The monitoring part 502 monitors whether the pseudo client 501 uses the transmitted trace value at various places in the system. The integrating part 503 generates a check rule on the basis of processing results of the pseudo client 501 and the monitoring part 502 and a preregistered check policy 510. Parameter usage and correspondence of check processing are registered in the check policy 510. <P>COPYRIGHT: (C)2007,JPO&INPIT
The present invention relates to a communication information monitoring apparatus suitable for use in, for example, information security, and more particularly to a technique for protecting a system from various attacks via a network in a system that provides a service via the network. .
With the development of network technologies such as the Internet and Intranet, many systems currently provide services to clients via the network. As a system for providing a service via such a network, for example, there is a web application.
[Overview of Web Application]
When using a web application, the client sends a request message to the web application. In response, the web application returns a response message. The request message and the response message are transmitted / received using HTTP (HyperText Transfer Protocol). The response message includes a web page described using HTML (HyperText Markup Language).
[Web application parameters]
Various parameters may be included in a request message sent by a client. These parameters are included in, for example, a POST payload, a URL query, a cookie, or the like. These parameters are used for various processes in the web application. For example, it is used as a part of an SQL (Structured Query Language) sentence for accessing a database, or included in a web page transmitted to a client.
[Attack using parameters]
As described above, since the parameter transmitted from the client affects the operation of the web application, the web application may perform an unexpected operation if an invalid command or script is described in the parameter. Therefore, the parameters included in the request message are often used for attacks on web applications. As a technique for attacking a web application using parameters, there are, for example, a cross-site scripting (hereinafter referred to as XSS) attack and SQL injection.
[XSS attack]
When the web application includes the received parameter as it is in the response web page, there is a possibility that a vulnerability to an XSS attack exists. If the XSS attack is successful, an invalid script described in the parameter is included in the web page returned by the web application and executed on the client. This can cause serious problems such as eavesdropping and tampering with cookies.
If the web application uses the received parameters as part of an SQL statement to access the database, there may be a vulnerability to SQL injection. If the SQL injection is successful, an SQL sentence having an unexpected meaning is issued by the character string described in the parameter. This can cause serious problems such as spoofing and leakage of important data.
[Conventional countermeasures (Web application firewall)]
In order to prevent an attack to a web application using these parameters, it is effective to check whether an illegal character string is included in the parameters transmitted from the client. A system for checking parameters included in a request message is called, for example, a web application firewall (hereinafter referred to as WAF) and has already been put into practical use.
In the following, an example of parameter check will be described with reference to FIG. In the example of FIG. 13, parameter check is executed by the security filter 103. The client 101 and the security filter 103 are connected via the network 102. The security filter 103 and the web application 104 may be connected via a network or may operate on the same computer.
The client 101 transmits a request message to the web application 104. The security filter 103 blocks the request message transmitted from the client and checks the parameters. The check is executed based on a preset check rule 105.
There are several ways to check parameters. For example, a character string that may cause a security problem may be set in advance in the check rule 105 as a prohibited character string. In this case, the security filter 103 blocks the request from the client and checks whether the prohibited character string is included in the parameter.
That is, if the prohibited character string is not included, the request is transferred to the web application 104 as it is. If the prohibited character string is included, the request is rejected and an error is returned to the client 101. By performing such parameter checking, the system can be protected from attacks on web applications.
Here, in order for the security filter 103 to function effectively, it is necessary to set an appropriate check rule 105, but setting the check rule 105 is often a cumbersome task. That is, in order to specify the prohibited character string, detailed knowledge of each attack method is required. Therefore, advanced security knowledge is required for setting check rules.
Further, the character string used for the XSS attack is different from the character string used for the SQL injection. For this reason, check parameters for XSS attacks are set for parameters that may be used for XSS attacks, and check rules for SQL injection are set for parameters that may be used for SQL injection. It is necessary to keep.
Therefore, detailed knowledge of the web application is required to set appropriate check rules to protect the system from attacks on the web application. Thus, the setting of the check rule is an advanced task that requires both security knowledge and web application knowledge.
Therefore, as a technique related to the setting of such a check rule, a technique for limiting a range of values that can be taken by a parameter by analyzing a response message is known (for example, see Patent Document 1).
In addition, as a technique for detecting the vulnerability of the XSS attack, a technique for identifying whether the web application has a vulnerability to the XSS attack by inserting a trace value into the request message and analyzing the response message obtained as a result. (For example, refer to Patent Document 2).
That is, a technique for setting a check rule and a technique for identifying whether or not there is vulnerability to an XSS attack are known from Patent Document 1 and Patent Document 2.
Japanese translation of PCT publication No. 2003-504723 JP 2004-164617 A
However, with the technique described in Patent Document 1, it is difficult to limit the values of parameters with a high degree of freedom of description, and there is a possibility that sufficient checking cannot be performed. Further, since the technique described in Patent Document 2 only analyzes response messages, it is not possible to detect attacks such as SQL injection that execute illegal commands inside a web application.
The present invention was created to solve the above problems, and the object of the present invention is to easily create an appropriate check rule without knowledge of security or detailed knowledge of web applications. There is to be able to do it.
In order to achieve the above object, the communication information monitoring apparatus of the present invention includes a pseudo client, a monitoring unit, and an integration unit.
That is, according to the present invention, parameters are tracked by the pseudo client and the monitoring unit, and a location where the parameters are used is specified. The pseudo client transmits a request message in which a trace value is set as a parameter value to a system that provides services to the client via the network. The monitoring unit monitors whether the trace value is used in each part of the system. Thereby, the location where the parameter in the request message is used can be specified.
Further, the integration unit generates an appropriate check rule based on the tracking results of the pseudo client and the monitoring unit and a preset check policy. In the check policy, appropriate check rules are set for the usage points of various parameters. Therefore, it is possible to easily generate an appropriate check rule by associating with the tracking result in which the parameter usage location is described.
By applying the present invention described above, even those who do not have advanced security knowledge or who do not know detailed information of the system can easily create check rules. Further, by applying the present invention, it is possible to expect reduction in man-hours for system construction and reduction in setting mistakes.
In the following description, an embodiment of a web application will be described as an example of a system that provides services to clients. However, the scope of the present invention is not limited to a web application. In the following example, parameters are checked by a security filter existing outside the web application. However, the present invention can also be applied to a case where a parameter check is performed inside a web application.
FIG. 1 is a diagram illustrating a configuration of the entire system according to the present embodiment. The web application 104 provides a service to a client (not shown). The security filter 103 checks parameters included in the request message in order to prevent an attack on the web application 104. The parameter check is executed according to the check rule 105. The check rule 105 is generated by the communication information monitoring device 104 as will be described in detail below.
The web application 104, the security filter 103, and the communication information monitoring apparatus 201 can be realized by using a general computer 301 as shown in FIG. The computer 301 includes a CPU 305, a memory 306, a storage device 307 such as a hard disk, an input device 303 such as a keyboard and a mouse, an output device 304 such as a display, and a communication device 302 for connecting to a network.
The computer 301 is connected to the network 102 such as the Internet via the communication device 105. In the computer 301, each function is realized by the CPU 305 executing a predetermined program called on the memory 306. The web application 104, the security filter 103, and the communication information monitoring apparatus 201 may be executed on different computers, or may be executed on one computer.
[Internal structure of web application]
FIG. 3 shows an example of the internal configuration of the web application 104. When the web application 104 receives a request message from the client, the web application 104 performs various business processes according to the request message, and returns a response message to the client. The request message transmitted from the client is received by the HTTP processing unit 401.
The processing performed by the business processing unit 403 is greatly different for each web application. For example, a web application for online shopping performs processing such as product search and product purchase. The business database 404 stores various data necessary for executing business processing. For example, product data and the like are stored in the business database 404. The business processing unit 403 generates an SQL statement for accessing the business database 404 using parameters included in the request message.
The database access unit 402 accesses the business database 404 based on the SQL statement generated by the business processing unit 403 and performs processing such as data search and update. Further, the business processing unit 403 generates a web page to be returned to the client by using a result of accessing the business database 404, a parameter included in the request message, or the like. The generated web page is returned to the client by the HTTP processing unit 401.
[Internal configuration of communication information monitoring device]
FIG. 4 shows an example of the internal configuration of the communication information monitoring apparatus 201. The communication information monitoring apparatus includes a pseudo client 501, a monitoring unit 502, and an integration unit 503.
[Description of pseudo client]
As described in detail below, the pseudo client 501 transmits a request message including a trace value as a parameter to the web application. The response message returned from the web application is analyzed. The pseudo client 501 includes a screen input / output processing unit 504, a request generation unit 505, a response analysis unit 507, and an HTTP processing unit 506. The HTTP processing unit 506 transmits a request message and receives a response message.
The response analysis unit 507 analyzes the response message returned from the web application, and generates a parameter list described below. The screen input / output processing unit 504 displays the analysis result by the response analysis unit 507 on the screen or accepts user input. The request generation unit generates a request message including a trace value as a parameter.
[Description of monitoring unit]
The monitoring unit 502 monitors whether or not the trace value transmitted by the pseudo client 501 is used at various points in the system. In this embodiment, monitoring of an SQL sentence and monitoring of a response message will be described as examples of monitoring processing. You may monitor in this other location as needed.
The SQL statement monitoring unit 508 monitors the SQL statement used when accessing the business database 404. SQL statement monitoring can be realized by, for example, linking with the database access unit 402 or monitoring communication between the database access unit 402 and the business database 404. In addition, monitoring of the SQL sentence may be realized by other methods.
The response monitoring unit 509 monitors response data returned from the web application 104. The response message can be monitored by, for example, cooperating with the HTTP processing unit 506 of the pseudo client 501 or by monitoring communication between the web application 104 and the pseudo client 501. In addition, monitoring of response data may be realized by other methods.
[Explanation of integration unit]
The integration unit 503 generates the check rule 105 based on the processing results of the pseudo client 501 and the monitoring unit 502 and the check policy 510 registered in advance. In the check policy 510, correspondence between parameter usage and check processing is registered.
Hereinafter, the details of the check rule generation process will be described with reference to the flowchart shown in FIG. The check rule generation process is executed when the user inputs an instruction to the communication information monitoring apparatus 201 using, for example, a GUI (Graphical User Interface).
When an instruction is input, first, in step S601, the user inputs the URL of the web application to the pseudo client 501. Next, in step S602, the pseudo client 501 transmits a request message to the web application 104 and receives a response message in the same manner as a normal browser. Here, FIG. 6 shows an example of a response message returned from the web application, and a specific example will be described.
This response message shown in FIG. 6 is described using HTML. In addition, although the line number is attached to the head of each line of FIG. 6 for description, the actual response message does not include the line number.
In the message shown in FIG. 6, the 01st to 21st lines are surrounded by html tags. This indicates that the content enclosed by the html tag is data described in HTML. Also, lines 02 to 20 are surrounded by body tags. This indicates that the content enclosed by the body tag is the text of the HTLM. In line 04, the character string “product purchase system” is surrounded by h2 tags. This indicates that the characters “product purchase system” are headings.
Further, the 06th to 18th lines are surrounded by form tags. This indicates that the content enclosed by the form tag is one form. The action attribute (line 06) of this form tag represents the URL of the transmission destination of the input content. A method attribute (line 07) of the form tag represents an HTTP method used when transmitting input contents.
Further, the 09th to 12th lines are surrounded by a select tag. This indicates that the content enclosed by the select tag is one select box. The select box is one of the parts under the form, and the value selected here is transmitted to the web application as one of the parameters. When transmitting a parameter, the name attribute (line 09) of the select tag is used as the name of the parameter.
The option tags on the 10th and 11th lines represent selection box selection candidates, respectively. In this case, when the content enclosed by the option tag is selected, the value of the value attribute of the option tag is transmitted as a parameter value to the web application.
For example, when “TV” is selected, a parameter having a name “item” and a value “tv” is transmitted to the web application. When “video” is selected, a parameter having a name “item” and a value “video” is transmitted to the web application. Note that the select tag in the 10th row has a selected attribute. This indicates that the option tag on the 10th line is selected next best.
Further, <br> on the 13th and 16th lines represents a line feed. The input tags on the 15th and 17th lines each represent one of the components of the input form.
Here, an input tag having text as a type attribute as in the 15th line represents a text input field. The name attribute of the input tag is used as the name of the parameter when transmitting the parameter. In the 15th line, since the name attribute name is “bikou”, the value input in this text input field is transmitted to the web application as the value of the parameter whose name is “bikou”.
An input tag having submit as a type attribute as shown in the 17th line represents an execution button. When this execution button is pressed here, the contents of the input form are transmitted as parameters to the web application. In this way, a response message is received with respect to the request message transmitted from the pseudo client 501 to the web application 104.
Therefore, in step S602 of FIG. 5, the received response message is analyzed by the response analysis unit 507 and displayed on the screen by the screen input / output processing unit 504. An example of the screen 801 displayed in FIG. 7 is shown. The target screen 802 at the top of the screen displays the response message returned by the web application in the same manner as a normal browser. The parameter list 803 at the bottom of the screen is a list of parameters transmitted from the client in response to the next request, determined from the contents of the HTML.
In each item of the parameter list 803, a check box 807, a URL 808, a name 809, a value 810, a status 811, and a result 812 are displayed. The check box 807 is used when the user specifies a parameter to be tracked, as will be described below. URL 808 is a column indicating a URL to which a parameter is transmitted. In the HTML shown in FIG. 6, a URL (http://example.com/purchase) is described in the action attribute 701 of the form tag.
A name 809 is a column indicating the name of the parameter. In the HTML shown in FIG. 6, the name “item” is described in the name attribute 702 of the select tag, and the name “bikou” is described in the name attribute 703 of the input tag.
A value 810 is a column indicating a parameter value. If an initial value or a preselected value is specified in HTML, it is displayed here. In the HTML shown in FIG. 6, since the value “tv” is preselected for the parameter whose name is “item” (hereinafter referred to as “item” parameter), “tv” is displayed in the value 810. The For a parameter whose name is “bikou” (hereinafter referred to as “bikou” parameter), there is no initial value or pre-selected value, so a blank text box is displayed.
The status 811 is a column for displaying the tracking status of each parameter. However, in step S602, since parameter tracking has not yet been executed, the characters “untracked” are displayed for all parameters. The use location 812 is a column in which the tracking result of each parameter is displayed. In step 602, since parameter tracking has not yet been executed, a slash "-" indicating that results have not yet been obtained for all parameters is displayed.
Therefore, returning to the flowchart of FIG. 5, in step S603, the user designates a parameter to be tracked. Here, the user selects a parameter to be tracked from the parameters displayed in the parameter list 803 and puts a mark in the check box 807. As will be described below, a trace value is set as a parameter value for a parameter marked in the check box 807.
For parameters that are not tracked, that is, parameters that are not marked in the check box 807, an arbitrary character string can be set as a parameter value by editing the value 810 column. Further, when the parameter specification is completed, the user presses a request transmission button 813.
When the request transmission button 813 is pressed in step S604, the request generation unit 505 generates a pseudo request message for tracking parameters. FIG. 8 shows an example of the pseudo request generated. In the example of FIG. 8, only the POST payload including parameters in the request message is described.
The request generation unit sets a trace value as a parameter value for the parameter marked in the check box 807. For example, a random character string can be used as the trace value. When setting trace values for multiple parameters, set different trace values. In the example of FIG. 8, a random character string “H8rJi4” is set as a trace value in the “bikou” parameter.
In step S605, the monitoring unit 502 starts monitoring the trace value. When the pseudo request is transmitted, each monitoring unit in the monitoring unit 502 starts monitoring the system. That is, the SQL sentence management unit 508 monitors the SQL sentence transmitted to the business database, and monitors the request message generated in step 604. If the issued SQL statement includes a trace value, it can be seen that the parameter to be tracked is used in the SQL statement.
Further, the response management unit 509 monitors a response message returned from the web application to the client. If the response message includes a trace value, it can be seen that the parameter to be tracked is used for screen output.
In step S606, the HTTP processing unit 506 of the pseudo client 501 transmits the pseudo request generated by the request generation unit 505 to the web application. In step S607, the web application 104 performs the same processing as when a normal request is received. That is, a pseudo request is received, business processing is executed, and a response is returned to the pseudo client.
In step S608, when a response message is returned from the web application, the pseudo client displays the tracking result to the user.
FIG. 9 shows an example of displaying the tracking result. The basic screen configuration of the screen is the same as in FIG. On the target screen 802, the HTML returned in step S607 is displayed in the same manner as a normal browser. In addition to the parameters displayed in step S602, parameters included in the HTML returned in step 607 are newly added to the parameter list 803. Further, in the example of FIG. 9, a parameter having a name “busho” is newly added. The destination of this parameter is “http://example.com/department”.
Further, the parameter list 803 displays the tracking results monitored by the monitoring unit 502 for the parameters (“item” parameter and “bikou” parameter) displayed in step S602. Here, characters “SQL statement” are output to the use location 812 when the trace value is detected by the SQL statement monitoring unit 508, and “response” is output when the trace value is detected by the response monitoring unit 509. As a result, the user can know in which part of the system each parameter is used.
In step S609, the user selects whether to continue the parameter tracking process or end the tracking process and create a check rule. Here, when the tracking is ended, the user presses the check tool generation button 814 in step S610. When the check tool generation button 814 is pressed, the monitoring unit 502 ends the monitoring in step S611. Thereafter, a check rule is generated by the integration unit 503 in step S612.
In the integration unit, a check policy 510 indicating a check policy is set in advance. For example, information shown in FIG. 10 is set in the check policy. Each row in FIG. 10 represents one check policy. The first column 1101 is a row number given for explanation. The second column 1102 represents the parameter usage location. Examples of parameter usage locations include SQL statements and response messages. The third column 1103 represents prohibited characters. If the parameter value contains the character specified here, the request is rejected and an error is returned to the client.
That is, the first line 1104 in FIG. 10 is a parameter used in the SQL statement. The parameter value includes colon (:), semicolon (;), equal (=), double quote ("), and single quote ('). When either one is used, it represents a check policy of rejecting the request and returning an error to the client.
Here, characters such as colon, semicolon, equal, double quote, and single quote have special meanings in SQL, and if these characters are abused, there is a possibility of being subjected to a SQL injection attack. Therefore, by prohibiting the use of these characters, SQL injection can be prevented.
The second line 1105 in FIG. 10 is a parameter used in the HTML of the response message, and the parameter value is less than parenthesis (<), greater than parenthesis (>), double quote ("), single quote ("). , And (&) represents a check policy of rejecting a request and returning an error.
Here, characters such as less-than brackets, greater-than brackets, double quotes, single quotes, and ANDs are characters used when writing scripts, and if these characters are abused, there is a possibility of being subjected to a cross-site scripting attack There is. Therefore, by prohibiting the use of these characters, cross-site scripting can be prevented.
Further, in the example of FIG. 10, in addition to this, when using a parameter as an OS command, a check policy (third line 1106) for preventing OS command injection, and when using a parameter as an LDAP query, LDAP injection is used. A check policy (line 1107 on the 4th line) and a check policy (line 1106 on the 5th line) for preventing XPath injection when the parameter is used as an XPath query are set.
Therefore, the integration unit 503 generates a check rule 105 based on the parameter tracking result and the check policy 510. That is, when the parameter tracking result is shown in FIG. 11, the generated check rule is as shown in FIG. In this way, if the check policy shown in FIG. 10 and the tracking result shown in FIG. 11 are combined and integrated, the check rule shown in FIG. 12 can be easily generated.
By the method described above, the check rule 103 can be easily generated without detailed knowledge about the web application 104. The security filter 103 can perform an appropriate check process using the check rule 105.
Thus, according to the communication information monitoring apparatus of the present invention, an apparatus used in a system that provides services to clients via a network, a pseudo client that transmits a request including a trace value, and a portion of the system It has a monitoring unit that monitors the trace value, and by identifying the location where the parameter is used by monitoring the trace value at each location in the system, without knowledge of security or detailed knowledge of the web application, Appropriate check rules can be easily created.
The present invention is not limited to the embodiment described above, and it goes without saying that the present invention includes more embodiments without departing from the gist of the present invention described in the claims.
1 is a configuration diagram of a system according to an embodiment of the present invention. It is a hardware block diagram of the computer which implements this invention. It is an internal block diagram of the web application for the description. It is an internal block diagram of the communication information monitoring apparatus to which this invention is applied. It is a flowchart of the check rule production | generation process to which this invention is applied. It is a diagram which shows the example of the response message for the description. It is a diagram which shows the example of the output screen which the pseudo client for the description produces | generates. It is a diagram which shows the example of the request message which the pseudo client for the description produces | generates. It is a diagram which shows the example of the tracking result which the pseudo | simulation client for the description produces | generates. It is a diagram which shows the example of the check policy for the description. It is a diagram which shows the example of the parameter tracking result for the description. It is a diagram which shows the example of the check rule produced | generated by the check tool production | generation apparatus for the description. It is a block diagram of the system which performs a parameter check.
DESCRIPTION OF SYMBOLS 101 ... Client, 103 ... Security filter, 104 ... Web application, 105 ... Check rule, 201 ... Communication information monitoring apparatus, 401 ... HTTP processing part, 402 ... Database access part, 403 ... Business processing part, 404 ... Business database, 501 ... Pseudo client, 502 ... Monitoring unit, 503 ... Integration unit, 504 ... Screen input / output processing unit, 505 ... Request generation unit, 506 ... HTTP processing unit, 507 ... Response analysis unit, 508 ... SQL statement monitoring unit, 509 ... Response Monitoring unit, 510 ... check policy
A communication information monitoring device used in a system that provides services to clients via a network,
A pseudo client that sends a request with a trace value;
A monitoring unit for monitoring the trace value at each location of the system,
A communication information monitoring apparatus characterized by identifying a parameter use location by monitoring a trace value at each location of the system.
The communication information monitoring apparatus according to claim 1,
The use location of the parameter is specified as follows:
A communication information monitoring device characterized by identifying the location where a parameter of a web application is used.
In the communication information monitoring apparatus according to claim 2, the monitoring unit that monitors the trace value includes:
An SQL monitoring unit for monitoring an SQL statement for accessing the database;
A communication information monitoring apparatus, comprising: a response monitoring unit that monitors a response message for replying to the web application.
In the communication information monitoring apparatus according to any one of claims 1 to 3,
An integration unit that integrates a result of specifying the parameter usage location and a preset security policy;
A communication information monitoring apparatus characterized by generating a check rule in communication information monitoring.
JP2005186694A 2005-06-27 2005-06-27 Communication information monitoring device Pending JP2007004685A (en)
JP2005186694A JP2007004685A (en) 2005-06-27 2005-06-27 Communication information monitoring device
US11/274,411 US20070011742A1 (en) 2005-06-27 2005-11-16 Communication information monitoring apparatus
JP2007004685A true JP2007004685A (en) 2007-01-11
ID=37619738
JP2005186694A Pending JP2007004685A (en) 2005-06-27 2005-06-27 Communication information monitoring device
US (1) US20070011742A1 (en)
JP (1) JP2007004685A (en)
JP2010250791A (en) * 2009-04-17 2010-11-04 Piolink Inc Web security management device and method for monitoring communication between web server and client
JP2012533806A (en) * 2009-07-23 2012-12-27 エヌエスフォーカス インフォメーション テクノロジー カンパニー，リミテッド XSS detection method and apparatus
JP2013520719A (en) * 2010-02-19 2013-06-06 パク，ヒジョン Web service real-time vulnerability diagnosis and result information service system
JP2014123298A (en) * 2012-12-21 2014-07-03 Fujitsu Ltd Information management program and information management method
JP2014157483A (en) * 2013-02-15 2014-08-28 Omron Corp Controller and information processing device
JP2015510618A (en) * 2011-12-16 2015-04-09 北京神州▲緑▼盟信息安全科技股▲分▼有限公司 Network security protection method, apparatus and system
2005-06-27 JP JP2005186694A patent/JP2007004685A/en active Pending
2005-11-16 US US11/274,411 patent/US20070011742A1/en not_active Abandoned
US20070011742A1 (en) 2007-01-11
JP2008502046A (en) 2008-01-24 Apparatus and method for developing, testing and monitoring secure software
US20200028864A1 (en) 2020-01-23 Non-harmful insertion of data mimicking computer network attacks