<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>surveillance - The Black Vault</title>
	<atom:link href="https://www.theblackvault.com/documentarchive/tag/surveillance/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.theblackvault.com/documentarchive</link>
	<description>Discover the Truth</description>
	<lastBuildDate>Wed, 16 Sep 2026 23:59:53 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.3</generator>

<image>
	<url>https://www.theblackvault.com/documentarchive/wp-content/uploads/2020/06/cropped-siteicon-2-150x150.jpg</url>
	<title>surveillance - The Black Vault</title>
	<link>https://www.theblackvault.com/documentarchive</link>
	<width>32</width>
	<height>32</height>
</image> 
<site xmlns="com-wordpress:feed-additions:1">87123917</site>	<item>
		<title>NSA&#8217;s PROMIS: What the Declassified Records Actually Show</title>
		<link>https://www.theblackvault.com/documentarchive/nsas-promis-what-the-declassified-records-actually-show/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=nsas-promis-what-the-declassified-records-actually-show</link>
		
		<dc:creator><![CDATA[John Greenewald]]></dc:creator>
		<pubDate>Wed, 16 Sep 2026 16:00:00 +0000</pubDate>
				<category><![CDATA[Intelligence]]></category>
		<category><![CDATA[National Security Agency]]></category>
		<category><![CDATA[NSA]]></category>
		<category><![CDATA[prism]]></category>
		<category><![CDATA[surveillance]]></category>
		<guid isPermaLink="false">http://www.theblackvault.com/documentarchive/?p=826</guid>

					<description><![CDATA[<p>PROMIS has accumulated decades of controversy, competing claims and, at times, confusion over what the name itself actually refers to. The records released by the National Security Agency provide an important distinction. The NSA&#8217;s PROMIS, or Product Management Information System, was an intelligence-product management database developed during the 1970s. According to records released to The [...]</p>
<p>The post <a href="https://www.theblackvault.com/documentarchive/nsas-promis-what-the-declassified-records-actually-show/">NSA’s PROMIS: What the Declassified Records Actually Show</a> first appeared on <a href="https://www.theblackvault.com/documentarchive">The Black Vault</a>.</p>]]></description>
										<content:encoded><![CDATA[<p>PROMIS has accumulated decades of controversy, competing claims and, at times, confusion over what the name itself actually refers to.</p>
<p>The records released by the National Security Agency provide an important distinction.</p>
<p>The NSA&#8217;s PROMIS, or Product Management Information System, was an intelligence-product management database developed during the 1970s. According to records released to The Black Vault under the Freedom of Information Act (FOIA), the system was designed to organize information associated with intelligence reports and give senior signals intelligence managers a way to search, analyze and manage information about those products.</p>
<p>It should not simply be equated with the better-known Prosecutor&#8217;s Management Information System, also called PROMIS, associated with INSLAW, Inc. and the Department of Justice.</p>
<p>That distinction became a central issue when the Justice Department investigated allegations surrounding INSLAW and its software in the 1990s. DOJ ultimately concluded in 1994 that there was no credible evidence that INSLAW&#8217;s PROMIS had been improperly distributed elsewhere in the federal government or to foreign governments. A subsequent Court of Federal Claims proceeding also rejected INSLAW&#8217;s claims.</p>
<p>Yet NSA did, in fact, have something called PROMIS.</p>
<p>The records obtained by The Black Vault document what it was, and then a FOIA request filed in 2013 to uncover those records produced one final surprise nearly 13 years later.</p>
<p><strong>Two Systems Called PROMIS</strong></p>
<p>The Black Vault&#8217;s pursuit began with a passage contained in Justice Department records concerning the INSLAW controversy.</p>
<p>On November 14, 2013, The Black Vault filed a FOIA request with NSA seeking:</p>
<p>&#8220;a copy of all records pertaining to the NSA&#8217;s use of the computer program PROMIS.&#8221;</p>
<p>The request specifically cited a Justice Department account stating that investigators had contacted NSA to determine whether the agency &#8220;used or developed any program called PROMIS.&#8221; According to that account, NSA explained that it had developed a database in the 1970s using the M204 database system and called it PROMIS, an acronym for Product Related On-line Management Information System.</p>
<p>The NSA records subsequently released provide considerably more detail.</p>
<p>A draft Justice Department report sent to NSA for review in May 1994 recounts interviews with NSA personnel about the issue. The document states:</p>
<p>&#8220;the NSA maintains a database known as Product Management Information System, or &#8216;PROMIS.'&#8221;</p>
<p>It explains that &#8220;Product&#8221; was an NSA term for intelligence reports and that the database contained &#8220;abstracts of intelligence reports generated by various parts of the NSA.&#8221;</p>
<p>Most importantly, the DOJ account records an explicit distinction between NSA&#8217;s database and the software at the center of the INSLAW controversy:</p>
<p>&#8220;the NSA &#8216;PROMIS&#8217; is not a software program, but rather is an application of the M204 database management system.&#8221;</p>
<p>One NSA employee interviewed by DOJ said she had participated in the original development of the database during the 1970s. According to the document, it was developed &#8220;primarily to allow the accumulation of management information regarding the productivity of various NSA divisions.&#8221;</p>
<p>That distinction is important because the Justice Department&#8217;s own PROMIS was the Prosecutor&#8217;s Management Information System, a case-management system used by U.S. Attorneys&#8217; Offices. DOJ records describe that system as a tool for maintaining and tracking information involving defendants, crimes, charges, court events and witnesses.</p>
<p>The common acronym helped produce decades of confusion, but the NSA records released through this FOIA case document an independently developed intelligence-product management database.</p>
<p><strong>Building PROMIS Inside NSA</strong></p>
<p>The released records trace the NSA system to early 1974.</p>
<p>A January 15, 1974, memorandum titled &#8220;SIGINT Management Data Bases&#8221; described the underlying management problem. The Deputy Director for Operations wrote that existing management statistics were prepared separately by different production groups and therefore were not available in a form that fully met his needs.</p>
<p>The memorandum called for:</p>
<p>&#8220;a system which will cut across Group lines&#8221;</p>
<p>and provide management data while allowing officials to respond to Intelligence Community questions.</p>
<p>Another memorandum, dated January 21, 1974, described plans to implement:</p>
<p>&#8220;an on-line computer system to provide product-related data needed at the DDO level and outside the agency.&#8221;</p>
<p>The document also made clear that security was built into the design requirements. Because some of the information was sensitive, the system would need controls governing both security and access. The memorandum stated that access to data, &#8220;either in part or in whole,&#8221; would be restricted to those who actually needed it.</p>
<p>A February 12, 1974, memorandum described the existing process the proposed database was intended to improve. The older Offline Coversheet Processing system was characterized as costly and inadequate, with manual data conversion alone consuming approximately 500 man-hours each quarter. Output could lag by roughly two weeks, while the memorandum estimated an error rate of seven to eight percent.</p>
<p>By May 1974, the name PROMIS was explicitly appearing in the records.</p>
<p>A May 8 memorandum titled &#8220;PROMIS Content and Timeliness Requirements&#8221; discussed a study of the database and asked what SIGINT products should be included initially, what products should eventually be covered and how current the information needed to be.</p>
<p>The memorandum stated:</p>
<p>&#8220;We expect to conclude the study and to recommend a system for PROMIS in the very near future.&#8221;</p>
<p>The surviving documents therefore portray PROMIS not as a mysterious stand-alone surveillance package, but as a management and retrieval system built around NSA intelligence &#8220;products,&#8221; with requirements involving searchable information, access controls, timeliness and the handling of sensitive SIGINT data.</p>
<p><strong>The Black Vault&#8217;s FOIA Pursuit</strong></p>
<p>Obtaining those records became its own unusually long story.</p>
<p>The Black Vault filed the request on November 14, 2013.</p>
<p>By March 2016, NSA had located a substantial volume of potentially responsive material but sought $440 in fees to continue processing the request. The Black Vault did not pay the requested amount, and there was no expectation that a release would follow.</p>
<p>Then, unexpectedly, one did.</p>
<p>On October 4, 2018, nearly five years after the original request, NSA sent The Black Vault a partial release. The agency wrote:</p>
<p>&#8220;Your request has been processed under the FOIA and some of the documents you requested are enclosed.&#8221;</p>
<p>NSA withheld portions under FOIA Exemptions 1, 3 and 6, citing classified national-security information, statutory protections applicable to NSA activities and personal privacy.</p>
<p>Significantly, the October 4 letter also stated:</p>
<p>&#8220;Additional documents will be provided when their processing is complete.&#8221;</p>
<p>The first release included internal NSA memoranda from the 1970s describing the creation and requirements of the system, along with Justice Department correspondence concerning its later INSLAW investigation.</p>
<p>A second, much larger release followed on October 22, 2018. That production contained 85 pages, including a PROMIS user&#8217;s manual and additional memoranda. NSA characterized that production as the final release in the case. The Black Vault subsequently archived the material on this page.</p>
<p>And for years, that appeared to be the end of FOIA case 75611.</p>
<p>It wasn&#8217;t.</p>
<p><strong>An Unexpected Letter — Nearly Eight Years Later</strong></p>
<p>On April 29, 2026, The Black Vault received another response from NSA.</p>
<p>There had been no indication to The Black Vault that the 2013 request remained open, and nearly eight years had passed since NSA&#8217;s October 2018 releases.</p>
<p>Nevertheless, NSA&#8217;s new letter identified the same underlying November 14, 2013 request and described the 2026 correspondence as:</p>
<p>&#8220;a final response to your Freedom of Information Act (FOIA) request&#8221;</p>
<p>The agency then provided an explanation for why a case that had seemingly ended years earlier had suddenly produced another record:</p>
<p>&#8220;During a review of our files, we located one document that was not provided to you with our final response to your request.&#8221;</p>
<p>NSA said it had reviewed the newly located document under FOIA and released it with redactions. Portions were withheld under the statutory protection applicable to NSA, while NSA also stated that the CIA had requested protection of CIA information under FOIA Exemptions 6 and 3.</p>
<p>The newly released record was dated February 8, 1978.</p>
<p>Its subject was:</p>
<p>&#8220;Regular PROMIS Listings for CIA&#8221;</p>
<p>That document added a significant piece to the historical record.</p>
<p>Addressed to the DDO from NSA&#8217;s Chief, V, the memorandum states that an individual identified as being with CIA/COMP had asked NSA to provide &#8220;regular quarterly PROMIS listings&#8221; for certain sites. Portions identifying the sites remain redacted.</p>
<p>The memorandum indicates that NSA had previously provided the information on a &#8220;one-time basis&#8221; the preceding August. The author then questioned whether NSA should establish recurring distribution:</p>
<p>&#8220;I don&#8217;t see any grounds for standing fast on one-time lists, since we are providing monthly listings for [redacted]&#8221;</p>
<p>and noted that another party was &#8220;obviously aware of this agreement.&#8221;</p>
<p>The identities and portions of the operational context remain withheld, preventing a complete reconstruction of what information was being supplied and to whom. The document does, however, establish that by 1978 NSA officials were discussing providing CIA personnel with recurring PROMIS-generated listings and that at least one earlier PROMIS listing had already been supplied.</p>
<p><strong>What the Records Establish — and What They Do Not</strong></p>
<p>The documents now accumulated through this FOIA case establish that NSA developed a system called PROMIS during the 1970s; that the name referred to a product-management database associated with intelligence reporting; that the system grew out of an effort to replace or supplement cumbersome offline management processes; and that its design contemplated searchable product information with controls over sensitive SIGINT data.</p>
<p>They also show that PROMIS information crossed organizational boundaries. The January 1974 planning records contemplated information needed &#8220;outside the agency,&#8221; while the newly released 1978 memorandum documents discussions about recurring PROMIS listings for CIA.</p>
<p>What these records do not establish is equally important.</p>
<p>They do not demonstrate that NSA&#8217;s PROMIS was INSLAW&#8217;s Prosecutor&#8217;s Management Information System. In fact, the Justice Department material contained within NSA&#8217;s own release specifically records NSA personnel distinguishing the agency&#8217;s PROMIS database from a separate software program. Nor do the released records, standing alone, substantiate broader claims that have circulated for decades connecting PROMIS to later NSA surveillance systems.</p>
<p>The documentary record supports a narrower conclusion: NSA developed and operated a PROMIS database for managing intelligence-product information beginning in the 1970s, and surviving records show the system being discussed internally and in connection with information provided to the CIA.</p>
<p>The history of the FOIA request has now lasted almost as long as some modern government information systems themselves. A request submitted in November 2013 produced records in 2018, appeared finished, and then resurfaced without warning in April 2026 when NSA discovered that a responsive 1978 document had been left out of its earlier final production.</p>
<p>Whether additional responsive records remain undiscovered is unknown. NSA&#8217;s April 29, 2026, letter again labels its response &#8220;final.&#8221;</p>
<p>For now, the documents below represent the record released by the government, including the document NSA itself found nearly eight years after its previous final response.</p>
<h3>Document Archive</h3>
<h4>Department of Justice (DOJ)</h4>
<p><img decoding="async" src="https://www.theblackvault.com/images/pdf.gif" alt="" /> <a href="https://documents.theblackvault.com/documents/nsa/DOJ-OIP-INSLAW_1993.pdf">Report of Special Counsel Nicholas J. </a><a href="https://documents.theblackvault.com/documents/nsa/DOJ-OIP-INSLAW_1993.pdf">Bua to the Attorney General of the United States Regarding the Allegations of INSLAW, Inc., March 1993, and the 1994 DOJ Report on INSLAW/PROMIS matter, released by the Department of Justice (DOJ) Office of Information Policy (OIP)</a> [465 Pages, 11MB] &#8211; Special thanks to <a href="http://www.governmentattic.org/" target="_blank" rel="noopener">GovernmentAttic.org</a> for this record.</p>
<h4>National Security Agency (NSA)</h4>
<p><img decoding="async" src="https://www.theblackvault.com/images/pdf.gif" alt="" /> <a href="https://documents2.theblackvault.com/documents/nsa/75611B.pdf">NSA Documents Regarding PROMIS</a>, Released 4 October 2018 [17 Pages, 2.7MB] &#8211; In March of 2016, see below, the NSA required a $440 payment in order to continue to process my request on PROMIS. Although I did not respond, I was surprised to receive this in October of 2018. It appears that this is only part of what the NSA has on PROMIS, and additional records are still being processed. I will add them when they are released to me.</p>
<p><img decoding="async" src="https://www.theblackvault.com/images/pdf.gif" alt="" /> <a href="https://documents2.theblackvault.com/documents/nsa/promis-75611c.pdf">NSA Documents Regarding PROMIS</a>, Released 22 October 2018 [85 Pages, 8MB] &#8211; This release includes the user&#8217;s manual of the PROMIS system, various memorandums and more. One document was withheld entirely and this, according to the NSA, is now the final release of information.</p>
<p><img decoding="async" src="https://www.theblackvault.com/images/pdf.gif" alt="" /> <a href="https://documents3.theblackvault.com/documents/nsa/76511D.pdf">NSA Documents Regarding PROMIS</a>, Released 22 October 2018 [3 Pages, 1MB]</p>
<p><img decoding="async" src="https://www.theblackvault.com/images/pdf.gif" alt="" /> <strong>Payment Estimate Letter (Read Above)</strong> <a href="https://documents.theblackvault.com/documents/nsa/nsa-promis.pdf">Letter regarding the NSA use of the PROMIS System</a> [4 Pages, 1.1MB] &#8211; The NSA did find a considerable amount of documents, however, they are requiring a payment of $440 for the release of the material.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<hr />
<p>&nbsp;</p><p>The post <a href="https://www.theblackvault.com/documentarchive/nsas-promis-what-the-declassified-records-actually-show/">NSA’s PROMIS: What the Declassified Records Actually Show</a> first appeared on <a href="https://www.theblackvault.com/documentarchive">The Black Vault</a>.</p>]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">826</post-id>	</item>
		<item>
		<title>CARNIVORE (DCS1000): FBI Files on Their Email and Electronic Communication Monitoring Software</title>
		<link>https://www.theblackvault.com/documentarchive/carnivore-dcs1000-fbi-files-on-their-email-and-electronic-communication-monitoring-software/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=carnivore-dcs1000-fbi-files-on-their-email-and-electronic-communication-monitoring-software</link>
		
		<dc:creator><![CDATA[John Greenewald]]></dc:creator>
		<pubDate>Thu, 27 Jun 2024 05:50:16 +0000</pubDate>
				<category><![CDATA[Controversies]]></category>
		<category><![CDATA[Federal Bureau of Investigation (FBI) Collection]]></category>
		<category><![CDATA[Government]]></category>
		<category><![CDATA[Carnivore]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[FBI]]></category>
		<category><![CDATA[surveillance]]></category>
		<guid isPermaLink="false">http://www.theblackvault.com/documentarchive/?p=6478</guid>

					<description><![CDATA[<p>The below documents began being published here on The Black Vault in 2018, as the FBI released them. The final response for this FOIA case came in August of 2024, with multiple updates through that timeframe. In October of 2024, The Black Vault added the August release for download, and since this is final release [...]</p>
<p>The post <a href="https://www.theblackvault.com/documentarchive/carnivore-dcs1000-fbi-files-on-their-email-and-electronic-communication-monitoring-software/">CARNIVORE (DCS1000): FBI Files on Their Email and Electronic Communication Monitoring Software</a> first appeared on <a href="https://www.theblackvault.com/documentarchive">The Black Vault</a>.</p>]]></description>
										<content:encoded><![CDATA[<p><em>The below documents began being published here on The Black Vault in 2018, as the FBI released them. The final response for this FOIA case came in August of 2024, with multiple updates through that timeframe. In October of 2024, The Black Vault added the August release for download, and since this is final release for the case, this page will likely not be updated again. All documents are available below this article.</em></p>
<hr />
<p>In the late 1990s and early 2000s, the FBI&#8217;s Carnivore system drew considerable attention and debate. Unveiled during this period, Carnivore was a sophisticated email wiretapping system designed to intercept and analyze digital communications. The system&#8217;s capabilities and the implications for privacy and civil liberties were subjects of intense scrutiny and concern among privacy advocates, Internet service providers (ISPs), and the public at large.</p>
<p>Carnivore, officially known as DCS1000, was a network diagnostic tool utilized by the FBI to monitor and intercept email and other online communications. The system was installed at an ISP’s premises and was capable of scanning vast amounts of digital data passing through the ISP’s network. Carnivore specifically targeted communications of suspects under investigation, allowing the FBI to capture emails, chat sessions, and other forms of online interactions.</p>
<p>The Carnivore system operated by tapping into the ISP&#8217;s network and filtering the data packets that flowed through it. According to an internal FBI document, the system was designed to &#8220;ensure that only the exact communications authorized by the court to be intercepted are what is intercepted&#8221;​​. This meant that Carnivore could be configured to capture only the communications of a specific target while excluding all other traffic.</p>
<p><a href="https://www.theblackvault.com/documentarchive/wp-content/uploads/2018/09/2024-06-27_04-58-20.png"><img fetchpriority="high" decoding="async" class="alignright size-medium wp-image-19720" src="https://www.theblackvault.com/documentarchive/wp-content/uploads/2018/09/2024-06-27_04-58-20-300x199.png" alt="" width="300" height="199" srcset="https://www.theblackvault.com/documentarchive/wp-content/uploads/2018/09/2024-06-27_04-58-20-300x199.png 300w, https://www.theblackvault.com/documentarchive/wp-content/uploads/2018/09/2024-06-27_04-58-20-150x100.png 150w, https://www.theblackvault.com/documentarchive/wp-content/uploads/2018/09/2024-06-27_04-58-20-450x299.png 450w, https://www.theblackvault.com/documentarchive/wp-content/uploads/2018/09/2024-06-27_04-58-20-600x399.png 600w, https://www.theblackvault.com/documentarchive/wp-content/uploads/2018/09/2024-06-27_04-58-20.png 724w" sizes="(max-width: 300px) 100vw, 300px" /></a>The deployment of Carnivore was subject to strict legal guidelines and required a court order based on probable cause. The FBI had to demonstrate that the interception of communications was necessary for an ongoing investigation and that it would yield evidence of criminal activity. The court order specified the scope of the surveillance, including the types of communications to be intercepted and the duration of the surveillance.</p>
<p>Despite these legal safeguards, privacy advocates raised significant concerns about the potential for abuse and the broader implications for digital privacy. A key issue was the transparency and accountability of the Carnivore system. ISPs and privacy groups worried that the system could be used for more extensive monitoring than intended, potentially capturing the communications of individuals not under investigation.</p>
<p>In a letter to Congress, John E. Collingwood, Assistant Director of the FBI’s Office of Public and Congressional Affairs, emphasized that Carnivore was used &#8220;only when Internet Service Providers are unable on their own to restrict interceptions within the narrow confines of the controlling court order&#8221;​​. However, ISPs expressed doubts about their ability to verify that the FBI adhered strictly to these limitations once Carnivore was installed on their networks.</p>
<p>The reaction from the Internet industry was mixed. Some ISPs resisted the installation of Carnivore on their networks, citing concerns about the system&#8217;s impact on network performance and the privacy of their customers. In one notable case, EarthLink, a major ISP, refused to install Carnivore, arguing that it could cause disruptions to their service and compromise customer privacy​​.</p>
<p>EarthLink&#8217;s concerns were not isolated. The American Civil Liberties Union (ACLU) and other privacy organizations filed Freedom of Information Act (FOIA) requests to uncover more details about Carnivore’s technical capabilities and its use in investigations. The ACLU&#8217;s efforts aimed to obtain the source code of Carnivore, which would reveal the inner workings of the system and potentially confirm whether it could be used for broader surveillance than officially stated​​.</p>
<p>The controversy surrounding Carnivore led to calls for greater oversight and transparency in the deployment of digital surveillance tools. Critics argued that without independent verification of the system’s operations, there was no way to ensure that the FBI&#8217;s use of Carnivore was consistent with legal requirements and respected individual privacy rights.</p>
<p>In response to these concerns, the FBI conducted briefings with industry specialists and members of Congress to explain how Carnivore worked and the measures in place to prevent abuse. However, skepticism remained, and the debate over digital surveillance and privacy continued to evolve.</p>
<p>By circa 2005, it was reported that Carnivore had been replaced by more commercially available software​​. This shift indicated an evolution in the FBI&#8217;s approach to digital surveillance, moving away from proprietary systems like Carnivore to leveraging advancements in commercial technology.</p>
<p>Carnivore represented a significant development in law enforcement&#8217;s ability to monitor digital communications. While it provided a powerful tool for investigating and preventing criminal activity, it also raised critical questions about the balance between security and privacy in the digital age. As technology continues to advance and digital communication becomes even more integral to daily life, the need for clear legal frameworks and robust oversight mechanisms remains essential to protect civil liberties while enabling effective law enforcement.</p>
<p>In June of 2018, The Black Vault requested all FBI documents about the system. In July of 2018, the first release of records was received. In June of 2024, a second batch of records were released.</p>
<h3>Document Archive</h3>
<h4><img decoding="async" src="https://www.theblackvault.com/images/pdf.gif" alt="" /> <a href="https://documents2.theblackvault.com/documents/fbifiles/carnivore-fbi1.pdf">FBI Release #1 on CARNIVORE</a> <strong>&#8211; [608 Pages, 377MB] &#8211; Released July 2018</strong></h4>
<h4><img decoding="async" src="https://www.theblackvault.com/images/pdf.gif" alt="" /> <a href="https://documents3.theblackvault.com/documents/fbifiles/carnivore-fbi2.pdf">FBI Release #2 on CARNIVORE</a> <strong>&#8211; [468 Pages, 220MB] &#8211; </strong><strong>Released June 2024</strong></h4>
<h4><img decoding="async" src="https://www.theblackvault.com/images/pdf.gif" alt="" /> <a href="https://documents3.theblackvault.com/documents/fbifiles/carnivore-fbi3.pdf">FBI Release #3 on CARNIVORE</a> <strong>&#8211; [443 Pages, 265MB] &#8211; </strong><strong>Released August 2024</strong></h4>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<hr />
<p>&nbsp;</p><p>The post <a href="https://www.theblackvault.com/documentarchive/carnivore-dcs1000-fbi-files-on-their-email-and-electronic-communication-monitoring-software/">CARNIVORE (DCS1000): FBI Files on Their Email and Electronic Communication Monitoring Software</a> first appeared on <a href="https://www.theblackvault.com/documentarchive">The Black Vault</a>.</p>]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">6478</post-id>	</item>
		<item>
		<title>NSA Surveillance Program: PRISM</title>
		<link>https://www.theblackvault.com/documentarchive/nsa-surveillance-program-prism/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=nsa-surveillance-program-prism</link>
		
		<dc:creator><![CDATA[John Greenewald]]></dc:creator>
		<pubDate>Sun, 22 Nov 2020 02:31:08 +0000</pubDate>
				<category><![CDATA[Intelligence]]></category>
		<category><![CDATA[NSA]]></category>
		<category><![CDATA[prism]]></category>
		<category><![CDATA[surveillance]]></category>
		<guid isPermaLink="false">https://www.theblackvault.com/documentarchive/?p=12489</guid>

					<description><![CDATA[<p>Background PRISM is a code name for a program under which the United States National Security Agency (NSA) collects internet communications from various U.S. internet companies. The program is also known by the SIGAD US-984XN. PRISM collects stored internet communications based on demands made to internet companies such as Google LLC under Section 702 of [...]</p>
<p>The post <a href="https://www.theblackvault.com/documentarchive/nsa-surveillance-program-prism/">NSA Surveillance Program: PRISM</a> first appeared on <a href="https://www.theblackvault.com/documentarchive">The Black Vault</a>.</p>]]></description>
										<content:encoded><![CDATA[<h3>Background</h3>
<p>PRISM is a code name for a program under which the United States National Security Agency (NSA) collects internet communications from various U.S. internet companies. The program is also known by the SIGAD US-984XN. PRISM collects stored internet communications based on demands made to internet companies such as Google LLC under Section 702 of the FISA Amendments Act of 2008 to turn over any data that match court-approved search terms. Among other things, the NSA can use these PRISM requests to target communications that were encrypted when they traveled across the internet backbone, to focus on stored data that telecommunication filtering systems discarded earlier, and to get data that is easier to handle.</p>
<p>PRISM began in 2007 in the wake of the passage of the Protect America Act under the Bush Administration. The program is operated under the supervision of the U.S. Foreign Intelligence Surveillance Court (FISA Court, or FISC) pursuant to the Foreign Intelligence Surveillance Act (FISA). Its existence was leaked six years later by NSA contractor Edward Snowden, who warned that the extent of mass data collection was far greater than the public knew and included what he characterized as &#8220;dangerous&#8221; and &#8220;criminal&#8221; activities. The disclosures were published by The Guardian and The Washington Post on June 6, 2013. Subsequent documents have demonstrated a financial arrangement between the NSA&#8217;s Special Source Operations (SSO) division and PRISM partners in the millions of dollars.</p>
<p>Documents indicate that PRISM is &#8220;the number one source of raw intelligence used for NSA analytic reports&#8221;, and it accounts for 91% of the NSA&#8217;s internet traffic acquired under FISA section 702 authority.&#8221; The leaked information came after the revelation that the FISA Court had been ordering a subsidiary of telecommunications company Verizon Communications to turn over to the NSA logs tracking all of its customers&#8217; telephone calls.</p>
<p>U.S. government officials have disputed criticisms of PRISM in the Guardian and Washington Post articles and have defended the program, asserting that it cannot be used on domestic targets without a warrant, that it has helped to prevent acts of terrorism, and that it receives independent oversight from the federal government&#8217;s executive, judicial and legislative branches. On June 19, 2013, U.S. President Barack Obama, during a visit to Germany, stated that the NSA&#8217;s data gathering practices constitute &#8220;a circumscribed, narrow system directed at us being able to protect our people.&#8221;</p>
<h3>Document Archive</h3>
<p><img decoding="async" src="https://www.theblackvault.com/images/pdf.gif" /> <a href="https://documents2.theblackvault.com/documents/nsa/MDR-107072.pdf">NSA Email: FOIAs for PRISM Information</a> [21 Pages, 5.5MB] &#8211; This was an attempt to get previously released records further redacted. In May of 2019, an MDR request was filed to get these e-mails reviewed. Sadly, this time, nothing new was uncovered.</p>
<div class="ead-preview"><div class="ead-document" style="position: relative;padding-top: 90%;"><div class="ead-iframe-wrapper"><iframe src="//docs.google.com/viewer?url=https%3A%2F%2Fdocuments2.theblackvault.com%2Fdocuments%2Fnsa%2FMDR-107072.pdf&amp;embedded=true&amp;hl=en" title="Embedded Document" class="ead-iframe" style="width: 100%;height: 100%;border: none;position: absolute;left: 0;top: 0;visibility: hidden;"></iframe></div>			<div class="ead-document-loading" style="width:100%;height:100%;position:absolute;left:0;top:0;z-index:10;">
				<div class="ead-loading-wrap">
					<div class="ead-loading-main">
						<div class="ead-loading">
							<img decoding="async" src="https://www.theblackvault.com/documentarchive/wp-content/plugins/embed-any-document/images/loading.svg" width="55" height="55" alt="Loader">
							<span>Loading...</span>
						</div>
					</div>
					<div class="ead-loading-foot">
						<div class="ead-loading-foot-title">
							<img decoding="async" src="https://www.theblackvault.com/documentarchive/wp-content/plugins/embed-any-document/images/EAD-logo.svg" alt="EAD Logo" width="36" height="23"/>
							<span>Taking too long?</span>
						</div>
						<p>
							<div class="ead-document-btn ead-reload-btn" role="button">
								<img loading="lazy" decoding="async" src="https://www.theblackvault.com/documentarchive/wp-content/plugins/embed-any-document/images/reload.svg" alt="Reload" width="12" height="12"/> Reload document							</div>
							<span>|</span>
							<a href="https://documents2.theblackvault.com/documents/nsa/MDR-107072.pdf" class="ead-document-btn" target="_blank">
								<img loading="lazy" decoding="async" src="https://www.theblackvault.com/documentarchive/wp-content/plugins/embed-any-document/images/open.svg" alt="Open" width="12" height="12"/> Open in new tab							</a>
					</div>
				</div>
			</div>
		</div><p class="embed_download"><a href="https://documents2.theblackvault.com/documents/nsa/MDR-107072.pdf" download>Download [5.58 MB] </a></p></div><p>&nbsp;</p><p>The post <a href="https://www.theblackvault.com/documentarchive/nsa-surveillance-program-prism/">NSA Surveillance Program: PRISM</a> first appeared on <a href="https://www.theblackvault.com/documentarchive">The Black Vault</a>.</p>]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">12489</post-id>	</item>
		<item>
		<title>FBI File on Tracing Telephone Calls &#8212; File #80-HQ-789</title>
		<link>https://www.theblackvault.com/documentarchive/fbi-file-on-tracing-telephone-calls-file-80-hq-789/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=fbi-file-on-tracing-telephone-calls-file-80-hq-789</link>
		
		<dc:creator><![CDATA[John Greenewald]]></dc:creator>
		<pubDate>Wed, 02 May 2018 03:55:48 +0000</pubDate>
				<category><![CDATA[Federal Bureau of Investigation (FBI) Collection]]></category>
		<category><![CDATA[History]]></category>
		<category><![CDATA[eavesdropping]]></category>
		<category><![CDATA[FBI Files]]></category>
		<category><![CDATA[phone]]></category>
		<category><![CDATA[phone trace]]></category>
		<category><![CDATA[surveillance]]></category>
		<guid isPermaLink="false">http://www.theblackvault.com/documentarchive/?p=5961</guid>

					<description><![CDATA[<p>Background The following FBI was requested in May of 2014. In December of 2016, it was released. It is believed this is the entire releasable portions of File #80-HQ-789 on &#8220;Tracing Telephone Calls.&#8221; The approximate dates of the files within range from the 1950s through the 1970s. Document Archive  FBI File on Tracing Telephone Calls &#8212; [...]</p>
<p>The post <a href="https://www.theblackvault.com/documentarchive/fbi-file-on-tracing-telephone-calls-file-80-hq-789/">FBI File on Tracing Telephone Calls — File #80-HQ-789</a> first appeared on <a href="https://www.theblackvault.com/documentarchive">The Black Vault</a>.</p>]]></description>
										<content:encoded><![CDATA[<h3>Background</h3>
<p>The following FBI was requested in May of 2014. In December of 2016, it was released.</p>
<p>It is believed this is the entire releasable portions of File #80-HQ-789 on &#8220;Tracing Telephone Calls.&#8221;</p>
<p>The approximate dates of the files within range from the 1950s through the 1970s.</p>
<h3>Document Archive</h3>
<h4><img decoding="async" src="https://www.theblackvault.com/images/pdf.gif" /> <a href="https://documents.theblackvault.com/documents/fbifiles/80-HQ-789-TracingTelephoneCalls.pdf">FBI File on Tracing Telephone Calls &#8212; File #80-HQ-789</a> [496 Pages, 302MB]</h4><p>The post <a href="https://www.theblackvault.com/documentarchive/fbi-file-on-tracing-telephone-calls-file-80-hq-789/">FBI File on Tracing Telephone Calls — File #80-HQ-789</a> first appeared on <a href="https://www.theblackvault.com/documentarchive">The Black Vault</a>.</p>]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">5961</post-id>	</item>
	</channel>
</rss>
