Video: Anatomy of an Application Attack | Duration: 2128s | Summary: Anatomy of an Application Attack | Chapters: Welcome and Introduction (105.8s), Cloudflare's Global Network (224.015s), Unified Security Platform (373.555s), DDoS Protection System (797.03s), Advanced Security Features (1239.94s), Conclusion and Partnership (1777.515s)
Transcript for "Anatomy of an Application Attack":
Okay. Hello, everyone. Let's give it another thirty seconds more, before we have, everyone join in, and then we can begin our session for today. Okay. So half a minute have passed. Let us begin today's session hosted by CloudFare. So today, we'll be talking about anatomy of an advanced automated applications attack. So hello, everyone, and welcome to today's webinar. So my name is Sean, and I'm the digital solutions engineer for APAC here at Cloudflare. So for today, we are so excited to have you all join us for today's session. We'll take a closer look at the anatomy of advanced automated application attacks and how Cloudflare's threat intelligence can actually help to protect your application from ever evolving threats, especially nowadays with the growth of AI. So attacks grow more automated, more sophisticated. It's always important for us to understand how they operate, what kind of targets is in their radar, and how you can build defenses to actually adapt and overcome these challenges. So we'll explore real world attack patterns that Cloudflare sees across its global network and how the intelligence is used to enforce security policies. By the end of this webinar, hopefully, you have a clearer picture of how to strengthen your security posture using some of Cloudflare's tools and offerings to help you stay ahead of threats without compromising performance or user experience. Okay. Before we begin, a quick reminder, this session is being recorded, and we will share the recording with you afterwards. So we encourage you to post any questions you may have in the q and a box throughout the entire session. We will make sure to have someone address all your questions, or you could also share those questions at the end of the presentation. So let's begin. Okay. So before we talk about attacks, right, let's take a moment to step back and look at the bigger picture. What is behind Cloudflare's security platform and offering? So the very foundation of Cloudflare is we have the powerful global network that powers and enables everything. So Cloudflare isn't just a security company. It's also one of the world's largest and fastest growing networks. As of today, it handles about more or less 20% of the entire Internet traffic. So meaning, one in five Internet requests will go through Cloudflare. So you might be asking, why does this matter? So in this context, it matters because this amount of data and network distribution actually gives us unmatched visibility, speed, and reach. This is what we need as a solid foundation for today to protect modern distributed businesses. So the map shows here that we are available in 335 cities with 210 plus of them are actually AI enabled. So when I mean AI enabled, it just means that we have the GPU power to actually enable AI workloads. Right? And in practical term, it means that it doesn't matter where your end users are or where your application is hosted. Cloudflare using this leveraging this platform is able to deliver fast and secure experiences globally. So as you can see here, we have around fifty milliseconds to reach Cloudflare end users from 95% of the world's population. So we have actually built a very solid connection throughout every country. So around 13,000 networks, each of them consisting of ISPs, cloud services, peering with data centers, and things like that. So for you as the customer or the users of Cloudflare, you won't even have to actually manage or think about all this infrastructure. Right? It just works behind the scene because Cloudflare has been leveraging this technology throughout its history of cybersecurity. Okay. So today's work environment is no longer just limited to office buildings or a gated system, network system. Right? Your team might be logging in from a remote site, like a cafe or whenever you're visiting a client sites or throughout all around the world. So your application and infrastructure must live in the cloud on-site and everything in between to accommodate this kind of hybrid workspaces. So what hasn't changed is the need to keep everything and everyone online secure, and that's exactly what Cloudflash Unified Security Platform is built for. So there are three subsections. Let's begin with employee. So it doesn't matter where they are, what kind of devices they are using. Cloudflare ensures that they can actually work safely. This also accounts for bring your own devices. So think of it like this. No matter whether if someone is actually checking the email at the airport or accessing files from the cafe or perhaps they are connecting to a public hotspot or public Wi Fi, they will actually be guaranteed to be protected by a fast and secure path to the Internet, irrelevant of whether it's a public resources or an internal company resources. So, basically, what I'm saying is that we can block harmful web sites, stop phishing email, and the most important thing for companies nowadays is to keep sensitive data from leaking out from these devices, which could be a point of vulnerability. And to that matter, we also did not sacrifice a seamless experience for the users. Then on the next box, we're going to discuss about apps and businesses that you'll rely on. So things like SaaS tools, like Salesforce, perhaps internal AI tools that you built in house, or it could be customer portals, APIs, or real life databases. So, normally, where it hurts the most and where hackers actually targets are applications like this critical mission critical. So Cloudflare actually helps to keep them safe behind the scenes by spotting threats like bots, misuse attempts, DDoS beforehand, and put in proper mitigation to allow your apps to function as is intended. So it doesn't matter whether the app is hosted on your own server, perhaps in the office or data center, or perhaps it doesn't matter if your app is hosted in cloud infrastructure. Cloudflare as a unified platform actually puts a strong layer of protection around them. So lastly, we'll talk about infrastructure. So infrastructure means everything that connects your office, your cloud system, your data centers, your databases, and things like that. So Cloudflare acts like a very smart traffic controller. It makes sure your data flows quick and safe between location. Not only location, but also safe between users as well as their devices. So instead of using a very complicated, might be expensive patchwork of different tools and vendors, everything is being managed through one system. So everything on a unified platform online, and those changes are instantaneous. So mission critical changes and configurations can be done on the spot. Right. DDoS attacks. So one of the most important protections that we offer as a product is our DDoS protection or DDoS mitigation solutions. So Cloudflare is unique in the sense that in a world of other vendors, we provide unmetered and unlimited protection against DDoS attacks. We do protect across different layers of your instruct infrastructure. Like this slide says here, we protect layer seven, layer four, and layer three as well. So a DDoS attack, if you for clarity, right, is when a bad actor floods your system with fake traffic and overwhelm them to take them online. So it is surprisingly a a very simple methodology attack. Regardless, it is very effective and highly disruptive to a lot of global companies. So with this unmetered protection, right, Cloudflare won't spring you with surprise bills or any kind of throttling to your application. It's basically a peace of mind kind of business model. So things, for example, will start from the very beginning, right, at layer seven, application layer. So for things like websites, APIs, SaaS application, and mobile applications, it will all be in this layer seven. So this is normally where users actually interact with your services through the mediums that I mentioned before and where attackers are most likely would try to disrupt things. So they will use methods like bots or overloading with a request with no return address. And to that, we will offer our web application firewall or WAV for short to identify and block this malicious traffic before it ever reaches your origin. So for non web application, things like game servers, email servers, web tree, or cryptocurrency exchanges, that this all lies in layer four, the transport layer. So for this non web applications, they don't live in a browser, so they need a fundamentally different kind of protection. For that, we would offer Cloudflare Spectrum. This acts like a smart traffic shield for this kind of application. It is mainly used to ensure that throughout this DDoS attacks, it keeps connection stables and protected. So finally, we have layer three, which is basically IPs. Right? We are stopping DDoS attack at the network layer before they even get close to your system. All in all, whenever you're on Cloudflare in itself, we are already protecting you to some certain extent as whenever you're on Cloudflare onboarded there, we will always review our IP from Cloudflare service edges instead of your actual origin. So attackers that actually do host name based attacks will also, to a certain extent, be protected by IP flooding. However, we also have another product called Magic Transit. This is specifically used to protect any IP space that you own. So if, let's say, for example, your IPs were to be publicly leaked and it becomes a target for IP based attacks, our magic transit will also be able to protect flooding and taking down your infrastructure. Okay. Big network is a very strong fundamentals, but then it's another thing to make that network smart and to protect. So Cloudflare's data system isn't just basically brute forcing with a massive amount of network and capacity. It also has to be accurate and autonomous, Meaning that it doesn't just block everything in hindsight that looks suspicious, but to actually block accurately what's truly dangerous with speed and precision. So at the heart of the system, here is a very simple diagram. We have a in house built system called DOSD, which is short for denial of service demand. So what makes this special is that we install a copy of this system, right, the DOSD software, on every single Cloudflare server. Okay. So these softwares live natively right at our edge server, and then it is deployed to work autonomously as well. Meaning, twenty four seven, they are detecting and stopping DDoS attacks right at the edge, basically, as a unified distributed system. So there is no need for whenever we are encountering this kind of DDoS attack, there is no need for a central or a cost server to actually do the evaluation, the calculation, and sending instructions for the edge to deny this request. So instead of relying on one single brain to make all the decision, each server in all these different locations in 330 cities have its own intelligence, and that makes the system incredibly fast and resilient. So each data center shares that threat intelligence between its servers as well as across the entire global network. So if, let's say, for example, an attack supposedly supposedly hits a Cloudflare server in Singapore, so that system will learn and deny the packet. But other than automatically blocking it, it will also synchronize with our distributed system across the global network. So it means that the similar attacks with those similar fingerprints, similar signature, similar methods, it will also simultaneously be blocked across nodes, like, for example, in London, New York, or Japan instantaneously as well. So it's basically, in a nutshell, like an immune system that learns from an exposure and then immediately protect the rest of the body. Okay. So what are some explanation without numbers? Right? Let's talk about the growing threat of DDoS attacks. So over the few years, the scale and frequency of these attacks have exploded. Okay. Reason being, more businesses and applications are actually moving their infrastructure, their their needs, their services online. So it doesn't matter if it's ecommerce's, SaaS platforms, gaming, or even health care services. Everything is moving online as we become more and more distributed. So as we rely more and more on cloud and digital infrastructure, the more attractive this system actually becomes as a target. So volumetric DDoS attacks are all about one thing. Basically, bad actors will overwhelm your networks so with so much traffic that they simply cannot function and racking up amounts of loss for that services or company. So to give you a sense of how big these attacks are getting, let's look at the late one of the latest and the highest volume attack that we've encountered in 2025. So what you're looking right now in this presentation is the Isuru Kimwolf attack. So if you wanna read more about it, on the docs tab, you're able to see a blog discussing and talking about everything that high every highlight that is about this specific attack. But, basically, if I were to break it down, it's a massive collection of malware infected devices. So in this case, with the iSorokin booth, it's primarily from Android TVs. So the graph you're seeing here actually shows traffic from a massive DDoS attack that peaked at 31.4 terabits per second. Thus far, 2025 has been a large it's been a year with a lot of large records, a lot of large attacks. But so far at q four, thirty one terabits per second actually takes the cake, and it is the largest we've ever recorded until today. So what's even more shocking is that this entire attack only lasted thirty five seconds. That's basically less than a minute. However, in that time, the system is able to absorb and detect these petabytes of junk traffic, basically targeting customers all around the world in different location. So we are dealing this in a context. Imagine if someone is trying to crush your website by throwing an entire ocean of data in under a minute. So this is what scale that Cloudflare is dealing on sometimes and thus far. However, with all this, right, no downtime, no panic alerts. It's just normal. Hopefully I mean, it's a good thing that there is no disruption to application, and then there is also the same thing, no disruption to other users on that network as well. So this attack wasn't just about volume. It's about precision. This iSuru attack is basically a distributor botnet involving tens of thousands of IPs across multiple geography. It's short, fast, and a classic hit and run DDoS. So why we are able to mitigate this is because Cloudflare system didn't have the need to detect, wake up, and spend more time confirming because our system, the DOSD system, has always been watching twenty four seven. So during that time, our DDoS mitigation engine detected the unusual spike within milliseconds. It analyzed the flow, matched to the pattern, instantaneously activated appropriate filters, and dropped the traffic not only at a single edge but across our global networks. So what does this actually show to you from Cloudflare is that onto as we progress onto a more free, a more Internet cloud reliant kind of services and application for mission critical services, attacks are actually getting more and more shorter and sharper. And in that sense, intense as well because we're seeing a peak peak volume of 31.4 terabit per second. So this is exactly why proactive always on protection, especially for DDoS, is no longer an option today, especially in 2026. It is actually a necessity. Because if we are talking about the traffic that we're looking through this graph, it might not even need thirty five seconds for it to actually take down your critical infrastructure. So reaction time isn't actually enough. You will need a always on preemptive defense. Okay. Here are some context and data that I'm going to show you. It basically highlights what are the top 10 most attack industries that we've encountered so far in turning 25. So this is for this covers the fourth quarter. So if you can see here, most of the hyper volumetric DDoS attacks actually target customers, Cloudflare customers, most in the telecommunications, service providers, and carriers industry. So Cloudflare customers in the gaming industry and customers providing generative AI were actually also heavily targeted. Okay. Now that we've seen massive volumetric attacks in layer seven, let's talk about our web application firewall. So it's basically the frontline defense for your web apps protecting against things like commonly known HTTP vulnerabilities, injection attack, cross site scripting, and credential stuffing, and so much more. So we're not just talking about a reactive defense. Cloudflare's WAF actually offer a zero day threat mitigation, meaning we can block emerging exploits before they even make headlines within twenty four hours. So why this is possible with Cloudflare is because we have a team constantly updating this managed rule sets. So these security teams push it globally within minutes. So when new vulnerabilities are discovered, for example, like, Log for Shell or Spring for Shell, which are pretty famous vulnerabilities, our system are actually ready before attackers or can actually capitalize or exploit them towards our customers' infrastructure. Okay. It doesn't stop there. Right? Our protection is layered. First, you've seen the DDoS. Now you've seen our managed rule set. We also add static rules, dynamic analysis, and machine learning models to actually adapt to evolving attack patterns. So those that are already familiar with Cloudflare might know that we have scorings based on machine learning, scoring based on WAF tech scores, and things like that. So even if, let's say, for example, someone tried to bypass known rules or tried to bypass the curated custom rules that you have for your application, the system can regardless still detect anomalies in the behavior and shut it down. We also make complex security simple. So things when it comes to things like stolen credentials and data exfiltrations, these are highly complex. However, with Cloudflare's intelligence and the amount of traffic that we get to learn from, Cloudflare actually can identify login abuse and unusual data access patterns without heavy configuration or a lot of know how on the customer's part. But, of course, let's not forget about API. In today's world, over 70% of the global traffic is actually API based. So meaning that they have the biggest surface area and makes them the best targets for abuse. So that's why we built an API first approach to security with advanced rate limiting. So traditional API calls that are used to file upload, even if the file does not contain lots of calls that manage rules that get triggered and attack WAF score is at higher end due to which genuine traffic get blocked. So if, let's say, for example, perhaps you could whitelist the API endpoint, which could be a risk as well. I acknowledge that. However, we need to know what is actually okay. So you can enable manage rule sets. You can stop whitelist that display endpoint based on the scoring. However, at the same time, I will highly recommend you to actually investigate what could possibly be triggering the rules. So for example, if we're talking about file upload, sometimes those file have suspicious signatures. Or perhaps when you are doing a post request or a some kind of request from the origin, there might be things like query string that contains sensitive information. So in that end, at the same time as Cloudflare have to curate, you can implement very specific, very stringent rules to protect and allow things that are that are verified by your application team. Right? But at the same time, it is also good for you to consider that what is the actual vulnerability at play. Could it be that inside a file signature, something is a known vulnerability, or is it that whenever your customers request at the back end of the payload, there is very sensitive query string or keys attached to it? That is one way we evaluate the entire security stack in a holistic method. So I hope that answers your answers your question, mister Raj Kumar. Okay. So continuing on, whether it's bot traffic actually hammering a login form or some kind of scanner that is probing your APIs, Cloudflare actually provides a fast, smart, and autonomous protection. Okay. Customization. So like I said before, some applications are built different from others. Some still carry legacy code that are dependent on critical infrastructure. So through Cloudflare's custom WAF, this basically gives you a powerful and flexible rule engine that allows you to tailor very specific protection to exactly what your application may need. So you can create the rules. It is very straightforward. If you need something more precise, of course, on the higher end, you can also create rules that match things on headers, query string, cookies, payload contents, and request method. Right? And something that really helps during testing is that you can set any rules. Like, for example, if you're trying to curate and do testing, right, you can set rule action to log instead of blocking to ensure that to ensure that you actually do the testing before you deploy false positive changes. Okay. So, again, if you're you don't feel the need to write custom rules or if you're not familiar, we always have that base protection. Okay. We always have that base protection based on the managed rule sets that our security team curate every weekly. So other than managed rule set, we also have OWASP top 10. Basically, these are the most famous zero day exploits, and our security team have put up a custom patch to actually block these kinds of known vulnerabilities. So the best part of all this is actually these rules, whenever they're inside the dashboard, as you enable, they are still being constantly updated. So we're talking about weekly updates. Or, however, sometimes when very big vulnerabilities, we're talking about zero day threats, that pops up faster, we will push the the the update even faster, and you do not have to lift a single finger. So it basically just means that you're always protected regardless of whether you're active or not. And then this also applies to future emerging threats. So whether you're hosting a blog or a online store, it doesn't matter what kind of content you're running on your application or website. Cloudflare actually manage to give you a base protection, a proactive protection without the need for you to configure everything itself. So it's basically security on autopilot. Okay. Another problem with today's security is bots. So, of course, not all bets are bot. When we talk about bots that are beneficial to humanity, we always talk about things like search engine crawlers, uptime monitors. These are the bots that you would want to allow to your website. However, today, we'll be focusing on the bad ones. So they are the growing threat. So things like, for example, scraping content, abusing APIs that is wasting your resources, hoarding inventory, or launching credential stuffing. So Cloudflare's bot management is able to identify and mitigate these attacks in a targeted way so we can reduce the amount of false positive. And with machine learning on hand so every minute with machine learning, our system will get smarter. Okay. Quick overview. Basically, how bot has evolved throughout the years. We will start with the basic. The basic ones were relatively harmless. Their main job is just to collect data. So they use a very small subset of IP addresses, and their attacks were actually easier to spot, especially when it comes to volumetric attack because they just belong to the same few request method as well as IP addresses. Then came the modern bots. So, basically, a level up. They're not just collecting info. They are basically be able to diversify and steal sensitive data and take down individual websites. So instead of just IPs, they operate in massive botnet. So today, we are facing against sophisticated modern bots powered by AI. So they are the biggest problem nowadays. And these bots are no longer tools. They are actually able to imitate real life users. So they can commit things like fraud, disrupt businesses, attack government, and actually mess with a personal daily life. So with how human like they behave, they're able to mimic clicks, use real browser sessions, change request methods, and things like that things like that on the flight. And stopping them is actually a real challenge because you need a combination of threat intelligence, device, and browser fingerprinting, and machine learning. Okay. Advanced Relay Limited, we talked about it. It's one of the effective way to stop abusive traffic before it reaches your application. So Advanced Relay Limited actually gives you fine control over traditional ones, which are actually just IP based, and that is to stop mostly brute force login attempts, mitigating DDoS, as well as managing unexpected API traffic search. And, of course, protection is only half the battle. We have visibility Because the more you can see, the faster you can respond, improve, and stay ahead. So Cloudflash analytics and visibility gives you a clear return view of actually what's happening across your application stack. Okay. Finally, Cloudflare. For us, it's not just about security products. It's about partnership. So a quick shout out to our team or known as the threat advisory solutions engineers. They basically are twenty four seven and ready to jump in the moment you face a big threat or suspicious activity. So their roles actually goes beyond incident response. So the testing team will work closely with you to provide a strategic guidance from onboarding all the way to future mitigation. So if there is any attack or threats on your way, feel free to contact our AE or contact us through the website, and we'll be happy to help you. Okay. With that, I end my presentation. Thank you very much. If there's any q and a, we'll be happy to answer, so stay tuned. And, again, with the recording, we will be sending it to you shortly after the session ends. Thank you so much for your time.