You do not have permission to edit this page, for the following reasons:

This IP address has been blocked from editing Wikipedia.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.

The IP address or range 54.166.0.0/16 has been blocked (disabled) by ‪Blablubbs‬ for the following reason(s):

The IP address that you are currently using has been blocked because it is believed to be a web host provider or colocation provider. To prevent abuse, web hosts and colocation providers may be blocked from editing Wikipedia.
You will not be able to edit Wikipedia using a web host or colocation provider because it hides your IP address, much like a proxy or VPN.
We recommend that you attempt to use another connection to edit. For example, if you use a proxy or VPN to connect to the internet, turn it off when editing Wikipedia. If you edit using a mobile connection, try using a Wi-Fi connection, and vice versa. If you are using a corporate internet connection, switch to a different Wi-Fi network. If you have a Wikipedia account, please log in.
If you do not have any other way to edit Wikipedia, you will need to request an IP block exemption.

How to appeal if you are confident that your connection does not use a colocation provider's IP address:
If you are confident that you are not using a web host, you may appeal this block by adding the following text on your talk page: ((unblock|reason=Caught by a colocation web host block but this host or IP is not a web host. My IP address is _______. Place any further information here. ~~~~)). You must fill in the blank with your IP address for this block to be investigated. Your IP address can be determined here. Alternatively, if you wish to keep your IP address private you can use the unblock ticket request system. There are several reasons you might be editing using the IP address of a web host or colocation provider (such as if you are using VPN software or a business network); please use this method of appeal only if you think your IP address is in fact not a web host or colocation provider.

Administrators: The IP block exemption user right should only be applied to allow users to edit using web host in exceptional circumstances, and requests should usually be directed to the functionaries team via email. If you intend to give the IPBE user right, a CheckUser needs to take a look at the account. This can be requested most easily at SPI Quick Checkuser Requests. Unblocking an IP or IP range with this template is highly discouraged without at least contacting the blocking administrator.

This block will expire on 10:02, 6 May 2025.

Even when blocked, you will usually still be able to edit your user talk page, as well as email administrators and other editors.

For information on how to proceed, please read the FAQ for blocked users and the guideline on block appeals. The guide to appealing blocks may also be helpful.

Other useful links: Blocking policy · Help:I have been blocked
Your IP address is in a range that has been blocked on all Wikimedia Foundation wikis. The block was made by ‪Jon Kolbert‬. The reason given is Open proxy/Webhost: See the help page if you are affected .
- Start of block: 18:27, 12 November 2023
- Expiry of block: 18:27, 12 November 2028
Your current IP address is 54.166.193.9. The blocked range is 54.166.0.0/16. Please include all above details in any queries you make. If you believe you were blocked by mistake, you can find additional information and instructions in the No open proxies global policy. Otherwise, to discuss the block please post a request for review on Meta-Wiki. You could also send an email to the stewards VRT queue at stewards@wikimedia.org including all above details.

You can view and copy the source of this page:

((Short description|Process of managing and organising the collection of evidence))
((Multiple issues|
((Technical|date=June 2013))
((More footnotes needed|date=March 2011))
))

'''Intelligence collection management''' is the process of managing and organizing the [[Intelligence (information gathering)|collection of intelligence]] from various sources.  The collection department of an [[intelligence organization]] may attempt basic validation of what it collects, but is not supposed to analyze its significance. There is debate in [[U.S. intelligence community]] on the difference between validation and analysis, where the [[National Security Agency]] may (in the opinion of the [[Central Intelligence Agency]] or the [[Defense Intelligence Agency]]) try to interpret information when such interpretation is the job of another agency.

== Collection disciplines ==
((see also|List of intelligence gathering disciplines))
Disciplines which postprocess raw data more than collect it are:((Citation needed|date=February 2024))
*[[Cyber intelligence]] (CYBINT)
*[[Financial intelligence]] (FININT)
*[[Geospatial intelligence|Geo-spatial intelligence]] (GEOINT)
*[[Human intelligence (espionage)|Human intelligence]] (HUMINT)
*[[Imagery intelligence]] (IMINT)
*[[Measurement and signature intelligence]] (MASINT)
*[[Open-source intelligence]] (OSINT)
*[[Signals intelligence]] (SIGINT)
*[[Technical intelligence]] (TECHINT)

