Department of War | Counter-UAS & Tactical Edge AI
You do not lose readiness on the battlefield. You lose it in the contract and the architecture diagram.
Adversary unmanned systems compress the kill chain, saturate the electromagnetic spectrum, and punish stove-piped defenses. Here is how open, modular Edge AI restores decision advantage—from forward maneuver brigades under Project Flytrap to domestic installations under FORTRESS America.
01
Compress the OODA loop from minutes to seconds under uncertainty
02
Keep sensing, fusing, and tracking locally when backhaul links drop
03
Eliminate six-screen "swivel-chair" silos across sensors and C2
04
Enforce FIPS 140-3, signed models, and bounded human authority
Adversary unmanned systems compress engagement timelines, widen the reconnaissance envelope, and make it exponentially harder for forces to hide, concentrate, communicate, or maneuver. Pushing artificial intelligence to the tactical edge restores decision advantage—converting raw radar, radio-frequency (RF), acoustic, and electro-optical sensor streams into unified, actionable tracks before an incoming drone completes its attack run.
Across the Department of War, counter-unmanned aircraft systems (C-UAS) policy has shifted from ad-hoc urgent operational needs to a unified, department-wide architecture. From the establishment of Joint Interagency Task Force 401 (JIATF-401) and the Defense Autonomous Warfare Group (DAWG) to the September 30, 2026 announcements of the four-star Autonomous Warfare Command (AutoWarCom), FORTRESS America, and Project Meridian, Pentagon directives emphasize the same mandate: pair active and passive defenses with open, modular architectures across Doctrine, Organization, Training, Materiel, Leadership and Education, Personnel, Facilities, and Policy (DOTMLPF-P).
Crucially, Department of War strategy warns that non-integrated, redundant solutions slow the force down and overload operators. Paragon Micro, through its Public Sector Division, helps program offices, installation commanders, and Federal System Integrators turn Edge AI from a briefing buzzword into a fieldable, governable, cyber-resilient capability engineered to survive degraded networks.
Bottom line up front (BLUF)
- Drones are an information problem before they are a fires problem: Formations now enter continuous multi-sensor observation before hearing the first shot. Winning the timeline requires fusing disparate sensor alerts into a single track at machine speed.
- End the six-screen "swivel-chair" bottleneck: As the U.S. Army's 2nd Cavalry Regiment proved while evaluating 50+ vendor systems in Project Flytrap, proprietary sensor silos paralyze troop commanders. Open middleware standards like the Integrated Sensor Architecture (ISA) and MOSA are mandatory.
- Design for DDIL and real SWaP-C physics: Edge inference nodes must continue classifying targets and cueing effectors when backhaul links are jammed, while respecting strict vehicle power bus, thermal, and battery budgets.
- Calibrate human authority through "reps and sets": Responsible AI governance requires traceable logs, signed model updates, and repeated field training iterations so commanders understand model confidence boundaries before delegating machine-speed responses.
- Enforce 2026–2027 cyber and supply-chain gates: Every C-UAS edge build must account for the September 21, 2026 FIPS 140-3 transition, CMMC Phase 1 / NIST SP 800-171 safeguards, UFC 4-010-06 control-system segmentation, and the December 23, 2027 NDAA Section 5949 semiconductor ban.
Chapter 1
The battlefield already watches you
A maneuver formation or domestic installation no longer "enters contact." It enters continuous, multi-spectral observation long before the first kinetic round is fired. Modern operational doctrine recognizes this structural shift: low-cost unmanned systems saturate the operating environment, creating persistent overhead surveillance that strips away traditional concealment, compresses movement windows, and exposes command posts through their electromagnetic emissions.
Department of War strategy documents state this reality plainly. The proliferation of inexpensive commercial and military-grade drones has democratized precision strike—pushing air-to-ground threat vectors that once required exquisite strike aircraft all the way down to the platoon, the logistics convoy, and the domestic base flight line.
Forward maneuver (Project Flytrap)
The reconnaissance-strike complex
In the tactical close fight, brigades confront a networked reconnaissance-strike complex combining enemy ISR drones, electronic warfare (EW) direction-finding, one-way attack munitions, and precision artillery. Functionally, it operates like a connected alarm system wired to a weapon: sensors spot a unit's thermal or RF signature, networks pass the coordinates, and fires arrive within minutes.
Theater deep fight (MDCPAC & CDCL)
Inside the Weapons Engagement Zone
In the Indo-Pacific, Multi-Domain Command Pacific (MDCPAC) operates inside sophisticated anti-access/area-denial (A2/AD) networks where legacy 72-hour joint targeting cycles are obsolete. Surviving and creating windows of overmatch requires an integrated Cross-Domain Contact Layer (CDCL) that compresses sensor-to-shooter loops from minutes to seconds.
Homeland installations (FORTRESS America)
Coordinated waves over domestic bases
Unmanned saturation is no longer confined overseas. U.S. Northern Command (NORTHCOM) tracked roughly 420 unauthorized drone sightings over domestic installations in the year ending September 2025 (up 82%), followed by coordinated waves of 12 to 15 drones over Barksdale Air Force Base in March 2026.
Operational mindset shift
If your organization treats drones as a niche air-defense problem, it will lose the timeline. If your organization treats drones as an information and architecture problem that precedes a fires problem, you can break the adversary's kill chain before launch.
Chapter 2
Reframe Counter-UAS as a mission command problem
Effective Counter-UAS does not begin with the kinetic interceptor, the electronic jammer, or the high-energy laser. It begins with command and control under uncertainty. U.S. Army mission command doctrine (ADP 6-0 and FM 3-0) emphasizes that combat decision-making requires leaders to act decisively with imperfect information—balancing the risk of acting immediately on a partial picture against the danger of waiting too long for certainty.
Small unmanned aircraft systems (sUAS) weaponize that dilemma by compressing the Observe–Orient–Decide–Act (OODA) loop into seconds:
- Observe
Radar, RF, acoustic, and optical sensors detect a small, low-signature object moving through ground clutter or urban multipath interference.
- Orient
Operators must determine within seconds whether the return is bird clutter, a friendly quadcopter, a commercial delivery drone, or a hostile one-way attack munition.
- Decide
Commanders must weigh statutory authorities (such as 10 U.S.C. § 130i on domestic bases), collateral damage rules of engagement, and electromagnetic fratricide risks.
- Act
The formation or installation must cue the right kinetic or non-kinetic effector and verify neutralization before the airframe reaches its terminal dive.
From sensor glut to command clarity
Why adding more unintegrated sensors slows commanders down
When a brigade or base security force fields six different counter-drone sensors from six different vendors without an open integration layer, the result is not situational awareness—it is cognitive paralysis.
During early iterations of the U.S. Army's Project Flytrap experimentation series in Europe, troop and battalion commanders reported severe cognitive overload trying to correlate six or seven standalone vendor monitors while manually bridging data between higher-echelon Maven Smart System (MSS) terminals and tactical-edge ATAK tablets.
- Raw video is a liability without triage: Streaming uncompressed high-definition EO/IR video from every perimeter tower chokes tactical bandwidth and forces soldiers to stare at empty screens for hours.
- Uncorrelated alerts multiply false alarms: Without edge sensor fusion, a single quadcopter detected by radar, RF, and thermal cameras generates three separate alarms at three different workstations.
- Edge AI automates the science of control: By running computer vision, RF signal classification, and multi-sensor track correlation directly on ruggedized edge servers, Edge AI filters out clutter and presents the commander with one unified track, a confidence score, and a recommended response.
Chapter 3
Edge AI as the shortest path to decision advantage
Applied correctly at the tactical edge, artificial intelligence performs one vital mission function: it converts high-volume raw sensor telemetry into actionable combat information inside the enemy's decision cycle. That capability aligns directly with the Department of War Data Strategy—which directs leaders to treat data as a weapon system—and the January 9, 2026 Department of War Artificial Intelligence Strategy, which mandates federated data catalogs within 30 days, consolidates analytics into a centralized War Data Platform, and accelerates reciprocal Authorizations to Operate (ATO) for edge and enterprise AI models.
In practical Counter-UAS architectures, Edge AI delivers four operational advantages:
01 · Clutter suppression
Filter noise at the sensor source
Convolutional neural networks and acoustic/RF classifiers running on forward GPU nodes distinguish micro-doppler rotor signatures from birds, windblown foliage, and commercial vehicle traffic—slashing false-positive alarm rates and preserving operator alertness across 12-hour watch shifts.
02 · Multi-modal correlation
Fuse three alerts into one story
When passive RF sensors detect a controller hop, 3D radar locks an azimuth, and an EO/IR gimbal slews to the target, edge fusion middleware correlates the timestamps and coordinates into a single, deduplicated track ID on the Common Operating Picture (COP).
03 · Automated cueing
Recommend ROE-aligned effectors
Agentic decision-support models evaluate the track's flight profile, payload class, and proximity to friendly assets against pre-loaded rules of engagement—recommending whether to cue a directional RF jammer, a high-power microwave array, a kinetic interceptor, or a soldier with a shotgun at 50 meters.
04 · Zero backhaul latency
Infer locally when links go dark
When an autonomous one-way attack drone closes at 50 meters per second, a unit cannot wait for video frames to traverse a congested satellite link to a continental U.S. cloud server. Local GPU inference executes in milliseconds right at the sensor mast or command vehicle.
The strategic payoff of this architecture was underscored at AUSA 2026 by leaders from the 2nd Cavalry Regiment and Multi-Domain Command Pacific: by using edge AI systems to orchestrate sensors and manage the fires chain, formations automate the science of control—freeing commanders from spreadsheets and swivel-chair monitors so they can focus on the art of command, tactical judgment, and maneuver initiative.
Chapter 4
Build a C-UAS kill web that survives degraded networks and SWaP-C limits
Department of War counter-UAS guidance emphasizes near-term improvements in detection alongside layered active and passive defenses, while preparing formations for high-stress future scenarios involving autonomous swarms and severe electronic attack. In Ukraine, Royal United Services Institute estimates indicate that forces lose roughly 10,000 drones per month—primarily to electronic warfare jamming—driving both sides to field fiber-optic FPV drones and onboard optical terminal navigation that operate with zero RF emissions.
Defending against silent, autonomous threats while your own communications are jammed requires engineering the C-UAS architecture for DDIL (Denied, Degraded, Intermittent, and Limited) spectrum and harsh physical SWaP-C (Size, Weight, Power, and Cooling) constraints:
01 · Sensor & airframe edge
Passive RF, radar, EO/IR optics, and small attritable interceptor drones
SWaP-C reality: Putting a full-stack GPU autonomy suite onto a hip-carried quadcopter drains its battery. Airframes require lightweight, milliwatt-optimized vision models, while heavy multi-sensor fusion belongs on vehicle or shelter nodes.
02 · Forward rugged compute
Short-depth ruggedized GPU servers (e.g., MIL-STD-810H / NEBS Level 3 nodes) in vehicles, shelters, and perimeter towers
DDIL behavior: Executes local object recognition, multi-sensor track fusion, and automated camera slewing with zero dependency on external cloud reachback.
03 · Tactical mesh & store-and-forward
MANET mesh radios, private 5G, and local NVMe telemetry buffers
DDIL behavior: Reroutes track alerts across peer nodes when links drop, caches high-resolution engagement logs during EMCON silence, and burst-syncs deltas when bandwidth returns.
04 · Power & thermal foundation
Vehicle alternators, -48V DC buses, tactical solar/lithium-ion banks, and base microgrids
SWaP-C reality: You cannot endlessly pile circuit boards onto a vehicle electrical bus or leave base server room HVAC off backup circuits without triggering thermal shutdowns.
This is where military doctrine and hardware engineering converge. Mission command thrives when subordinate elements can act in accordance with the commander's intent amid chaos. That same principle must govern C-UAS edge infrastructure: pre-stage local compute, size battery and generator backup for the full stack (including cooling and switches), define disconnected operating bounds, and let the local defense keep tracking and defeating threats when higher-echelon links go dark.
Chapter 5
Design for speed and scale: open, modular, and integrated
Across five years of Pentagon counter-drone directives, one architectural lesson stands above all others: the Joint Force cannot afford proprietary, stove-piped C-UAS "science projects" that lock units into a single vendor's hardware and software stack.
The 2021 Counter-sUAS Strategy warned that early urgent procurements produced *"many non-integrated, redundant solutions."* The December 2024 Department of War Strategy for Countering Unmanned Systems doubled down—demanding delivery at speed and scale, prioritizing integrated, open, modular solutions, and targeting the steep cost curve between cheap threat drones and expensive kinetic interceptors. Over the past 15 months, the department has backed that strategy with sweeping organizational and acquisition enforcement:
Joint C-UAS Authority (Aug & Dec 2025)
From JCO and Replicator 2 to JIATF-401 & DAWG
On August 28, 2025, the Pentagon disestablished the legacy Joint Counter-sUAS Office (JCO) and activated Joint Interagency Task Force 401 (JIATF-401)—codified in the FY2026 NDAA with authority to approve up to $50 million per rapid C-UAS initiative and leading the May 2026 five-base directed-energy pilot.
Concurrently, the Defense Autonomous Warfare Group (DAWG) absorbed the Replicator initiative (backed by a $54.6 billion FY2027 budget request) ahead of the October 1, 2027 stand-up of the four-star Autonomous Warfare Command.
Acquisition Overhaul (Nov 7, 2025)
Warfighting Acquisition System & MOSA
Secretary Hegseth's November 7, 2025 memorandum replaced the legacy Defense Acquisition System with the Warfighting Acquisition System (WAS)—making commercial solutions the default preference, requiring at least two qualified sources for critical program content unless waived, and enforcing a Modular Open Systems Approach (MOSA).
Under WAS, C-UAS programs must publish documented, machine-readable interfaces so third-party sensors, AI models, and effectors can compete at the module level without OEM lock-in.
Field-Validated Middleware (Nov 2025–2026)
Integrated Sensor Architecture (ISA)
During Project Flytrap 4.5 in Europe, U.S. Army teams deployed the Integrated Sensor Architecture (ISA) to solve data sharing across incompatible vendor systems—translating disparate radar, RF, and optical feeds into standardized, open-architecture data formats.
V Corps and the 2nd Cavalry Regiment now use open-architecture compliance as a mandatory screening gate before any vendor's C-UAS tool is allowed to touch tactical formations.
What this means for program offices and integrators: Edge AI hardware and software must plug cleanly into a system-of-systems architecture. Any C-UAS sensor or inference box that insists on its own proprietary display tablet or refuses to publish machine-readable tracks into ISA, ATAK, or Maven Smart System is a liability on the modern battlefield.
Chapter 6
Trust the machine, but govern the machine
When an air-defense crew or base security watch officer has ten seconds to decide whether to jam, laser, or kinetically engage an inbound track, they will not use an AI model they do not trust. Building operator confidence in safety-critical and lethal C-UAS environments requires baking Department of War Responsible AI (RAI) ethical principles—Responsible, Equitable, Traceable, Reliable, and Governable—directly into the edge architecture from day one.
Traceability
Explainable confidence at combat speed
The edge interface must log and display why an algorithm classified a track as a hostile one-way attack munition—exposing the contributing sensor sources, signal-to-noise ratio, model version, and confidence score in a glanceable format.
Reliability
Tested in real clutter and weather
Models trained solely on synthetic or clear-sky range data fail in rain, urban RF multipath, and heavy electronic jamming. Reliability requires continuous retraining on real field telemetry and validation against novel adversary airframes.
Governability
Instant override and rollback
Operators must be able to constrain engagement zones, adjust confidence thresholds, override automated recommendations instantly, or roll back a degraded model weight to the last known good baseline with a single command.
Responsible authority
Calibrated through "reps and sets"
As commanders in Multi-Domain Command Pacific and 2nd Cavalry Regiment emphasized at AUSA 2026, units keep a human in the loop while using repeated training "reps and sets" to learn what an AI agent can and cannot do—setting explicit risk boundaries before expanding autonomous speed.
Chapter 7
Secure the edge: treat every node as contested
Counter-UAS operations do not merely defend against physical airframes; they defend against an adversary actively probing your electromagnetic signature, tactical networks, and facility control seams. Forward sensor towers, mobile command shelters, and base perimeter cameras must be engineered under the assumption that physical capture and network intrusion attempts are inevitable.
Meeting the Department of War's September 30, 2027 Target-Level Zero Trust deadline across both tactical edge deployments and FORTRESS America installations requires enforcing six non-negotiable security and supply-chain controls:
Six cybersecurity & compliance mandates for C-UAS edge infrastructure
- Mandate FIPS 140-3 and plan for CNSA 2.0: On September 21, 2026, NIST moved all FIPS 140-2 cryptographic certificates to its Historical List. Every new C-UAS radio, rugged laptop, edge server, and self-encrypting drive handling Controlled Unclassified Information (CUI) must specify FIPS 140-3 validated modules—and National Security System (NSS) acquisitions must support quantum-resistant CNSA 2.0 algorithms starting January 1, 2027.
- Enforce hardware root of trust and rapid cryptographic sanitization: Specify servers with Silicon Root of Trust, TPM 2.0, Secure Boot, and tested Secure Erase procedures. If a forward C-UAS sensor node risks being overrun, operators must be able to sanitize cached sensor logs and fine-tuned model weights in seconds.
- Cryptographically sign and verify all model and container updates: Prevent supply-chain poisoning by requiring edge nodes to verify digital signatures before executing any over-the-air or USB model weight, container image, or firmware update.
- Segment C-UAS and facility control networks under UFC 4-010-06: On domestic installations, perimeter cameras, radar controllers, and microgrid switchgear are classified as Facility-Related Control Systems (FRCS). Microsegment sensor VLANs from enterprise IT so a compromised perimeter camera cannot pivot into the base command center—blocking the exact lateral-movement playbook used by Volt Typhoon.
- Maintain active CMMC Phase 1 & NIST SP 800-171 compliance: While the Department of War suspended CMMC Phase 2 third-party assessment mandates on July 13, 2026 pending its Reform Task Force review, CMMC Phase 1 remains in full force. Every integrator staging C-UAS configurations or handling CUI test data must maintain current SPRS scores, annual Level 2 self-assessment affirmations, and full NIST SP 800-171 Rev 2 safeguards.
- Scrub bills of materials for Section 889, ASDA, and Section 5949: Enforce FAR 52.204-25 (barring Hikvision, Dahua, Huawei, ZTE, and Hytera components inside optical gimbals and radios), FAR 52.240-1 (American Security Drone Act), and prepare now for the December 23, 2027 NDAA Section 5949 prohibition on SMIC, YMTC, and CXMT semiconductors across COTS servers and cameras.
Chapter 8
Operationalize it: training, metrics, and live experimentation
Department of War counter-UAS strategy demands rigorous, quantitative measures of effectiveness. The fastest way to waste procurement dollars on Edge AI is to evaluate a model in a clean vendor lab using abstract "classification accuracy" slides rather than measuring end-to-end mission outcomes in realistic clutter and electronic attack.
Five mission-outcome metrics every C-UAS pilot must measure
- Time-to-alert & characterize
Measure elapsed seconds from initial sensor horizon break to a classified, actionable track on the commander's display.
- Operator workload
Track false alarms per shift, screens monitored per soldier, and cognitive load during multi-axis swarm saturation.
- Track continuity
Verify whether the fused track holds a single ID through low-altitude terrain masking, hovering, and high-G evasive maneuvers.
- Open interoperability
Confirm zero-loss schema translation across ISA, ATAK, and Maven Smart System without proprietary vendor middleware lock-in.
- DDIL survivorship
Pull the backhaul fiber or jam the primary reachback link mid-trial and measure how local edge inference and cueing perform.
Proven models of high-stress experimentation and training
Live, force-on-force and multi-system stress testing is now the gold standard across the department:
- Multi-system swarm stress tests: In July 2024 at Yuma Proving Ground, Army counter-sUAS evaluators set the benchmark by launching more than 40 simultaneous UAS targets per session to stress command-and-control and sensor fusion across nine separate systems—a model now expanded under JIATF-401 and the May 2026 five-base directed-energy pilot.
- Iterative brigade breaching in Project Flytrap: Between March 2025 and May 2026, the 2nd Cavalry Regiment and V Corps executed five progressive iterations of Project Flytrap in Poland and Lithuania—evaluating roughly 50 vendor systems, validating ISA data sharing, adapting the SORA (Suppress, Obscure, Reduce, Assault) multi-domain breaching framework, and embedding the regiment's EW platoon directly inside its multifunctional reconnaissance company ahead of Flytrap 6.0 in Latvia in May 2027.
- Institutionalizing the "New Basics": Technology fails if only contractor field service representatives know how to run it. As 2nd Cavalry Regiment leaders proposed at AUSA 2026, operating small UAS, counter-UAS tools, unmanned ground vehicles (UGVs), and spectral camouflage must become standardized "New Basics" across every military occupational specialty—supported by disciplined Unit Training Management (UTM) and integrated into the Army's Expert Badge (E3B) testing framework.
Chapter 9
What Paragon Micro’s Public Sector Division delivers
Paragon Micro, through its Public Sector Division, helps Department of War program offices, maneuver formations, installation commanders, and Federal System Integrators translate C-UAS doctrine into deployed, supportable capability—solving the exact integration, resilience, and supply-chain bottlenecks that stall field readiness.
01 · Multi-OEM integration
Eliminate redundant stovepipes
As a Dell Technologies Federal Platinum Partner and multi-vendor integrator, we combine ruggedized GPU edge servers (such as Dell PowerEdge XR8000, XR7620, and XR4000), NVIDIA Spectrum-X and PowerSwitch networking, sunlight-readable Pro Rugged endpoints, and multi-OEM tactical radios, cameras, and power into a single open architecture—satisfying the Warfighting Acquisition System's two-source mandate.
02 · Pre-staged speed & scale
Kitted in our System Readiness Center
Units cannot waste range time building RAID arrays or debugging BIOS mismatches. Inside our 55,000+ sq. ft., AS9120-certified System Readiness Center, vetted U.S. citizens verify component provenance (including Dell Secured Component Verification checks), load golden software images, burn-in test complete transit-case or rack kits under load, and ship ready-to-operate systems with serialized custody manifests.
03 · Cyber & Zero Trust resilience
Hardened for IT and OT enclaves
Our Zero Trust and Cyber Resilience and Video Surveillance and Physical Security teams design UFC 4-010-06 segmented control networks, FIPS 140-3 encrypted data paths, and air-gapped cyber recovery vaults—delivering complete configuration artifacts to accelerate your program's ATO package.
04 · Pre-competed contract vehicles
Fast ordering across DoW vehicles
Procure complete C-UAS edge infrastructure rapidly through Army ITES-4H (ordering through 2035), the $151B MDA SHIELD IDIQ (HQ0859-26-D-E455, ordering through December 2035), NASA SEWP V & NASA SEWP VI (80TECH26D2050, November 2026–November 2036), and GSA MAS teaming arrangements.
Recommended first engagement for a program office, base, or integrator
The 4-Step Counter-UAS Edge Architecture Sprint
- 01 · Operational vignette & authority mapping: Define mission threads, 10 U.S.C. § 130i or tactical ROE constraints, and operator decision points across your formation or installation.
- 02 · Edge architecture & SWaP-C design: Map sensors → rugged edge GPU compute → open C2 outputs (ISA / ATAK / MSS), sizing UPS backup circuits, vehicle power, and DDIL store-and-forward buffers.
- 03 · Pre-staged pilot build: Configure, golden-image, and burn-in test a kitted prototype inside the Paragon Micro System Readiness Center to benchmark time-to-alert, false-alarm suppression, and track continuity.
- 04 · Governance, Zero Trust & sustainment plan: Lock baseline configurations, establish signed model-update workflows, verify FIPS 140-3 and Section 889/5949 compliance, and stage bonded mission spares.
FAQ
Frequently asked questions
Why does Counter-UAS require Edge AI instead of cloud-only processing?
Small unmanned aircraft compress engagement timelines to seconds and frequently operate alongside electronic warfare jamming that degrades or severs reachback communications. Running AI inference on ruggedized servers directly at the tactical edge filters clutter, fuses multi-sensor tracks, and cues effectors in milliseconds without waiting for a cloud round-trip.
How did Joint Interagency Task Force 401 (JIATF-401) replace the Joint Counter-sUAS Office (JCO)?
On August 28, 2025, the Secretary of War disestablished the legacy Joint Counter-sUAS Office (JCO) and established Joint Interagency Task Force 401 (JIATF-401) to accelerate counter-drone delivery across homeland installations and forward forces. Codified into law by the FY2026 NDAA on December 18, 2025, JIATF-401 holds authority to approve up to $50 million per rapid initiative and launched a five-base directed-energy C-UAS pilot in May 2026.
How does the Integrated Sensor Architecture (ISA) solve the C-UAS "swivel-chair" problem?
When units field multiple proprietary C-UAS sensors, operators are forced to monitor six or seven separate vendor screens and manually bridge data between Maven Smart System (MSS) and ATAK. Validated during U.S. Army Project Flytrap 4.5 in Europe, the Integrated Sensor Architecture (ISA) enforces open-architecture data standards so disparate radar, RF, acoustic, and optical sensors publish into a single Common Operating Picture (COP).
What cryptographic and Zero Trust rules apply to new C-UAS edge hardware?
On September 21, 2026, NIST moved all FIPS 140-2 certificates to its Historical List, meaning new C-UAS servers, radios, and self-encrypting drives handling CUI must specify FIPS 140-3 validated cryptographic modules (and CNSA 2.0 quantum-resistant algorithms for new National Security System acquisitions starting January 1, 2027). Systems must also align with the September 30, 2027 DoW Target-Level Zero Trust deadline and UFC 4-010-06 control-system segmentation rules on installations.
How does the July 2026 CMMC Phase 2 suspension affect C-UAS integrators and suppliers?
On July 13, 2026, the Department of War suspended the November 10, 2026 rollout of CMMC Phase 2 (mandatory third-party C3PAO assessments) pending a CMMC Reform Task Force review. However, CMMC Phase 1 remains mandatory: contractors handling CUI configurations or sensor logs must maintain active SPRS scores, complete Level 2 self-assessments with annual senior-official affirmations, and comply fully with NIST SP 800-171 Rev 2 and DFARS 252.204-7012.
Which contract vehicles can DoW buyers use to procure C-UAS edge infrastructure from Paragon Micro?
Paragon Micro’s Public Sector division delivers pre-staged, AS9120-certified C-UAS compute, networking, physical security, and power kits through Army ITES-4H (ordering through 2035), the $151B MDA SHIELD IDIQ (HQ0859-26-D-E455, ordering through December 2035), NASA SEWP V (NNG15SD91B) and NASA SEWP VI (80TECH26D2050, November 2026–November 2036), and GSA MAS teaming arrangements.
Timeline
Key dates through 2027
Sep 21, 2026
FIPS 140-2 moved to NIST Historical List; specify FIPS 140-3 on new CUI buys
NIST CMVP cryptographic cutoff
Oct 30, 2026
FORTRESS America Program Office core cell & Project Agincourt 30-day plan due
September 30, 2026 Quantico directives
Nov 2026
Paragon Micro NASA SEWP VI ordering period begins (80TECH26D2050)
Original Nov 10 CMMC Phase 2 date suspended
Jan 1, 2027
CNSA 2.0 required for new NSS acquisitions & DFARS magnet rule expands
NSA CNSA 2.0 & DFARS 252.225-7052
Jan 28, 2027
Project Meridian 120-day future warfare findings due to the Secretary of War
Public report + classified annex
May 2027
Project Flytrap 6.0 squadron-on-squadron C-UAS exercise in Sēlija, Latvia
U.S. Army Europe and Africa
Sep 30, 2027
Department of War Target-Level Zero Trust deadline across IT and OT enclaves
Covers 91 capability outcomes
Oct 1, 2027
Autonomous Warfare Command (AutoWarCom) target stand-up date
Pending congressional authorization
Dec 23, 2027
NDAA Section 5949 semiconductor prohibition takes effect across COTS hardware
Bars SMIC, YMTC, and CXMT chips
The unmanned threat is not waiting for perfect five-year specifications. Program offices, maneuver units, and installation commanders that lock down open sensor schemas, ruggedized edge GPU compute, backed-up power circuits, and verified supply chains today will own the timeline tomorrow.
Paragon Micro · Public Sector Division
Take control of your Counter-UAS architecture before it controls you.
Engage Paragon Micro’s Public Sector defense team for a focused Counter-UAS Edge AI architecture session. In one working discussion, our engineers will help you map your current sensors, C2 interfaces, and edge compute posture, define DDIL degraded-mode behaviors, and deliver a pre-staged, AS9120-backed hardware roadmap through ITES-4H, MDA SHIELD, NASA SEWP V/VI, or GSA.
Schedule your Counter-UAS Edge AI session
Tactical and Rugged Equipment Zero Trust and Cyber Resilience Video Surveillance and Physical Security System Readiness Center
Related reading



