All Downloads are FREE. Search and download functionalities are using the official Maven repository.

com.amazonaws.services.networkfirewall.model.StatefulEngineOptions Maven / Gradle / Ivy

Go to download

The AWS Java SDK for AWS Network Firewall module holds the client classes that are used for communicating with AWS Network Firewall Service

There is a newer version: 1.12.780
Show newest version
/*
 * Copyright 2019-2024 Amazon.com, Inc. or its affiliates. All Rights Reserved.
 * 
 * Licensed under the Apache License, Version 2.0 (the "License"). You may not use this file except in compliance with
 * the License. A copy of the License is located at
 * 
 * http://aws.amazon.com/apache2.0
 * 
 * or in the "license" file accompanying this file. This file is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
 * CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions
 * and limitations under the License.
 */
package com.amazonaws.services.networkfirewall.model;

import java.io.Serializable;
import javax.annotation.Generated;
import com.amazonaws.protocol.StructuredPojo;
import com.amazonaws.protocol.ProtocolMarshaller;

/**
 * 

* Configuration settings for the handling of the stateful rule groups in a firewall policy. *

* * @see AWS API Documentation */ @Generated("com.amazonaws:aws-java-sdk-code-generator") public class StatefulEngineOptions implements Serializable, Cloneable, StructuredPojo { /** *

* Indicates how to manage the order of stateful rule evaluation for the policy. STRICT_ORDER is the * default and recommended option. With STRICT_ORDER, provide your rules in the order that you want * them to be evaluated. You can then choose one or more default actions for packets that don't match any rules. * Choose STRICT_ORDER to have the stateful rules engine determine the evaluation order of your rules. * The default action for this rule order is PASS, followed by DROP, REJECT, * and ALERT actions. Stateful rules are provided to the rule engine as Suricata compatible strings, * and Suricata evaluates them based on your settings. For more information, see Evaluation order for stateful rules in the Network Firewall Developer Guide. *

*/ private String ruleOrder; /** *

* Configures how Network Firewall processes traffic when a network connection breaks midstream. Network connections * can break due to disruptions in external networks or within the firewall itself. *

*
    *
  • *

    * DROP - Network Firewall fails closed and drops all subsequent traffic going to the firewall. This is * the default behavior. *

    *
  • *
  • *

    * CONTINUE - Network Firewall continues to apply rules to the subsequent traffic without context from * traffic before the break. This impacts the behavior of rules that depend on this context. For example, if you * have a stateful rule to drop http traffic, Network Firewall won't match the traffic for this rule * because the service won't have the context from session initialization defining the application layer protocol as * HTTP. However, this behavior is rule dependent—a TCP-layer rule using a flow:stateless rule would * still match, as would the aws:drop_strict default action. *

    *
  • *
  • *

    * REJECT - Network Firewall fails closed and drops all subsequent traffic going to the firewall. * Network Firewall also sends a TCP reject packet back to your client so that the client can immediately establish * a new session. Network Firewall will have context about the new session and will apply rules to the subsequent * traffic. *

    *
  • *
*/ private String streamExceptionPolicy; /** *

* Indicates how to manage the order of stateful rule evaluation for the policy. STRICT_ORDER is the * default and recommended option. With STRICT_ORDER, provide your rules in the order that you want * them to be evaluated. You can then choose one or more default actions for packets that don't match any rules. * Choose STRICT_ORDER to have the stateful rules engine determine the evaluation order of your rules. * The default action for this rule order is PASS, followed by DROP, REJECT, * and ALERT actions. Stateful rules are provided to the rule engine as Suricata compatible strings, * and Suricata evaluates them based on your settings. For more information, see Evaluation order for stateful rules in the Network Firewall Developer Guide. *

* * @param ruleOrder * Indicates how to manage the order of stateful rule evaluation for the policy. STRICT_ORDER is * the default and recommended option. With STRICT_ORDER, provide your rules in the order that * you want them to be evaluated. You can then choose one or more default actions for packets that don't * match any rules. Choose STRICT_ORDER to have the stateful rules engine determine the * evaluation order of your rules. The default action for this rule order is PASS, followed by * DROP, REJECT, and ALERT actions. Stateful rules are provided to the * rule engine as Suricata compatible strings, and Suricata evaluates them based on your settings. For more * information, see Evaluation order for stateful rules in the Network Firewall Developer Guide. * @see RuleOrder */ public void setRuleOrder(String ruleOrder) { this.ruleOrder = ruleOrder; } /** *

* Indicates how to manage the order of stateful rule evaluation for the policy. STRICT_ORDER is the * default and recommended option. With STRICT_ORDER, provide your rules in the order that you want * them to be evaluated. You can then choose one or more default actions for packets that don't match any rules. * Choose STRICT_ORDER to have the stateful rules engine determine the evaluation order of your rules. * The default action for this rule order is PASS, followed by DROP, REJECT, * and ALERT actions. Stateful rules are provided to the rule engine as Suricata compatible strings, * and Suricata evaluates them based on your settings. For more information, see Evaluation order for stateful rules in the Network Firewall Developer Guide. *

* * @return Indicates how to manage the order of stateful rule evaluation for the policy. STRICT_ORDER * is the default and recommended option. With STRICT_ORDER, provide your rules in the order * that you want them to be evaluated. You can then choose one or more default actions for packets that * don't match any rules. Choose STRICT_ORDER to have the stateful rules engine determine the * evaluation order of your rules. The default action for this rule order is PASS, followed by * DROP, REJECT, and ALERT actions. Stateful rules are provided to * the rule engine as Suricata compatible strings, and Suricata evaluates them based on your settings. For * more information, see Evaluation order for stateful rules in the Network Firewall Developer Guide. * @see RuleOrder */ public String getRuleOrder() { return this.ruleOrder; } /** *

* Indicates how to manage the order of stateful rule evaluation for the policy. STRICT_ORDER is the * default and recommended option. With STRICT_ORDER, provide your rules in the order that you want * them to be evaluated. You can then choose one or more default actions for packets that don't match any rules. * Choose STRICT_ORDER to have the stateful rules engine determine the evaluation order of your rules. * The default action for this rule order is PASS, followed by DROP, REJECT, * and ALERT actions. Stateful rules are provided to the rule engine as Suricata compatible strings, * and Suricata evaluates them based on your settings. For more information, see Evaluation order for stateful rules in the Network Firewall Developer Guide. *

* * @param ruleOrder * Indicates how to manage the order of stateful rule evaluation for the policy. STRICT_ORDER is * the default and recommended option. With STRICT_ORDER, provide your rules in the order that * you want them to be evaluated. You can then choose one or more default actions for packets that don't * match any rules. Choose STRICT_ORDER to have the stateful rules engine determine the * evaluation order of your rules. The default action for this rule order is PASS, followed by * DROP, REJECT, and ALERT actions. Stateful rules are provided to the * rule engine as Suricata compatible strings, and Suricata evaluates them based on your settings. For more * information, see Evaluation order for stateful rules in the Network Firewall Developer Guide. * @return Returns a reference to this object so that method calls can be chained together. * @see RuleOrder */ public StatefulEngineOptions withRuleOrder(String ruleOrder) { setRuleOrder(ruleOrder); return this; } /** *

* Indicates how to manage the order of stateful rule evaluation for the policy. STRICT_ORDER is the * default and recommended option. With STRICT_ORDER, provide your rules in the order that you want * them to be evaluated. You can then choose one or more default actions for packets that don't match any rules. * Choose STRICT_ORDER to have the stateful rules engine determine the evaluation order of your rules. * The default action for this rule order is PASS, followed by DROP, REJECT, * and ALERT actions. Stateful rules are provided to the rule engine as Suricata compatible strings, * and Suricata evaluates them based on your settings. For more information, see Evaluation order for stateful rules in the Network Firewall Developer Guide. *

* * @param ruleOrder * Indicates how to manage the order of stateful rule evaluation for the policy. STRICT_ORDER is * the default and recommended option. With STRICT_ORDER, provide your rules in the order that * you want them to be evaluated. You can then choose one or more default actions for packets that don't * match any rules. Choose STRICT_ORDER to have the stateful rules engine determine the * evaluation order of your rules. The default action for this rule order is PASS, followed by * DROP, REJECT, and ALERT actions. Stateful rules are provided to the * rule engine as Suricata compatible strings, and Suricata evaluates them based on your settings. For more * information, see Evaluation order for stateful rules in the Network Firewall Developer Guide. * @return Returns a reference to this object so that method calls can be chained together. * @see RuleOrder */ public StatefulEngineOptions withRuleOrder(RuleOrder ruleOrder) { this.ruleOrder = ruleOrder.toString(); return this; } /** *

* Configures how Network Firewall processes traffic when a network connection breaks midstream. Network connections * can break due to disruptions in external networks or within the firewall itself. *

*
    *
  • *

    * DROP - Network Firewall fails closed and drops all subsequent traffic going to the firewall. This is * the default behavior. *

    *
  • *
  • *

    * CONTINUE - Network Firewall continues to apply rules to the subsequent traffic without context from * traffic before the break. This impacts the behavior of rules that depend on this context. For example, if you * have a stateful rule to drop http traffic, Network Firewall won't match the traffic for this rule * because the service won't have the context from session initialization defining the application layer protocol as * HTTP. However, this behavior is rule dependent—a TCP-layer rule using a flow:stateless rule would * still match, as would the aws:drop_strict default action. *

    *
  • *
  • *

    * REJECT - Network Firewall fails closed and drops all subsequent traffic going to the firewall. * Network Firewall also sends a TCP reject packet back to your client so that the client can immediately establish * a new session. Network Firewall will have context about the new session and will apply rules to the subsequent * traffic. *

    *
  • *
* * @param streamExceptionPolicy * Configures how Network Firewall processes traffic when a network connection breaks midstream. Network * connections can break due to disruptions in external networks or within the firewall itself.

*
    *
  • *

    * DROP - Network Firewall fails closed and drops all subsequent traffic going to the firewall. * This is the default behavior. *

    *
  • *
  • *

    * CONTINUE - Network Firewall continues to apply rules to the subsequent traffic without * context from traffic before the break. This impacts the behavior of rules that depend on this context. For * example, if you have a stateful rule to drop http traffic, Network Firewall won't match the * traffic for this rule because the service won't have the context from session initialization defining the * application layer protocol as HTTP. However, this behavior is rule dependent—a TCP-layer rule using a * flow:stateless rule would still match, as would the aws:drop_strict default * action. *

    *
  • *
  • *

    * REJECT - Network Firewall fails closed and drops all subsequent traffic going to the * firewall. Network Firewall also sends a TCP reject packet back to your client so that the client can * immediately establish a new session. Network Firewall will have context about the new session and will * apply rules to the subsequent traffic. *

    *
  • * @see StreamExceptionPolicy */ public void setStreamExceptionPolicy(String streamExceptionPolicy) { this.streamExceptionPolicy = streamExceptionPolicy; } /** *

    * Configures how Network Firewall processes traffic when a network connection breaks midstream. Network connections * can break due to disruptions in external networks or within the firewall itself. *

    *
      *
    • *

      * DROP - Network Firewall fails closed and drops all subsequent traffic going to the firewall. This is * the default behavior. *

      *
    • *
    • *

      * CONTINUE - Network Firewall continues to apply rules to the subsequent traffic without context from * traffic before the break. This impacts the behavior of rules that depend on this context. For example, if you * have a stateful rule to drop http traffic, Network Firewall won't match the traffic for this rule * because the service won't have the context from session initialization defining the application layer protocol as * HTTP. However, this behavior is rule dependent—a TCP-layer rule using a flow:stateless rule would * still match, as would the aws:drop_strict default action. *

      *
    • *
    • *

      * REJECT - Network Firewall fails closed and drops all subsequent traffic going to the firewall. * Network Firewall also sends a TCP reject packet back to your client so that the client can immediately establish * a new session. Network Firewall will have context about the new session and will apply rules to the subsequent * traffic. *

      *
    • *
    * * @return Configures how Network Firewall processes traffic when a network connection breaks midstream. Network * connections can break due to disruptions in external networks or within the firewall itself.

    *
      *
    • *

      * DROP - Network Firewall fails closed and drops all subsequent traffic going to the firewall. * This is the default behavior. *

      *
    • *
    • *

      * CONTINUE - Network Firewall continues to apply rules to the subsequent traffic without * context from traffic before the break. This impacts the behavior of rules that depend on this context. * For example, if you have a stateful rule to drop http traffic, Network Firewall won't match * the traffic for this rule because the service won't have the context from session initialization defining * the application layer protocol as HTTP. However, this behavior is rule dependent—a TCP-layer rule using a * flow:stateless rule would still match, as would the aws:drop_strict default * action. *

      *
    • *
    • *

      * REJECT - Network Firewall fails closed and drops all subsequent traffic going to the * firewall. Network Firewall also sends a TCP reject packet back to your client so that the client can * immediately establish a new session. Network Firewall will have context about the new session and will * apply rules to the subsequent traffic. *

      *
    • * @see StreamExceptionPolicy */ public String getStreamExceptionPolicy() { return this.streamExceptionPolicy; } /** *

      * Configures how Network Firewall processes traffic when a network connection breaks midstream. Network connections * can break due to disruptions in external networks or within the firewall itself. *

      *
        *
      • *

        * DROP - Network Firewall fails closed and drops all subsequent traffic going to the firewall. This is * the default behavior. *

        *
      • *
      • *

        * CONTINUE - Network Firewall continues to apply rules to the subsequent traffic without context from * traffic before the break. This impacts the behavior of rules that depend on this context. For example, if you * have a stateful rule to drop http traffic, Network Firewall won't match the traffic for this rule * because the service won't have the context from session initialization defining the application layer protocol as * HTTP. However, this behavior is rule dependent—a TCP-layer rule using a flow:stateless rule would * still match, as would the aws:drop_strict default action. *

        *
      • *
      • *

        * REJECT - Network Firewall fails closed and drops all subsequent traffic going to the firewall. * Network Firewall also sends a TCP reject packet back to your client so that the client can immediately establish * a new session. Network Firewall will have context about the new session and will apply rules to the subsequent * traffic. *

        *
      • *
      * * @param streamExceptionPolicy * Configures how Network Firewall processes traffic when a network connection breaks midstream. Network * connections can break due to disruptions in external networks or within the firewall itself.

      *
        *
      • *

        * DROP - Network Firewall fails closed and drops all subsequent traffic going to the firewall. * This is the default behavior. *

        *
      • *
      • *

        * CONTINUE - Network Firewall continues to apply rules to the subsequent traffic without * context from traffic before the break. This impacts the behavior of rules that depend on this context. For * example, if you have a stateful rule to drop http traffic, Network Firewall won't match the * traffic for this rule because the service won't have the context from session initialization defining the * application layer protocol as HTTP. However, this behavior is rule dependent—a TCP-layer rule using a * flow:stateless rule would still match, as would the aws:drop_strict default * action. *

        *
      • *
      • *

        * REJECT - Network Firewall fails closed and drops all subsequent traffic going to the * firewall. Network Firewall also sends a TCP reject packet back to your client so that the client can * immediately establish a new session. Network Firewall will have context about the new session and will * apply rules to the subsequent traffic. *

        *
      • * @return Returns a reference to this object so that method calls can be chained together. * @see StreamExceptionPolicy */ public StatefulEngineOptions withStreamExceptionPolicy(String streamExceptionPolicy) { setStreamExceptionPolicy(streamExceptionPolicy); return this; } /** *

        * Configures how Network Firewall processes traffic when a network connection breaks midstream. Network connections * can break due to disruptions in external networks or within the firewall itself. *

        *
          *
        • *

          * DROP - Network Firewall fails closed and drops all subsequent traffic going to the firewall. This is * the default behavior. *

          *
        • *
        • *

          * CONTINUE - Network Firewall continues to apply rules to the subsequent traffic without context from * traffic before the break. This impacts the behavior of rules that depend on this context. For example, if you * have a stateful rule to drop http traffic, Network Firewall won't match the traffic for this rule * because the service won't have the context from session initialization defining the application layer protocol as * HTTP. However, this behavior is rule dependent—a TCP-layer rule using a flow:stateless rule would * still match, as would the aws:drop_strict default action. *

          *
        • *
        • *

          * REJECT - Network Firewall fails closed and drops all subsequent traffic going to the firewall. * Network Firewall also sends a TCP reject packet back to your client so that the client can immediately establish * a new session. Network Firewall will have context about the new session and will apply rules to the subsequent * traffic. *

          *
        • *
        * * @param streamExceptionPolicy * Configures how Network Firewall processes traffic when a network connection breaks midstream. Network * connections can break due to disruptions in external networks or within the firewall itself.

        *
          *
        • *

          * DROP - Network Firewall fails closed and drops all subsequent traffic going to the firewall. * This is the default behavior. *

          *
        • *
        • *

          * CONTINUE - Network Firewall continues to apply rules to the subsequent traffic without * context from traffic before the break. This impacts the behavior of rules that depend on this context. For * example, if you have a stateful rule to drop http traffic, Network Firewall won't match the * traffic for this rule because the service won't have the context from session initialization defining the * application layer protocol as HTTP. However, this behavior is rule dependent—a TCP-layer rule using a * flow:stateless rule would still match, as would the aws:drop_strict default * action. *

          *
        • *
        • *

          * REJECT - Network Firewall fails closed and drops all subsequent traffic going to the * firewall. Network Firewall also sends a TCP reject packet back to your client so that the client can * immediately establish a new session. Network Firewall will have context about the new session and will * apply rules to the subsequent traffic. *

          *
        • * @return Returns a reference to this object so that method calls can be chained together. * @see StreamExceptionPolicy */ public StatefulEngineOptions withStreamExceptionPolicy(StreamExceptionPolicy streamExceptionPolicy) { this.streamExceptionPolicy = streamExceptionPolicy.toString(); return this; } /** * Returns a string representation of this object. This is useful for testing and debugging. Sensitive data will be * redacted from this string using a placeholder value. * * @return A string representation of this object. * * @see java.lang.Object#toString() */ @Override public String toString() { StringBuilder sb = new StringBuilder(); sb.append("{"); if (getRuleOrder() != null) sb.append("RuleOrder: ").append(getRuleOrder()).append(","); if (getStreamExceptionPolicy() != null) sb.append("StreamExceptionPolicy: ").append(getStreamExceptionPolicy()); sb.append("}"); return sb.toString(); } @Override public boolean equals(Object obj) { if (this == obj) return true; if (obj == null) return false; if (obj instanceof StatefulEngineOptions == false) return false; StatefulEngineOptions other = (StatefulEngineOptions) obj; if (other.getRuleOrder() == null ^ this.getRuleOrder() == null) return false; if (other.getRuleOrder() != null && other.getRuleOrder().equals(this.getRuleOrder()) == false) return false; if (other.getStreamExceptionPolicy() == null ^ this.getStreamExceptionPolicy() == null) return false; if (other.getStreamExceptionPolicy() != null && other.getStreamExceptionPolicy().equals(this.getStreamExceptionPolicy()) == false) return false; return true; } @Override public int hashCode() { final int prime = 31; int hashCode = 1; hashCode = prime * hashCode + ((getRuleOrder() == null) ? 0 : getRuleOrder().hashCode()); hashCode = prime * hashCode + ((getStreamExceptionPolicy() == null) ? 0 : getStreamExceptionPolicy().hashCode()); return hashCode; } @Override public StatefulEngineOptions clone() { try { return (StatefulEngineOptions) super.clone(); } catch (CloneNotSupportedException e) { throw new IllegalStateException("Got a CloneNotSupportedException from Object.clone() " + "even though we're Cloneable!", e); } } @com.amazonaws.annotation.SdkInternalApi @Override public void marshall(ProtocolMarshaller protocolMarshaller) { com.amazonaws.services.networkfirewall.model.transform.StatefulEngineOptionsMarshaller.getInstance().marshall(this, protocolMarshaller); } }




© 2015 - 2024 Weber Informatics LLC | Privacy Policy