Inside Pete Hegseth’s Push for Pentagon “Volunteers” at DHS—and What It Means for Law, Tech, and the Civil Service

Background

The US government has a long history of interagency support along the southern border, but the lines between defense aid and direct law enforcement are deliberately bright. For decades, the military has provided logistics, engineering, aviation, and surveillance support to border authorities—carefully avoiding activities barred by the Posse Comitatus Act. That law limits federal troops from conducting domestic law enforcement, with narrow exceptions. National Guard forces under state control (Title 32) can sometimes play a more hands-on role, but even then, the mission is typically constrained.

Past administrations of both parties have relied on Pentagon capabilities at the border:

• 2006–2008: Operation Jump Start (Bush) deployed National Guard units for surveillance and infrastructure support.
• 2010–2016: Operation Phalanx (Obama) emphasized aerial surveillance and counterdrug cooperation.
• 2018–2020: Deployments under the Trump administration added barriers, logistics, and ISR support while trying to stay within legal limits on law enforcement.

Beyond uniformed personnel, the Department of Homeland Security (DHS) has previously mobilized internal “volunteer forces” from across its components—such as TSA, FEMA, and USCIS—to support Customs and Border Protection (CBP) during surges. Pulling civilian employees from outside DHS, particularly from the Department of Defense (DoD), pushes into more novel territory and raises new legal, labor, and ethical questions.

Pete Hegseth—an Army veteran and media figure—has emerged in this period as a defense secretary intent on aligning military-adjacent resources behind a sharper immigration enforcement posture. WIRED reports that Hegseth has made clear to Pentagon managers that they are to encourage workers, including civilians, to volunteer to assist DHS in the administration’s immigration crackdown.

What happened

According to WIRED’s reporting, Defense Secretary Pete Hegseth is pressing Pentagon managers to solicit “volunteers” from within the DoD workforce—including civilian employees—to support DHS activities tied to immigration enforcement. While the term “volunteer” suggests discretion, in a hierarchical organization like the Pentagon, a managerial nudge can feel like a directive. The initiative signals a more muscular posture toward interagency assistance and a willingness to reallocate talent from defense programs to domestic enforcement support.

Key operational contours likely in play:

• Administrative and logistics augmentation: Civilian specialists could help DHS process data, move supplies, coordinate transport, or stand up temporary facilities—areas where the Pentagon excels.
• Technical support: DoD personnel might aid with systems integration, analytics, and command-and-control workflows that DHS uses for case management, surveillance feeds, and operational planning.
• Planning and liaison roles: Staff with joint planning or NORTHCOM experience could serve on interagency planning teams, helping translate military-style task organization into DHS operations—without crossing into direct law enforcement.

What they are not supposed to do:

• Make arrests or conduct searches and seizures. That would likely violate Posse Comitatus for federal troops and be outside the permissible scope for DoD civilians. Any assistance must cleave to “support” roles.

The legal pathways for such details exist but are intricate:

• Economy Act (31 U.S.C. § 1535): Allows one federal agency to provide reimbursable support to another when certain conditions are met.
• Defense Support of Civil Authorities (DSCA): A doctrine and process funnel for interagency requests; DHS submits a Request for Assistance (RFA), which DoD evaluates for legality, feasibility, and risk to readiness.
• Anti-Deficiency Act (31 U.S.C. § 1342): Limits “volunteer” services. In practice, volunteers must be formally authorized details with pay, timekeeping, and liability covered; unpaid labor by federal employees is generally prohibited.

In other words, the optics may be of volunteerism, but the mechanics have to be formal—funded, documented, and within job series or detail authorities.

Why this matters now

Hegseth’s approach arrives amid high border apprehensions, constrained DHS staffing, and political pressure for decisive action. It also coincides with rapid adoption of sensors, drones, and AI-enabled analytics on the border. The Pentagon’s deep bench in ISR (intelligence, surveillance, reconnaissance), data fusion, logistics, and expeditionary construction is tempting for policymakers trying to scale enforcement quickly. But importing defense tools and talent into domestic enforcement, even indirectly, carries risks for civil liberties, workforce integrity, and military readiness.

