Interface AnalysisResult.Builder
- All Superinterfaces:
Buildable
,CopyableBuilder<AnalysisResult.Builder,
,AnalysisResult> SdkBuilder<AnalysisResult.Builder,
,AnalysisResult> SdkPojo
- Enclosing class:
AnalysisResult
-
Method Summary
Modifier and TypeMethodDescriptionanalysisDetail
(String analysisDetail) Provides analysis details for the identified rule.identifiedRuleIds
(String... identifiedRuleIds) The priority number of the stateless rules identified in the analysis.identifiedRuleIds
(Collection<String> identifiedRuleIds) The priority number of the stateless rules identified in the analysis.identifiedType
(String identifiedType) The types of rule configurations that Network Firewall analyzes your rule groups for.identifiedType
(IdentifiedType identifiedType) The types of rule configurations that Network Firewall analyzes your rule groups for.Methods inherited from interface software.amazon.awssdk.utils.builder.CopyableBuilder
copy
Methods inherited from interface software.amazon.awssdk.utils.builder.SdkBuilder
applyMutation, build
Methods inherited from interface software.amazon.awssdk.core.SdkPojo
equalsBySdkFields, sdkFields
-
Method Details
-
identifiedRuleIds
The priority number of the stateless rules identified in the analysis.
- Parameters:
identifiedRuleIds
- The priority number of the stateless rules identified in the analysis.- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
identifiedRuleIds
The priority number of the stateless rules identified in the analysis.
- Parameters:
identifiedRuleIds
- The priority number of the stateless rules identified in the analysis.- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
identifiedType
The types of rule configurations that Network Firewall analyzes your rule groups for. Network Firewall analyzes stateless rule groups for the following types of rule configurations:
-
STATELESS_RULE_FORWARDING_ASYMMETRICALLY
Cause: One or more stateless rules with the action
pass
orforward
are forwarding traffic asymmetrically. Specifically, the rule's set of source IP addresses or their associated port numbers, don't match the set of destination IP addresses or their associated port numbers.To mitigate: Make sure that there's an existing return path. For example, if the rule allows traffic from source 10.1.0.0/24 to destination 20.1.0.0/24, you should allow return traffic from source 20.1.0.0/24 to destination 10.1.0.0/24.
-
STATELESS_RULE_CONTAINS_TCP_FLAGS
Cause: At least one stateless rule with the action
pass
orforward
contains TCP flags that are inconsistent in the forward and return directions.To mitigate: Prevent asymmetric routing issues caused by TCP flags by following these actions:
-
Remove unnecessary TCP flag inspections from the rules.
-
If you need to inspect TCP flags, check that the rules correctly account for changes in TCP flags throughout the TCP connection cycle, for example
SYN
andACK
flags used in a 3-way TCP handshake.
-
- Parameters:
identifiedType
- The types of rule configurations that Network Firewall analyzes your rule groups for. Network Firewall analyzes stateless rule groups for the following types of rule configurations:-
STATELESS_RULE_FORWARDING_ASYMMETRICALLY
Cause: One or more stateless rules with the action
pass
orforward
are forwarding traffic asymmetrically. Specifically, the rule's set of source IP addresses or their associated port numbers, don't match the set of destination IP addresses or their associated port numbers.To mitigate: Make sure that there's an existing return path. For example, if the rule allows traffic from source 10.1.0.0/24 to destination 20.1.0.0/24, you should allow return traffic from source 20.1.0.0/24 to destination 10.1.0.0/24.
-
STATELESS_RULE_CONTAINS_TCP_FLAGS
Cause: At least one stateless rule with the action
pass
orforward
contains TCP flags that are inconsistent in the forward and return directions.To mitigate: Prevent asymmetric routing issues caused by TCP flags by following these actions:
-
Remove unnecessary TCP flag inspections from the rules.
-
If you need to inspect TCP flags, check that the rules correctly account for changes in TCP flags throughout the TCP connection cycle, for example
SYN
andACK
flags used in a 3-way TCP handshake.
-
-
- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
-
-
identifiedType
The types of rule configurations that Network Firewall analyzes your rule groups for. Network Firewall analyzes stateless rule groups for the following types of rule configurations:
-
STATELESS_RULE_FORWARDING_ASYMMETRICALLY
Cause: One or more stateless rules with the action
pass
orforward
are forwarding traffic asymmetrically. Specifically, the rule's set of source IP addresses or their associated port numbers, don't match the set of destination IP addresses or their associated port numbers.To mitigate: Make sure that there's an existing return path. For example, if the rule allows traffic from source 10.1.0.0/24 to destination 20.1.0.0/24, you should allow return traffic from source 20.1.0.0/24 to destination 10.1.0.0/24.
-
STATELESS_RULE_CONTAINS_TCP_FLAGS
Cause: At least one stateless rule with the action
pass
orforward
contains TCP flags that are inconsistent in the forward and return directions.To mitigate: Prevent asymmetric routing issues caused by TCP flags by following these actions:
-
Remove unnecessary TCP flag inspections from the rules.
-
If you need to inspect TCP flags, check that the rules correctly account for changes in TCP flags throughout the TCP connection cycle, for example
SYN
andACK
flags used in a 3-way TCP handshake.
-
- Parameters:
identifiedType
- The types of rule configurations that Network Firewall analyzes your rule groups for. Network Firewall analyzes stateless rule groups for the following types of rule configurations:-
STATELESS_RULE_FORWARDING_ASYMMETRICALLY
Cause: One or more stateless rules with the action
pass
orforward
are forwarding traffic asymmetrically. Specifically, the rule's set of source IP addresses or their associated port numbers, don't match the set of destination IP addresses or their associated port numbers.To mitigate: Make sure that there's an existing return path. For example, if the rule allows traffic from source 10.1.0.0/24 to destination 20.1.0.0/24, you should allow return traffic from source 20.1.0.0/24 to destination 10.1.0.0/24.
-
STATELESS_RULE_CONTAINS_TCP_FLAGS
Cause: At least one stateless rule with the action
pass
orforward
contains TCP flags that are inconsistent in the forward and return directions.To mitigate: Prevent asymmetric routing issues caused by TCP flags by following these actions:
-
Remove unnecessary TCP flag inspections from the rules.
-
If you need to inspect TCP flags, check that the rules correctly account for changes in TCP flags throughout the TCP connection cycle, for example
SYN
andACK
flags used in a 3-way TCP handshake.
-
-
- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
-
-
analysisDetail
Provides analysis details for the identified rule.
- Parameters:
analysisDetail
- Provides analysis details for the identified rule.- Returns:
- Returns a reference to this object so that method calls can be chained together.
-