> but independent security researcher Kevin Beaumont and other analysts see evidence that some X origin servers, which respond to web requests, weren't properly secured behind the company's Cloudflare DDoS protection and were publicly visible. As a result, attackers could target them directly. X has since secured the servers.
X forgetting to put some important servers behind Cloudflare is some very important context
> But one researcher from a prominent firm, who requested anonymity because they are not authorized to speak about X, noted that they did not even see Ukraine in the breakdown of the top 20 IP address origins involved in the X attacks.
Traffic from Ukraine was present, but not anywhere near the top of the list. Also some important context.
Don’t worry, the same crack team that can’t figure out how to properly set up a CDN for a second rate social media website are totally competent to fix the $4t federal government.
What's with topics on this matter going off the top page this fast? The services had been intermittent for last couple days, and the current top link goes to Twitter so it's clear that everyone is on it. It warrants a lot more commentaries. Feels like divide-and-conquer is going on.
Thought it was strange that X got hit when they are using Cloudflare. Not much competence left at X I guess. What more have they done? No encryption between CF and origins?
The hackers can probably just launch a new attack from CF. Not like X is checking the headers if they failed with the basic setup.
X forgetting to put some important servers behind Cloudflare is some very important context
> But one researcher from a prominent firm, who requested anonymity because they are not authorized to speak about X, noted that they did not even see Ukraine in the breakdown of the top 20 IP address origins involved in the X attacks.
Traffic from Ukraine was present, but not anywhere near the top of the list. Also some important context.