How this could work in practice

• Tasking and approvals: DHS components (e.g., CBP, ICE) submit RFAs to DoD. The Office of the Secretary of Defense vets the scope; the Chairman’s staff and NORTHCOM assess mission fit and resourcing. Legal counsel screens for Posse Comitatus and other constraints.
• Resourcing model: Details are reimbursed under interagency agreements. Overtime, travel, per diem, and hazard pay—if applicable—must be budgeted. Unions may demand bargaining over conditions of employment.
• Roles for civilians: Likely in IT, logistics, civil engineering, budgeting, contracts, program management, and data analysis. Civilians may staff operations centers, manage sensor feeds, or streamline case paperwork—but not conduct law enforcement actions.
• Guard and reserve dimension: If the civilian volunteer pool falls short, states could be asked to put National Guard units on state active duty or Title 32 orders for support missions. That pathway has different legal contours but also political sensitivities.

The technology angle: defense-grade tools at the border

The Pentagon’s technical advantage is not just manpower; it is an operating system for complex missions:

• ISR and sensors: Aerostats, ground radars, and electro-optical systems feed real-time situational awareness. While DoD operators can tune and maintain these, the legal endpoint—who cues an interdiction—must remain DHS.
• Data fusion and AI: From object detection to pattern-of-life analysis, defense-built analytics could speed target development for DHS. Care is needed to prevent “function creep” into generalized domestic surveillance.
• Command-and-control software: Joint operations systems (and their commercial analogs) can knit together far-flung teams. Integrating DHS case tools with defense C2 risks over-collecting personal data unless privacy and minimization safeguards are enforced.
• Biometric and identity tech: Interoperability with DODABIS/ABIS can accelerate identity checks. Governance is key to avoid improper retention and to respect limits on use in civil contexts.

Any tech infusion demands strict guardrails:

• Minimize personally identifiable information (PII) and impose role-based access.
• Log access and decisions for auditability and after-action review.
• Apply civil liberties impact assessments akin to Privacy Impact Assessments, not just standard DoD cyber checklists.
• Sunset authorities and data retention aligned to case requirements, not convenience.

Legal and labor tripwires

• Posse Comitatus Act: Federal troops (Title 10) cannot execute domestic law except under statutory exceptions or if the Insurrection Act is invoked. Even “advice” must avoid morphing into direction of law enforcement operations.
• Anti-Deficiency Act: “Volunteering” cannot mean unpaid labor. Agencies must formally detail, compensate, and supervise work within legal authorities.
• Bargaining obligations: DoD civilians represented by unions (e.g., AFGE) may require negotiations over schedules, safety, and travel. Skipping this step can trigger unfair labor practice complaints.
• Whistleblower protections: Employees who report coercion, misuse of funds, or unlawful tasking are protected. The Office of Special Counsel can investigate retaliation.
• Hatch Act limits: Encouraging participation is not per se political, but framing the effort in electoral terms or pressuring subordinates toward a partisan policy goal can create Hatch Act risk.

Strategic risks and second-order effects

• Readiness and mission creep: Pulling program managers, engineers, and analysts off acquisition timelines or operational planning can ripple into delayed weapons programs or training cycles.
• Morale and retention: A perceived political litmus test—“volunteer” or be sidelined—could degrade trust. Highly specialized civilians may exit for industry.
• Oversight and litigation: Expect congressional committees, Inspectors General, and civil liberties groups to probe whether roles crossed legal lines, particularly if surveillance data flows to local law enforcement without proper authorizations.
• International optics: Defense-adjacent support to domestic enforcement may complicate bilateral ties with Mexico and Central American partners if seen as militarization.

Key takeaways