== Collection guidance ==
At the director level and within the collection organization (depending on the intelligence service), collection guidance assigns collection to one or more source managers who may order reconnaissance missions, budget for agent recruitment, or both.

===((anchor|Research in collection guidance))Research===
This may be an auction for resources, and there is joint UK-US research on applying more formal methods. One method is "semantic matchmaking" based on [[ontology]], originally a field of [[philosophy]] but finding applications in intelligent searching. Researchers match missions to the capabilities of available resources,<ref name="Preece">((cite web 
| url = http://www.usukita.org/files/1569048201.pdf
| title = An Ontology-Based Approach to Sensor-Mission Assignment
|author=Preece, Alun| year = 2007
| access-date = 2007-10-31
|archive-url = https://web.archive.org/web/20071011041842/http://www.usukita.org/files/1569048201.pdf <!-- Bot retrieved archive --> |archive-date = 2007-10-11|display-authors=etal))</ref> defining ontology as "a set of logical axioms designed to account for the intended meaning of a vocabulary".<ref>((Cite web|url=http://citeseerx.ist.psu.edu/messages/downloadsexceeded.html|title=A New Approach for Developing Ontology from Generated Ruleset|access-date=2019-01-19))</ref> The requester is asked, "What are the requirements of a mission?" These include the type of [[data]] to be collected (distinct from the collection method), the priority of the request, and the need for secrecy in collection.

Collection system managers are asked to specify the capabilities of their assets. Preece's ontology focuses on [[ISTAR]] sensors, but also considers [[Human intelligence (intelligence gathering)|HUMINT]], OSINT and possible methodologies. The intelligence model compares "the specification of a mission against the specification of available assets, to assess the utility or fitness for purpose of available assets; based on these assessments, obtain a set of recommended assets for the mission: either decide whether there is a solution—a single asset or combination of assets—that satisfies the requirements of the mission, or alternatively provide a ranking of solutions according to their relative degree of utility."((citation needed|date=January 2014))

===NATO collection guidance===
In NATO, the questions driving collection management are Priority Intelligence Requirements (PIR). PIRs are a component of Collection Coordination and Intelligence Requirements Management ([[CCIRM]]) focused on the collection process, uniting the intelligence effort to maneuver through Decision Points (DPs). These questions, refined into Information Requirements (IRs), enable the Collection Manager (CM) to focus assets on a problem. Without this synchronization, it would be impossible to ensure that the intelligence focus meets the commander's requirements and priorities.<ref>((cite web | title = ARRC [Allied Rapid Response Corps] Intelligence Collection Management Process | url = http://www.arrc.nato.int/journal/april03/inteligence.htm | author = Grebe, Carl | id = Grebe | access-date = 2007-10-28 | url-status = dead | archive-url = https://web.archive.org/web/20070623004953/http://www.arrc.nato.int/journal/april03/inteligence.htm | archive-date = 2007-06-23 ))</ref>

====((anchor|Collection discipline selection))Discipline selection====
When a PIR defining the information to be collected exists, discipline specialists and resource schedulers select the appropriate collection system and plan the mission, taking into account the capabilities and limitations of collection platforms. Weather, terrain, technical capabilities and opponents' countermeasures determine the potential for successful collection. Through an understanding of all available platforms (tied to questions related to the PIR) the collection manager synchronizes available assets, theatre and corps collection, national capabilities and coalition resources (such as the [[European Union Satellite Centre|Torrejon Space Center]]) to maximize capabilities.((Citation needed|date=November 2019))

====((anchor|Finding alternative collection disciplines))Alternative disciplines====
Despite the desirability of a given method, the information required may not be collectible due to interfering circumstances. The most desirable platform may not be available; weather and enemy air-defense might limit the practicality of UAVs and fixed-wing IMINT platforms. If air defense is the limitation, planners might request support from a national-level IMINT satellite. If a satellite will do the job, the orbits of available satellites may not be suitable for the requirement.

If weather is the issue, it might be necessary to substitute MASINT sensors which can penetrate the weather and get some of the information. SIGINT might be desired, but terrain masking and technical capabilities of available platforms might require a space-based (or long-range) sensor or exploring whether HUMINT assets might be able to provide information. The collection manager must take these effects into consideration and advise the commander on the situational awareness available for planning and execution.

Other sources may take some time to collect the necessary information. MASINT depends on a library of signatures of normal sensor readings, so deviations stand out. Cryptanalytic COMINT can take considerable time to enter into a cryptosystem, with no guarantee of success.

====((anchor|Collection support resource management))Support resource management====
An available, appropriate collection platform does not mean it will be useful if the facilities needed to receive and process the information are unavailable. Two factors affect this process: the physical capabilities of the intelligence systems and the training and capabilities of the intelligence section.

Collection platforms able to collect tens of thousands of pieces of information per hour need receivers which can accept that volume. The collection capability, even with self-generating reports, can quickly overwhelm inexperienced or understaffed analysts. While the CM is primarily concerned with collection, they must also know if analysis for the requested system has the resources to reduce and analyze the sensor data within a useful length of time.

IMINT and SIGINT ground stations may be able to accept sensor data, but the networks and information-processing systems may be inadequate to get data to analysts and commanders; an example is imagery intelligence derived from UAVs and fixed-wing IMINT platforms. Commanders and staff are accustomed to receiving quality imagery products and UAV feeds for planning and execution of their missions. In exercises, this is often done with high-speed fixed networks; in a mobile, fluid battle it would be nearly impossible to develop a network capable of carrying the same amount of information. The CM must decide if an analytic report (rather than the imagery itself) will answer the question; when a hard-copy image or video is required, the CM must inform staff members of the cost to the IT network and HQ bandwidth.

Collection management is the cornerstone on which intelligence support to [[Allied Rapid Reaction Corps|ARRC]] operations is built. Since the starting point of the collection process is the commander's PIRs, they are a critical component of the staff planning process and support the commander's decision-making.

===CIA collection guidance===
Intelligence requirements were introduced after World War II. After an initial phase where field personnel decided priorities, an interim period began in which requirements were considered "as desirable but were not thought to present any special problem. Perhaps the man in the field did, after all, need some guidance; if so, the expert in Washington had only to jot down a list of questions and all would be well."<ref name="Heffter">((Cite journal
 | url = https://www.cia.gov/library/center-for-the-study-of-intelligence/kent-csi/vol4no4/html/v04i4a03p_0001.htm
 | archive-url = https://web.archive.org/web/20080109201631/https://www.cia.gov/library/center-for-the-study-of-intelligence/kent-csi/vol4no4/html/v04i4a03p_0001.htm
 | url-status = dead
 | archive-date = January 9, 2008
 | title = A Fresh Look at Collection Requirements
 | journal = Studies in Intelligence
 | author = Heffter, Clyde R.
 | publisher = Kent Center for the Study of Intelligence
 | access-date = 2013-02-28
 ))</ref>

In a third phase (by the early 1950s), a consensus was established that a formal requirement structure was needed. When that machinery was set up, specialized methodologies for requirement management needed to be developed. The methodologies first needed were those used against the Sino-Soviet bloc, and radical changes in the threat environment may make some of those methodologies inappropriate.

Requirements may be cast in terms of analysis technique, collection method, subject matter, source type or priority. Heffter's article says that not every problem is a special case, but may be a problem "central to the very nature of the requirements process. One cannot help feeling that too little of the best thinking of the community has gone into these central problems—into the development, in a word, of an adequate theory of requirements."<ref>((Cite web|url=https://www.cia.gov/library/center-for-the-study-of-intelligence/kent-csi/vol4no4/html/v04i4a03p_0001.htm|archive-url=https://web.archive.org/web/20080109201631/https://www.cia.gov/library/center-for-the-study-of-intelligence/kent-csi/vol4no4/html/v04i4a03p_0001.htm|url-status=dead|archive-date=January 9, 2008|title=A Fresh Look at Collection Requirements — Central Intelligence Agency|website=www.cia.gov|access-date=2019-01-19))</ref>
 	 
"But there is often a conspicuous hiatus" between requirements produced at a managerial level "and the requirements produced on the working level. Dealing with general matters has itself become a specialty. We lack a vigorous exchange of views between generalists and specialists, requirements officers and administrators, members of all agencies, analysts in all intelligence fields, practitioners of all collection methods, which might lead at least to a clarification of ideas and at best to a solution of some common problems."<ref name="Heffter"/>

====((anchor|The problem of priorities))Priorities====
Priority-based needs must be presented, with the best way to meet those needs based on an effective use of the collection means available. Heffter's paper centers on the management of priorities for the use of collection assets; three factors which must be balanced are:
*Administration and system (for example, the top-level directive)
*Intellectual discipline, using the analytical method 
*Training and responsibilities of the individual intelligence officer

"&nbsp;... Each of the three kinds answers a deep-felt need, has a life of its own, and plays a role of its own in the total complex of intelligence guidance". Since Heffter focused on the problem of priorities, he concerned himself chiefly with policy directives, which set overall priorities. Within that policy, "requests are also very much in the picture since priorities must govern their fulfillment".<ref name="Heffter"/>

====((anchor|Types of requirements))Requirements====
A collection requirement is "a statement of information to be collected".((citation needed|date=September 2014)) Several tendencies hinder precision:
*Analysts publish lists of their needs in the hope that someone will satisfy them.
*Theorists and administrators want a closely knit system where all requirements can be fed into a single machine, integrated, ranged by priorities and allocated as directives to all parts of the collection apparatus.
*Collectors demand specific requests for information, keyed to their capabilities.
 
These differing desires can cause friction or complement one another. The tendencies can complement each other if brought into balance, but their coexistence has often been marked with friction.
 
The characteristics of a requirement are:
*Need
*Compulsion or command (stated under authority)
*Request (with a specific intelligence meaning)

In intelligence, the meaning of "require" has been redefined. Under this interpretation, one person (the "customer") makes a request (or puts a question) to another of equal status (the collector) who fulfills (or answers) it as best they can.

There is an honor system on both sides:
*The requester vouches for the validity of the requirement.
*The collector is free to reject it.
*If he accepts it, the collector implies assurance that he will do his best to fulfill it.

The relationship is free from compulsion. The use of direct requests appeals to collectors, who find that it provides them with more viable, collectible requirements than any other method. It sometimes appeals to requester-analysts, who (if they find a receptive collector) can get more requirements accepted than would be possible otherwise.
 
The elements of need, compulsion and request are embodied in three types of collection requirements: the inventory of needs, addressed to the community at large and to nobody in particular; the directive, addressed by a higher to a lower echelon; and the request, addressed by a customer to a collector.

====((anchor|The requirement as inventory of needs))Inventory of needs====
Intelligence watch centers and interdisciplinary groups, such as the Counterterrorism Center, can create and update requirements lists. Commercial [[customer relationship management]] (CRM) software or the more-powerful [[enterprise relationship management]] (ERM) systems might be adapted to managing the workflow separate from the most sensitive content. No collector is directed (required) to collect on the basis of these lists, and the lists are not addressed to any single collector. CRM, ERM and social-networking software routinely build ''ad hoc'' alliances for specific projects (see [[#NATO Collection Guidance|NATO Collection Guidance]], above).

[[File:Net2.jpg| thumb |alt=Spheres of several colors, connected by lines|A simple business relationship, such as CRM and ERM; compare to a [[semantic web]] and [[mind maps]], with related (but different) functions.]]

Branch and station chiefs have refused to handle the Periodic Requirements List (PRL) because these are "not really requirements," i.e., they are not requests to the clandestine collector for information which only he can provide. Intelligence requirements in the PRL may be crafted to elicit information from a specific source, sidestepping a request process which could have ended in denial.<ref name="Heffter"/>

PRLs are sometimes used for guidance, despite their description as inventories. Revised three times a year, they are the most up-to-date requirement statements and their main subject is current affairs of political significance. Although the inventory of needs is a valuable analytical instrument in the intelligence-production office which originates it, it cannot set priorities.

====((anchor|The requirement as directive))Directives====
Although short, prioritized directives for collection missions have come from top-level inter-agency policy boards, directives more often come from lower managerial levels. They are most useful in the following circumstances: 
*Where a command relationship exists
*Where there is only one customer, or one customer is more important than the others
*Where a single method of collection, with precise, limited, comprehensible capabilities, is involved

Technical collection methods are the least ambiguous, with meaningful priorities and actual, scheduled resources. HUMINT is flexible, but uses a wider range of methods. Agencies requiring HUMINT prepare lists of priorities which establish goals, provide a basis for planning and summarize the information needs of consumers.

====((anchor|The requirement as request))Requests====
Most requirements fall into this category, including the majority of those with requirement-tracking identifiers in a community-wide numbering system administered by a central group.  Requests vary, from a twenty-word question to a fifty-page questionnaire and asking for one fact or a thousand related facts. Its essence is the relationship between requester and collector.
 	 
A variant on the request is the solicited requirement, in which the request itself is requested by the collector. The collector informs the customer of their capability and asks for requirements tailored to it. The consumer and collector then negotiate a requirement and priority. In clandestine collection, solicited requirements are regularly used for legal travelers, for defectors and returnees, and for others whose capability or knowledge can be used only through detailed guidance or questioning. Solicited requirements blend into jointly developed ones, in which collector and consumer work out the requirement (usually for a subject of broad scope, at the collector's initiative).

====((anchor|System and administration|Discipline: method and language))Administration====
A department (or agency) which collects intelligence primarily to satisfy its own requirements usually maintains an internal requirements system with its own terminology, categories and priorities, with a single requirements office to direct its collection on behalf of its consumers. One requirements office, or a separate branch of it, represents collector and consumer in dealing with other agencies. Where consumers depend on many collectors and collections serve consumers throughout the community, no such one-to-one system is possible and each major component (collector or consumer) has its own requirements office.
 
Requirements offices are middlemen, with an understanding of the problems of those they represent and those whom they deal with on the outside. A consumer requirements officer must find the best collection bargain he can for his analyst client, and a collector requirements officer must find the best use for the resources he represents and protect them from unreasonable demands.

== Source sensitivity ==
Intelligence taken from sensitive sources cannot be used without exposing the methods or persons providing it. A strength of the British penetration of the German [[Enigma machine|Enigma]] cryptosystem was that no [[Ultra (cryptography)|information learned from it or other systems]] was used for operations without a more plausible reason for the information leak that the Germans would believe. If the movement of a ship was learned through deciphered Enigma, a reconnaissance aircraft was sent into the same area and allowed to be seen by the Axis so the detection was attributed to the aircraft. When an adversary knows that a cryptosystem has been broken, they usually change systems immediately, cutting off a source of information and turning the break against the attacker, or they leave the system unchanged and use it to deliver [[disinformation]].<ref>((Harv | Layton|1985))</ref>

In strategic arms limitation, a different sensitivity applied. Early in the discussion, the public acknowledgement of satellite photography elicited concern that the "Soviet Union could be particularly disturbed by public recognition of this capability [satellite photography]...which it has veiled."<ref>((cite web
  | last = Laird
  | first = Melvin R.
  | author-link = Melvin R. Laird
  | title = Memorandum for Assistant to the President for National Security Affairs, Subject: Revelation of the Fact of Satellite Reconnaissance in Connection with the Submission of Arms Limitation Agreements to Congress
  | date = June 8, 1972
  | url = http://www.gwu.edu/~nsarchiv/NSAEBB/NSAEBB231/doc02.pdf
  | id = Laird
  | access-date = 2007-10-02))</ref>

== Separating source from content ==
Early in the collection process, the identity of the source is removed from reports to protect clandestine sources from being discovered. A basic model is to separate the raw material into three parts:
# True source identity; very closely held
# Pseudonyms, [[code name]]s or other identifiers
# All reports from the source

Since the consumer will need some idea of source quality, it is not uncommon in the intelligence community to have several variants on the source identifier. At the highest level, the source might be described as "a person with access to the exact words of cabinet meetings". At the next level of sensitivity, a more general description could be "a source with good knowledge of the discussions in cabinet meetings". Going down another level the description gets even broader, as "a generally reliable source familiar with thinking in high levels of the government".

== ((anchor|Ratings by the Collection Department))Collection department ratings ==
In U.S. practice,<ref>((cite web 
 | author = US Department of the Army
 | url = https://fas.org/irp/doddir/army/fm2-22-3.pdf
 | title = FM 2-22.3 (FM 34-52) Human Intelligence Collector Operations
 | ref = ((harvid|FM 2-22.3))
 |date=September 2006
 | access-date = 2007-10-31
))</ref> a typical system, using the basic A-F and 1-6 conventions below, comes from ((Harv | FM 2-22.3 |loc= Appendix B, Source and Information Reliability Matrix)). Raw reports are typically given a two-part rating by the collection department, which also removes all precise source identification before sending the report to the analysts.
{| class="wikitable"
|+ Source ratings
! Code
! Source rating
! Explanation
|-
|A
|Reliable
|No doubt of authenticity, trustworthiness or competency; has a history of complete reliability
|-
|B
|Usually reliable
| Minor doubt about authenticity, trustworthiness or competency; has a history of valid information most of the time
|-
|C
| Fairly reliable
| Doubt of authenticity, trustworthiness or competency, but has provided valid information in the past
|-
|D
| Not usually reliable
| Significant doubt about authenticity, trustworthiness or competency but has provided valid information in the past
|-
|E
|Unreliable
| Lacking in authenticity, trustworthiness and competency; history of invalid information
|-
|F
| Cannot be judged
| No basis exists
|}

{| class="wikitable"
|+Information content ratings
|-
! Code
! Rating
! Explanation
|-
| 1
| Confirmed
| Confirmed by other independent sources; logical in itself; consistent with other information on the subject
|-
| 2
| Probably true
| Not confirmed; logical in itself; consistent with other information on the subject
|-
| 3
| Possibly true
| Not confirmed; reasonably logical in itself; agrees with some other information on the subject
|-
| 4
| Doubtfully true
| Not confirmed; possible but not logical; no other information on the subject
|-
| 5
| Improbable
| Not confirmed; not logical in itself; contradicted by other information on the subject
|-
| 6
| Cannot be judged
| No basis exists
|}

An "A" rating might mean a thoroughly trusted source, such as your own communications intelligence operation. Although that source might be completely reliable, if it has intercepted a message which other intelligence has indicated was deceptive the report reliability might be rated 5 (known false) and the report would be A-5. A human source's reliability rating would be lower if the source is reporting on a technical subject and its expertise is unknown.

Another source might be a habitual liar, but provides enough accurate information to be useful. Its trust rating would be "E"; if the report was independently confirmed, it would be rated "E-1".

Most intelligence reports are somewhere in the middle, and a "B-2" is taken seriously. It is sometimes impossible to rate the reliability of the source (often from lack of experience with it), so an F-3 could be a reasonably probable report from an unknown source. An extremely trusted source might submit a report which cannot be confirmed or denied, so it would get an "A-6" rating.

===((anchor|Evaluating Sources))Evaluating sources===
In a report rating the source part is a composite, reflecting experience with the source's reporting history, their direct knowledge of what is being reported and their understanding of the subject. Similarly, technical collection may have uncertainty about a specific report, such as partial cloud cover obscuring a photograph.

When a source is untested, "then evaluation of the information must be done solely on its own merits, independent of its origin".((citation needed|date=September 2014)) A primary source passes direct knowledge of an event to the analyst. A secondary source provides information twice removed from the original event: one observer informs another, who then relays the account to the analyst. The more numerous the steps between the information and the source, the greater the opportunity for error or distortion.

Another part of a source rating is proximity. A human source who participated in a conversation has the best proximity, but the proximity is lower if the source recounts what a participant told him was said. Was the source a direct observer of the event, or (if a human source) is he or she reporting hearsay? Technical sensors may directly view an event, or infer it. A geophysical [[infrasound]] sensor can record the pressure wave of an explosion, but may be unable to tell if an explosion was due to a natural event or an industrial accident. It may be able to tell that the explosion was not nuclear, since nuclear explosions are more concentrated in time.

If a human source who has provided reliable political information submits a report on the technical details of a missile system, the source's reliability in political matters only generally supports the likelihood that the source understands rocket engineering. If they describe rocket details making no more sense than a low-budget science-fiction movie, such a report should be discounted (a component of the source rating known as appropriateness).

===((anchor|Evaluating the information))Evaluating information===
Separate from the source evaluation is the evaluation of the report's substance. The first factor is ''plausibility'', indicating that the information is certain, uncertain, or impossible. Deception always must be considered for otherwise-plausible information.

Based on the analyst's knowledge of the subject, is the information something that reasonably follows from other things known about the situation? This is ''expectability''. If traffic analysis puts the headquarters of a tank unit at a given location, and IMINT reveals a tank unit at that location doing maintenance typical of preparation for an attack, and a separate COMINT report indicates that a senior armor officer is flying to that location, an attack can be expected. In this example, the COMINT report has the ''support'' of traffic analysis and IMINT.

===((anchor|Confirming Reports))Confirming reports===
When evaluating a report is difficult, its confirmation may be the responsibility of the analysts, the collectors or both. In the U.S. the NSA is seen as a collection organization, with its reports to be analyzed by the CIA and [[Defense Intelligence Agency]].

One example came from World War II, when U.S. Navy cryptanalysts intercepted a message in the [[JN-25]] Japanese naval cryptosystem clearly related to an impending invasion of "AF". Analysts in Honolulu and Washington differed, however, as to whether AF referred to a location in the Central Pacific or in the Aleutians. Midway Island was the likely Central Pacific target, but the U.S. commanders needed to know where to concentrate their forces. Jason Holmes at the Honolulu station knew that Midway had to make (or import) its fresh water and arranged for a message to be sent to the Midway garrison via a secure undersea cable, in a cryptosystem known to have been broken by the Japanese, that their desalination plant was broken. Soon afterwards, a message in JN-25 said that "AF" was short of fresh water (confirming the target was Midway).<ref name=Layton>((cite book
 | last = Layton |first=Edwin 
 | author-link = Edwin T. Layton 
 | title = And I Was There: Breaking the Secrets - Pearl Harbor and Midway 
 | url = https://archive.org/details/andiwastherepear00layt
 | url-access = registration
 | publisher = William Morrow & Co 
 | year =1985 
 | isbn = 0-688-04883-8
))</ref>

==See also==

*[[Intelligence analysis]]
*[[Intelligence analysis management]]
*[[Intelligence cycle management]]

==References==
((reflist))

((Intelligence cycle management))

((DEFAULTSORT:Collection Management))
[[Category:Intelligence assessment]]
[[Category:Intelligence analysis]]
[[Category:Intelligence gathering disciplines]]
[[Category:Military intelligence collection]]

Pages transcluded onto the current version of this page (help):

Intelligence collection management (edit)
Template:Ambox (view source) (template editor protected)
Template:Anchor (view source) (template editor protected)
Template:Category handler (view source) (protected)
Template:Citation needed (view source) (protected)
Template:Cite book (view source) (protected)
Template:Cite journal (view source) (protected)
Template:Cite web (view source) (protected)
Template:Delink (view source) (protected)
Template:Fix (view source) (protected)
Template:Fix/category (view source) (protected)
Template:Harv (view source) (template editor protected)
Template:Harvard citation (view source) (template editor protected)
Template:Harvid (view source) (template editor protected)
Template:Hlist/styles.css (view source) (protected)
Template:Intelligence cycle management (edit)
Template:Main other (view source) (protected)
Template:More footnotes needed (view source) (template editor protected)
Template:Multiple issues (view source) (template editor protected)
Template:Multiple issues/styles.css (view source) (template editor protected)
Template:Navbox (view source) (template editor protected)
Template:Pagetype (view source) (protected)
Template:Reflist (view source) (protected)
Template:Reflist/styles.css (view source) (protected)
Template:SDcat (view source) (protected)
Template:See also (view source) (template editor protected)
Template:SfnRef (view source) (template editor protected)
Template:Short description (view source) (protected)
Template:Short description/lowercasecheck (view source) (protected)
Template:Technical (view source) (template editor protected)
Template:Yesno (view source) (protected)
Template:Yesno-no (view source) (template editor protected)
Module:Anchor (view source) (template editor protected)
Module:Arguments (view source) (protected)
Module:Category handler (view source) (protected)
Module:Category handler/blacklist (view source) (protected)
Module:Category handler/config (view source) (protected)
Module:Category handler/data (view source) (protected)
Module:Category handler/shared (view source) (protected)
Module:Check for unknown parameters (view source) (protected)
Module:Citation/CS1 (view source) (protected)
Module:Citation/CS1/COinS (view source) (protected)
Module:Citation/CS1/Configuration (view source) (protected)
Module:Citation/CS1/Date validation (view source) (protected)
Module:Citation/CS1/Identifiers (view source) (protected)
Module:Citation/CS1/Utilities (view source) (protected)
Module:Citation/CS1/Whitelist (view source) (protected)
Module:Citation/CS1/styles.css (view source) (protected)
Module:Delink (view source) (protected)
Module:Disambiguation/templates (view source) (protected)
Module:Footnotes (view source) (template editor protected)
Module:Footnotes/anchor id list (view source) (template editor protected)
Module:Footnotes/anchor id list/data (view source) (template editor protected)
Module:Footnotes/whitelist (view source) (template editor protected)
Module:Format link (view source) (template editor protected)
Module:Hatnote (view source) (template editor protected)
Module:Hatnote/styles.css (view source) (template editor protected)
Module:Hatnote list (view source) (template editor protected)
Module:Labelled list hatnote (view source) (template editor protected)
Module:Message box (view source) (protected)
Module:Message box/ambox.css (view source) (protected)
Module:Message box/configuration (view source) (protected)
Module:Namespace detect/config (view source) (protected)
Module:Namespace detect/data (view source) (protected)
Module:Navbar (view source) (protected)
Module:Navbar/configuration (view source) (protected)
Module:Navbar/styles.css (view source) (protected)
Module:Navbox (view source) (template editor protected)
Module:Navbox/configuration (view source) (template editor protected)
Module:Navbox/styles.css (view source) (template editor protected)
Module:Pagetype (view source) (protected)
Module:Pagetype/config (view source) (protected)
Module:Pagetype/disambiguation (view source) (protected)
Module:Pagetype/setindex (view source) (protected)
Module:Pagetype/softredirect (view source) (protected)
Module:SDcat (view source) (protected)
Module:String (view source) (protected)
Module:TableTools (view source) (protected)
Module:Unsubst (view source) (protected)
Module:Wikitext Parsing (view source) (protected)
Module:Yesno (view source) (protected)

Return to Intelligence collection management.

Retrieved from "https://en.wikipedia.org/wiki/Intelligence_collection_management"