More on Data Mining and Able Danger

Phil,

Let me add a couple of comments to your post.

1. Information Sharing and US Persons.


The critical part of your first quote block below is:


Under American law, United States citizens and green-card holders may not be singled out in intelligence-collection operations by the military or intelligence agencies. That protection does not extend to visa holders, but Mr. Weldon and the former intelligence official said it might have reinforced a sense of discomfort common before Sept. 11 about sharing intelligence information with a law enforcement agency.



This is just flat-out wrong. First, the "law" cited is Executive Order 12333, which defines the Intelligence Community and its authority to conduct operations. The most important provision of EO 12333 is its rules for when the IC can collect information on "US Persons." This is a specific definition and applies to a) US citizens, b) Permanent Resident Aliens (green-card holders), c) un-incorporated organizations composed by a majority of a) or b), or d) US corporations not owned by a foreign government.

The general rule for EO 12333 is basically, "thou shalt not collect information (that is, spy on) US Persons, except . . ." The "except" portion is critical. There are 13 exceptions under which an intelligence agency can collect information on US Persons. These include for personnel security investigations, for administrative purposes, when the subject gives consent to collect. The two most important categories are for Foreign Intelligence purposes (that is, collecting information on US Persons who are agents of a foreign power) and for Counterintelligence purposes. The Counterintelligence exception also includes collection for counternarcotics and international counterterrorism purposes. It also allows for collection of not just individuals reasonably believed to be engaged in international terrorism activities, but also collection of information on people associated with individuals reasonably believed to engaged in international terrorism activities (for the purpose of determining the relationship — if no significant relationship, then the info is destroyed).

All of this falls under the rubric of "intelligence oversight", which is a well-ingrained program within the military intelligence community ensuring that collection (especially HUMINT) activities did not retain information on US Persons without authority.

So when someone says that the military couldn't share information because of rules against collection of US Person information, that is not an accurate statement. Even if Mohammed Atta was a Permanent Resident Alien, the Intelligence Community was free to spy on him, collect the information, database it, and use it in intelligence reporting community-wide. The excuse doesn't make sense logically, either: How could have Able Danger conducted intelligence collection, using Army intelligence resources at LIWA have built the briefing to begin with? Once the information has been properly collected, it can be shared (theoretically). The reason the information was not forwarded probably had more to do with the infamous "wall" created by Justice Department's misreading of the Foreign Intelligence Surveillance Act, fixed by the Foreign Intelligence Surveillance Court of Appeals and the Patriot Act.

2. Datamining.

When one talks of datamining, they need to be clear on what exactly they mean. All datamining is is a set of tools used to dip into databases which can sort through the data and provide the answer to the query. Think of Westlaw or Lexis/Nexis on speed. The controversy in TIA was created over the types of databases they were going to search. DARPA was talking about applying the analytical toolkits to civilian business databases such as credit cards, hotel bookings, rental cars, etc. Even then, there were rules in place (using EO 12333 as the foundation) to ensure that the databases were not being queried without a legitimate purpose.

However, TIA was killed in a spate of misinformation. Before its death, these toolkits were already being used and improved by the Information Dominance Center at Fort Belvoir, VA. The significant difference between TIA's goals and the IDC's actual practice is that IDC is only analyzing databases of Intel Community information already collected.

Here's how IDC (at this discussion level) works: if Army intelligence has a reasonable belief that I am either engaging in or supporting international terrorist activities (or had a relationship with those engaged in the same) based on information that I had attended a mosque with a known terrorist and/or had made pro-terrorist statements, the first thing Army intel is going to do is to "tip" its own databases and see what has already been collected on me. Low and behold, they find a report written about a Gitmo detainee, explaining the pocket litter when he was captured. In his pocket litter was my business card. Now analysts can build linkages and determine relationships between me and others in the database to see if there may be other linkages out there that look innocuous at first, but when compared with other pieces of information show patterns and indications of terrorist activity. And the best thing is that the database check is multi-INT, tapping into SIGINT, HUMINT, and other sources of information. What happens with this information? Do the links mean anything? Maybe, maybe not. It's usually not enough to create "actionable intelligence". But what it does is become used to determine whether further investigation is required or whether the linkages are just coincidental. It is also used to build the bigger intel picture of the hydra that is international jihadist terrorism.

