[NEW EPISODE]
In the latest Telemetry Now, @JustinRyburn joins me to talk about BGP Flowspec and how it's used to mitigate the effect of a DDoS attack
Check it out!
https://t.co/RPdtKGDD4l
The @FCC is seeking comment on a proposal to require 9 major US service providers to deploy RPKI ROV. (comments are due on July 17)
In my post for @kentikinc, I look at the proposal and where the service providers stand with respect to ROV.
https://t.co/kpD4KoNOPE
We are observing a sharp increase of #DDoS in 2024 at @OVHcloud with a new record of 840Mpps received in April. We decided to share few insights in a blog post:
https://t.co/kihAJADzHl
Last week's (PA)NUG near Philly was great and a wonderful time to see some friends!
Thanks Dwight Mohry for hosting and great to see @scottrobohn@andylapteff @Drew_CM & @RonWinward@us_nua@kentikinc
Check here for an event near you ---> https://t.co/5X5FgetreS
Little known fact - I had been thinking about Slowloris for about 10 years before I finally actually sat down to write it.
In the early 90's I had encountered a situation where Apache would die when people would do what I used to call "half-open" attacks where they'd see if they got the first packet (200 or 401) and then close the socket without seeing the rest of the result or sending RST or FIN packets causing Apache to be confused and hang, patiently waiting to finish it's response. Our interprocess communication would lock - something related to dead semaphores, and the whole system would halt and no longer deliver HTTP responses.
Every day at around 5PM Japan time, some kid would come home from school and attack us trying to break in. It was annoying, and it never really had a chance of working but it did break our website and cause my phone to start alerting due to the outage... every... single... night... at... 1am. Grr.
The solution at the time was simply to block the attackers and build a self-healing solution that would reboot Apache when we detected those hung IPC semaphores. Fairly ugly solution but it worked and was pretty cutting edge for it being the 90's. I also got my first Blackhat talk out of it with subsequent solutions we came up with to hide the responses requiring full HTTP responses to be analyzed before they could close the socket.
The talk was "Military Hardening of .htaccess" and was exclusively attended by Chinese speakers and like 3 of my friends - I was speaking opposite Mitnick, I think, so the room was virtually empty. I was also extremely, mind-bendingly, hung-over. I ended up throwing up right before going on stage, like under a minute before, and my head was spinning through the whole talk.
The Chinese audience members had a translator and it was making me sick to hear my own translation and I was already having a hard time keeping it together. I cannot believe Blackhat ever gave me a second chance after that mess. Friendly note kids - don't go full Vegas the night before your preso.
As you might imagine, after that I was pretty much totally done with the whole idea so I sat on the idea of Slowloris for a decade. Yes, a really really bad hang-over made me uninterested in developing a denial of service tool. It literally made me a little nauseous to think about it.
I digress...
But it got me thinking that there would be a way to do something similar as an intentionally malicious attack rather than just efficient brute forcing. The way to do that would be to send the packet with the first half of the HTTP headers and then just keep the socket open, never finishing the request.
I do wonder how many other exploits are out there where people are sitting on it forever just because they haven't gotten around to writing it yet.
In RPKI, determining when a #ROA expires is complex. 🤔
In our latest article, #BGP experts @DougMadory and @fastly's @JobSnijders dive deep into the expiration dates embedded inside ROAs and the shorter effective expiration dates used by validators.
https://t.co/tqXe5Tx1nK
Here's my analysis for @kentikinc cited in today's @WIRED feature story about the Red Sea submarine cable cuts.
I looked into the timing and impacts of the loss of SEACOM and AAE-1 (EIG was already down due to a pre-existing cable fault).
https://t.co/tWnhrreXHM
Kentik provides invaluable insights to businesses for their network traffic, enabling analysis and proactive measures to defend against evolving DDoS threats. 🛡️ #Cybersecurity#NetworkObservability#DDoS
https://t.co/GrTuSfB5Ao
It would appear that AS174 (Cogent) and AS2914 (NTT) have depeered in Europe. Causing a decent latency spike between single homed customers on both sides in Europe.
This is not Cogent's first de-peering, their wikipedia page has a mostly complete list https://t.co/rPGD6lTvzL
Internet service was cut for multiple Pakistani mobile providers in the hours prior to today's #PakistanElection.
According to @kentikinc aggregate NetFlow, Zong (China Mobile Pakistan) and Jazz (Mobilink) stopped carrying traffic between 02:00-04:00 UTC today. We also observed a reduction in traffic for Telenor Pakistan.
Kentik AI was recently featured in Forbes for innovation in network observability. With Kentik AI, you can use Natural Language Query (NLQ) to ask the platform specific questions about your network.💡@kentikinc@Forbes https://t.co/Ap0nUBwmAP
Another way to look at this incident is that RPKI ROV deployment (specifically the rejection of RPKI-invalid routes) has arrived at a point where a service provider can be knocked offline due to its routes being suddenly rendered RPKI-invalid. #BGP
Major outages for Azure and Optus, subsea cable cuts and an activation, and BGP/RPKI analysis made 2023 another eventful year on the Internet!
Here's my end-of-year post reviewing the analysis @kentikinc published in the past 12 months. Enjoy!
https://t.co/VlLN8RpuF1
Wow! 5 Years in Federal Prison for Defrauding @TeamARIN. The world of ipv4 address space.. 🤯
“through this scheme, Golestan and Micfo obtained the rights to approximately 757,760 IP addresses, with a market value between $9,850,880 and $14,397,440.”
https://t.co/34KNjSrBkF