Tasking of SCALAWAG

Open PDF
Creating agency: NSA National Security Agency (US)
Document date: -
Pages: 2
Genre: other
Classification: TOP SECRET SI
Dissemination: REL TO USA, FVEY

An NSA Special Source Operations memo describing bandwidth and latency problems caused by the SCALAWAG bulk voice collection program, and introducing the RETRO Tool — a capability allowing analysts to reach back up to 30 days into a buffer of recorded phone calls from an entire country to retrieve audio that was never individually targeted.

Long Description:
This classified NSA Special Source Operations document describes operational and technical challenges encountered with SCALAWAG (SIGAD US-3310BG), identified as NSA's number one provider of actionable SIGINT on a redacted country. The core problem documented is one of scale: SCALAWAG had grown so prolific in its bulk voice collection that it was sending home far more data than available bandwidth could handle, creating severe latency for high-priority content. To address this, SSO took a series of measures beginning in summer 2011 — deleting large quantities of lower-priority tasking that had gone untouched according to the DOUBLEARROW database, and downgrading other tasking from priority 4 to priority 6. When these measures proved insufficient given continued growth in collection volume, SSO implemented a formal rule on December 15, 2011 prohibiting any Effective Collection Priority 4 or below tasking through the Unified Targeting Tool, and deleted all existing sub-priority-4 tasking. The document's most significant disclosure is its description of the RETRO Tool — described as a "unique one-off capability" existing only at SCALAWAG — which allows analysts to reach nominally 30 days into the past and retrieve audio of calls that were never individually tasked at the time they occurred. The workflow described is telling: analysts are instructed to use metadata from the FASCIA database to identify targets of interest detected in SCALAWAG's environment, retrieve the relevant historical audio, forward it to their NUCLEON account, and only then consider formally tasking the number for future collection. This inverts the traditional surveillance model entirely — rather than identifying a target and then monitoring them, the system records everyone first and allows targeting decisions to be made retroactively. The document also reveals the tension between the program's ambition and its infrastructure constraints. SSO explicitly warns analysts not to artificially inflate tasking priorities just to ensure collection, and urges TOPIs to use the RETRO Tool as the primary SIGDEV mechanism rather than blanket tasking. The instruction to "not task and forget" underscores that the system's bottleneck is not collection capacity — which is effectively unlimited at the intake end — but the bandwidth and storage infrastructure needed to move and retain that data. The Washington Post, which reported on this document in March 2014, withheld the identity of the target country at the request of U.S. officials.

(U) Tasking of SCALAWAG

(TS//SI//REL TO USA, FVEY) SCALAWAG/US-3310BG has long since reached the point where it was collecting and sending home far more than the bandwidth could handle. Over collecting has significantly increased the latency of pri 1-2 content data. Because SCALAWAG is NSA's #1 provider of actionable SIGINT on [REDACTED COUNTRY NAME], measures had to be taken to alleviate pressure on the bandwidth and decrease latency of priority 1-2 data. In the summer of 2011, in an effort decrease the amount of voice content brought home, SSO deleted a large quantity of priority 4 and below tasking that was bringing content and according to the DOUBLEARROW database had not been "touched". Additionally, a change of priority 4 tasking to priority 6 was effected, again based on DOUBLEARROW results. As a result, the latency for primarily pri 1-2 had dropped considerably. However, these actions were still falling short because the volume of collection was increasing ....

(S//SI//REL TO USA, FVEY) On 15 December 2011, SSO collection and program management implemented a rule for SCALAWAG UTT tasking, that basically does not allow any "Effective Collection Priority" (ECP) pri 4 and below tasking. It must be understood that the priority of tasking in UTT IS NOT the same and straight forward as OCTAVE. Analysts must choose fields whose net result is priority 1-3. Additionally, all UTT ECP pri 4 and below tasking was deleted. Since implementation, some TOPIS may have noted a decrease total volume in their SCALAWAG collection delivered to their NUCLEON accounts. Many SCALAWAG users are familiar with and have access to the
RETROSPECTIVE retrieval tool (RETRO TOOL). The RETRO tool is a unique one-off capability that exists only at SCALAWAG. It allows analysts to go nominally 30-days into the past and retrieve audio of interest that was not tasked at the time of the original call. Analyst retrievals should be based on metadata, SRI found in FASCIA, that'll indicate there's a target of interest that's been detected in SCALAWAG's environment. Once the audio is identified, retrieved, and forwarded to your NUCLEON account, analysts would then consider tasking the number in UTT at ECP 1-3, based on the critical need for the data.

(S//SI//REL TO USA, FVEY) Retrieval and forwarding via the RETRO TOOL will significantly reduce bandwidth and latency issues. It will also likely result in getting the audio data back to your NUCLEON account more quickly than if tasked at ECP 4 and below. We strongly request that TOPIs do not artificially inflate the priority of their tasking just to get numbers tasked. SIGDEV/Target development should be accomplished using the RETRO TOOL and subsequent tasking occur based on SIGDEV. TOPIs should make use of the RETRO TOOL whenever possible to retrieve the desired audio content. We do not have the luxury of task and forget.