If I could actually explain how the datamining toolkits work, you would be amazed at their speed and accuracy in pointing out links and indicators (think Minority Report without the precogs). Of course, with great power comes great responsibility, but after the TIA debacle, the owners of IDC have ensured that its operations receive the highest levels of oversight and scrutiny. In the IDC operations I was involved in, each US Person database query had to have legal counsel approval.

The defense contractors involved in developing the datamining software are interested in taking it civilian, so you may see variations of the technology on the market soon. For instance, it would very helpful in complex litigation, such as tobacco or asbestos litigation, where discovery leads to thousands of documents and reports.

There's a longer discussion about whether information already databased by the intel community is already "collected" for purposes of intelligence oversight and therefore can be queried using analytical toolkits without worrying about collection exceptions. This will be for another day.

UPDATE:

One other issue that doesn't pass the smell test is the reluctance on the part of the military to pass information on terrorist threats w/in the borders over to the FBI. There is a 1979 document called the Delimitations Agreement, between the DOJ and SECDEF which outlines investigatory authorities for counterintelligence (and by extension counterterrorism) cases between the Bureau and military CI agencies. The bottom line is that DOD does not have jurisdiction to investigate civilians in the United States without FBI coordination. They can investigate civilians overseas who may post a threat to DOD personnel/installations, but once bad guys pass over into the States, FBI retains investigatory jurisdiction.

Able Danger appears to be the codename to the forerunner of the Information Dominance Center, or at least IDC-type tools were being applied to the Able Danger mission, but analysis presumes collection, or investigation. If Able Danger was conducting an investigation in to Atta et. al., it would have no jurisdiction to conduct collection or investigative activities in Brooklyn — that would fall under FBI.

To say that the "wall" prevented DOD from talking to FBI doesn't make sense. The "wall" existed between FBI-Criminal Division and FBI-Intelligence Division and was managed by the DOJ Office of Intelligence Policy and Review (OIPR). DOD was free, in fact required, to discuss counterintelligence and counterterrorism investigations taking place in the United States (or even taking place outside the United States if they involved US persons or potential prosecutions) with FBI-Intelligence officials.

It sounds more and more like the NYT and possibly Weldon were fed a stinker.

UPDATE 2:

Some have suggested that DOD may not have shared Able Danger information with the FBI because it was a JCS Special Access Program (SAP) with a limited number of people being able to get read on*, or that DOD lawyers felt that FBI didn't have the clearance or compartments required to receive the information. That doesn't wash. SAPs don't have any magic exemption from the ban on conducting intelligence collection inside the United States w/o FBI coordination (Posse Comitatus, anyone?) and you would think that this information would be important enough (individuals in the US, preparing for some sort of terrorist activity) to read on at least the Chief of the Intel Division or Louis Freeh. If it was a mere policy decision based on sensitivities or appearances, then someone in the Pentagon screwed up in a big way.

*fun piece of interesting trivia — the list of who gets access is sometimes called a "bigot list" and people who are on the list have been "bigoted". Sometimes its good to be a bigot.

1 Trackbacks /
Roach (mail) (www):
It seems possible that this could have been a reflexive, secrecy-oriented decision by policymakers who did not trust the FBI to handle the information properly.
8.10.2005 10:25am
kris alexander (mail) (www):
I can attest to the robustness of the Army Intel Oversight program. I don't think the problem is abuse on who is collecting what. The problem is the lack of sharing on what we do collect. The "golden nugget" often goes overlooked.
8.10.2005 11:25am
sheerahkahn:
Hmmm, somehow the overall idea of this has ill entwined in it's eventual use. Somehow, I think this is the "Rubicon" in regards to the constitution for us, and I'm afraid that Bush will fancy himself superior to Ceasar in it's "limited and constrained" use.

No sir, not comfortable with it one dam bit.
8.10.2005 12:51pm
libertarian soldier:
Actually there are currently 16 exceptions. I can also attest to the robustness of the I/O program--at least inspection-wise.
And I don't think the statement is necessarily inaccurate, because the sharing outside of DoD would have been a policy decision (not DC/PC level but still not done at the collector/analyst level) where the sensitivities would be real.
Also, remember pre-9/11 (and still, unfortunately, to a large extent today) that information would have gone into a non-shared database that would have required positive efforts on the part of DoD to make it available to an outside agency.
8.10.2005 10:58pm
Jon Holdaway (mail):
libertarian soldier:

