NSA SSO Content Acquisition Optimization
NSA SSO Content Acquisition Optimization
NSA SSO Content Acquisition Optimization
TOP SECRET//SI//NOFORN
TOP SECRET//SI//NOFORN
Yahoo Webmessenger
Update data sent to individuals logged into Yahoos Instant Messenger service online
Online contact status, unread emails in Yahoo inbox Usually small sessions (2-4kB)
Sporadic collection (30,000 60,000 sessions per day) Intermittent bursts of collection against contacts of targets
Large numbers of sessions (20,000+) against a single targeted selector Not collected against the target (online presence/unread email from target) No owner attribution (metadata value limited to fact-of comms for emails, online presence events for buddies)
TOP SECRET//SI//NOFORN
TOP SECRET//SI//NOFORN
Address Books
Email address books for most major webmail are collected as stand-alone sessions (no content present*) Address books are repetitive, large, and metadata-rich Data is stored multiple times (MARINA/MAINWAY, PINWALE, CLOUDs) Fewer and fewer address books attributable to users, targets Address books account for ~ 22% of SSOs major accesses (up from ~ 12% in August)
Access (10 Jan 12) US-3171 DS-200B US-3261 US-3145 US-3180 US-3180 (16 Dec 11) TOTAL Total Sessions 1488453 938378 94132 177663 269794 289318 3257738 Address Books 237067 (16% of trac) 311113 (33% of trac) 2477 (3% of trac) 29336 (16% of trac) 40409 (15% of trac) 91964 (32% of trac) 712366 (22% of trac) Provider Yahoo Hotmail Gmail Facebook Other TOTAL Collected 444743 105068 33697 82857 22881 689246 A;ributed 11009 1115 2350 79437 1175 95086 A;ributed% 2.48% 1.06% 6.97% 95.87% 5.14% 13.80%
TOP SECRET//SI//NOFORN
TOP SECRET//SI//NOFORN
Buddy Lists,Inboxes
Unlike address books, frequently contain content data
Offline messages, buddy icon updates, other data included Webmail inboxes increasingly include email content Most collection is due to the presence of a target on a buddy list where the communication is not to, from, or about that target
Identifying buddylists and inboxes without content (or without useful content) an ongoing challenge
TOP SECRET//SI//NOFORN
TOP SECRET//SI//NOFORN
Scenario:
@yahoo
Sep 2011 @yahoo.com (tasked S2E, asw Iran Quds Force) has his/her Yahoo account hacked by an unknown actor, sends out spam email to his/her contact list:
TOP SECRET//SI//NOFORN
TOP SECRET//SI//NOFORN
Scenario:
@yahoo
@yahoo.com has a number of Yahoo groups in his/her contact list, some with many hundreds or thousands of members At DS-200B in particular, collection spiked as:
The initial spam messages were sent (and collected) Inboxes of email recipients were viewed by contact list Messages were sometimes viewed, but more often sent as precached views on Google and Yahoo (along with inboxes) Inboxes where the recipient did not delete the spam message continued to be collected every time they were viewed Some recipients added @yahoo.com to their address books (possibly as a spam defeat?) address books were collected every time
TOP SECRET//SI//NOFORN
TOP SECRET//SI//NOFORN
Scenario:
120000 100000 80000 60000 40000 20000 0
@yahoo
TOP SECRET//SI//NOFORN
TOP SECRET//SI//NOFORN
Scenario:
@yahoo
@yahoo.com emergency detasked from DS-200B and US-3171 at 13:04Z on 20 Oct Numerous first-order address books and inboxes collected meant tasked selectors on address books or buddy lists of contacts of @yahoo.com also affected:
@yahoo.com and detasked off US-3171 at 13:10Z on 20 Sep @gmail.com emergency
Memorializing to PINWALE only address books and inboxes owned by target selectors would have reduced PINWALE volumes 90%+
Site XKEYSCOREs would buffer data for SIGDEV purposes Metadata from known owner address books and inboxes stored regardless
TOP SECRET//SI//NOFORN
TOP SECRET//SI//NOFORN
Mobile IMAP
IMAP protocol used by email clients to fetch mail from server(s) Not designed for devices with intermittent connections (i.e. mobile phones) Android implementation in particular uses a lot of bandwidth
TOP SECRET//SI//NOFORN