23.10.2014 Views

jp3_12r

jp3_12r

jp3_12r

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter IV<br />

nation states, groups, or individuals, and the parts of cyberspace they control are not<br />

necessarily either within the geographic borders associated with the actor’s nationality, or<br />

proportional to the actor’s geopolitical influence. A criminal element, a politically motivated<br />

group, or even an individual may have a greater presence and capability in cyberspace than<br />

many nations do today. Regardless of what operational phase may be underway, it is always<br />

important to determine what authorities are required to execute CO. Cyberspace planners<br />

must account for the lead time to acquire the authorities needed to implement the desired<br />

cyberspace capabilities. This does not change the JFC’s planning fundamentals, but does<br />

emphasize the importance of coordination with interagency partners, who may have<br />

authorities that are different from DOD. Despite the additional considerations and<br />

challenges of integrating CO in JFC planning, planners can use many elements of the<br />

traditional processes to implement the JFC’s intent and guidance.<br />

b. Cyberspace-Related Intelligence Requirements (IRs). During mission analysis,<br />

the joint force staff identifies significant gaps in what is known about the adversary and other<br />

relevant aspects of the OE and formulates IRs. IRs are general or specific subjects upon<br />

which there is a need for the collection of information or the production of intelligence.<br />

Based on the command’s IRs, the intelligence staff develops more specific questions known<br />

as information requirements (those items of information that must be collected and processed<br />

to develop the intelligence required by the commander). Information requirements related to<br />

cyberspace may include: network infrastructures, personnel status and readiness of<br />

adversaries’ equipment, and unique cyberspace signature identifiers such as<br />

software/firmware versions, configuration files, etc.<br />

For additional information on IRs, see JP 2-01, Joint and National Intelligence Support to<br />

Military Operations.<br />

(1) Requests for Information (RFIs). Cyberspace planners can submit an RFI to<br />

generate intelligence collection efforts in support of CO support to JOPP. RFIs respond to<br />

customer requirements, ranging from dissemination of existing products through the<br />

integration or tailoring of on hand information to scheduling original production. The<br />

intelligence office translating the customer’s requirement and the primary intelligence<br />

producer determine how best to meet the customer’s needs. The information must be timely,<br />

accurate, and in a usable format.<br />

For additional information on RFIs, see JP 2-01, Joint and National Intelligence Support to<br />

Military Operations.<br />

(2) Tasking, Collection, Processing, Exploitation, and Dissemination (TCPED)<br />

Architecture. The DOD’s global connectivity has enabled joint force collection managers<br />

to levy tasking against all-source intelligence assets and resources, and submit tasking,<br />

collection, and production requirements directly to the appropriate CCDR. Further,<br />

collection databases can be leveraged via reachback to retrieve current and historical<br />

products. However, much of the TCPED may occur outside the theater because the sheer<br />

volume of requirements for first and second phase exploitation may quickly overwhelm intheater<br />

assets.<br />

IV-2 JP 3-12

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!