Skip to content
English
  • There are no suggestions because the search field is empty.

DDoS Attack – Preparation, Response & Mitigation

DDoS Attack – Preparation, Response & Mitigation Distributed Denial-of-Service (DDoS) attacks are constantly changing. While the objective is still to cause a service outage, attacks and attackers are becoming more sophisticated. Motivations for attacks are increasingly financial or political with more serious consequences for the targeted victims. For this reason, FLEX has put together a plan to Prepare, Respond and Mitigate an attack.

Preparation Check List:

  1. Identify and reduce the attack surface by limiting Internet accessible resources and hosts.

 

  1. Identify and reduce attack vectors by eliminating vulnerabilities produced by operating systems, software and hardware exploits.

 

  1. Reduce attack surface by limiting resources on the same Internet accessible hose i.e., running dns, www, vpn, etc. on one host system.

 

  1. Contact VIAWEST, XO, COMCAST to discuss paid and free DDoS mitigation options.

 

  1. Establish contacts with ISP, law enforcement, Managed Services team, Network Operations, and IT Security team. Identify who should be contacted during a DDoS attack and what processes should be followed.

 

  1. Have a conference bridge set up and distributed for all parties to connect to for faster response.

 

  1. Document IT Infrastructure to include business owners, IP addresses and circuit IDs as well as what IP addresses are public facing and what services are on each.

 

  1. Determine a baseline of current network performance so attack identification will be faster and more accurate.

 

  1. Identify critical services that must be maintained during an attack and set up a failover for these services.

 

  1. Harden the configuration of network, operating systems, and applications that may be targeted by DDoS attacks.

 

  1. Determine DNS time-to-live settings for systems that may be attacked and lower the TTLs, if necessary, to facilitate DNS redirection if the original IP addresses are attacked.

 

Response:

  1. Notify company executive.

 

  1. Contact law enforcement if directed by company executive level authority.

 

  1. Identify the owners of the attacking addresses. This can be used to track down the prime IP address of the attacking system and attempt to notify the ISP that owns the bot’s IP address.

 

  1. Contact vendors of affected systems and equipment, if necessary, to assist with DDoS traffic or collecting evidence.

 

Mitigation Checklist:

  1. Attempt to throttle or block DDoS traffic as close the network’s cloud as possible via router, firewall, load balancer, etc.

 

  1. Terminate unwanted or unneeded connections or processes on servers and routers.

 

  1. Blackhole DDoS traffic targeting the original IPS.

 

  1. If possible, add network or server hardware to handle the DDoS load.

 

  1. If possible, route traffic through a traffic-scrubbing service or product via DNS or routing changes.

 

  1. Adjust defense changes one at a time and notate the changes you may observe.

 

  1. Configure egress (outbound) filters to block traffic that systems may send in response to DDoS traffic to avoid adding unnecessary traffic load to the network.

 

 

 

Confidentiality Notice: This document is published by Computer Marketing Corporation/FLEX and is intended solely for its contracted clients. It may contain information that is privileged, confidential or otherwise protected from disclosure. Dissemination, distribution or copying of this document and any accompanying attached information by someone other than the intended recipient(s), or an employee or agent acting on behalf of the intended recipient, is strictly prohibited.