The bill amends section 201(d) of the Homeland Security Act of 2002 by adding a new paragraph that reorients the Office of Intelligence and Analysis (I&A) toward an operational, partner-facing mission. It directs I&A to prioritize forward‑deployed intelligence capabilities, two‑way information sharing, sustained engagement with fusion centers, and to ensure departmental leadership support does not crowd out services to State, local, Tribal, and territorial (SLTT) governments and private sector entities.
The Act also imposes a concrete oversight step: the Under Secretary for Intelligence and Analysis must submit a report within 180 days describing steps taken, progress on two‑way sharing, metrics for measuring effectiveness, and any resource or organizational changes needed to sustain the realignment. A safeguard clarifies that I&A’s watchlisting functions are unchanged.
For compliance officers and agency planners, the bill signals likely shifts in resourcing, reporting, and engagement priorities rather than new criminal penalties or statutory authorities.
At a Glance
What It Does
The bill inserts a new statutory mission requirement for I&A to balance intelligence support to SLTT partners and private-sector entities with its existing obligations to the broader intelligence community. It lists four operational priorities—forward deployment, two‑way sharing, fusion center engagement, and protecting partner support from being deprioritized by leadership tasks—and requires a 180‑day implementation report to key congressional committees.
Who It Affects
Directly affected parties include DHS’s Office of Intelligence and Analysis, fusion centers, State/local/Tribal/territorial intelligence and law enforcement entities, and private sector critical‑infrastructure partners that receive DHS intelligence. Congressional oversight committees named in the bill will also receive detailed implementation reporting.
Why It Matters
The change hardens a partner‑facing posture in statute, shifting how DHS puts weight on local dissemination and collection activities. That can alter budget priorities, operational posture in the field, and day‑to‑day information flows between DHS, SLTT partners, and private entities, with downstream implications for classified handling, privacy controls, and interagency coordination.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The central change in this bill is a single addition to section 201(d) of the Homeland Security Act that tells I&A to treat its operational mission to serve SLTT partners and the private sector as an equal priority to any support it gives to the broader intelligence community. Practically, the statute names four discrete areas I&A must carry out: deploying intelligence capabilities forward into the field to identify emerging threats, facilitating two‑way sharing so local partners both provide and receive usable intelligence, maintaining ongoing engagement with fusion centers, and ensuring that analytic support to DHS leadership does not squeeze out partner support.
Beyond the added duties, the bill builds in congressional oversight: the Under Secretary must file a report within 180 days to specific House and Senate committees. That report must explain steps taken to implement the realignment, show progress on two‑way sharing, lay out the metrics I&A will use to judge effectiveness, and identify any resource or organizational changes required.
The named recipients—House Homeland Security, House Permanent Select on Intelligence, Senate Homeland Security and Governmental Affairs, and the Senate Select Committee on Intelligence—signal that Congress expects both operational detail and intelligence‑community coordination in the response.The bill also includes a narrow rule of construction preserving I&A’s existing watchlisting functions, so the reorientation does not change that statutory authority. The statute references “fusion centers” by pointing to the existing definition in section 210A, which ties this requirement into the broader federal‑state fusion center network.
The language leaves key terms—like what precisely counts as a “forward‑deployed intelligence capability” or the specific metrics for “effectiveness”—to the Department to define in its implementation and reporting, so operational guidance and resource shifts will follow the report rather than the statute itself.
The Five Things You Need to Know
The bill adds paragraph (24) to 6 U.S.C. 121(d), legally directing I&A to prioritize operational intelligence support to SLTT governments and private sector entities on par with support to the intelligence community.
It mandates four named priorities for I&A: forward‑deployed intelligence capabilities, two‑way information sharing, sustained engagement with fusion centers, and protecting partner support from being deprioritized by leadership demands.
The Under Secretary for Intelligence and Analysis must submit a report to four congressional committees within 180 days detailing implementation steps, progress on two‑way sharing, metrics for effectiveness, and any required resource or organizational changes.
The bill explicitly preserves I&A’s existing watchlisting functions by rule of construction, preventing the amendment from being read to alter that authority.
The statute ties fusion center engagement to the existing statutory definition (section 210A), effectively requiring coordination with the federally recognized fusion center network rather than creating a new program.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Provides the Act’s short name, the 'I&A Mission Reorientation Act of 2026.' This is a drafting formality but anchors the bill’s purpose for drafting and interpretation in subsequent materials and reports.
Findings and sense of Congress
Lists factual findings about I&A’s role and a non‑binding sense of Congress emphasizing two‑way collaboration and that support for DHS leadership should not dominate partner support. While not creating enforceable duties, the findings frame legislative intent and will guide statutory interpretation and oversight inquiries during implementation.
Statutory mission realignment for I&A
Adds paragraph (24) to section 201(d), a substantive change that places partner‑facing operational priorities into statute. The provision names four obligations—forward‑deployment, two‑way sharing, fusion center engagement, and ensuring leadership support does not deprioritize partner services—each of which creates discrete implementation needs (e.g., staffing field liaisons, data sharing processes, MOUs with fusion centers). Departments and program managers will need to translate these into operational plans, security protocols, and budgets.
180‑day implementation report to specific congressional committees
Requires the Under Secretary to deliver a detailed report within 180 days to House Homeland Security, House Permanent Select on Intelligence, Senate Homeland Security and Governmental Affairs, and Senate Select on Intelligence. The report must enumerate steps taken, measure progress on two‑way sharing, specify metrics for evaluating effectiveness, and identify resource or organizational changes. This creates a short statutory timetable for operational decisions and makes the report a primary vehicle for oversight and for clarifying ambiguous statutory terms.
Watchlisting functions preserved
Clarifies that nothing in the amendment alters I&A’s watchlisting responsibilities. This carve‑out narrows litigation risk and signals to intelligence partners that sensitive, centralized functions remain intact despite a statutory push toward decentralized partner support.
This bill is one of many.
Codify tracks hundreds of bills on Government across all five countries.
Explore Government 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
- State, local, Tribal, and territorial (SLTT) law enforcement and emergency management agencies — They gain statutory backing for more proactive intelligence support, improved access to actionable products, and stronger expectations of reciprocal information flows from DHS.
- Fusion centers — The statute explicitly requires sustained engagement, which can translate into more formalized partnerships, resources, and clearer lines of communication between I&A and the fusion center network.
- Private‑sector critical infrastructure operators and corporate security teams — The bill elevates the private sector as an explicit intelligence recipient, potentially increasing timely, tailored threat reporting and operational alerts to companies responsible for critical systems.
- Local analysts and field intelligence personnel — A focus on forward‑deployed capabilities supports embedding analysts or liaison officers closer to state and local partners, enhancing situational awareness at the community level.
Who Bears the Cost
- Department of Homeland Security (I&A) — The Office must reallocate staff time, budget, and operational focus to meet forward‑deployed and partner‑engagement requirements, potentially diverting resources from other I&A activities unless appropriations follow.
- Other DHS components and federal intelligence partners — If I&A shifts personnel or assets toward SLTT support, coordination friction and competition for analytic resources could increase, requiring new interagency governance structures.
- Private entities receiving intelligence — Companies may need to adopt new security and handling protocols for DHS intelligence, accept liaison relationships, and potentially provide more data to I&A, raising compliance and liability considerations.
- Congressional oversight offices — The named committees will absorb the burden of scrutinizing the 180‑day report and monitoring implementation, which can drive further hearings or legislative follow‑up that agencies must respond to.
Key Issues
The Core Tension
The bill forces a trade‑off between decentralizing intelligence to better serve local and private partners and preserving centralized, sensitive analytic functions and national priorities: improving operational responsiveness at the community level can undermine oversight, protectiveness of classified sources, and national analytic focus unless resourcing, legal safeguards, and clear procedures are simultaneously and adequately addressed.
The bill sets priorities but leaves key implementation details—definition of “forward‑deployed intelligence capabilities,” the specific metrics for “effectiveness,” and privacy or classification handling protocols—undefined. That means the 180‑day report will be decisive in shaping how the statute changes practice, but it also creates a short window for agencies to make significant operational and budgetary choices.
Without accompanying appropriations or clear administrative guidance, I&A could be required to shift emphasis on paper without the resources to sustain it, producing either superficial compliance or realignment that degrades other functions.
A second tension is between openness to SLTT partners and the safeguarding of sensitive intelligence. Expanding two‑way sharing and dissemination to private sector entities increases the risk of unauthorized disclosures and complicates adherence to classification and privacy laws.
The statute’s preservation of watchlisting functions narrows some risks but does not resolve how I&A will reconcile transparency with security, or how civil‑liberties safeguards will be applied when information flows broaden. Finally, the statute gives Congress a reporting lever but no explicit enforcement mechanism; much will depend on congressional appetite to fund and oversee the operational changes the report recommends.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.