Skip to content

Tactical Data Link Certification

Multi-agency certification across JITC, NMSC, FAA, and NSA. Unified tracking for Link 16, Link 22, MIDS, and space-based TDL programs.

Abstract gradient
TDL Certification
4
Certification agencies unified
Link 16/22
Protocol coverage
JITC
Interoperability testing
The Challenge

Multi-Agency Certification Bottlenecks

Program delays worth billions

Tactical data links form the connective tissue of modern joint operations. Link 16, Link 22, and emerging waveforms enable the real-time information sharing that joint and coalition forces depend upon.

Yet certification bottlenecks across multiple government agencies have become the primary schedule driver for major programs, delaying fielding by years.

Certification Agencies
JITC
Joint Interoperability
Test Command
NMSC
Navy Marine Corps
Spectrum Center
FAA
Federal Aviation
Administration
NSA
National Security
Agency (Crypto)
Thalorin
Unified Multi-Agency Tracking
Track all certification activities within a single workflow that surfaces interdependencies and identifies critical path items.
Case Study

MIDS Program Delays

The Multifunctional Information Distribution System program illustrates how certification bottlenecks affect major defense acquisition.

SAR
MIDS Selected Acquisition Report
December 2022

Schedule status assessed as Yellow due to certification bottlenecks—not technical challenges.

6,000+
MIDS JTRS Terminals
by 2024 (10x growth)
$2B
June 2024 Contracts
Split between vendors
Contract Awards
L3Harris$998.8M
Data Link Solutions$998.8M
Sustainment & JPR Investment
~$60Min separate delivery orders
$26.7M sustainment + $33.7M JPR work
Emerging Domain

Space-Based Link 16

The Space Development Agency conducted the first successful space-to-ground Link 16 transmission in November 2023—demonstrating that tactical data links can extend to satellite constellation nodes.

126
Link 16 Equipped Satellites
Operating in worldwide mesh network by end 2025
Space TDL Certification Requirements
FAA
Civilian interference prevention
JITC
Interoperability validation
NMSC
4-stage spectrum authorization
NSA
Cryptographic approval
Spectrum Management

Spectrum Access Constraints Limit Testing

MIDS JTRS TTNT variants require 22-channel, multiple frequency band operation to achieve design performance. However, current channel allocation for most CONUS-based integration and test events provides fewer than five channels.

Required channels
22
Available for testing
<5
Gap limits ability to validate Full Operational Capability

The gap between test environment spectrum access and operational requirements creates certification risk.

NMSC Certification Stages
1
Initial Application
Documentation submission
2
Technical Review
Frequency coordination
3
Testing Validation
Interference assessment
4
Final Certification
Operational approval
Thalorin
Automated Spectrum Workflows
Stage 1-4 tracking, temporary frequency assignments, and NMSC documentation management.
Multinational Transition

Link 22 Introduces Multinational Complexity

Link 11 sunset scheduled for 2025 is driving accelerated transition to Link 22 across NATO and allied forces. The seven-nation NATO Improved Link Eleven program established Link 22 as the replacement waveform.

HF-EPM mode capability remains pending due to US regulations on TRANSEC availability, limiting the full Link 22 capability set for some partner nations.

Compliance Costs
Software Levy
Per operational copy
$46,767
BCR Fee
Annual baseline configuration
$300K
NATO Nations
NILE program participants
7
Standard
STANAG 5522
Thalorin tracks conformance across participating nations while managing software levies, BCR fees, and FMS coordination alongside technical certification.
Problem Management

Joint Problem Report Investigation

When tactical data link systems exhibit anomalous behavior, JPR investigation processes determine root cause and corrective actions—coordinating across multiple contractors, agencies, and potentially allied nations.

Report
Anomaly documented
Investigate
Cross-contractor coordination
Remediate
Corrective actions
Recertify
Updated certification
JPR Resource Investment
~$60M
Allocated for MIDS sustainment and investigations
Thalorin
JPR Compliance Management
Track problem reports across OEM boundaries with resolution status and certification implications. Document findings, track remediation, maintain the evidence chain for recertification.
The Imperative

Certification Cannot Be the Bottleneck

Tactical data link programs cannot afford certification bottlenecks that delay capability to warfighters.

Space-based TDL expansionCrypto modernization growthLink 22 transitionCoalition interoperability

By consolidating multi-agency coordination, spectrum management, multinational compliance, and problem report tracking within integrated workflows, organizations can identify and address certification risks before they become program delays.

Questions

Common questions

Why is tactical data link security not just network security?

Because the link is a radio, and the threat model includes an adversary who is receiving your transmissions whether or not they can read them. Protection therefore has two independent layers: cryptographic protection of the message content, and transmission security that denies an adversary the ability to detect, exploit or jam the signal itself. A link can be cryptographically sound and still leak operationally useful information through its emissions, which is a category of risk that has no analogue in an enterprise network.

What determines whether two platforms can actually exchange data?

Agreement at every layer at once — the same link standard, compatible message implementations, aligned network design and time reference, and matching cryptographic keying material for the period concerned. Any one of those out of alignment produces silence or, worse, partial exchange that looks like a working link. This is why interoperability is established by test rather than by inspection of specifications: each platform implements a subset, and the intersection is what you actually have.

What does cryptographic modernisation change for a data link programme?

It turns a communications question into a schedule and logistics one. Modernisation obliges platforms to move to new cryptographic implementations, and a mixed fleet has to remain interoperable during the transition — which means both the old and new configurations must be managed, keyed and tested concurrently. The constraint that binds is rarely the cryptography; it is fleet upgrade timing, and platforms that fall behind lose interoperability with those that have moved.

How does key management fail on tactical links?

Operationally, not cryptographically. Keying material has a validity period, has to be distributed to every participant before it starts, and has to be loaded onto platforms that may be deployed, in maintenance or offline. The failure is almost always a platform that did not receive or load the current material in time, which presents as a platform that cannot join the network — and diagnosing it as a radio fault rather than a keying one costs the mission time it did not have.

How do coalition partners join a data link network?

Through a combination of technical compatibility, a network design that assigns them participation, and a release authorisation covering both the equipment and the keying material — which is where it usually stops. Sharing cryptographic material with a partner nation is an export and disclosure decision made under its own authority, on its own timeline, and it is not implied by an interoperability agreement or by the partner operating compatible equipment.

Regulatory state described as of August 2026. Requirements change; verify against the current rule before relying on any date above.

Certification bottlenecks solved.

Tactical data link programs cannot afford delays that keep capability from warfighters. Thalorin provides the unified certification tracking that TDL programs require.