Back in 2012, Verizon labeled 2011 as the year of the hacktivist, as 58% of all data stolen was the result of hacktivism attacks. Attention seems to have shifted to cybercrime at the enterprise level, but CISOs must stay alert to hacktivism.
The truth is that hacktivism attacks are growing larger every year and all companies are susceptible.
Cybercrime is often separated from hacktivism in terms of security threats. Studies found that in late 2014, cybercrime accounted for 70.8% of attacks while hacktivism came in at 18.1%. Despite a lower percentage, hacktivism is still a major concern. Hackers have become more powerful, upping their ability to flood enterprise networks from 100Gbps in 2011 to upwards of 400Gbps in 2014.
Although some of the biggest hacktivism collectives are dying, major entities are rising in the interim. In an effort to spread a public message, hacktivist groups like ISIS and the Syrian Electronic Army target governmental figures and departments. However, hacktivists can target any industry or company, and if you think you’re immune, take a look at some of these high profile victims:
Hacktivism is considered to be a cyber attack with political of social undertones. Although governmental messages are involved, there is no telling what entity will actually be attacked. The unpredictability of these cause-driven attackers makes it essential for CISOs to be prepared.
Hacktivism attacks aren’t just after financial gains or customer data. Publicity is a major goal because of the social message attackers are trying to convey. Distributed denial of service (DDoS) attacks are the key vehicle for hacktivists to get their message across.
As mobile devices and apps grow increasingly important to businesses of all sizes, hackers are finding ways to exploit endpoint weaknesses. Because of the growing amount of public-facing applications, hackers can steal user credentials, get into the enterprise cloud and steal any amount of corporate data. With hacktivism, the threat goes even deeper.
Once a hacktivist has gained access to user credentials, they can deploy malware into the system with phishing. The malware spreads throughout the network, using bots to steal more login information until the hacker has a litany of endpoints to attack with. Controlling so many user accounts allows hacktivists to flood weak targets with massive amounts of packets until the site or system crashes.
DDoS attacks are some of the most dangerous threats in the cybersecurity landscape. Costing approximately $40,000 per hour, CISOs can’t afford to fall behind on hacktivist DDoS security.
Studies show that user devices factor into 82% of web app attacks and 95% of DDoS attacks involve credentials that were stolen from the users themselves. It’s clear that protecting endpoints is an essential start to defending your organization from hacktivists.
Identity access management is key to hacktivism security. Information Age reports that “if you are not already using multi-factor authentication, then start using this, at least for sensitive applications and those that are public-facing.” Total control of mobile endpoints isn’t 100% feasible, but CISOs must do everything they can to prevent phishing attacks that may lead to the dangerous DDoS attacks that hacktivists conduct.
One thing that IT can control is network design. It’s not enough to just deploy a firewall and threat detection solutions hope that it protects you from every attack – you need to be sure that your defenses are set up to work the heavy load conditions generated by DDoS attacks. That means architecting a solution that includes system redundancy and load balancing of traffic across all appliances. As attacks become more sophisticated and targeted, it is critical that companies eliminate known weaknesses as quickly as possible.
Download, How to Determine Your Baseline Traffic, by Tim O'Neill, for a step-by-step guide with typical measurements and screen shots.
If the inline security tool goes off-line, the TAP will bypass the tool and automatically keep the link flowing. The Bypass TAP does this by sending heartbeat packets to the inline security tool. As long as the inline security tool is on-line, the heartbeat packets will be returned to the TAP, and the link traffic will continue to flow through the inline security tool.
If the heartbeat packets are not returned to the TAP (indicating that the inline security tool has gone off-line), the TAP will automatically 'bypass' the inline security tool and keep the link traffic flowing. The TAP also removes the heartbeat packets before sending the network traffic back onto the critical link.
While the TAP is in bypass mode, it continues to send heartbeat packets out to the inline security tool so that once the tool is back on-line, it will begin returning the heartbeat packets back to the TAP indicating that the tool is ready to go back to work. The TAP will then direct the network traffic back through the inline security tool along with the heartbeat packets placing the tool back inline.
Some of you may have noticed a flaw in the logic behind this solution! You say, “What if the TAP should fail because it is also in-line? Then the link will also fail!” The TAP would now be considered a point of failure. That is a good catch – but in our blog on Bypass vs. Failsafe, I explained that if a TAP were to fail or lose power, it must provide failsafe protection to the link it is attached to. So our network TAP will go into Failsafe mode keeping the link flowing.
Single point of failure: a risk to an IT network if one part of the system brings down a larger part of the entire system.
Heartbeat packet: a soft detection technology that monitors the health of inline appliances. Read the heartbeat packet blog here.
Critical link: the connection between two or more network devices or appliances that if the connection fails then the network is disrupted.