Last I checked it it just referred to NSA searches on upstream. Tho possible violation is getting upstream metadata and using it for PRISM.
-
-
Replying to @emptywheel @charlie_savage
So wait,
@charlie_savage does the changing of the Upstream search audience broaden it to FBI, or just NSA looking for USP identifiers?3 replies 0 retweets 0 likes -
Replying to @MiekeEoyang @charlie_savage
Also note: To some degree it doesn't matter, as all upstream about is at least ostensibly intl comms, so available under 12333.
1 reply 0 retweets 0 likes -
Replying to @emptywheel @charlie_savage
Except a 12333 database searched by NSA, has a different constitutional set than a combined Upstream/PRISM one searched by FBI.
1 reply 0 retweets 0 likes -
Replying to @MiekeEoyang @charlie_savage
Under the new sharing rules FBI can search that 12333 database now. The biggest diff is AG approval standard actually higher than FISA.
1 reply 3 retweets 0 likes -
Replying to @emptywheel @MiekeEoyang
Not necessarily same/full database. I have been led to believe that agencies that get 12333 sharing have to make case for specific streams
2 replies 2 retweets 0 likes -
Replying to @charlie_savage @MiekeEoyang
Which is not dissimilar from what it does now, no? Except that 702 raw sharing would be limited to existing certs and 12333 would not be.
1 reply 1 retweet 0 likes -
Replying to @emptywheel @MiekeEoyang
Possible it's more limited than that. Supposedly for ex FBI doesn't get all 702 prism raw, only selectors relevant to investigations ...
1 reply 0 retweets 0 likes -
... i.e. CT stuff for sure, but maybe not selectors relevant to trade talks or military maneuvers in South China Sea etc...
2 replies 0 retweets 0 likes -
Replying to @charlie_savage @MiekeEoyang
Right: FBI would be CT, CP, CI, and CYBERZ under known 702 certs. But under 12333 you'd add Transnational Crime, and MOAR CYBERZ.
1 reply 0 retweets 0 likes
And I suspect EO 12333 sharing rules have explicit focus on leak investigations (tho they'd be under CI on 702 as well).
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.