By Ross Weatherford, Senior Director of National Security Programs at Coder

Over the last several months, the conversation inside the IC about AI-augmented development has moved fast. Platform engineering is replacing the monolithic software factory. The builder population is expanding beyond credentialed engineers to analysts, operators, and specialists who carry the community’s most irreplaceable asset: domain expertise. Both of those shifts are real, and together they create a problem the IC has not yet solved.

More builders mean more environments. More environments mean more surface area. And when autonomous AI coding agents are introduced into that expanded landscape, agents that can access repositories, generate code, and execute tasks without continuous human direction, the blast radius of a misconfiguration, a compromised dependency, or an insider threat expands in ways that traditional security models were not designed to handle.

This is not a theoretical concern: Georgia Tech’s Systems Software & Security Lab tracked 35 new CVE entries in March 2026 alone that resulted directly from AI-generated code, up from six in January and fifteen in February. Veracode’s 2025 GenAI Code Security Report found that AI-generated code contains 2.74 times more vulnerabilities than code written by humans. Apiiro found AI-generated code creates 322 percent more privilege escalation paths. The democratization of development is genuinely transformative, yet it comes with a governance challenge that the IC needs to get ahead of before the scale arrives, not after.

The agentic AI risk layer

The security risks of AI-assisted coding are real enough on their own. But AI coding agents, autonomous systems that do not merely suggest code but take actions, access file systems, call APIs, and modify repositories, introduce a qualitatively different class of risk.

These agents can access repositories outside their intended scope, generate verbose outputs that inadvertently leak sensitive context, and escalate privileges in ways that no human developer would, simply because the agent’s optimization function does not include the same threat model a trained engineer carries. Check Point Research disclosed critical vulnerabilities in a major AI coding tool in February 2026, including configuration injection flaws that allowed remote code execution the moment a developer opened a compromised project, and the OpenClaw supply chain attack confirmed over 1,100 malicious packages in an AI agent ecosystem, roughly one in five packages in the affected repository.

This is already informing how the Intelligence Community approaches AI deployment. The question is no longer whether AI agents will operate in IC development environments, because they will. The question is whether the governance infrastructure will exist when they do.

Human on the loop as operational reality

The IC cannot have a human reviewing every line of AI -generated code. With developers estimating that 42 percent of committed code is already AI-assisted, and increasing, that model is not merely impractical, it is impossible. Yet the alternative is not abandoning oversight, but moving oversight to where it can actually operate: the policy and boundary level rather than the task level.

In practice, this means immutable audit logs that capture what every agent did, when it did it, and in what context; toolchain limits that constrain what an agent can access so a coding assistant working on a frontend component cannot reach into a classified data pipeline; sandboxed execution environments where agent generated code runs in isolation before it touches anything in production; and SIEM integration that treats agent activity as a first class telemetry source rather than an afterthought bolted onto existing monitoring.

The shift from human in the loop to human on the loop is not about reducing accountability. It is about making accountability scalable. A senior engineer reviewing a pull request is valuable, but a platform that prevents the pull request from ever containing unauthorized access patterns is more valuable, because it operates continuously and does not depend on one person’s attention on a random Tuesday.

What coherent governance looks like across agencies

Each IC agency has distinct missions, infrastructure, and risk tolerances. No one is arguing for a single centralized governance platform because that would repeat the exact mistake the monolithic software factories made. What the community needs is shared baselines.

ODNI is already moving in this direction. In March 2026, ODNI announced it is building the policy framework, governance, and standards to accelerate AI adoption across the IC, and DNI Gabbard has since announced the largest ever IC cybersecurity investment and modernization effort, which includes policy standards for AI in cyber defense, a shared repository for security reviewed applications, and expanded threat hunting capabilities.

The architecture this points toward is one in which ODNI sets minimum standards for red teaming, auditability, and incident reporting. Meanwhile agencies deploy on their own infrastructure and use their own toolchains, yet produce logs and controls compatible with a common framework. It is better understood as the difference between requiring everyone to use the same car and requiring everyone to drive on the same side of the road, because the goal is interoperability rather than uniformity.

