Cartel drone ops on the U.S.-Mexico border ‘get more creative every day,’ task force warns

TL;DR

The Department of Defense established Joint Task Force–Southern Border (JTF‑SB) in March 2025 to create a unified military command structure supporting DHS (Department of Homeland Security) and CBP with counter‑drone operations and border security. The task force is deploying various counter‑UAS technologies and capabilities to counter evolving drone threats from cartels, which the Summary identifies as generating potential contracting opportunities for counter‑drone systems, surveillance technologies, and related support services. This is a significant expansion of DOD’s involvement in border security and shifts demand toward firms that provide counter‑UAS, surveillance, electronic warfare, command-and-control, and intelligence services. Immediate implications: contractors should inventory relevant capabilities, validate regulatory and security posture against listed compliance regimes, map offerings to the contract vehicles called out in segmentation, and initiate capture activities. Use targeted intelligence and proposal automation to convert early situational awareness into prioritized pursuits.

Key Points

• The DOD established Joint Task Force–Southern Border (JTF‑SB) in March 2025 to support DHS and CBP with counter‑drone operations and border security; the task force is deploying counter‑UAS technologies and capabilities to address evolving cartel drone threats.
• Affected segments include NAICS 336411, 334511, 541330, 541512, 541715, 561621, 922160, 928110 and agencies DOD, DHS, CBP, U.S. Army, U.S. Air Force, and U.S. Northern Command.
• Timeline: JTF‑SB established in March 2025; follow‑on deployment and procurement schedules TBD pending source review.
• What contractors should do NOW: inventory and gap‑assess counter‑UAS and surveillance capabilities; validate compliance against CMMC (Cybersecurity Maturity Model Certification), NIST 800‑171, ITAR (International Traffic in Arms Regulations), EAR, DFARS (Defense Federal Acquisition Regulation Supplement) 252.204‑7012, and NIST 800‑53; map solutions to OASIS+, GSA (General Services Administration) MAS, ASTRO, DHS EAGLE II, SeaPort‑NxG, and ITES‑SW2; notify capture, proposal, and security leads; and spin up Cabrillo saved searches and capture workflows.

Who Is Affected

Organizations and teams focused on defense, counter‑UAS, border security, surveillance technology, electronic warfare, command and control systems, intelligence and analysis, and homeland security work are directly affected. Specific NAICS codes, agencies, contract vehicles, and compliance regimes named in segmentation are relevant and should be prioritized in capture planning:

• NAICS: 336411, 334511, 541330, 541512, 541715, 561621, 922160, 928110
• Agencies: DOD, DHS, CBP, U.S. Army, U.S. Air Force, U.S. Northern Command
• Contract vehicles: OASIS+, GSA MAS, ASTRO, DHS EAGLE II, SeaPort‑NxG, ITES‑SW2
• Compliance surfaces: CMMC, NIST 800‑171, ITAR, EAR, DFARS 252.204‑7012, NIST 800‑53

Frequently Asked Questions

Q: Does the JTF‑SB announcement create near‑term contracting opportunities?

A: The Summary identifies potential contracting opportunities for counter‑drone systems, surveillance technology, and related support services. Specific solicitations, timelines, and award mechanisms are TBD pending source review.

Q: Which agencies will likely be the primary buyers?

A: The Summary and segmentation identify DOD, DHS, and CBP as primary actors; segmentation also includes U.S. Army, U.S. Air Force, and U.S. Northern Command. Exact sourcing authorities and lead buyers for specific procurements are pending source review.

Q: What contract vehicles should companies prioritize for capture?

A: Segmentation lists OASIS+, GSA MAS, ASTRO, DHS EAGLE II, SeaPort‑NxG, and ITES‑SW2 as relevant contract vehicles. Which vehicle is used for a given requirement will depend on solicitation language; specific vehicle use per procurement is pending source review.

Definitions

• Joint Task Force–Southern Border (JTF‑SB): The DOD‑established unified military command structure created in March 2025 to support DHS and CBP with counter‑drone operations and border security.
• counter‑UAS (counter‑drone): Systems and tactics designed to detect, track, mitigate, or defeat unmanned aircraft systems posing threats to operations or security.

Intelligence Response

• Cabrillo Signals War Room — Already detected this event and delivered this briefing. Continuously monitors regulatory changes, contract vehicles, and policy shifts relevant to counter‑UAS and border security missions.
• Cabrillo Signals Match Engine — Automatically rescoring opportunity pipelines and reprioritizing pursuits when this event shifts competitive posture toward counter‑UAS and surveillance capabilities.
• Cabrillo Signals Intelligence Hub — Tracking affected agencies, NAICS codes, and the listed contract vehicles. Saved searches will notify teams when follow‑on solicitations or RFIs appear on public listing sites.
• Proposal Studio (Proposal OS) and Proposal Studio Workflow Tracker — Used to accelerate capture decisions, generate compliance matrices against CMMC/NIST/DFARS requirements, and run the 9‑gate capture workflow with automated compliance routing and audit‑ready documentation.

Recommended internal notifications:

• Notify Capture Lead and VP Business Development to assess pipeline and rebid priorities.
• Notify CTO/CISO and Security Compliance Lead to perform immediate compliance posture review against listed compliance surfaces.
• Notify Proposal Manager and Contracts Lead to map offerings to the named contract vehicles and begin template SOWs.

First 48‑hour response playbook:

• Hour 0–4: Triage alert — Cabrillo Signals War Room confirms event and pushes briefing. Convene capture standup (capture lead, BD, proposal manager, security lead). Create Cabrillo Signals Intelligence Hub saved searches for keywords and the named vehicles.
• Hour 4–12: Run Cabrillo Signals Match Engine to rescore active opportunities and identify near‑term targets on the named vehicles. CTO/security runs rapid compliance gap assessment against CMMC, NIST 800‑171, DFARS 252.204‑7012, ITAR/EAR.
• Hour 12–24: Proposal Studio generates initial compliance matrices and a draft bid/no‑bid recommendation. Assign Proposal Studio Workflow Tracker gates for capture tasks and assign authors.
• Hour 24–48: Finalize prioritized pursuit list, begin win‑theme and solution outline development, and prepare capture packages mapped to OASIS+, GSA MAS, ASTRO, DHS EAGLE II, SeaPort‑NxG, or ITES‑SW2 as applicable.