Federal procurement—not tech—blocks IT/OT cybersecurity integration, industry warns

An industry government-affairs executive outlined a case this week that the main obstacle to integrating information-technology and operational-technology cybersecurity in federal systems is funding and procurement, not engineering. The piece points to fragmented budgets, mismatched contracting authorities and rigid acquisition vehicles as barriers that prevent agencies and vendors from deploying unified monitoring and response across IT and OT environments.

The author frames the argument against the backdrop of escalating nation-state cyber activity and reports of offensive cyber operations tied to U.S. military actions. He says those shifts increase urgency for federal agencies to close visibility gaps where industrial control systems and other operational assets remain isolated from standard federal cybersecurity tooling.

Funding structures create practical blind spots

According to the argument, many federal buyers separate IT and OT spending into different accounts and program offices, which complicates lifecycle planning for devices and sensors that span both worlds. That split, the author contends, means procurement officers cannot easily buy integrated monitoring platforms or continuous detection services on a single contract, leaving gaps in discovery, asset inventories and threat detection.

On the vendor side, commercial firms that offer cross-domain platforms confront multiple workstreams and sales channels inside agencies. The author recommends that contracting offices and appropriators instead prioritize funding flexibility, shared line items for IT/OT security, and more permissive contract vehicles that allow vendors to roll out unified visibility and management tools.

Policy levers and market incentives

The commentary urges lawmakers and federal procurement officials to shift incentives: favor contracts that require or reward continuous monitoring, standardized asset discovery, and interoperable telemetry across IT and OT. It also calls for clearer responsibilities between integrators, vendors and system owners so that operational assets receive regular security updates and monitoring rather than ad hoc protections.

Industry proposals in the piece include consolidating funding streams, updating acquisition guidance to accommodate cross-domain purchases, and using existing contract vehicles to bundle IT and OT cybersecurity capabilities. The author stresses that many of the required technologies already exist in the commercial market; the barrier is aligning budgets and buying practices to adopt them at scale in government environments.

For Washington’s federal IT community, the recommendation is practical: change how agencies and congressional appropriators frame security line items so integrated solutions can be purchased and maintained. That, the author argues, would reduce long-term costs and improve resilience across critical infrastructure connected to federal networks.

Watch for upcoming budget decisions and procurement updates from agency acquisition offices and central buying bodies, which will indicate whether the federal government moves to remove the financial and contracting barriers the author highlights.