Sorry, its 13. See Procedure 2, AR 381-10:

1. Information obtained with consent. In may be collected about a United States person who consents to such collection.

2. Publicly available information. Information may be collected about a United States person if it is publicly available.

3. Foreign intelligence. Subject to the special limitations contained in section E., below, information may be collected about a United States person if the in constitutes foreign intelligence, provided the intentional collection of foreign intelligence about United States persons shall be limited to persons who are:

(a) Individuals reasonably believed to be officers or employees, or otherwise acting for or on behalf, of a foreign power;

(b) An organization reasonably believed to be owned or controlled, directly or indirectly, by a foreign power;

(c) Persons or organizations reasonably believed to be engaged or about to engage, in international terrorist or international narcotics activities. (See AR 190-52.);

(d) Persons who are reasonably believed to be prisoners of war; missing in action; or art the targets, the hostages, or victims of international terrorist organizations; or

(e) Corporations or other commercial organizations believed to have some relationship with foreign powers, organizations or persons.

4. Counterintelligence. Information may be collected about a United States person if the information constitutes counterintelligence, provided the international collection of counterintelligence about United States persons must be limited to:

(a) Person who are reasonably believed to be engaged in, or about to engage in, intelligence activities on behalf of a foreign power, or international terrorist activities. (See AR 190-52,
AR 381-12 , and AR 381-20 .)

(b) Persons in contact with persons described in paragraph C.4.a., above, for the purpose of identifying such persons and assessing their relationship with persons described in paragraph C.4.a., above.

5. Potential sources of assistant to intelligence activities. Information may be collected about United States person reasonably believed to be potential sources of intelligence, or potential sources of assistant to intelligence activities, for the purpose of assessing their suitability and credibility. This category does not include investigations undertaken for personnel security purposes. (See subsection 8.)

6. Protection of intelligence sources and methods. Information may be collected about a United States person who has access to, had access to, or is otherwise in possession of, information which reveals foreign intelligence and counterintelligence sources or methods, when collection is reasonably believed necessary to protect against the unauthorized disclosure of such information; provided that within the United States, intentional collection of such information shall be limited to persons who are:

(a) Present and former DoD employees;

(b) Present or former employees of a present or former DoD contractor; and

(c) Applicants for employment at DoD or at a contractor of DoD.

7. Physical security. Information may be collected about the United States person who is reasonably believed to threaten the physical security of DoD employees, installations, operations or official visitors. Information may also be collected in the course of a lawful physical security investigation. (See AR 381-12, AR 381-20, AR 190-1, and AR 190-52.)

8. Personnel security. Information may be collected on a United States person that arises out of a lawful personnel security investigation. This includes information concerning relatives and associates of the subject of the investigation, if required by the scope of the investigation and the information has a bearing on the matter being investigated or the security determination being made. (See AR 604-5, AR 381-12, AR 381-20, and AR 190-52.)

9. Communications security. Information may be collected about a United States person that arises out of a lawful communications security investigation. (See
AR 380-53 .)

10. Narcotics. Information may be collected about a United States person who is reasonably believed to be engaged in international narcotics activities.

11. Threats to safety. Information may be collected about a United States person when the information is needed to protect the safety of any person or organization, including those who are targets, victims or hostages of international terrorist organizations. (See AR 190-52.)

12. Overhead reconnaissance. Information may be collected for overhead reconnaissance not directed at specific United States persons.

13. Administrative purposes. Information may be collected about a United States person that is necessary for administrative purposes.

Jon
8.11.2005 1:09am
just wondering (mail):
Foreign intelligence gathered inside the United States about U.S. persons is apparently allowed without FBI coordination if it is by overt means. According to AR 380-10:

E. SPECIAL LIMITATION ON THE COLLECTION OF
FEDERAL INTELLIGENCE WITHIN THE UNITED STATES
Within the United States, foreign intelligence concerning United States persons may be collected only by overt mean unless all the following conditions are met:
1. The foreign intelligence sought is significant and collection is not undertaken for the purpose of acquiring information concerning the domestic activities of any United States person;
2. Such foreign intelligence cannot be reasonable obtained by overt means;
3. The collection of such foreign intelligence has been coordinated with the Federal Bureau of Investigation (FBI); and
4. The use of other than overt means has been approved in
writing by the head of the DoD intelligence components concerned, or his single designee, as being consistent with these procedures. . . .

