Manual Chapter : Configure a DoS/DDoS protection profile

Applies To:

Show Versions Show Versions

BIG-IP AFM

  • 15.0.0
Manual Chapter

Configure a DoS/DDoS protection profile

You can create a new DoS protection profile and configure settings to identify, and rate limit possible DNS DoS attacks.
  1. On the Main tab, click
    Security
    DoS Protection
    Protection Profiles
    .
    The Protection Profiles list screen opens.
  2. Click
    Create
    .
    The New Protection Profile screen opens.
  3. In the
    Name
    field, type the name for the profile.
  4. For
    Threshold Sensitivity
    , select
    Low
    ,
    Medium
    , or
    High
    .
    Low
    means the automatic threshold calculations are less sensitive to changes in traffic and CPU usage. A lower setting causes the system to adjust the thresholds more slowly over time, but will also trigger fewer false positives. If traffic rates are consistent over time, set this to
    Medium
    or
    High
    because even a small variation in generally consistent traffic could signal an attack. If traffic patterns vary, set this to
    Low
    to get fewer false positives.
  5. If you have created a whitelist on the system, from the
    Default Whitelist
    list, select the list.
    You can also click
    Manage Address Lists
    to jump to the Address Lists screen where you can create or edit address lists.
  6. From
    Families
    , select
    Network
    ,
    DNS
    , or
    SIP
    .
  7. At the bottom of the screen, click the selected family.
    The screen displays the attack vectors for the selected family.
  8. Click a specific Vector Name, to change the state, threshold or rate increase of the attack vector.
    The Properties page for the attack vector opens to the right of the page.
  9. In the Properties pane, from the
    State
    list, choose the appropriate enforcement option.
    • Select
      Mitigate
      to enforce the configured DoS vector by examining packets, logging the results of the vector, learning patterns, alerting to trouble, and mitigating the attack (watch, learn, alert, and mitigate).
    • Select
      Detect Only
      to configure the vector, log the results of the vector without applying rate limits or other actions, and alerting to trouble (watch, learn, and alert).
    • Select
      Learn Only
      to configure the vector, log the results of the vector, without applying rate limits or other actions (watch and learn).
    • Select
      Disabled
      to disable logging and enforcement of the DoS vector (no stat collection, no mitigation).
  10. For
    Threshold Mode
    , select whether to have the system determine thresholds for the vector (
    Fully Automatic
    ), have partially automatic settings (
    Manual Detection /Auto Mitigation
    ), or, you can control the settings (
    Fully Manual
    ).
    The settings differ depending on the option you select. Here, we describe the settings for automatic threshold configuration. If you want to set thresholds manually, select one of the manual options and refer to online Help for details on the settings.
  11. To allow the DoS vector thresholds to be automatically adjusted, for
    Threshold Mode
    , select
    Fully Automatic
    (available only for DNS, Flood, SIP, some Fragmentation, and a few other vectors).
    Automatic thresholding is not available for every DoS vector. In particular, for error packets that are broken by their nature, such as those listed under Bad Headers, you must configure them manually.
    1. In the
      Attack Floor EPS
      field, type the number of events per second of the vector type to allow at a minimum, before automatically calculated thresholds are determined.
      Because automatic thresholds take time to be reliably established, this setting defines the minimum packets allowed before automatic thresholds are calculated.
    2. In the
      Attack Ceiling EPS
      field, specify the absolute maximum allowable for packets of this type before automatically calculated thresholds are determined.
      Because automatic thresholds take time to be reliably established, this setting rate limits packets to the events per second setting, when specified. To set no hard limit, set this to
      Infinite
      .
      Unless set to infinite, if the maximum number of packets exceeds the ceiling value, the system considers it to be an attack.
  12. To detect IP address sources from which possible attacks originate, enable
    Bad Actor Detection
    .
    Bad Actor Detection is not available for every vector.
  13. To automatically blacklist bad actor IP addresses, select
    Add Source Address to Category
    .
    For this to work, you need to assign an IP Intelligence policy to the appropriate context (device, virtual server, or route domain). For the device, assign a global policy:
    Security
    Network Firewall
    IP Intelligence
    Policies
    . For the virtual server or route domain, assign the IP Intelligence policy on the Security tab.
  14. From the
    Category Name
    list, select the blacklist category to which to add blacklist entries generated by
    Bad Actor Detection
    .
  15. In the
    Sustained Attack Detection Time
    field, specify the duration in seconds after which the attacking endpoint is blacklisted. By default, the configuration adds an IP address to the blacklist after one minute (60 seconds).
  16. In the
    Category Duration Time
    field, specify the length of time in seconds that the address will remain on the blacklist. The default is
    14400
    seconds (4 hours).
  17. To allow IP source blacklist entries to be advertised to edge routers so they will null route their traffic, select
    Allow External Advertisement
    .
    To advertise to edge routers, you must configure a Blacklist Publisher and Publisher Profile at
    Security
    Options
    External Redirection
    Blacklist Publisher
    .
  18. Click
    Commit Changes to System
    at the top of the page.
You have now configured a protection profile to provide custom responses to malformed SIP attacks, SIP flood attacks, and to allow such attacks to be identified in system logs and reports.
Now you need to associate the protection profile with a protected object to apply the settings in the profile to traffic on that protected object.