ICE awards contested, controversial surveillance contract to Thomson Reuters

TL;DR

ICE has awarded a $125 million surveillance contract to Thomson Reuters Special Services to monitor up to 1 million individuals and identify potentially criminal behavior before it occurs. The award continues and expands DHS (Department of Homeland Security) surveillance capabilities that the Summary says began at least six years ago with CACI, and the effort includes access to proprietary data, social media, geolocation, and deep web sources. The procurement drew controversy after being announced as sole-source, then reopened to competition and ultimately receiving only one bid from Thomson Reuters, raising transparency and civil‑liberties concerns for firms active in surveillance and analytics markets. Immediate implications: incumbent and prospective contractors in surveillance technology, data analytics, OSINT, and related services should assume increased agency buying and heightened scrutiny on privacy/compliance posture. Expect tactical shifts in capture priorities, altered competitive landscape, and demand signals for robust privacy and security controls. Cabrillo Club has detected this change and recommends immediate pipeline reprioritization and compliance validation.

Key Points

• What happened: ICE awarded a $125 million surveillance contract to Thomson Reuters Special Services to monitor up to 1 million individuals using proprietary data, social media, geolocation, and deep web sources; procurement was controversial (initially sole‑source, reopened, then only one bid).
• Who is affected: Surveillance Technology, Data Analytics, Intelligence Services, Biometric Services, Social Media Monitoring, Geospatial Intelligence, Law Enforcement Support, Predictive Analytics, Open Source Intelligence (OSINT), Dark Web Monitoring; NAICS and agencies listed in segmentation include 541512, 541513, 541519, 518210, 561611, 561621, 519130 and DHS, ICE, CBP; vehicles listed include DHS EAGLE II and OASIS+.
• Timeline: Continuation and expansion of DHS surveillance capabilities that began at least six years ago with CACI; procurement process moved from an initial sole‑source announcement to a reopened competition that ultimately received only one bid.
• What contractors should do NOW: Re‑score opportunities and reprioritize pipelines; run immediate compliance and privacy posture reviews against the listed regimes; enable saved searches for follow‑on solicitations; notify BD/capture, security, privacy, and proposal teams; begin rapid capture planning for potential task orders and future recompetes.

Who Is Affected

• Affected market segments (general): Surveillance Technology, Data Analytics, Intelligence Services, Biometric Services, Social Media Monitoring, Geospatial Intelligence, Law Enforcement Support, Predictive Analytics, OSINT, Dark Web Monitoring.
• Specific NAICS codes, agencies, contract vehicles, and compliance regimes are explicitly named in segmentation and apply: NAICS 541512, 541513, 541519, 518210, 561611, 561621, 519130; agencies DHS, ICE, CBP; contract vehicles DHS EAGLE II, OASIS+; compliance surfaces include NIST 800-171 (NIST Special Publication 800-171), FedRAMP (Federal Risk and Authorization Management Program), Privacy Act, FISMA, DHS Sensitive Systems Policy Directive 4300A.

Frequently Asked Questions

Q: What exactly did ICE buy under this award?

A: According to the Summary, ICE awarded a $125 million surveillance contract to Thomson Reuters Special Services to monitor up to 1 million individuals and identify potentially criminal behavior using proprietary data, social media, geolocation, and deep web sources.

Q: Does this create immediate new opportunities on named vehicles?

A: The Summary notes the award and lists DHS EAGLE II and OASIS+ in segmentation, but specific follow‑on task order opportunities or timelines are not provided. Timeline and opportunity details: Pending source review.

Q: What compliance and privacy controls should bidders prioritize now?

A: Use the compliance surfaces listed in segmentation as the baseline: NIST 800-171, FedRAMP, Privacy Act, FISMA, and DHS Sensitive Systems Policy Directive 4300A. Contractors should validate their controls against those regimes immediately.

Definitions

• Surveillance contract: A contract to collect, monitor, or analyze data about individuals or groups for law‑enforcement or national‑security purposes, as used in the Title and Summary.
• Proprietary data: Non‑public datasets owned or controlled by a company that are used to supplement open or commercial sources, as referenced in the Summary.
• Deep web: Online content not indexed by standard search engines, referenced in the Summary as a source for monitoring and analysis.
• Sole‑source: A procurement approach where a contract is initially awarded without competition, referenced in the Summary as part of the procurement history.

Intelligence Response

• Cabrillo Club detection & configuration:
• Cabrillo Signals War Room — Already detected this event and delivered this briefing. Use it to maintain an active alert for any protest filings, official agency announcements, or related awards that update the situation.
• Cabrillo Signals Match Engine — Immediately rescore and reprioritize your opportunity pipeline to reflect increased agency spend and the stronger incumbent position created by this award.
• Cabrillo Signals Intelligence Hub — Configure saved searches for DHS/ICE/CBP solicitations, task orders, and amendments on the named vehicles. Set alerts for any follow‑on solicitations or RFIs.
• Proposal Studio (Proposal OS) and Proposal Studio Workflow Tracker — Start capture artifacts: build compliance matrices against NIST 800-171, FedRAMP, Privacy Act, FISMA, and DHS Sensitive Systems Policy Directive 4300A; prepare draft win themes and a 9‑gate capture timeline.
• Who to notify:
• BD/Capture Lead — immediate reprioritization of pipeline and capture assignments.
• Chief Security Officer / Privacy Officer — validate security and privacy posture against the listed compliance surfaces.
• Proposal Manager — begin rapid capture and compliance documentation.
• Legal / Contracts Lead — review procurement record and any opportunities for engagement or protest monitoring.
• First 48‑hour playbook:
• Hour 0–4: Acknowledge briefing; create an incident/opportunity in Proposal Studio; assign BD and capture owners; flag priority opportunities in Match Engine.
• Hour 4–12: Run an automated compliance gap check in Proposal Studio against NIST 800-171, FedRAMP, Privacy Act, FISMA, and DHS Sensitive Systems Policy Directive 4300A; compile remediation list.
• Hour 12–24: In Intelligence Hub, enable saved searches for DHS/ICE/CBP and the named vehicles; collect incumbent scope and capability signals; begin initial win themes.
• Hour 24–48: Convene cross‑functional capture standup (BD, proposal, security/privacy, legal); finalize 9‑gate capture milestones in Workflow Tracker; start draft responses for likely solicitation sections.
• Further reading and references: See the Winning Federal Contracts Guide (/insights/winning-federal-contracts) and our related operational guides: CMMC (Cybersecurity Maturity Model Certification) Compliance Guide (/insights/cmmc-compliance-guide) and CUI (Controlled Unclassified Information)-Safe CRM Guide (/insights/cui-safe-crm-guide).