The National Guard Proper Use Act inserts new statutory language into both Title 10 and Title 32 of the U.S. Code that bars members of the Armed Forces and the National Guard from being ordered to perform duty to enforce, or to support enforcement of, the immigration laws. The new provisions cross‑reference the Posse Comitatus Act and the statutory definition of "immigration laws" in the Immigration and Nationality Act.
The change codifies a limitation that has been supplied by executive practice and court decisions in some contexts, while extending that prohibition explicitly into Title 32 (state‑status Guard operations funded under federal law). For federal, state, and local officials who rely on DOD or Guard capabilities at the border, the bill raises immediate operational and legal questions about what activities qualify as "support" for immigration enforcement and who will perform excluded functions.
At a Glance
What It Does
The bill adds §975 to Title 10 and §330 to Title 32, each stating that in accordance with 18 U.S.C. 1385 a service member may not be ordered to perform duty under that title to enforce or support enforcement of the immigration laws (as defined in 8 U.S.C. 1101). The prohibition covers both direct enforcement and activities characterized as "support."
Who It Affects
The change directly affects DoD policy and commanders, the National Guard when activated under Title 10 or Title 32, DHS components that coordinate with military forces (including CBP and ICE), and state governors who request Title 32 support. It also affects contractors and local law enforcement units that currently receive military support for border operations.
Why It Matters
By placing the prohibition in Titles 10 and 32, the bill narrows a pathway that has been used to provide military manpower and resources at the border. That shift could force operational redesigns, new interagency agreements, and legal guidance on what qualifies as prohibited "support."
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill accomplishes one specific change: it inserts parallel, short prohibitions into the two federal law titles that govern active‑duty military (Title 10) and federally funded National Guard duties (Title 32). Each new section says, in effect, that members of the Armed Forces or the National Guard cannot be ordered, under that title, to carry out immigration‑law enforcement or to support others carrying out that enforcement.
Instead of listing specific activities, the bill ties its scope to the Posse Comitatus framework and to the statutory definition of "immigration laws" in the Immigration and Nationality Act.
Because the text covers both "enforce" and "support the enforcement of" immigration laws, it reaches beyond arrests or detentions to include activities that assist immigration enforcement—logistics, surveillance, intelligence sharing, transportation of detainees, and even some infrastructure work—if those activities are characterized as supporting enforcement. The bill does not elaborate on categories of support or create a regulatory test; it relies on existing references to section 1385 and the INA to set boundaries.A distinctive operational consequence is its placement in Title 32 as well as Title 10.
Title 32 is the statutory basis commonly used when governors request federally funded Guard missions that keep the Guard under state control but with federal pay or authorities. By putting the prohibition in Title 32, the bill constrains the use of Guard forces even when they operate at governors' direction under federal funding, closing a pathway some administrations have used to provide Guard assistance at the border without triggering Posse Comitatus limitations.The text is compact and mechanical: it inserts two new sections after existing section numbers in each title, cites the Posse Comitatus statute, and references the INA definition of immigration laws.
It does not set an effective date, describe enforcement mechanisms, enumerate exceptions, or adopt implementing procedures; those gaps leave significant discretion for agencies and courts to interpret how the ban applies in practice.
The Five Things You Need to Know
The bill adds two new code sections: §975 (inserted after 10 U.S.C. §974) and §330 (inserted after 32 U.S.C. §329), each forbidding ordering duty under that title to enforce or support enforcement of immigration laws.
Both new sections explicitly invoke 18 U.S.C. §1385 (the Posse Comitatus Act) and use the Immigration and Nationality Act’s definition of "immigration laws" (8 U.S.C. §1101) rather than defining prohibited activities itself.
The phrase "support the enforcement of" is included, which can sweep in non‑arrest activities—surveillance, intelligence, transport, logistics, and construction—if those tasks are framed as aiding immigration enforcement.
The Title 32 insertion restricts Guard missions that are state‑directed but federally funded, closing a statutory route previously used to provide Guard assistance to border operations without Title 10 activation.
The bill contains no implementing guidance, exceptions, penalty provisions, or specified effective date, leaving questions about enforcement, narrowness, and transition planning to agencies and courts.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Designates the Act as the "National Guard Proper Use Act." This is purely nominal but signals the bill’s focus on limiting military roles in domestic immigration enforcement.
Bars ordering active‑duty Armed Forces to perform or support immigration enforcement
Adds a single, concise new section to chapter 49 of Title 10 stating that, consistent with 18 U.S.C. §1385, members of the Armed Forces may not be ordered under Title 10 to enforce or support enforcement of the immigration laws (as defined in 8 U.S.C. §1101). Practically, this codifies a Posse Comitatus‑aligned ban for federal active‑duty forces and frames the prohibition to include ancillary support activities, not just direct arrests.
Bars ordering National Guard, under Title 32, to perform or support immigration enforcement
Inserts an equivalent prohibition into chapter 3 of Title 32, stating that National Guard members may not be ordered under Title 32 to enforce or support enforcement of immigration laws. This is the key mechanical change: it reaches Title 32 missions (state control with federal funding), constraining a common avenue for Guard participation in border operations and creating a statutory limit where prior practice sometimes left room for interpretation.
This bill is one of many.
Codify tracks hundreds of bills on Defense across all five countries.
Explore Defense in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Immigrant communities and civil‑liberties organizations — gain a clearer statutory barrier against military involvement in immigration enforcement, reducing the risk of military personnel engaging in arrests, detentions, or surveillance tied to immigration status.
- National Guard members and active‑duty personnel — receive statutory protection from being ordered into civilian immigration‑enforcement roles, reducing role confusion and legal exposure for service members asked to perform law‑enforcement activities.
- Defense Department legal and policy offices — obtain a clearer statutory baseline that can simplify internal policy and training by clarifying that certain missions are off‑limits under Titles 10 and 32.
Who Bears the Cost
- Department of Homeland Security components (CBP, ICE) — lose a pool of military capabilities previously tapped for logistics, surveillance, transport, and other support, requiring procurement, staffing, or coordination changes.
- State governors and state homeland security agencies — face reduced operational options if they used Title 32 Guard missions for immigration‑related tasks, potentially requiring reallocation of state resources or new state statutes to fill gaps.
- Local law enforcement agencies at the border — may see diminished timely access to military equipment, intelligence, and transportation that they previously relied on, increasing pressure on local budgets and staffing.
- Defense Department and National Guard Bureau — must update mission charters, rules of engagement, interagency memoranda of understanding, and training curricula to reflect the new statutory bars, imposing administrative and implementation costs.
Key Issues
The Core Tension
The bill resolves one longstanding concern—keeping the military out of domestic immigration enforcement—by tightening statutory controls, but it does so at the cost of operational flexibility at the border: lawmakers must choose between a clear civil‑military boundary and the operational benefits of having the Guard as a rapidly deployable resource that can be used, under some configurations, to support immigration objectives.
The bill’s economy is also its principal ambiguity. It uses shorthand references—"in accordance with section 1385 of title 18" and the INA’s definition of "immigration laws"—without drawing lines around "support" activities.
That drafting choice leaves broad interpretive work to the departments and the courts: does providing aerial surveillance for border situational awareness constitute prohibited "support" if the data is fed to CBP? Is construction of barriers "support" if performed by Guard engineers under a governor’s order?
Agencies will need to adopt operational tests or engineering examples to avoid ad hoc litigation and mission delay.
Another implementation gap is enforcement clarity. The bill creates prohibitions but does not specify remedies, administrative penalties, or criminal sanctions.
That raises questions about how the prohibition will be enforced—by DoD policy, by administrative action, or through private litigation—and what remedies states or federal agencies have if they believe DoD is misapplying the statute. The lack of an effective date or transition rules means ongoing missions could face sudden stoppage without a statutory grace period, which is a practical problem for area commanders and interagency partners.
Finally, the Title 32 ban introduces federal‑state friction. Governors often rely on Title 32 specifically because it preserves state control while enabling federal funding or authorities.
The statutory bar narrows governors’ latitude and will likely prompt new political and legal maneuvering—states may seek alternative state‑only activations, new contracting approaches, or legislative workarounds. Each workaround risks creating second‑order issues (costs, oversight gaps, or replacement actors whose use of force and training differ from Guard standards).
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.