The last few weeks have seen several high-profile outages in legacy DNS and DDoS-mitigation services due to large scale attacks. Cloudflare's customers have, understandably, asked how we are positioned to handle similar attacks.
While there are limits to any service, including Cloudflare, we are well architected to withstand these recent attacks and continue to scale to stop the larger attacks that will inevitably come. We are, multiple times per day, mitigating the very botnets that have been in the news. Based on the attack data that has been released publicly, and what has been shared with us privately, we have been successfully mitigating attacks of a similar scale and type without customer outages.
I thought it was a good time to talk about how Cloudflare's architecture is different than most legacy DNS and DDoS-mitigation services and how that's helped us keep our customers online in the face of these extremely high volume attacks.
Before delving into our architecture, it's worth taking a second to think about another analogous technology problem that is better understood: scaling databases. From the mid-1980s, when relational databases started taking off, through the early 2000s the way companies thought of scaling Continue reading
Noction is pleased to announce the release of IRP 3.6. The major feature available in the new product version is the capability
The post Noction announces the release of IRP 3.6 appeared first on Noction.
EMA finds that the rise of internet connectivity for next-gen WAN does not spell the death of MPLS.
Check out this selection of tunes tailored for those who work to keep the network up and running.
I was reading Ivan’s blog as I often do when I came across this post about why certifications suck.
The author Robert Graham had a sample question from the GIAC Penetration Tester (GPEN) exam. The question looked like this:
By default, which protocol do Linux systems use to transmit packets for tracing a network path? a) UDP b) TCP c) ICMP d) TTL e) ECHO
Obviously being a networking expert I have my networking glasses on but I have to respectfully disagree with these gentlemen that I don’t think this is such a bad question at all. Trust me, I’ve seen much worse.
So traceroute works differently on different operating systems. If you work with penetration testing I would argue that you need to have a good understanding of different operating systems. You should know how they behave, what their characteristics are and how you can fingerprint them. The correct answer here is UDP. Linux systems and Cisco devices normally use UDP to send packets for a traceroute while Windows systems use ICMP when doing a traceroute. The answer is of course not TCP because TCP would require the three-way handshake and why would a device want to start a Continue reading