AI Governance Institute
← News
Corporate Policy2026-10-02

ICE Agentic Software Factory Bans Self-Approval and Permission Escalation by Design

Source

ICE IT shop looks to build 'agentic software factory'

U.S. Immigration and Customs Enforcement (ICE)

What happened

ICE's Office of the Chief Information Officer published an RFI seeking vendor support for an agentic software factory built on STELLA, its existing development platform. The initiative would delegate planning, implementation, testing, and mission-acceptance tasks to AI agents. ICE describes three distinct layers: an enterprise control plane, an agentic orchestration tier, and an independent assurance boundary. The assurance boundary handles cybersecurity review and production acceptance before any code reaches live systems. Two governance rules stand out: no agent may silently expand its own permissions, and no agent may approve its own release to production. This follows a broader pattern of federal agencies deploying AI agents at scale. Recent examples include 50,000 Agents in Two Weeks: GenAI.mil Exposes Scale vs. Governance Gap and HUD's AI Grant Monitor Launches September 30 With Oversight Rules Unfinished.

Why it matters

  • ·The explicit ban on self-permission expansion directly addresses a risk that has caused real harm in commercial deployments. Compliance and risk teams should treat this as a named benchmark. If a government agency can write this rule into architecture, enterprise programs should demonstrate an equivalent control.
  • ·The three-layer design, separating orchestration from assurance, gives compliance teams a practical model for segregation of duties in agentic systems. Regulators reviewing agentic deployments under frameworks like the Five Eyes Guidance on the Careful Adoption of Agentic AI Services are increasingly asking exactly this question.
  • ·Because this is an RFI rather than a contract award, vendors responding will be shaping the government's eventual requirements. Enterprises that sell software to federal agencies should watch what governance conditions ICE codifies, as those conditions are likely to flow into procurement contracts and downstream compliance obligations.

Governance controls affected

AGT-001Agent Permission BoundariesAGT-005Human Approval Gate for Irreversible Agent ActionsAGT-015Agent OAuth Scope Drift DetectionAGT-016Agentic AI Deployment Readiness AssessmentAGT-006Agent Action Audit Trail

What to do now

  • ☐Review your agentic AI deployments and confirm that no agent can request, grant, or expand its own access permissions without a separate human or system approval step.
  • ☐Check whether your software development pipelines that use AI agents have a separate, independent review layer before any AI-assisted code reaches production, and document who owns that gate.
  • ☐Map your existing agent governance controls against ICE's three-layer model (control plane, orchestration tier, independent assurance boundary) and identify which layer, if any, is missing or undocumented.
  • ☐If your organization sells technology to federal agencies, assign someone to monitor the ICE RFI responses and any resulting contract requirements, since those requirements will likely define procurement conditions for vendors.
  • ☐Update your agent governance documentation to explicitly prohibit self-approval of production releases, and confirm that prohibition is enforced technically, not just stated in policy.

What to watch next

The ICE RFI responses will shape the eventual contract requirements, making this a live opportunity to observe how the government codifies agentic governance conditions into binding procurement language. Compliance teams should monitor whether other federal agencies adopt similar three-layer assurance models. Key precedents include IRS Deployed High-Impact AI With No Testing Records in 80% of Cases and the SBA's AI Fraud Pilot Never Classified as High-Impact. The White House AI Oversight Framework will likely be cited as regulatory backdrop when ICE finalizes its requirements. The OMB Memorandum M-26-04: Increasing Public Trust in AI Through Unbiased AI Principles is expected to be cited as well.

Stay ahead of stories like this

Get every US AI governance development like this one, plus the rest of the week's developments. Every Thursday.

Free every Thursday. Unsubscribe anytime.

Related Coverage

Corporate Policy2026-09-22

PwC's Three Governance Shifts Put Runtime Agent Controls at the Center

PwC has published implementation guidance framing agentic AI governance as a continuous runtime discipline rather than a pre-deployment checklist. The guidance identifies three core shifts: defined ownership of agent actions, constrained task authority, and auditable logs of autonomous behavior. Enterprises deploying AI agents are the primary audience.

Corporate Policy2026-09-22

No Cryptographic Attestation Means No Audit Trail for AI Agents

DigiCert's Chief Product Officer has outlined a practitioner case for cryptographic identity attestation as a baseline governance control for AI agents. The argument follows a wave of documented sandbox escapes and containment failures involving models from Anthropic, Google, and OpenAI during pre-release testing. Without signed, verifiable authorization records, compliance teams cannot demonstrate that an agent acted within sanctioned boundaries after an incident occurs.

Research2026-09-22

Agent Governance Shifts From Logging to Pre-Action Authorization Evidence

A September 2026 analysis by The Cube Research argues that enterprise agent governance is moving beyond passive observability toward a model of provable trust. The framework requires that each agent action be tied to a distinct identity and authorized against current context before it executes. Organizations relying on post-hoc audit logs alone face a structural control gap.