Systems and methods for improving accuracy in recognizing and neutralizing injection attacks in computer services
A method for handing of injection attacks in requests for computer services is disclosed. The method includes receiving request data that represents a service to be provided by a server computer, parsing a data element from the request data wherein the data element includes a data key and a data value, determining whether the data key is one of one or more predetermined allowed data keys, and upon a condition in which the data key is not one of the predetermined allowed data keys, disabling any injection attacks in the request data before processing the request data by performing the service.
1 . A method for handing of injection attacks in requests for computer services, the method comprising:
receiving request data that represents a service to be provided by a server computer;
parsing a data element from the request data wherein the data element includes a data key and a data value;
determining whether the data key is one of one or more predetermined allowed data keys;
upon a condition in which the data key is not one of the predetermined allowed data keys, disabling any injection attacks in the request data before processing the request data by performing the service;
processing, the one or more requests, each of which specifies a service to be performed by the server computer, wherein processing each request causes the server computer to perform each specified service and generate log data representative of each specified service;
parsing a second data element from the log data wherein the second data element includes a second data key and a second data value;
determining whether the second data key is one of one or more predetermined masked data keys; upon a condition in which the second data key is one of the predetermined masked data keys, replacing the second data value with obscured data within the log data; and
storing the log data resulting from the replacing.
2 . The method of claim 1 , further comprising:
receiving second request data that is distinct from the first-mentioned request data and that represents a second service to be provided by a server computer and that is distinct from the first-mentioned service;
parsing a second data element from the second request data wherein the second data element is distinct from the first-mentioned data element and includes a second data key and a second data value;
determining whether the second data key is one of the predetermined allowed data keys; and
upon a condition in which the second data key is one of the predetermined allowed data keys, processing the second request data by performing the second service without attempting to identify or disable any injection attacks in the second request data.
3 . The method of claim 1 , further comprising:
selecting, from a plurality of key specifications included in protective behavior settings for a query security engine, a key specification having a data path that matches a path associated with the request data, wherein the determining whether the data key is one of the one or more predetermined allowed data keys involves accessing a list of data keys included in the selected key specification.
4 . The method of claim 3 , wherein the plurality of key specifications is formatted in a JavaScript Object Notation (JSON) format.
5 . The method of claim 1 , wherein the request data includes structured data with a plurality of key-value pairs.
6 . A set of one or more non-transitory machine-readable storage media storing instructions which, when executed by one or more processors of a computer system, causes the computer system to perform operations for handling injection attacks in requests for computer services, the operations comprising:
receiving request data that represents a service to be provided by a server computer;
parsing a data element from the request data wherein the data element includes a data key and a data value;
determining whether the data key is one of one or more predetermined allowed data keys;
upon a condition in which the data key is not one of the predetermined allowed data keys, disabling any injection attacks in the request data before processing the request data by performing the service;
processing, the one or more requests, each of which specifies a service to be performed by the server computer, wherein processing each request causes the server computer to perform each specified service and generate log data representative of each specified service;
parsing a second data element from the log data wherein the second data element includes a second data key and a second data value;
determining whether the second data key is one of one or more predetermined masked data keys; upon a condition in which the second data key is one of the predetermined masked data keys, replacing the second data value with obscured data within the log data; and
storing the log data resulting from the replacing.
7 . The set of one or more non-transitory machine-readable storage media of claim 6 , wherein the operations further comprise:
receiving second request data that is distinct from the first-mentioned request data and that represents a second service to be provided by a server computer and that is distinct from the first-mentioned service;
parsing a second data element from the second request data wherein the second data element is distinct from the first-mentioned data element and includes a second data key and a second data value;
determining whether the second data key is one of the predetermined allowed data keys; and
upon a condition in which the second data key is one of the predetermined allowed data keys, processing the second request data by performing the second service without attempting to identify or disable any injection attacks in the second request data.
8 . The set of one or more non-transitory machine-readable storage media of claim 6 , wherein the operations further comprise:
selecting, from a plurality of key specifications included in protective behavior settings for a query security engine, a key specification having a data path that matches a path associated with the request data, wherein the determining whether the data key is one of the one or more predetermined allowed data keys involves accessing a list of data keys included in the selected key specification.
9 . The set of one or more non-transitory machine-readable storage media of claim 8 , wherein the plurality of key specifications is formatted in a JavaScript Object Notation (JSON) format.
10 . The set of one or more non-transitory machine-readable storage media of claim 6 , wherein the request data includes structured data with a plurality of key-value pairs.
11 . The set of one or more non-transitory machine-readable storage media of claim 6 , wherein the operations further comprise:
processing one or more requests, each of which specifies a service to be performed by the server computer, wherein processing each request causes the server computer to perform each specified service and generate log data representative of each specified service;
for each of one or more predetermined patterns:
identifying all matching data in the log data that matches the predetermined pattern;
replacing the matching data with obscured data within the log data; and
storing the log data resulting from the replacing.
12 . The set of one or more non-transitory machine-readable storage media of claim 11 , wherein the predetermined patterns are regular expressions.
13 . The set of one or more non-transitory machine-readable storage media of claim 6 , wherein the determining whether the second data key is one of the one or more predetermined masked data keys involves accessing a list of data keys included in a particular key specification of a plurality of key specifications included in protective behavior settings for a query security engine.