2.5.1.2. Section 2: Threat Summary. No change from a regular CDD to the threat summary of the IS-CDD; however, the Sponsor should strongly consider the cyber threats posed to an IS solution.

For reference or comparison, below is what the JCIDS Manual says for the CDD 2021 itself:

2.5.2. Section 2: Threat Summary. (Reference the Intelligence Supportability Guide described in Annex G to Appendix G to this enclosure)

2.5.2.1. The purpose of this section is to ensure the capability solution(s) being developed to address the capability and associated gaps are based on consistent threat environment information and references. All acquisition programs or capabilities expected to operate in a threat environment (lethal or non-lethal) must be developed IAW the most current threat products from the DIE.

2.5.2.2. Cite the latest approved threat products used during the development of the CDD. Update the threat summary from the validated ICD with current threat analysis from the DIE. As the threat environment may have evolved since the validation of the ICD, clearly identify threats that are consistent with factors used to determine the capability captured in the ICD. If new threats have emerged since the validation of the ICD, describe the threat capabilities as outlined for Section 2 of the ICD.

2.5.2.3. From the source document(s), outline the threat summary(ies) associated with the validated requirements addressed by the CDD. Consider evolving threats to on-going and follow-on RDT&E, production, and O&M resulting from technology transfer, espionage, and other adversarial collection efforts.

2.5.2.3.1. Summarize CIPs, in the manner expressed below, that are applicable to the KPPs and KSAs in the CDD. These can be CIPs that are associated with intelligence production requirements assigned to DIE and/or proposed CIPs that are part of the CDD currently under review.

2.5.2.3.1.1. Describe the relationship between the CIP and the supported KPP.

2.5.2.3.1.2. Cite the Community On-Line Intelligence System for End Users and Managers (COLISEUM) production requirement number, CIP number, and threat topic.

2.5.2.3.1.3. CIPs (IAW Reference [37]) are defined as a threat capability or threshold established collaboratively by the requirements sponsor and the capability developer, changes to which could critically impact the effectiveness and survivability of the proposed system. System Survivability threshold attribute requirements should be considered, when developing CIPs.

2.5.2.3.2. Include summaries of all applicable threats cited in the SS) KPP (i.e., Kinetic, CBRN, Environmental, EMS, and Cyber) if the operational context requires operation in such environments. These summaries will form the basis for a risk-managed approach to developing SS requirements.

2.5.2.4. Additionally, if the CDD is not based on a validated JCIDS document, provide the threat summary as outlined for Section 2 of an ICD.