Blog
StormWall’s DDoS Year-in-Review report takes a look at the 2022 threat landscape, breaks down the industries that were most affected, and explores current DDoS trends.
StormWall is celebrating its 10th anniversary. For all these years we’ve been on guard for our clients and have done a lot — let's recall the main achievements.
Transparent DDoS protection settings, more useful features and attention to detail - since the end of last year, StormWall has added a number of new features to the StormWall Portal. Let's take a closer look.
Although customers of Internet service providers (ISPs) purchase communication channels with a precisely defined bandwidth, they are often not charged for the entire port capacity, but only for the bandwidth actually consumed. For ISP providers, this method is known as burstable billing. Moreover, this actually consumed bandwidth is usually taken into account not according to the highest of the indicators recorded during traffic measurements, but by subtracting 5% of the maximum - according to the largest of 95% of the remaining values. This method is called the 95th percentile.
On March 6-9, 2023 StormWall team is participating as a delegate in Capacity Middle East — the largest forum for representatives of the digital infrastructure industry in the Middle East region: cloud technology providers, digital content providers, famous operators, data centers and others. Middle East is one of our priority areas, StormWall is committed to expand its presence in this region.
The year proved to be difficult, but productive. We thank StormWall partners, colleagues and friends for the good engagement. Let us remember what we were able to do to improve the protection of your resources.
We are pleased to announce the opening of our sixth filtering location in partnership with cloud provider IDCloudHost. The new site is located in the Equinix SG3 data center in Singapore, the largest Internet hub in Southeast Asia, providing ultra-low latency connections.
Providers of Anti-DDoS services often offer to connect protection using the asymmetric scheme: only incoming traffic is filtered — the one that goes to the protected resources, and outgoing traffic is not considered at all. In a number of other situations, they use a symmetrical scheme when not only incoming, but also outgoing traffic or service information about it is analyzed. When and in which cases should the asymmetric filtering scheme be preferred, and when should the symmetric one be preferred?
Mistakes in the organization of protection against the risks associated with DDoS attacks almost always lead to a reduction in the resilience of their Internet resources to these risks, and it is impossible to compensate for them solely by connecting anti-DDoS services, even when they are most advanced. The situation is often aggravated by the fact that the combination of several flaws increases their overall negative impact. In this article, we will analyze some of these flaws we encountered while building protection against DDoS risks at a rather large client managing several hundred websites.
It often happens that customers of DDoS protection services believe that just by connecting to these services they are fully protected. Unfortunately, it is not quite right: DDoS protection is not magic or a superpower, and in order for it to work effectively, the services themselves must have sufficient immunity against DDoS risks.
We observed an unprecedented growth in the number of DDoS attacks in 2022. Unfortunately, this trend continued into the third quarter of the year. The report looks at the situation in the telecommunications, fintech, entertainment, education and logistic industries.
In this article we will discuss how to achieve security of websites and server components of browsers, mobile applications and services that interact with HTTP/HTTPS-based protocols via APIs.
We provide a brief guide that will help to improve the effectiveness of protecting networks and autonomous systems from DDoS attacks. It lists the aspects that should be taken into account.