Intelligence Community Directive 505 on Artificial Intelligence, combined with NIST’s Secure Software Development Framework and SP 800-218, provides the policy scaffolding, but what has been missing is the operational infrastructure that makes those directives enforceable at the speed development actually moves.

Compliance that travels with the workspace

The most durable governance model is one in which policy is embedded in the environment itself, not layered on top of it after the fact.

The principle is consistent across all of this: when compliance is embedded in the environment rather than layered on top, it scales. Small platform teams define it once in code. Every builder, human or agent, inherits it automatically. The governance model for AI agents is not a new problem — it is the same infrastructure problem, applied to a faster and less predictable actor.

When a workspace template defines what an AI agent can and cannot do, what repositories it can access, what actions it can take, and what boundaries it must respect, that governance is structural, and it does not depend on the individual developer configuring it correctly, and it does not depend on a security team reviewing every session, because a workspace that meets governance requirements on an unclassified network works identically on a classified one, since the controls are defined in the template rather than in a separate policy document that someone has to remember to apply.

Coder’s approach to agent boundaries, task definitions, and centralized environment management give security teams visibility and control over what AI agents do inside builder workspaces without requiring those teams to be present for every session, so the platform becomes the enforcement mechanism and governance becomes infrastructure.

The cost of waiting

Provisioning speed, prototype speed, the speed to turn domain expertise into mission capability — those are the stakes this argument has been building toward. But the most consequential speed question is not about development environments. It is about how fast adversaries are moving while the IC deliberates.

China is now estimated to spend roughly $2 billion annually on AI enabled military systems, comparable to United States levels, and has deployed autonomous ground robots, AI driven drone swarms, and machine learning systems for target recognition and operational planning at scale and the PLA is actively restructuring its joint operational frameworks around AI driven combat platforms. Russia, meanwhile, is taking a different but equally consequential approach, rapid, iterative deployment of autonomous systems in actual combat in Ukraine, refining capabilities through operational feedback loops that compress the development cycle in ways traditional procurement cannot match; Russian and Chinese officials held formal consultations on military AI cooperation in Moscow in November 2025, and they are not waiting to resolve governance before deploying, because they are deploying and adapting in parallel.

The IC’s advantage, and it is a genuine advantage, is that it can move fast and build trust simultaneously. Democratic accountability, rigorous oversight, and transparent governance are not obstacles to speed. When done correctly, they are accelerants, since they build the institutional confidence required to deploy AI capabilities broadly rather than keeping them confined to pilot programs and proofs of concept that never scale.

But that advantage has a shelf life. The Pentagon’s fiscal year 2026 budget requests $13.4 billion for AI, so the investment is there, the policy direction from ODNI is there, and the commercial technology to enforce governance at the platform level exists today. What remains is the execution, standing up the infrastructure that makes governance operational before the scale of AI augmented development outpaces the community’s ability to oversee it.

The organizations that get this right will not be the ones that moved cautiously. They will be the ones that built governance into their development infrastructure from the start, so that when the scale arrived, the trust was already in place.

The governance infrastructure the IC needs is not a future requirement. It is a current one. The factory has already given way to the framework. The builder population is already expanding. The agents are already operating. The window to get ahead of it is not as wide as it might appear.

About the author

Ross Weatherford is a Director of National Security Programs at Coder, where he partners with DoW, Intelligence Community, and defense contractor customers on secure, compliant development environments and agent ready workspaces. With over two decades in cybersecurity and federal technology, Ross has led cyber architecture and engineering teams at Northrop Grumman across classified space and ground systems and served as lead solutions architect for the largest account in national security programs at Red Hat. He holds CISSP, CCSP, RHCSA, and AWS certifications.

About Coder

Coder is the only AI development Infrastructure that unifies development environments, AI governance, and autonomous agents into a single, self-hosted system. It enables enterprises to move development off unmanaged endpoints and into standardized, policy-controlled environments where both builders and AI agents operate in parallel safely. With centralized governance, AI model-agnostic flexibility, and full observability, Coder allows organizations to scale AI adoption without compromising security, compliance, or cost control. Learn more at coder.com.

The post Governing What You Cannot See: How the IC Should Think About Security and Oversight for AI Augmented Development appeared first on Intelligence Community News.

