As federal agencies expand their use of data-intensive AI agents and software, they must also ensure that their underlying network infrastructure can handle the unprecedented demands placed on their systems, a panel of government technology leaders warned.<\/p>\n
Civilian agencies reported that more than 3,600 AI use cases<\/a> were in progress this past year, a nearly 70% increase from the previous year, according to the Office of Management and Budget. However, if infrastructure planning lags behind AI software adoption, agencies risk critical workflow bottlenecks that can stall operations and jeopardize data security, executives from the Department of Commerce, Verizon, and Cisco cautioned. \u00a0<\/p>\n Without a comprehensive assessment of their network infrastructure needs, the shift from pilot projects to active deployment could overwhelm legacy systems and throttle operations, they said during a video panel hosted by FedScoop.<\/p>\n Traditional practices, such as acquiring higher-bandwidth pipes or backhauling traffic to centralized gateways, won\u2019t necessarily meet these new demands.<\/p>\n Simply throwing raw capacity at the issue is a major misconception that fails to account for how internal routing and inspection points choke erratic data bursts, said Brian Epley, Chief Information Officer and Chief AI Officer for the U.S. Department of Commerce. Epley warned against underestimating the role of end-to-end transport in supporting AI.<\/p>\n \u201cThe pivot from generative AI to agentic AI\u2026 really requires that we bring compute and data together, and that transport is what\u2019s critical,\u201d Epley said. The transition demands highly adaptable environments that tightly integrate data sets with hardware accelerators. To get there, Epley said his office is focusing on software-defined agility, zero-trust alignment, dynamic bandwidth allocation and embedded micro-segmentation as part of a larger unification initiative called \u201cOne Commerce.\u201d<\/p>\n The stakes are significant. The department comprises 13 independent bureaus, including NOAA and the Census Bureau, that rely on \u201cmassive environmental and scientific data sets that live across multiple cloud environments.\u201d The goal, he said, is to \u201chave continuous identity attribute verification\u2026so that those autonomous agents continue to operate.\u201d<\/p>\n Addressing network boundaries<\/p>\n Agency leaders must also recognize that designing AI-ready infrastructure requires \u201csolving for two architectural realities\u201d to scale AI without sacrificing security compliance, said Sam Lakey, Associate Director of Solutions Architecture at Verizon Business Group.<\/p>\n One involves addressing historical security frameworks, such as Trusted Internet Connections (TICs) and Managed Trusted Internet Protocol Service (MTIPS), that were created for a centralized processing world and required backhauling traffic through rigid access points.<\/p>\n \u201cReal-time AI cannot wait for data to travel from the edge to a centralized MTIPS gateway and then back again. If you try and force modern, distributed AI through latency MTIPS, your AI initiatives can stall out on day one,\u201d he said.<\/p>\n The second reality involves shifting \u201cfrom physical choke points to a layered security approach, with telemetry-driven security. We need intelligent network fabrics that stream real-time telemetry to your CDM (Continuous Diagnostics and Mitigation) and security tools without killing throughput,\u201d he said.<\/p>\n Cisco Sales Leader Justin Fields stressed that as agencies assess their requirements, they need to map infrastructure to data locations rather than distant centralized hubs to accurately right-size the environment.<\/p>\n \u201cWhen you talk about AI, it\u2019s 100% about the data,\u201d Fields noted. \u201cYou have to connect the data. You have to secure the data. You have to visualize the data based on the agency needs\u2026 estimate how much throughput\u2026 and bandwidth is required, and how much data you\u2019re going to be analyzing to help right-size the infrastructure.\u201d<\/p>\n Failing to do so can lead to what Epley called \u201cGPU starvation,\u201d when an agency\u2019s network can\u2019t deliver data as fast as high-performance accelerators require and consume it. \u201cThat results in an expensive compute asset that may sit idle.\u201d<\/p>\n Agencies need to think about \u201cnot just the components of the (AI) transaction\u201d and the \u2018tokenomics\u2019 of training AI, but ensuring that the AI query costs are scaling predictably without surprises.\u201d<\/p>\n \u201cAgentic AI is an entirely new operational paradigm,\u201d argued Lakey. \u201cIt doesn\u2019t just consume data. It creates massive, erratic, unpredictable traffic patterns. If you build a model first and worry about the infrastructure later, your network could break.\u201d<\/p>\n He recommended that, before agencies pilot a single AI tool, teams must collaboratively look at three functional areas: <\/p>\n Data geography: Map the path of your data.<\/p>\n Security: \u00a0Autonomous agent acts like a superuser. Design your zero trust and micro-segmentation around AI itself, treating it as an independent entity.<\/p>\n Network elasticity: AI traffic is notorious for spiking. Your network must be intelligent, software-defined, and capable of scaling dynamically. <\/p>\n \u201cDon\u2019t let your AI strategy outpace your network strategy,\u201d he concluded.<\/p>\n This article and the original video panel were produced by Scoop News Group for FedScoop and sponsored by Verizon and Cisco.<\/p>\n Learn more about how Verizon<\/a> and Cisco<\/a> are helping public sector agencies ensure their network infrastructure is AI-ready. <\/p>\n","protected":false},"excerpt":{"rendered":"As federal agencies expand their use of data-intensive AI agents and software, they must also ensure that their…\n","protected":false},"author":2,"featured_media":143960,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[24,25,111,70891,329,70892,203,18709,70893,205,70894,70895,4115,70896,314,2015,70897,1226,70898],"class_list":["post-143959","post","type-post","status-publish","format-standard","has-post-thumbnail","category-ai","tag-ai","tag-artificial-intelligence","tag-artificial-intelligence-ai","tag-brian-epley","tag-cisco","tag-cisco-2026","tag-data","tag-department-of-commerce","tag-executive-video-panel","tag-infrastructure","tag-justin-fields","tag-managed-trusted-internet-protocol-service-mtips","tag-network","tag-sam-lakey","tag-security","tag-sponsored-content","tag-trusted-internet-connections-tic","tag-verizon","tag-verizon-2026"],"_links":{"self":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/143959","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/comments?post=143959"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/143959\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media\/143960"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media?parent=143959"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/categories?post=143959"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/tags?post=143959"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}