ICE plans AI assistant to have role in use case development, document shows

TL;DR

ICE is developing STELLA (Secure Technology Environment for Large Language Agents), a FedRAMP (Federal Risk and Authorization Management Program)-authorized AI platform to develop and deploy AI use cases inside the agency. The platform will provide standardized tools, security controls, and LLM access to support ICE’s 40+ AI initiatives, representing a sizable expansion of AI adoption in federal law enforcement operations. Contractors who provide AI/ML, cloud, cybersecurity, or law enforcement technology to ICE, DHS (Department of Homeland Security), or related components should monitor STELLA closely because it may create new integration points and establish technical and compliance expectations for future implementations. Expect opportunities to integrate capabilities or to respond to follow-on solicitations once ICE publishes integration or acquisition guidance. In the near term, align product roadmaps and security artifacts to FedRAMP and the other compliance surfaces listed for this market and prepare capture teams to react quickly when solicitations or tasking appear.

Key Points

• ICE is building STELLA, a FedRAMP-authorized AI platform to standardize development and deployment of AI use cases across the agency.
• Who is affected: NAICS 541512, 541511, 541513, 541519, 541715, 518210, 541330; agencies DHS, ICE, CISA; contract vehicles OASIS+, CIO‑SP4, SEWP, 8(a) STARS III, Alliant 3; market segments include Artificial Intelligence/Machine Learning, Cloud Computing, Cybersecurity, IT Services, Law Enforcement Technology, Data Analytics, Software Development; compliance surfaces include FedRAMP, NIST 800-53, FISMA, CJIS, NIST AI RMF, DHS AI Policy.
• Timeline: Timeline TBD pending source review.
• What contractors should do NOW: monitor for follow-on guidance and solicitations; map offerings to FedRAMP-authorized integration patterns and the compliance surfaces listed; prepare security and privacy artifacts for rapid submission; update capture pipelines and prioritize pursuits tied to ICE/DHS AI work.

Who Is Affected

Specific NAICS codes, agencies, and contract vehicles are explicitly named in segmentation and should be considered affected: NAICS 541512, 541511, 541513, 541519, 541715, 518210, 541330; agencies DHS, ICE, CISA; contract vehicles OASIS+, CIO‑SP4, SEWP, 8(a) STARS III, Alliant 3. Market segments and compliance regimes called out in segmentation are also in scope: Artificial Intelligence/Machine Learning, Cloud Computing, Cybersecurity, IT Services, Law Enforcement Technology, Data Analytics, Software Development, and compliance surfaces including FedRAMP, NIST 800-53, FISMA, CJIS, NIST AI RMF, and DHS AI Policy.

Frequently Asked Questions

Q: What is STELLA?

A: STELLA is described as the Secure Technology Environment for Large Language Agents — a FedRAMP-authorized AI platform ICE is developing to provide standardized tools, security controls, and LLM access for development and deployment of AI use cases across the agency.

Q: Will contractors need FedRAMP authorization to integrate with STELLA?

A: The Summary states STELLA is FedRAMP-authorized; whether external contractors need an independent FedRAMP authorization or can integrate via ICE-hosted interfaces is Pending source review. Contractors should prepare FedRAMP-ready artifacts and assume FedRAMP and the other listed compliance surfaces will be relevant.

Q: How should contractors prioritize business development activity based on this?

A: Contractors supporting AI/ML, cloud, cybersecurity, and law‑enforcement technology should monitor ICE and DHS channels for follow-on solicitations and align security/compliance documentation now. Specific solicitation timelines and scope are Pending source review.

Definitions

• STELLA: Secure Technology Environment for Large Language Agents — the FedRAMP-authorized AI platform ICE is developing for AI use case development and deployment.
• FedRAMP: Federal Risk and Authorization Management Program — a government program for authorizing cloud services (as referenced in the Summary).
• LLM: Large Language Model — referenced in the Summary as an accessible capability provided by STELLA.

Intelligence Response

• Cabrillo Signals War Room — Already detected this event and delivered this briefing. Continue monitoring ICE/DHS announcement channels and policy updates; flag any published STELLA integration guidance or solicitations.
• Cabrillo Signals Match Engine — Rescore existing opportunity pipelines to surface pursuits most likely affected by STELLA-driven demand (AI/ML, cloud integration, CJIS/FedRAMP compliance).
• Cabrillo Signals Intelligence Hub — Create saved searches for ICE/DHS solicitations and contract actions tied to the NAICS codes and contract vehicles in segmentation; alert BD and capture teams when related notices appear on SAM.gov (System for Award Management).
• Proposal Studio (Proposal OS) and Proposal Studio Workflow Tracker — Use Proposal Studio to generate compliance matrices and rapid proposal outlines tied to FedRAMP, NIST, CJIS, and DHS AI Policy requirements; track capture progress through the 9-gate Workflow Tracker and maintain an audit-ready record of decisions and artifacts.

Who to notify: Capture lead and BD leadership — to evaluate and prioritize pursuits; CTO/technical lead — to map integration and LLM access requirements; Chief Information Security Officer/Compliance lead — to validate FedRAMP, NIST, CJIS alignment; Proposal manager — to prepare for rapid response.

First 48-hour playbook:

• Hour 0–4: Validate the event in Cabrillo Signals War Room; issue an organization-wide alert to capture, BD, security, and engineering; create saved searches in the Cabrillo Signals Intelligence Hub.
• Hour 4–12: Run a Match Engine rescore to reprioritize active opportunities; inventory existing FedRAMP and CJIS artifacts; begin a compliance gap analysis.
• Hour 12–24: Stand up a capture team, start a compliance matrix in Proposal Studio, and draft a preliminary bid/no‑bid assessment.
• Hour 24–48: Produce a draft proposal outline and work plan in Proposal Studio; log all decisions and artifacts in Proposal Studio Workflow Tracker; schedule stakeholder briefing to finalize next steps.

See the Secure Operations Guide (/insights/secure-operations-guide) for operational security practices and related guidance in the CMMC (Cybersecurity Maturity Model Certification) Compliance Guide (/insights/cmmc-compliance-guide) and CUI (Controlled Unclassified Information)-Safe CRM Guide (/insights/cui-safe-crm-guide).