AI governance refers to how organizations put guardrails around the use of AI. Making sure systems are reviewed, approved, and monitored so leaders understand how they work, what risks they carry, and when they are ready to be used. It helps ensure AI is deployed responsibly, with transparency, accountability, and alignment to legal, ethical, and mission needs.

Built on Leidos’ AI that has been deployed in real-world missions over decades, the collaboration focuses on removing friction from AI adoption while maintaining accountability. By combining Trustible’s automated AI governance platform with Leidos’ experience building agentic capabilities at scale in national missions, the initiative helps agencies unlock innovation while managing AI risk.

As government agencies respond to new federal directives calling for accelerated AI alongside strong oversight, the need for governance that enables progress has become increasingly clear. The collaboration with Trustible helps operationalize governance through automation, enabling agencies to move from policy to practice more efficiently. At its core, the approach aims to ensure AI governance is outcome-driven—supporting real mission results as well as compliance.

“AI governance can’t be a manual, after-the-fact process—especially as agencies begin to adopt more autonomous and agentic systems,” said Gerald Kierce, co-founder and CEO of Trustible. “Working with Leidos, we’re using automation to streamline governance from the start—reducing friction, strengthening control, and helping agencies deploy AI faster while maintaining the oversight and risk management their missions demand.”

Source: Leidos

Stay in the know with breaking news from across the IC and IC contracting landscape by becoming a paid subscriber to IC News. Your support makes our work possible.

The post Leidos and Trustible launch initiative appeared first on Intelligence Community News.

Michael Epley, Chief Architect at Red Hat

Frank La Vigne, Data Cloud Services Global GTM Leader at Red Hat

Data is the lifeblood of the intelligence community. In the modern digital information age, we are deluged by an increasing volume and diversity of data. Finding the most significant parts or link information to convert this raw data into insights that drive policy and action is more challenging than ever. Maximizing the exploitation of this data with artificial intelligence (AI), data science, and decision-making processes is the fundamental challenge of the intelligence community. The significance of both data pipelines and data governance has become paramount as a result. These two concepts collectively help achieve data quality, security, and efficient utilization.

Understanding Data Pipelines

Data pipelines act as the nerves of the data ecosystem – moving the raw bits of information from the sensory cells in the skin to the brain. The action is like an assembly line for this information, and they are a series of steps designed to ingest, clean, transform, model, and visualize data. And like an assembly line, pipelines streamline data management, ensuring a smooth data flow from one phase to the next.

Figure 1: An example data pipeline built with open-source and Red Hat technologies

Whether it’s data science or AI, data pipelines play a critical role, from facilitating feature engineering in machine learning to automating the training and validation of models. Key benefits of data pipelines include:

• Efficiency: Automated data management accelerates processes and minimizes manual errors. Many data pipeline tools encode these processes in ways that can be configuration-managed and allow branching, experimentation, and reuse.
• Data Integrity: Consistent operations across all data ensure reliable analysis outcomes. Pipelines can be wired with validation checks or assertions to ensure they are working as expected and the data being processed is as expected.
• Collaboration: Unified data processing steps enable seamless teamwork among professionals. Data processing is reproducible, sharable, and consistent over time and across teams, even if the data itself is not.
• Scalability: As data grows, pipelines can be expanded or modified to handle more information and integrate new data sources. Pipelines can produce and consume intermediate data and allow users to create composite

Implementing data pipelines is not easy and can present various challenges:

• Shaping: Not all downstream users need the same data in the same way, making the reuse of data pipelines complicated and leading to stovepiping and siloing of the pipelines and the resulting data.
• Scaling to data: Expanding pipelines is easy, but scaling the backend data systems they leverage is complicated – and single or aggregations of pipelines may exceed the capacity of individual backends.
• Provence: By design, they transform and change the data and its representation – but keeping track of how and why is critical when we need to explain downstream conclusions to check for or correct for biases and contamination and give ourselves confidence in our conclusions.

The Imperative of Data Governance

Meeting these challenges is why data governance is imperative. While data pipelines focus on processing, data governance centers on protection and regulation. Policies, processes, and practices help ensure data remains accurate, consistent, and secure, and data governance applies these to our data pipelines to allow us to realize the benefits while addressing the challenges.