So. . .is "data-mining" overt?
8.11.2005 1:43pm
Jon Holdaway (mail):
just wondering,

Good question, but not the right question.

First, the provision you cite is from AR 381-10 and concerns collection of foreign intelligence (FI), that is, information regarding a person's activities on behalf of a foreign power. Those activities can be investigated overtly, but cannot extend to domestic activities; in other words, MI can investigate a person's business dealings with the Kingdom of Jordan or Republic of Korea, but not where they purchased gas or where they went on vacation last weekend (unless related). The only purpose of Section E is to let investigators know that they are limited to collection of information pertinent only to question of foreign activities, unless they coordinate further.

Second, is the question of what constitutes overt collection. That would involve any investigative technique that isn't a "special collection technique", which is more instrusive and invasive (and involves issues of constitutional rights). See Procedures 5-12. So, MI can Google information on the target -- it is publicly available information. MI can also check its own databases, which leads to . . .

Third, the question of what constitutes datamining. As I point out in my original post, it isn't just dipping into commercial databases owned by public sources. If I wanted to conduct that sort of search, I'd probably have to go through the 4-part test that you cited.

But if it is a US government-owned database, is querying the database a collection activity which kicks in oversight issues? Do I need to go through the Procedure 2 analysis and have justification to check a US persons name? There are two thoughts in the government right now. The first is that information already retained in US databases is presumed to have been properly collected under Procedure 2 and retained under Procedure 3, so querying the database is not a collection and needs no other authorization to query.

The other philosophy is that EO 12333, drafted in 1981, does not adequately address databasing -- it was created in an era of file folders and cabinets. There is information in these databases that is incidental, for instance, a report on Phil Carter may contain the name of Jon Holdaway, an associate. My name gets queried during a datamining operation, and this information, collected properly but incidental to an investigation into Phil, pops up. There are those in the intel overight community who would argue that this instant access to incidental information requires the agent querying the database to have original Procedure 2 authority to gather the information.

Easy, right?

So the bottom line answer is not whether datamining (of either commercial or government databases) is overt, but whether it is collection.

Oh, and the provision you cited only covers investigations for FI purposes. Those are actually rare. What is more prevelant is investigations for counterintelligence (CI) or counterterrorism (CT) purposes, which are governed by the provision you cited. In those cases, based on the Delimitations Agreement and Posse Comitatus, FBI has the lead for activities in the US.
8.11.2005 9:35pm
Anon:
OK smart guys - with your "smell tests" and "Thats just flat out wrong" opinions shown above - I hope you don't mind, but let me clear up a few things - I was there and I lived through the ABLE DANGER nightmare.

First - yes - The lawyers involved in this (and similar projects) did interpret the 9-11 terrorists as "US persons" - so while you can second guess them all you want - but that was their "legal" call as wrong as it was and is. Unfortunately, the chain of command at SOCOM went along with them (and this, I expect, will be a topic that will become more clear in the near future).

And lawyers of the era also felt that any intelligence officer viewing open internet information for the purpose of intelligence collection automatically required that any "open source" information obtained be treated as if it was "intelligence information"...does this sound like idiocy to you? It did to me - and we fought it - and I was in meetings at the OSD level, with OSD laywers, that debated this - and I even briefed the DCI George Tenet on this issue relating to an internet project.

And yes, Virgina - we tried to tell the lawyers that since the data identified Atta and the others as linked to Al Qaeda, we should be able to collect on them based on SecState Albright's declaration of Al Qaeda as transnational terrorist threat to the US...well the lawyers did not agree...go figure...so we could not collect on them - and for political reasons - could not pass them to the FBI...I know because I brokered three meetings between the FBI and SOCOM to allow SOCOM to pass the informaton to the FBI. And, sadly, SOCOM cancelled them every time...

Oh - and as to your opinion that ABLE DANGER was a precursor to the IDC - you are flat out wrong - and obviously not keeping up with what is coming out in the press. ABLE DANGER partnered with LIWA/IDC to use the LIWA/IDC capability to obtain the data on Atta and the other 9-11 terrorists. I brokered the relationship...
And - wrong again on the IDC using only "classified" databases - IDC used 2.5 terabytes (a whole hell of a lot of data) - all open source - to identify Atta and the others that have been identified. Classified data bases were only use to "confirm" the links subsequent to the open source data runs.

