Information Technology Standards Registry (DISR). While the DISR hosts many standards, JTNC-developed standards origi- nated in, and apply to, tactical SDRs.
JTNC recently developed an Open Systems Architecture Pro- curement Requirements Guide for Waveforms and Tactical Radios. Te guidance is modeled after language from DOD Instruction (DODI) 5000.02, the BBP 3.0 implementation directive, DOD Open Systems Architecture Contract Guide- book for Program Managers version 1.1, and recently released DOD requests for information and proposals. Te intent of the document is to increase DOD and industry adoption of open systems architecture. It is useful to program management offices procuring affordable SDR products and capabilities, providing recommendations for input to solicitations.
Te JTNC DOD Waveforms Standards Directorate continues to lead the effort based on proactive implementation of BBP 3.0 through collaboration with the open systems community. In FY16, the directorate engaged with more than 20 PM offices (leaders and technical experts) across the services, eight other government organizations, 14 industry stakeholders, three stan- dards organizations and two allies via working groups, meetings and training events. Te collaborative effort and open systems approach enabled the development of Software Communica- tions Architecture (SCA) Specification 4.1, the architecture framework that assists SDR development and meets military and commercial application requirements.
SECURITY GAPS While SDRs offer substantial improvements in communication capabilities, PM offices should strategically address identi- fied security gaps. Te team analyzing waveform security has observed waveform security gaps that require strategic solutions.
Te SDR development environment for security was created in 2005 based on National Security Agency Type 1 certifica- tion requirements to ensure trusted communication of classified information on radio platforms and pre-evaluation of waveform applications. Since SDRs are indeed software-based, the code is as potentially vulnerable as any other code. But because of the importance of this link in the digital chain, the security of the code is even more important. Cybersecurity threats and defensive techniques have both evolved to a new level of sophisti- cation, increasing the risk of compromise to the current products as a result. Development efforts compliant with SCA 4.1 miti- gate security risks based on incorporated architectural measures against more contemporary threats.
Coupled with outdated security controls is recognition that current DOD security reviews are too limited. Te DOD infor- mation assurance certification and accreditation process and risk management framework (RMF) control application are not focused on software-level requirements. DOD needs to invest in the development of an expanded life cycle approach for wave- form software based on the RMF controls.
To maximize the benefit to the government of funded software development, PMs should be specifying, at a minimum, gov- ernment purpose rights software and appropriate waveform documentation. Over the course of five in-depth analyses, JTNC has developed an experience-derived checklist of wave- form artifacts (including source code) that the team uses to make observations in the areas of interoperability, security, affordabil- ity and exportability. Tis list, referred to as entrance criteria for a JTNC waveform analysis, is a resource that PM offices can obtain by contacting JTNC and leverage during waveform pro- curement to improve the end product.
CONCLUSION JTNC will continue to execute its mission toward the vision assigned by the undersecretary of defense for acquisition, tech- nology and logistics and the DOD chief information officer for “interoperable, secure, and affordable waveforms and wireless communications in support of service, multiservice and coali- tion forces.” With a uniquely interagency perspective, experience base from waveform analyses and recommended standards from an open systems approach, JTNC will continue to fulfill its role as technical adviser and share observed trends along with associ- ated recommendations.
For more information or to request the white paper “Electronic Protection (EP) of Tactical Radio Systems,” contact the JTNC Public Affairs Office at
JTNC.Public.Affairs@
navy.mil. For CAC-enabled access, go to
https://www.dodir.mil/jtnc_docs#.
LT. COL. MATTHEW A. “MATT” JURY is deputy director of JTNC, San Diego, California, responsible for providing oversight and management in the execution of tactical and strategic plans. He has a master’s degree in acquisition management from Florida Institute of Technology and a bachelor’s degree in environmental engineering from the U.S. Military Academy at West Point. He is Level III certified in program management and a member of the Army Acquisition Corps.
+
ASC.ARMY.MIL 97
SCIENCE & TECHNOLOGY
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72 |
Page 73 |
Page 74 |
Page 75 |
Page 76 |
Page 77 |
Page 78 |
Page 79 |
Page 80 |
Page 81 |
Page 82 |
Page 83 |
Page 84 |
Page 85 |
Page 86 |
Page 87 |
Page 88 |
Page 89 |
Page 90 |
Page 91 |
Page 92 |
Page 93 |
Page 94 |
Page 95 |
Page 96 |
Page 97 |
Page 98 |
Page 99 |
Page 100 |
Page 101 |
Page 102 |
Page 103 |
Page 104 |
Page 105 |
Page 106 |
Page 107 |
Page 108 |
Page 109 |
Page 110 |
Page 111 |
Page 112 |
Page 113 |
Page 114 |
Page 115 |
Page 116 |
Page 117 |
Page 118 |
Page 119 |
Page 120 |
Page 121 |
Page 122 |
Page 123 |
Page 124 |
Page 125 |
Page 126 |
Page 127 |
Page 128 |
Page 129 |
Page 130 |
Page 131 |
Page 132 |
Page 133 |
Page 134 |
Page 135 |
Page 136 |
Page 137 |
Page 138 |
Page 139 |
Page 140 |
Page 141 |
Page 142 |
Page 143 |
Page 144 |
Page 145 |
Page 146 |
Page 147 |
Page 148 |
Page 149 |
Page 150 |
Page 151 |
Page 152 |
Page 153 |
Page 154 |
Page 155 |
Page 156 |
Page 157 |
Page 158 |
Page 159 |
Page 160 |
Page 161 |
Page 162 |
Page 163 |
Page 164 |
Page 165 |
Page 166 |
Page 167 |
Page 168 |
Page 169 |
Page 170 |
Page 171 |
Page 172 |
Page 173 |
Page 174 |
Page 175 |
Page 176