Data governance becomes indispensable because of the following:

• Explosive Data Growth: There is a surge in the number and diversity of data sources, including specialized organic sensor platforms, 3rd party IoT devices, social media harvesting, commercial and open-source data collection, and many others, each with their own data types, formats, operational and logistical constraints. A sturdy governance framework maintains data relevance by matching the needs for the data processing to the volume present and resources available.
• Compliance: Governance develops confidence that pipelines protect data from taint, misuse, spills, or exfiltration by attackers or insiders. When automated, we can further reduce risk by asserting where the data was used or manipulated, how, and what information protections were in place. Governance of pipelines can be used to ensure downstream users see only appropriately filtered and processed data and remove potentially malicious data.
• Quality Decision Making: Reliable data analytics and AI-driven insights are contingent upon high-quality data, ensured through governance. Downstream uses of the data – like data scientists who are building or training models – have to know the data is the best available, and good data governance provides this assurance. By applying governance to data pipelines, we can ensure necessary preparation, cleaning, and shaping operations are used and fit the end user’s needs.
• Data Security: Pipelines allow us to separate concerns and roles about how to massage data and who actually gets to access the data. Data governance lets data scientists focus on the former without worrying where the data comes from or can require them to use biased/unbiased, test or synthetic data in development or riskier environments.

To enforce effective data governance:

1. Establish a team: Comprising members from diverse departments like data science, IT, and policy.  Policy teams can express the procedure so IT professionals can encode these using their data governance tools. In contrast, the data scientists can verify they can still do meaningful work within those policies or provide feedback when policies need to be updated.
2. Craft policies: Comprehensive rules addressing various aspects, from data quality to security. Encoding these rules sets clear objectives when building and testing pipelines and helps flag and analyze unexpected behavior.
3. Adopt tools: Technology can help automate governance processes. When considering data governance, pipelines, and their management can get complex. Tools that remove the toil and provide consistency will remove pain points and bottlenecks, along with the other benefits noted above.
4. Monitor constantly: Find your KPIs and use KPIs to measure governance efficacy, recalibrating as needed. As an aid to governance, building and collecting metadata into our pipelines will provide the required feedback to improve continuously. By completing the circle, governance can ensure the metadata collection is injected into the pipelines.
5. Promote governance culture: Your key value stakeholders, the mission owners and data stewards, are critical to making sure the value of a robust governance model is understood, and your data scientists, data engineers, and application developers implement the model and assets like data pipelines to this target.

As we advance in the digital age, efficient data management and robust protection mechanisms become crucial. Data pipelines optimize data utilization, turning it into actionable insights, while data governance ensures the sanctity and security of this data. Together, they form the backbone of a successful data-driven enterprise, highlighting the intertwined relationship between processing efficiency and protective measures in the data domain. Visit red.ht/icn to learn more about this and other issues within the intelligence community.

About Red Hat

­Red Hat is the world’s leading provider of enterprise open source software solutions, using a community-powered approach to deliver reliable and high-performing Linux, hybrid cloud, container, and Kubernetes technologies. Red Hat helps customers develop cloud-native applications, integrate existing and new IT applications, and automate and manage complex environments. A trusted adviser to the Fortune 500, Red Hat provides award-winning support, training, and consulting services that bring the benefits of open innovation to any industry. Red Hat is a connective hub in a global network of enterprises, partners, and communities, helping organizations grow, transform, and prepare for the digital future.

About IC Insiders

IC Insiders is a special sponsored feature that provides deep-dive analysis, interviews with IC leaders, perspective from industry experts, and more. Learn how your company can become an IC Insider.

SOURCES

Merger of https://www.linkedin.com/pulse/data-governance-essential-framework-modern-business-success-la-vigne/ and https://www.linkedin.com/pulse/importance-data-pipelines-ai-frank-la-vigne/

Loosely based on the IC RFIs – ATOM SMASHER and NGA Data Science

The post Driving Digital Transformation: The Crucial Elements of Data Pipelines and Governance appeared first on Intelligence Community News.