/**
* Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
* SPDX-License-Identifier: Apache-2.0.
*/
#pragma once
#include A rule statement that inspects for malicious SQL code. Attackers insert
* malicious SQL code into web requests to do things like modify your database or
* extract data from it. See Also:
AWS
* API Reference
The part of the web request that you want WAF to inspect.
*/ inline const FieldToMatch& GetFieldToMatch() const{ return m_fieldToMatch; } /** *The part of the web request that you want WAF to inspect.
*/ inline bool FieldToMatchHasBeenSet() const { return m_fieldToMatchHasBeenSet; } /** *The part of the web request that you want WAF to inspect.
*/ inline void SetFieldToMatch(const FieldToMatch& value) { m_fieldToMatchHasBeenSet = true; m_fieldToMatch = value; } /** *The part of the web request that you want WAF to inspect.
*/ inline void SetFieldToMatch(FieldToMatch&& value) { m_fieldToMatchHasBeenSet = true; m_fieldToMatch = std::move(value); } /** *The part of the web request that you want WAF to inspect.
*/ inline SqliMatchStatement& WithFieldToMatch(const FieldToMatch& value) { SetFieldToMatch(value); return *this;} /** *The part of the web request that you want WAF to inspect.
*/ inline SqliMatchStatement& WithFieldToMatch(FieldToMatch&& value) { SetFieldToMatch(std::move(value)); return *this;} /** *Text transformations eliminate some of the unusual formatting that attackers
* use in web requests in an effort to bypass detection. Text transformations are
* used in rule match statements, to transform the FieldToMatch
* request component before inspecting it, and they're used in rate-based rule
* statements, to transform request components before using them as custom
* aggregation keys. If you specify one or more transformations to apply, WAF
* performs all transformations on the specified content, starting from the lowest
* priority setting, and then uses the component contents.
Text transformations eliminate some of the unusual formatting that attackers
* use in web requests in an effort to bypass detection. Text transformations are
* used in rule match statements, to transform the FieldToMatch
* request component before inspecting it, and they're used in rate-based rule
* statements, to transform request components before using them as custom
* aggregation keys. If you specify one or more transformations to apply, WAF
* performs all transformations on the specified content, starting from the lowest
* priority setting, and then uses the component contents.
Text transformations eliminate some of the unusual formatting that attackers
* use in web requests in an effort to bypass detection. Text transformations are
* used in rule match statements, to transform the FieldToMatch
* request component before inspecting it, and they're used in rate-based rule
* statements, to transform request components before using them as custom
* aggregation keys. If you specify one or more transformations to apply, WAF
* performs all transformations on the specified content, starting from the lowest
* priority setting, and then uses the component contents.
Text transformations eliminate some of the unusual formatting that attackers
* use in web requests in an effort to bypass detection. Text transformations are
* used in rule match statements, to transform the FieldToMatch
* request component before inspecting it, and they're used in rate-based rule
* statements, to transform request components before using them as custom
* aggregation keys. If you specify one or more transformations to apply, WAF
* performs all transformations on the specified content, starting from the lowest
* priority setting, and then uses the component contents.
Text transformations eliminate some of the unusual formatting that attackers
* use in web requests in an effort to bypass detection. Text transformations are
* used in rule match statements, to transform the FieldToMatch
* request component before inspecting it, and they're used in rate-based rule
* statements, to transform request components before using them as custom
* aggregation keys. If you specify one or more transformations to apply, WAF
* performs all transformations on the specified content, starting from the lowest
* priority setting, and then uses the component contents.
Text transformations eliminate some of the unusual formatting that attackers
* use in web requests in an effort to bypass detection. Text transformations are
* used in rule match statements, to transform the FieldToMatch
* request component before inspecting it, and they're used in rate-based rule
* statements, to transform request components before using them as custom
* aggregation keys. If you specify one or more transformations to apply, WAF
* performs all transformations on the specified content, starting from the lowest
* priority setting, and then uses the component contents.
Text transformations eliminate some of the unusual formatting that attackers
* use in web requests in an effort to bypass detection. Text transformations are
* used in rule match statements, to transform the FieldToMatch
* request component before inspecting it, and they're used in rate-based rule
* statements, to transform request components before using them as custom
* aggregation keys. If you specify one or more transformations to apply, WAF
* performs all transformations on the specified content, starting from the lowest
* priority setting, and then uses the component contents.
Text transformations eliminate some of the unusual formatting that attackers
* use in web requests in an effort to bypass detection. Text transformations are
* used in rule match statements, to transform the FieldToMatch
* request component before inspecting it, and they're used in rate-based rule
* statements, to transform request components before using them as custom
* aggregation keys. If you specify one or more transformations to apply, WAF
* performs all transformations on the specified content, starting from the lowest
* priority setting, and then uses the component contents.
The sensitivity that you want WAF to use to inspect for SQL injection * attacks.
HIGH
detects more attacks, but might generate
* more false positives, especially if your web requests frequently contain unusual
* strings. For information about identifying and mitigating false positives, see
* Testing
* and tuning in the WAF Developer Guide.
LOW
is
* generally a better choice for resources that already have other protections
* against SQL injection attacks or that have a low tolerance for false positives.
*
Default: LOW
The sensitivity that you want WAF to use to inspect for SQL injection * attacks.
HIGH
detects more attacks, but might generate
* more false positives, especially if your web requests frequently contain unusual
* strings. For information about identifying and mitigating false positives, see
* Testing
* and tuning in the WAF Developer Guide.
LOW
is
* generally a better choice for resources that already have other protections
* against SQL injection attacks or that have a low tolerance for false positives.
*
Default: LOW
The sensitivity that you want WAF to use to inspect for SQL injection * attacks.
HIGH
detects more attacks, but might generate
* more false positives, especially if your web requests frequently contain unusual
* strings. For information about identifying and mitigating false positives, see
* Testing
* and tuning in the WAF Developer Guide.
LOW
is
* generally a better choice for resources that already have other protections
* against SQL injection attacks or that have a low tolerance for false positives.
*
Default: LOW
The sensitivity that you want WAF to use to inspect for SQL injection * attacks.
HIGH
detects more attacks, but might generate
* more false positives, especially if your web requests frequently contain unusual
* strings. For information about identifying and mitigating false positives, see
* Testing
* and tuning in the WAF Developer Guide.
LOW
is
* generally a better choice for resources that already have other protections
* against SQL injection attacks or that have a low tolerance for false positives.
*
Default: LOW
The sensitivity that you want WAF to use to inspect for SQL injection * attacks.
HIGH
detects more attacks, but might generate
* more false positives, especially if your web requests frequently contain unusual
* strings. For information about identifying and mitigating false positives, see
* Testing
* and tuning in the WAF Developer Guide.
LOW
is
* generally a better choice for resources that already have other protections
* against SQL injection attacks or that have a low tolerance for false positives.
*
Default: LOW
The sensitivity that you want WAF to use to inspect for SQL injection * attacks.
HIGH
detects more attacks, but might generate
* more false positives, especially if your web requests frequently contain unusual
* strings. For information about identifying and mitigating false positives, see
* Testing
* and tuning in the WAF Developer Guide.
LOW
is
* generally a better choice for resources that already have other protections
* against SQL injection attacks or that have a low tolerance for false positives.
*
Default: LOW