One of the major tasks of PCLOB is to regulate the 702 surveillance activities of the NSA. Take away the ability to ask critical technical questions at the member-level, this amounts to taking the NSA’s technical statements at face value with no deeper follow up.
-
-
Replying to @matthew_d_green @WatsonLadd
To what extent does 702 oversight turn on technical questions rather than legal ones? Not fair to attribute to “tech” what “security/privacy twitter” thinks about things, but security/privacy twitter has been pretty terrible on FISA.
2 replies 0 retweets 3 likes -
Replying to @tqbf @WatsonLadd
To the extent that the PCLOB’s main activity was to obtain a clear technical understanding of what the NSA’s technical architecture was in implementing 702.pic.twitter.com/y1BmtSIdXl
2 replies 0 retweets 0 likes -
Which is to say that, without high-level expertise on the committee, they would have been entirely at the mercy of the IC’s representations of how the program worked. It goes without saying that any legal interpretations drawn from that understanding would be GIGO.
1 reply 0 retweets 0 likes -
Replying to @matthew_d_green @WatsonLadd
At the time you’re talking about, weren’t they entirely at the mercy of NSA’s representations?
1 reply 0 retweets 0 likes -
Replying to @tqbf @WatsonLadd
They had the ability to ask specific and detailed technical questions and (I presume) receive more complete answers. But without anyone who could do so, they were essentially receiving a PowerPoint presentation.
2 replies 0 retweets 0 likes -
Replying to @matthew_d_green @WatsonLadd
Right, I’m just saying that by these terms, everything PCLOB has done w/r/t/ 702 to date has been GIGO — unless I’m missing part of your argument.
1 reply 0 retweets 0 likes -
Replying to @tqbf @WatsonLadd
My assumption is that the IC does not lie to their oversight boards. But that they might not *volunteer* specific details that could fundamentally improve the board’s understanding of, say, the amount of incidental collection — in a way that would cast the IC in a bad light.
2 replies 0 retweets 1 like -
Note PCLOB didn't mention the cyber functions of 702, even though they knew about them and concerns about the kind of selectors used are more technically complex. That's an example where they were ill-served w/o a tech expert.
1 reply 0 retweets 3 likes -
Replying to @emptywheel @matthew_d_green and
Note, too, that the FISC definition of metadata remains redacted, and Congress just sort of blew wind on that issue in this year's reauth.
@SteveBellovin, of course, has perfect expertise for that but came in too late for the review.2 replies 1 retweet 1 like
Also one thing I find really obnoxious: PCLOB's 702 report was dated July 2, 2014. On August 26, 2014, FISC approved the Tor (and other location obscured) exception, a vast new impact on US persons. That timing was, surely, not accidental.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.