The few glimmers of details we get confirm to me we need to be concerned about who NSO's technology is being sold to & how it's being used.
I "live chatted" my reading of this to my teammates as my frustration & rage grew. There was so much. I'll limit this to just a few. 2/12
The main two points are: 1. We have strict processes to ensure our technology is not misused in ways that violate human rights. 2. We have no insight into how our customers use our technology.
🤔
This leads in to claims of how little misuse there is. 3/12
balances the need for legit law enforcement activities with the risk that state actors misuse cyber intelligence products against journalists, civil society, dissidents & political opponents, & vulnerable populations - pg 11
I reject this is the choice. It's a false dilemma. 4/x
"Over the past year, we have engaged with numerous NGOs" - pg 11
Who are these NGOs and what was their original position and what is it now? What was learned? Are they coming out now in support? 5/12
Another area that is emphasized is:
"Our customers are required to notify us of any
knowledge they have regarding any misuse or potential misuse of the products that may result in human rights violations."
I really trust customers to report themselves. 6/12
"our CEO includes human rights concerns in nearly all of his “all hands” meetings" - pg 29
Seriously. 32 pages of this BS fluff. 7/12
Their Contracts Provisions on pg 31 begins:
1. The End-User hereby represents and warrants that it and its respective employees and agents: (i)
shall fully Appendix and strictly comply with all applicable domestic laws and regulations
WTF is "Appendix"?!
8/12
The Contracts Provision isn't even taken seriously enough to have a real word there? If we look at the rest of the words, the end user is just agreeing to obey their own laws. There's a lot of things "legal" that are horrifying and absolutely violate human rights. 9/12
So no, I do not commend NSO for this "transparency" report because I don't think there's nothing transparent about it. I was hopeful that maybe a corner was being turned, but this is clearly just a checkbox with hand waving and no real substance. 10/12
As @tiraniddo said to me, "Maybe their plan is to waste your time you could have spent looking for their zero days." That feels about right. 11/12
P.S. "part of our human rights-focused journey" definitely gave me next season of The Bachelorette vibes. 12/12
• • •
Missing some Tweet in this thread? You can try to
force a refresh
This thread from ~yr ago was a turning point for me. Not because the harassment stopped, but because I finally no longer dealt with all this bs predominantly alone. As illogical & irrational as it is, I think I felt shame every time I received one of these messages. 1/x
*I* must have been doing something wrong, *I* must have been less than if all these people took the effort to say these things to me. If colleagues weren’t dealing with this, then *I* must be the problem. I’m *drama*. These were the quiet thoughts. 2/x
And while each time I came out of it knowing those thoughts were incorrect, it was exhausting & took capacity to process the messages and get to that point. Capacity & energy I would have much preferred to spend elsewhere...like maybe my actual work. 3/x
Along with many others in infosec, I've always cautioned against any of the voice activated smart gadgets, largely thinking there's only marginal benefit for the risks of an always-on microphone.
Recovering from surgery with only one usable arm has completely changed my views.1/
Using voice control, which has required turning on the mics on my phone and home mini, has made my quality of life substantially better and even prevented physical pain. 2/
2 days post-op I was staying at family's house & had gone for a nap. I woke up & was completely tangled in the velcro straps from the sling and ice pack. Hair & a pillowcase were involved in the velcro nightmare too. 3/
Can't believe I'm voluntarily wading into this, but here we go.
When you share those full details, that's when I drop everything & get to work (and I usually pull in my teammates too 💁🏽♀️). It's not just another cool vuln, it's something being used to harm. 1/6
As an example, here's how I approach it as soon as the details are out:
-understand the root cause & exploit method
-think of potential detection methods & talk to the folks who can implement them if it's not us 2/6
-find variants that the attackers either already have (and may even be using) or could easily switch to and try to get them fixed at the same time as the original bug
-brainstorm fixes, mitigations, system improvements & share them 3/6
Dondi is a proud #HBCU graduate & attended @aamuedu, earning a B.S. in Math w a focus in Applied Stats, & as an ugrad student, published research in regression analysis & number theory. As a student, Dondi went everywhere w his TI-82 graphing calculator, which he still has.
I’m really fucking tired. On average, about every week I receive some message about how I’m “unskilled”, “P0’s biggest mistake”, “not technical”. And about every other month one of these messages is posted very publicly or emailed to my managers. 1/7
This is nothing new since I first was an intern. It’s damn clear that the comments are bullshit. That the people taking the time to send me these msgs or create the anonymous accounts are telling a lot more about themselves than about me. But it’s still exhausting. 2/7
If you’re getting these messages too, it’s not about you. I’ve quite literally done everything these folks asked: I’ve done novel research at every level between a die on a CPU and applications. I have the CVEs. Large volumes of my work are publicly available...and yet. 3/7
Lately, I've been watching talks from pre-2010. There's so much important infosec work/history out there, but you need to know what to look for.
What are some of your favorite talks, blogs, events, etc from 2012 or before that you'd recommend to those newer to the industry?
For my "learning Windows" adventure, these have been awesome
* Analyzing local privilege escalations in win32k - @mxatone (2008)
* Kernel exploitation – r0 to r3 transitions via KeUserModeCallback -@j00ru (2010)
* Kernel Attacks through User-Mode Callbacks - @kernelpool (BH 2011)