Reflects the broad spectrum #spyware harms happen.
But *also* and critically, situations where vendors should expect that their product, once sold, will inevitably be abused.
#Pegasus factor: Ouch. NSO again would get dinged.
7/ I initially expected #SpywareEO to look like a allow/deny aka "blacklist" of spyware sellers..
But the EO's conduct based definitions = constant shell game of vendors corporate identities is blunted.
Even applies to companies that haven't been formed yet.
Probably better.
8/ Lots of spyware companies absolutely know what they are doing.
What's especially interesting is the term "remove" to describe risks.
Not the milquetoast & unverifiable "mitigate."
#SpywareEO is saying: cancel the contracts & more.
And you may still be toast. Do it now.
9/ Reports in the past that USG entities may have occasionally facilitated spyware purchases / acquisition by other governments.
If the #SpywareEO abuse/natsec/counterintelligence triggers are met... that door now closes.
10/ How does the USG know if #spyware vendors hit the #SpywareEO's triggers?
The EO contains a robust set of reporting requirements around misuses from the Intel community & procurement reporting.
Seems intended to prevent vendors from slipping through the cracks.
11/ Use of the "operational use" term is interesting.
And creates carve outs for things like testing & analysis.
Analogy: USG can buy an anti-tank missile from a shady entity to test it against armor, but can't reward the vendor by equipping the whole military with them.
12/ Takeaway: The #SpywareEO is the first comprehensive action by any government on #spyware.
It was clearly drafted to pump the breaks on proliferation & is written with a good understanding the slippery nature of the industry.
It closes many loopholes.
13/ Whenever the USG regulates there's always temptation to speculate about protectionism for American companies.
But reading the #SpywareEO...these provisions hit US-based spyware companies just as hard if they meet the triggers / contribute to proliferation.
Good.
14/ Every government wants to not tie their hands too tightly, so there is a waiver provision.
But what's interesting is how restricted this is. This is a very high bar.
The #SpywareEO is not designed to be easily circumvented by someone in a corner of the USG bureaucracy.
15/ I've spent over a decade researching commercial spyware.
The #spywareEO is one of the most consequential actions to blunt proliferation that I've seen a government take.
So, where do we go from here?
16/ While the #SpywareEO addresses federal procurement, it doesn't hit state & local agencies.
And we know these are targets for sales by NSO Group & others.
This is going to be a really important area in coming years.
NEW: @WhatsApp caught & fixed a sophisticated zero click attack...
Now they've published an advisory about it.
Say attackers combined the exploit with an @Apple vulnerability to hack a specific group of targets (i.e. this wasn't pointed at everybody)
Quick thoughts 1/
Wait, you say, haven't I heard of @WhatsApp zero-click exploits before?
You have.
A big user base makes a platform big target for exploit development.
Think about it from the attacker's perspective: an exploit against a popular messenger gives you potential access to a lot of devices.
You probably want maximum mileage from that painstakingly developed, weaponized, and tested exploit code you created/ purchased (or got bundled into your Pegasus subscription).
3/ The regular tempo of large platforms catching sophisticated exploits is a good sign.
They're paying attention & devoting resources to this growing category of highly targeted, sophisticated attacks.
But it's also a reminder of the magnitude of the threat out there...
WHOA: megapublisher @axelspringer is asking a German court to ban an ad-blocker.
Their claim that should make everyone nervous:
The HTML/ CSS code of websites are protected computer programs.
And influencing they are displayed (e.g by removing ads) violates copyright.
1/
2/ Preventing ad-blocking would be a huge blow to German cybersecurity and privacy.
There are critical security & privacy reasons to influence how a websites code gets displayed.
Like stripping out dangerous code & malvertising.
Or blocking unwanted trackers.
This is why most governments do it on their systems.
3/Defining HTML/CSS as a protected computer program will quickly lead to absurdities touching every corner of the internet.
Just think of the potential infringements:
-Screen readers for the blind
-'Dark mode' bowser extensions
-Displaying snippets of code in a university class
-Inspecting & modifying code in your own browser
-Website translators
3/ What still gives me chills is how many cases surfaced of people killed by cartels... or their family members... getting targeted with Pegasus spyware.
The #PegasusProject found even more potential cases in Mexico.