CISA released its new strategy, CISA 2030: Defend, Harden, Prevail, on October 26, 2026. The headline promise is bold. In his welcome letter, Acting Director Nick Andersen writes that CISA “will transition from passive defense to an aggressive, anticipatory stance that actively eliminates adversarial footholds in defense-critical infrastructure prior to weaponization against our systems.” If you run a water plant, a regional utility, a hospital network, or any other operational environment and you are reading up on the CISA strategic plan, critical infrastructure, and proactive defense, the question that matters is practical. What does this plan actually ask of the operators? I read the whole document. The honest answer is: less than the rhetoric suggests, at least so far.
What the Strategy Says
The document is short, about eight pages of substance. It is organized around three pillars, each named in the plan:
- Defend: Lead National Cyber Defense
- Harden: Prioritize National Infrastructure Security
- Prevail: Mobilize National Resilience
Andersen frames the premise realistically. He writes that “there is no guarantee that a strong defense will eliminate intrusions,” and that “we must ensure that when adversaries gain a foothold, we are prepared to detect them quickly, evict them decisively, and keep critical operations running without interruption.” CISA’s press release describes the approach as “decisive, proactive action to identify, disrupt, and eliminate adversarial access.” Those are CISA’s descriptions of its intent. They are not results, and the strategy does not claim they are.
The most consequential line, in my view, sits under the Harden pillar: “We will deprioritize threat-agnostic, all-hazards approaches and embrace risk-informed, consequence-based analysis.” CISA says it will focus attention, investment, and operational effort “on the infrastructure whose disruption would have the greatest impact on public health and safety, continuity of the economy, and national security.” CISA also says it will support the White House in developing a National Risk Register to quantify risk to national infrastructure.
What the Strategy Commits CISA to Do
Almost every key objective is written as something CISA will do, often “alongside” or “with” partners. Among them:
- Integrate cyber defense capabilities across government, industry, state, local, tribal, and territorial partners, and international organizations.
- “Work alongside critical infrastructure owners and operators to modernize OT environments, improve asset visibility and anomaly detection, and assure OT supply chain integrity.”
- Coordinate with partners on data-driven software security guidance and supply chain transparency.
- Mature an “intelligence-to-operations pipeline” with the Intelligence Community, industry, and agencies, including real-time decision making and alerts.
- Build capacity through CISA’s ten regional offices and modernize planning and exercise capabilities.
- Expand priority telecommunications services, including 5G/6G and commercial satellite constellations.
The timeline is also about CISA, not operators. The plan says that within 60 days CISA will “begin a programmatic review” of its core services and capabilities. Within 180 days it will deliver “an approach for implementation and measurement of outcomes.” Within 365 days it will deliver a progress update. As Nextgov/FCW points out, the 60-day deadline applies to starting the review, not finishing it.
What the CISA Strategic Plan Asks of Critical Infrastructure Operators
This is where I want to be careful, because it would be easy to read new mandates into this document. I did not find any. The strategy sets no new reporting requirements, deadlines, or technical controls for owners and operators. Nextgov/FCW also reports that it “does not establish new legal authorities.”
What the strategy does contain are appeals. Andersen writes: “I call on everyone to do their civic duty and take every step necessary to deny our adversaries a single foothold or advantage.” In the press release he goes further: “I call on every company and organization in the critical infrastructure community—from owners and operators to vendors and technology manufacturers—to act now.” DHS Secretary Markwayne Mullin’s foreword urges unity at every level, including “owners and operators of businesses and critical infrastructure.”
Beyond those calls to action, operators appear as partners. CISA says it will build “distributed collaboration frameworks that empower and enable SRMAs, regions, states, communities, and owners and operators to advance infrastructure security through localized action.” The specifics of what partnership will look like are deferred to the 180-day implementation approach.
My Read and Recommendations for Operators
These are my opinions, not CISA guidance, and none of them is a requirement in the strategy.
- Figure out which side of the prioritization line you are on. A consequence-based model means some sectors and some facilities get more CISA attention, and others get less. The strategy does not say which services lose resources. Do your own consequence analysis now so you can make your case when the implementation plan arrives.
- Invest in OT visibility before anyone asks. Asset visibility and anomaly detection are named objectives. You cannot be a useful partner in evicting an adversary from a network you cannot see.
- Rehearse eviction, not just detection. The strategy’s own language is “detect them quickly, evict them decisively.” Tabletop what removing a persistent intruder from your control environment would take without stopping operations.
- Inventory the free CISA services you depend on. The 60-day programmatic review covers CISA’s core services, and the plan does not say which ones might change. If a free scan or assessment is part of your program, note it and have a fallback in mind.
- Get to know your CISA regional office. Regional capacity is part of the plan. A relationship built before an incident pays off during one.
- Watch for the 180-day implementation approach. That document, expected roughly in late April 2027 if CISA hits its stated timeline, is where concrete expectations would likely show up.
Here is a hypothetical worth thinking through. A mid-sized municipal water utility reads this plan and assumes it is now in line for hands-on CISA help. If the risk register and prioritization land elsewhere, that utility could end up with less direct support than before. The strategy does not say that will happen. It does make the tradeoff explicit.
The Bottom Line
CISA 2030 promises, in CISA’s words, an “aggressive, anticipatory stance” against adversaries in critical infrastructure. For now it is a statement of agency priorities and a timeline for CISA’s own work. It is not a rulebook for operators. Treat the calls to “act now” as a strong signal, and build your visibility, eviction playbooks, and consequence analysis before the implementation details arrive.

Leave a Reply