FCC Says Its Specific Plan To Stop DDoS Attacks Must Remain Secret (arstechnica.com)
An anonymous reader quotes a report from Ars Technica: FCC Chairman Ajit Pai and Democratic lawmakers have been exchanging letters about a May 8 incident in which the public comments website was disrupted while many people were trying to file comments on Pai's plan to dismantle net neutrality rules. The FCC says it was hit by DDoS attacks. The commission hasn't revealed much about what it's doing to prevent future attacks, but it said in a letter last month that it was researching "additional solutions" to protect the comment system. Democratic Leaders of the House Commerce and Oversight committees then asked Pai what those additional solutions are, but they didn't get much detail in return.
"Given the ongoing nature of the threats to disrupt the Commission's electronic comment ling system, it would undermine our system's security to provide a specific roadmap of the additional solutions to which we have referred," the FCC chief information officer wrote. "However, we can state that the FCC's IT staff has worked with commercial cloud providers to implement Internetbased solutions to limit the amount of disruptive bot-related activity if another bot-driven event occurs." The CIO's answers to lawmakers' questions were sent along with a letter from Pai to Reps. Frank Pallone, Jr. (D-N.J.), Elijah Cummings (D-Md.), Mike Doyle (D-Penn.), DeGette (D-Colo.), Robin Kelly (D-Ill.), and Gerald Connolly (D-Va.). The letter is dated July 21, and it was posted to the FCC's website on July 28.
"Given the ongoing nature of the threats to disrupt the Commission's electronic comment ling system, it would undermine our system's security to provide a specific roadmap of the additional solutions to which we have referred," the FCC chief information officer wrote. "However, we can state that the FCC's IT staff has worked with commercial cloud providers to implement Internetbased solutions to limit the amount of disruptive bot-related activity if another bot-driven event occurs." The CIO's answers to lawmakers' questions were sent along with a letter from Pai to Reps. Frank Pallone, Jr. (D-N.J.), Elijah Cummings (D-Md.), Mike Doyle (D-Penn.), DeGette (D-Colo.), Robin Kelly (D-Ill.), and Gerald Connolly (D-Va.). The letter is dated July 21, and it was posted to the FCC's website on July 28.
It was in a drawer next to Trump's plan to defeat ISIS. More details to follow.
I want peace on earth and goodwill toward man.
We are the United States Government! We don't do that sort of thing.
After all, unvetted encryption and security have never failed. And the best security is obscurity!
is no security at all.
I know all of you are concerned about Net Neutrality and would like to submit your claims on our site, but someone decided to attack us when you visited our site. Oh, you want evidence of the hack? Sorry, we cannot provide that. But rest assured, it will be prevented in the future. Oh, you want to know how we will prevent it? Well, that's a secret too. Oh, you don't think it actually happened? No, it did. Don't worry.
Security through obscurity always works! In other news, Ajit recommends moving telnet to port 22 and changing the password from "secret" to "S3CR3T", and they'll never get in as long as you keep it secret. Foolproof!
whoops, now you've gone too far!
the preceding comment is my own and in no way reflects the opinion of the Joint Chiefs of Staff
There was never a DDOS attack. It was a delibarate attemps by the FCC to silence the critics of its plan to kill net neutrality.
Step #1: Listen to the American public and industry leaders and SUPPORT NET NEUTRALITY.
Expect my consultation bill in the mail, Mr. Pai.
The new system only accepts the submissions ajit agrees with.
Not a Trump hater, but it seems like anything done to discourage DDOS attacks needs to be public. I'm not sure how "secret" plans can be helpful on an open internet.
The government learns how to stop DDoS attacks from the civilian sector. What's the big secret there?
Wait, think I found their plan.
Was it the one to roll weak sauce servers with bad failback positions and not code for massive volumes of legit comment requests?
Yeah, it was right here, next to the plan marked Mooch's Retirement Plans.
-- Tigger warning: This post may contain tiggers! --
Given the ongoing nature of the threats to disrupt the Commission's electronic comment ling system, it would undermine our system's security to provide a specific roadmap of the additional solutions to which we have referred
Wow, and the FCC is what I would consider a pretty bland department much like USDA or FCIC. But wow, what a way to totally derail any credibility the department had. Hint, anytime an agency thinks doing something totally opaque to public review is a good idea, it's usually not a good idea.
Not hard to hide an orbiting death laser platform...just to be sure.
You'd be surprised how hard that is, actually.
-- Tigger warning: This post may contain tiggers! --
If obscurity is the primary method of security, meaning "if they discover how we are doing it then they can defeat it," then you have no security. You must plan for the eventuality that someone will know how you do it. So, if the FCC's new method requires that it remain obscure to remain effective, then it might as well have already been compromised. Of course, having an obscure security system that nobody knows about is helpful. Nobody would argue otherwise. But that should just be icing on the cake - a nice little perk. Think of this comparison of a time-lock safe vs. a hidden book box:
Look at a time lock safe:
1. It is known
2. The way it works is known
3. It is effective because of the security measures of the safe
This is opposed to hiding valuables in a hidden book box:
1. If it is not known, it might work
2. If it is not known, it might be discovered through thorough searches and thus fail
3. If it is known, it definitely won't work
If you hide the time lock safe, then you do add a layer of cursory security. However, it is not the location/disguise of the safe that matters. It's the function of the safe's defenses that protect the valuables.
Security by obscurity isn't a security mechanism, rather a puzzle... If getting into your house is simply a matter of finding where you left the Hide-a-key then your house was never secure in the first place.
Mike @ The Geek Pub. Let's Make Stuff!
Not if you throw enough Bothans at the problem.
Bark less. Wag more.
Oh, I thought you meant IRL.
-- Tigger warning: This post may contain tiggers! --
In other words, cloudflare.
If they are using SSL/TLS, this is a problem.
Cloudflare is a giant man in the middle, and a breach of trust between end-users and the websites they wrongly believe they are securely connected to. Sites that use it are subverting the intent of the SSL/TLS certificate system and making the little lock icon meaningless.
See Details
They don't have any plan to stop or even mitigate DDOS attacks. I bet most their "expert" IT staff barely even knows what one is, and the rest of them are the ones actually carrying out the DDOS attacks in the first place.
Nothing more to see here. This country is finished. Move along.
-- just stop accepting public comments?
well, actually, yeah. that is their plan.
they were getting too many public comments, getting "flooded" with comments if you will. and flooding is ddos. so therefore, they just stopped reading the stuff or taking them to consideration so the problem is solved.
world was created 5 seconds before this post as it is.
I personally feel that browsers should consider blocking all external scripts on HTTPS pages unless those scripts have a matching integrity attribute, or at least make valid integrity for foreign scripts a requirement for avoiding the Mixed Content warning.
I imagine just getting it up there would trigger a few alerts.