Oh - and DATA MINING is not overt or clandestine - it just "is" - it is something that is done with either open source or classified information. ABLE DANGER used an array of both open and close databases...

So...good try, gentlemen - good to see there is intellectual riggor here...but before you start doubting the story, perhaps you need to do better research.
8.12.2005 11:27pm
Jon Holdaway (mail):
Anon,

Sounds like you and I might have crossed paths somewhere or at least know some of the same people.

However, your story (while making sense based on my experiences) makes some serious allegations. You've posted as "anon" for obvious reasons and haven't left an email. In order to verify your creds, I'd like you to email me or contact me in some way.

BTW, I agree with everything you say. My original comments of skepticism are waning because much more has come out. The problem is that skepticism over the story is changing to frustration that DOD lawyers that should have known better about the rules of passing information to FBI didn't and they should have. This is the bigger story.
8.13.2005 1:55am
JohnG (mail):
There is certainly enough regulation posted here to establish that open source collection is within bounds by the DOD.

I've worked with civilian law enforcement on a number of occasions - in my case, law enforcement requested us, military JAG did a quick review and then we had an OK. This is not some laborious process as some would like to think.

In this case (as the press reports keep coming out), it would be easy to believe that there was interferance by military JAG lawyers. A law degree doesn't imply omniscience or wisdom. Even with interrogation, you can get vastly different opinions on what is legitmate. It would be quite easy to imagine that a JAG officer arbitralily denied the team the ability to turn over information to authorities who could have acted on it.
8.13.2005 12:42pm
Catch22:
Even then, there were rules in place (using EO 12333 as the foundation) to ensure that the databases were not being queried without a legitimate purpose.

However, TIA was killed in a spate of misinformation.


It was far from just misinformation that killed TIA. Needless to say not everyone has your (arguably highly naive or disingenuous) optimism that EO 12333 has everything we need to avoid abuse of such a system. You imply that it was just information that led to the demise of the program while the truth is far from it.

Part of what killed TIA was its own inneptitude and tin ear with the placement of Poindexter at the helm, choice of language and the all seeing eye. But there was a lot of substance beyond the style to be concerned about.

One good soure of information I recommend for those who are interested in learning more about Data Mining from the Congressional Research Service:
"Data Mining: An Overview," updated June 7, 2005: http://www.fas.org/sgp/crs/intel/RL31798.pdf

For example they note:

Critics of the TIA program were further incensed by two administrative aspects of the project. The first involved the Director of IAO, Dr. John M. Poindexter. Poindexter, a retired Admiral, was, until that time, perhaps most well-known for his alleged role in the Iran-contra scandal during the Reagan Administration. His involvement with the program caused many in the civil liberties community to Some of the information required includes spending schedules, likely effectiveness of the program, likely impact on privacy and civil liberties, and any laws and regulations that may need to be changed to fully deploy TIA.24 The second source of contention involved TIA’s original logo, which depicted an “all-seeing” eye atop of a pyramid looking down over the globe, accompanied by the Latin phrase scientia est potentia (knowledge is power).25 Although DARPA eventually removed the logo from its website, it left a lasting impression.

The continued negative publicity surrounding the TIA program contributed to the introduction of a number of bills in Congress that eventually led to the program’s dissolution. Among these bills was S. 188, the Data-Mining Moratorium Act of 2003, which, if passed, would have imposed a moratorium on the implementation of data mining under the TIA program by the Department of Defense, as well as any similar program by the Department of Homeland Security. An amendment included in the Omnibus Appropriations Act for Fiscal Year 2003 (P.L. 108-7) required the Director of Central Intelligence, the Secretary of Defense, and the Attorney General to submit a joint report to Congress within 90 days providing details about the TIA program.26 Funding for TIA as a whole was prohibited with the passage of the FY2004 Department of Defense Appropriations Act (P.L. 108-87) in September 2003. However, Section 8131 of the law allowed unspecified subcomponents of the TIA initiative to be funded as part of DOD’s classified budget, subject to the provisions of the National Foreign Intelligence Program, which restricts the processing and analysis of information on U.S. citizens.27