• The headline is not just about manpower; it is about moving defense-grade processes and tech into a civilian enforcement domain, with all the legal and ethical baggage that entails.
• “Volunteer” in federal service is a term of art: in practice it must be a paid, authorized detail. Anything else risks violating the Anti-Deficiency Act and labor law.
• There is real precedent for DoD-DHS support, but civilian details from outside DHS into frontline enforcement support is unusual and must be tightly scoped.
• The most sensitive boundary is data. Integrating defense ISR and analytics into DHS operations can accelerate missions—and magnify civil liberties risks—if not fenced by law and policy.
• The operational payoff (speed and scale) must be weighed against opportunity costs inside the Pentagon and the political costs of perceived coercion within the civil service.

What to watch next

• Paper trail and authorities: Look for formal Requests for Assistance, interagency agreements, and funding documents. If these surface publicly, they will reveal scope and duration.
• Union responses: Expect grievances or demands to bargain from DoD civilian unions, especially over travel, safety, and performance appraisals tied to “volunteering.”
• Oversight actions: Congress and Inspectors General may request briefings, seeking clarity on roles, data-sharing, and whether any law enforcement lines were crossed.
• Guard mobilizations: If civilian volunteers lag, watch for expanded National Guard roles under state control—often a prelude to larger, longer deployments.
• Tech procurement signals: Rapid buys of sensors, analytics, or C2 software for “interagency” use may indicate a deeper tech integration between DoD and DHS.
• Workforce pushback: Anonymous hotlines, OSC activity, or leaked memos would suggest employees feel coerced or see legal/ethical red flags.

FAQ

Q: Is it legal for the Pentagon to help DHS with border operations?
A: Yes, within limits. DoD can provide support—logistics, surveillance, engineering—under established authorities and reimbursable agreements. Direct law enforcement by federal troops is generally barred by the Posse Comitatus Act.

Q: Can DoD civilians be forced to “volunteer”?
A: No. While managers can inform and encourage, details should be voluntary and must be formally authorized and funded. Coercion or adverse actions tied to non-participation can trigger legal and labor violations.

Q: Will these volunteers carry out arrests or conduct searches?
A: They should not. Support roles must avoid direct law enforcement. If a task edges into law enforcement, it likely exceeds DoD’s permissible scope without special statutory authority.

Q: What would volunteers actually do?
A: Likely administrative processing, logistics, IT/systems integration, engineering for temporary facilities, planning, and data analysis—functions that speed DHS operations without executing enforcement actions.

Q: How does the Anti-Deficiency Act apply here?
A: It generally prohibits unpaid “voluntary” services. Any detail must be funded, with proper timekeeping, supervision, and liability coverage. Calling something a “volunteer” assignment does not bypass funding rules.

Q: Could military technology be used to monitor migrants inside the US?
A: Technology may support border security, but using defense-grade ISR and analytics inside the domestic sphere raises civil liberties issues. Any use must comply with privacy rules, minimization standards, and legal authorities specific to DHS operations.

Q: What happens if an employee believes the assignment is unlawful?
A: They can seek guidance from agency counsel, contact the Inspector General, or file a protected disclosure with the Office of Special Counsel. Whistleblower protections prohibit retaliation for lawful reporting.

Q: How might this affect military readiness?
A: Diverting specialized personnel to domestic support can slow acquisition schedules and training pipelines. Leadership must balance short-term enforcement gains against long-term defense obligations.

Bottom line

Hegseth’s push to mobilize Pentagon “volunteers” for DHS is more than a management memo; it is a test of how far the defense enterprise can and should bend toward domestic enforcement priorities. The legal path is navigable but narrow, the tech alluring but fraught, and the workforce implications significant. The clarity—and restraint—of implementation will determine whether this becomes a case study in interagency efficiency or a cautionary tale of mission creep and civil service politicization.

Source & original reading: https://www.wired.com/story/pete-hegseth-is-pushing-defense-employees-to-volunteer-for-dhs/