OK, a lot of us at FTP have been insanely busy, so we didn’t do any really good job covering CISPA, which some see as a bastard child of SOPA. Here’s what I’ve dug up.
CISPA (Cyber Intelligence Sharing And Protection Act) came onto the scene pretty quick earlier this month. It seemed to be an odd mix of overly broad language, added some privacy reviews, and troublingly, let people off the hook for sharing data with the government. It also had a lot of sponsors.
The odd thing with the bill is it seemed “less” SOPA-like than I’d expect, but then had some huge back doors and odd language revolving around security. It seems broad enough that it could be massively misused. The EFF has a roundup here, including amendments.
I’m not sure this is so much the “return of SOPA” as it is “general broad powers.”
It didn’t seem to cause nearly the kerfluffle that SOPA/PIPA did. That was kind of worrysome. Heck, *I* should have been more aware.
The bill got amended like crazy later, which the EFF found pretty lame.
It passed the house on April 26th.
It’s now on to the Sentate to do their own bill, and there’s at least two competing ones: The Cybersecurity Act of 2012 (Leiberman/Collins) and The SECURE IT Act of 2012 (McCain). There’s a nice roundup here.
The Obama Administration is backing the Leiberman/Collins Act, though there’s obviously plenty of concern about it (though from what I can tell it has some legitimate ideas which may be good). The White House issued a veto threat against CISPA.
So that’s where we stand. I can’t say this is “son of SOPA,” its’ broader in a way, which is probably why we didn’t get as much of a firestorm. It’s bad enough (and CISPA supersedes some past law) that I’m concerned.