24 Shane Harris, “Counterterrorism Project Assailed By Lawmakers, Privacy Advocates,”
Go v e r n m e n t E x e c u t i v e Ma g a z i n e , 25 Novemb e r 2 0 0 2 ,
[http://www.govexec.com/dailyfed/1102/112502h1.htm].
25 The original logo can be found at [http://www.thememoryhole.org/policestate/iaologo.
htm].
26 The report is available at http://www.eff.org/Privacy/TIA/TIA-report.pdf]. If the report had not submitted within 90 days, funding for the TIA program could have been discontinued. For more details regarding this amendment, see CRS Report RL31786, Total Information Awareness Programs: Funding, Composition, and Oversight Issues, by Amy Belasco.
27 For further details regarding this provision, see CRS Report RL31805 Authorization and Appropriations for FY2004: Defense, by Amy Belasco and Stephen Daggett.
question the true motives behind TIA.
8.13.2005 1:40pm
Catch22:
Jon Holdaway:

It sounds more and more like the NYT and possibly Weldon were fed a stinker. It does sound increasingly like there was a stinker and that Weldon is part of the problem and not a victim. Funny you dont note that it was the right wing that proceeded to make a big stink. John Podhoretz over at NRO under the heading WE MAY OWE THEM A BIG APOLOGY is honest enough to note that it now appears the right wing have been "had" on this one:

A day or two ago, I posted a note of caution about the Able Danger scandal, and that note of caution has now turned into a full-fledged symphony -- and some of us on the Right who have been making a big stink about this may have been had.

Over at the NRO they appear to be singing the same tune, that Weldon and this unnamed officer appear to have full of BS:

Of course, everything they’re saying completely contradicts what Rep. Curt Weldon and the unnamed military intelligence officer said. As for the Navy officer who told them about Able Danger finding Atta in 2000, the commission’s statement kind of makes him sound like a fruitcake.

We’re in an ugly spot. We’ve got Curt Weldon and bunch of anonymous sources making one of the biggest, most shocking allegations ever, and we’ve got the 9/11 Commission saying, ‘nope, not true, and no evidence to back it up.’
8.14.2005 4:50pm
Vistaviewer (mail):
Jon Holdaway, Concerning your article, and this passage:

"The defense contractors involved in developing the datamining software are interested in taking it civilian, so you may see variations of the technology on the market soon. For instance, it would very helpful in complex litigation, such as tobacco or asbestos litigation, where discovery leads to thousands of documents and reports."

...check out a small company called AdZone Research, www.AdzoneInteractive.com (ADZR), located on Long Island New York. They have been successfully doing this Data Mining activity for YEARS, and even prior to 9/11, using a product called NetGet. They currently have active contracts to track down movie bootleggers and pedophiles. They also track the viability of Internet Advertising campaigns and provide the info to the advertising community under a service contract. AdZone has actually been publically credited with finding real terrorist communications hidden on tne Internet, over a year ago. As far as I know AdZone is not connected with ABLE DANGER in any way. However, they have been actively trying to interest our government in NetGet since 9/11. But why the government has never given AdZone a contract is well beyond my understanding. VV
8.14.2005 6:10pm
jon holdaway (mail):
Catch-22:

I'm with ya. Its obvious that the conservative meme has been "blame the Gorelick Wall". However bad the "wall" was, its not the right target in this case. When this broke and Rush, Hannity, and NRO started going after Gorelick, I emailed several pundits, gave my creds, and told them the wall problem in this case is incorrect -- the wall doesn't affect DOD and FBI Intelligence communications.

However, blaming Gorelick means the right gets to blame Clinton, which is always fun sport. There is already enough to complain about Gorelick's presence on the 9/11 commission and Able Danger seemed to fit into all that.

What I think people are missing is that if, at a minimum, there were Analyst's Notebook (software that does link analysis) charts with the names of suspected terrorists located in Brooklyn (which it sounds like may be the case), why weren't those charts passed over to the FBI? Of course, the 9/11 commission says the couldn't find any such charts, so even this info might be wrong.

All along, this story has not made sense.
8.15.2005 1:52pm
just wondering (mail):
Jon wrote

"First, the provision you cite is from AR 381-10 and concerns collection of foreign intelligence (FI), that is, information regarding a person's activities on behalf of a foreign power."

Right, including foreign terrorist organizations.

Second, is the question of what constitutes overt collection....

Well, according to the reg, "overt means refers to methods of collection whereby the source of the information being collected is advised, or is otherwise aware, that he is providing such information to the Department of Defense or a component thereof."

Collection occurs when a DoD employee "take[s] some affirmative action that demonstrates an intent to use or retain the information received (such as production of a report, filing of an investigative summary, or electronic storage of received data.) ... Thus, information volunteered to a DoD intelligence component by a cooperating source would be “collected” under this procedures when an employee of such component officially accepts . . . such information for use within that component. Data acquired by electronic means is 'collected' only when it has been processed into intelligible form. Information held, or forwarded to a supervisory authority, solely for the purpose of making a determination about the collectability of that information under this procedure (and not otherwise
disseminated within the component) is not 'collected.'"

