A version of this post was originally published on CU Insight.
“DDoS botnet makes slaves of your home and office router”
“How 40,000 Routers Got Hijacked”
“Home routers co-opted into self-sustaining DDoS botnet”
“DDoS attacks affecting more countries than ever before”
If you’re unclear on the prevalence of DDoS issues, all it takes is a quick online search to turn up headline after headline of DDoS attacks. And those headlines are added to on an hourly basis.
DDoS is an epidemic on the rise. And though they are not alone in their susceptibility, most financial institutions are still significantly unprepared for a DDoS attack. Now, more than ever, it is crucial that your organization protects itself.
DDoS: A Problem We Can’t Ignore
If your financial institution has a server with public access, you have no choice but to consider the threat of a DDoS attack with the utmost seriousness. Now that the larger financial institutions have shored up their defenses, malevolent actors are focusing their sights on a new line of targets: smaller financial institutions.
Just how seriously your institution could be impacted by a DDoS attack depends on how much of your financial institution’s business and reputation depends on access and availability of your online services. If your online banking operations or other online services are down for an extended period of time, there is the potential for significant damage to your financial institution’s reputation.
DDoS preparedness is best considered to be a strategy. The approach should be similar to the strategy used for disaster recovery: understand the risk, know your environment, perform up-front front planning and preparation, document your findings and your plans, do occasional tests of your plan, and–finally–revisit your strategy on an ongoing basis.
A 7 Point Approach to DDoS Preparedness
Here’s what you can do to fight the epidemic.
1. Conduct a Company-wide DDoS Risk Assessment
Every financial institution should be accustomed to the process of documenting formal risk assessments, taking into consideration both regulatory guidance and best practices. Conducting a company-wide DDoS risk assessment is the essential first step in DDoS preparedness.
By evaluating your environment and taking into account specific points of exposure, you should be able to zero-in on most likely targets, such as home banking, public facing websites and other online services.
With this information in-hand you should then work to identify the potential impact of an attack on your business. What losses could your institution incur in the form of lost revenue or reputational damage?
2. Create an Action Plan to Prepare For and Respond to DDoS Attacks
Armed with the information you derive from your risk assessment, you are then better positioned to move to the next step: create an action plan to prepare for and respond to DDoS attacks.
If you haven’t prepared for an attack, your response is likely to be slow, disorganized and therefore ineffective.
We recommend that you develop a plan – much like the plan that you already have for the Unintended Disclosure of Non-Public Member Information. This should augment your existing Incident Response Plan, with a focus on the various DDoS-centric activities.
As with disaster recovery planning, the use of different scenarios to help shape specific responses is a constructive way to go about developing and detailing this plan. Taking into account the various types of DDoS attacks, such as Protocol Attacks, Application Attacks or Bandwidth Attacks,you can adjust scenario duration and plans based on the specific servers subjected to the attack.
An extremely important element of your action plan, which, unfortunately, is often forgotten or ignored, is to include the specific steps you will take to monitor the other systems that are not directly impacted by the DDoS.
Today DDoS attacks are frequently used as a smokescreen to create a crisis designed to distract your staff while something else – usually more nefarious – occurs elsewhere in your financial institution. A DDoS attack needs to be directly addressed, but this should also trigger heightened awareness for of other attacks that may be occurring against your enterprise.
3. Know Your Infrastructure Components
How well documented is your enterprise infrastructure? Do you have a complete inventory and map of all of your components? How frequently is this updated?
Having one or more IT people that know everything about your systems isn’t enough. If your infrastructure inventory isn’t documented and current, you are not prepared for an attack. Your enterprise infrastructure inventory will help you focus on the specific types of attacks you can withstand, and help you identify the best practice approaches to DDoS defense for your environment.
4. Understand Your Infrastructure Components
When asked about their state of DDoS preparedness, many financial institution executives reported that they would simply rely on their ISP to fix things. As Benjamin Franklin famously said, “Failing to prepare is preparing to fail.”
Don’t wait for an attack to learn the extent of your ISP’s defensive capabilities. It is essential that you proactively develop and document response plans with all of your online service providers.
A few things to document and understand about your ISP:
- Do you have a calling tree and support numbers, contacts and account numbers readily available to you? And, do you know where to find them if your site or network is down?
- Do you understand your ISP’s options for defending against DDoS attacks? Do they use black hole routes, upstream filtering or cloud-based mitigation?
- What are the SLA’s within your contract with your ISP?
A key question that every financial institution must also address is whether to depend on their ISP for DDoS protection, or to contract with a DDoS mitigation services provider.
While an ISP-based solution might seem to make sense, there are several factors to consider. If your organization is multi-homed, all your ISPs would need to participate. Otherwise, bandwidth availability during attacks would be spotty. It is also difficult to coordinate an active mitigation between multiple ISPs. Does your organization want to be the one coordinating this response? If not, then selecting and experienced, third-party DDoS protection provider should be an essential part of your plan.
5. Implement General Rules to Help Mitigate DDoS Attacks
This step is one that your IT team should already have as part of their general operating procedures. If not, make it an immediate priority. The following are general rules to help defend against a DDoS attack. They should only be used as a guide, since they will not stop all attacks, especially some of the more complex varieties.
• Turn off all unnecessary ports and protocols
• Implement an IP blacklist
• Block invalid and malformed packets
• Configure and harden network equipment
Ongoing vulnerability assessments will help you to validate that you’ve properly configured and protected your environment against these ever-evolving threats.
6. Conduct a Post-attack Analysis After a DDoS Attack
While it is crucial to have a plan in place to address a DDoS attack, it is equally important to perform a post-attack analysis. Some of the items to consider documenting an attack include:
- Type of attack (Volume, Protocol, Application Layer)
- What equipment helped you mitigate, even if it was only partially successful?
- What attack traffic had the most impact and why?
This analysis will help you evaluate the effectiveness of your response plan, identify any holes in your documentation, and also help you determine whether or not you need to replace or upgrade infrastructure components. If you don’t have the budget for more resilient infrastructure, you may want to think about outsourcing to a security service provider.
7. Leverage Monitored and Managed Services
Partnering with an experienced third-party DDoS mitigation provider has significant benefits. Such providers have deep experience in dealing with DDoS attacks and offer a wide array of equipment and resources. You can use their services on demand—for example, a DNS redirect service—or have them monitor your network 24/7 for signs of attacks.