I read this to mean that information gathered from non-DoD databases for inclusion into a DoD database is "collected", and that such collection is overt if the proprietor of the outside database is aware DoD is using it for intelligence-gathering purposes, unless maybe the database is wholly accessible to the public. So, no, DoD querying its own database would not be "collection" within the meaning of the reg, but there are rules that apply to retention of information, as well.

Oh, and the provision you cited only covers investigations for FI purposes. Those are actually rare. What is more prevelant is investigations for counterintelligence (CI) or counterterrorism (CT) purposes, which are governed by the provision you cited.

You mean CI and CT investigations aren't covered, right? Actually, the part of the reg we are talking about refers to types of information, not investigations. It is a bit difficult to discern the difference between FI and CI information in the terrorism context. "Counterintelligence" is defined in appendix A to mean "Information gathered and activities conducted to protect against espionage, other intelligence activities, sabotage,or assassinations conducted for or on behalf of foreign powers, organizations, persons, or international terrorist activities, but not including personnel, physical, document, or communications security programs."

Whereas "Foreign intelligence" information is "Information relating to the capabilities, intentions, and activities of foreign powers, organizations, and persons, but not including counterintelligence except for information on international terrorist activities."

I've always thought counterintelligence and counterterrorism were two different things, but now I'm not so sure. Maybe you can explain? (I used to be MI myself; I was even "intelligence oversight officer" for a sizable unit, but that was before any data were mined, and terrorism was not necessarily a national security issue).
8.15.2005 3:12pm
Catch22:
Jon Holdaway:

Maybe their is something to able danger?

From NYT:


WASHINGTON, Aug. 16 - A military intelligence team repeatedly contacted the F.B.I. in 2000 to warn about the existence of an American-based terrorist cell that included the ringleader of the Sept. 11 attacks, according to a veteran Army intelligence officer who said he had now decided to risk his career by discussing the information publicly. The officer, Lt. Col. Anthony Shaffer, said military lawyers later blocked the team from sharing any of its information with the F.B.I.
....
"And if these assertions are credible," he continued, "the Pentagon would need to explain why it was that the 9/11 commissioners were not provided this information despite request for all information regarding to Able Danger."
8.16.2005 8:52pm
jon holdaway (mail):
From what I can tell you (based on that part of my knowledge I can share and conversations I've had with friends still in the intel community), the existence of Able Danger doesn't seem to be a problem -- it most likely existed and did what the papers are saying it did.

The questions remaining are 1) whether they really had Atta's name, if so, 2) did the existence of the name in reporting have enough independent significance at the time to require forwarding his name to the FBI, and 3) if they should have passed the name and didn't, why not.

So far, the only name coming forward is Lt. Col Shaffer. He's the only person who says that there was information and lawyers (3 times!) didn't allow passage. Doesn't sound like the Pentagon lawyers working CT cases that I know (very proactive in involving FBI in both CT and CI cases). He's the only one who says DOD had the names prior to 9/11, despite Congressional and 9/11 commission orders for the MI community to scrub all records on these guys. 9/11 commission took a briefing on Able Danger, but according to them, the info wasn't significant enough to follow up. I'd look at Shaffer and see why, now, he's coming forward. I suspect there's more to him than meets the eye.

Lot's of speculation (yes, even on my part), little facts to go on, so I'm in wait-and-see mode.
8.16.2005 10:45pm