Skip to content
FederalSources soughtClosing soon Federal notice

Enterprise Inbound Email Retention and Forensic Analysis Solution

Internal Revenue Service› Department of Treasury IRS New Carrollton, MD

Solicitation # IT2027-06Updated Nov 18, 2026Scored Nov 20, 2026

Closes in 5 days, Nov 25, 2026, 3:00 PM EST

Confirm the deadline and time zone on the official notice before you submit.

Amended Nov 19, 2026: Description updated

Responses due

Nov 25

Nov 25, 2026, 3:00 PM EST

Posted Nov 13Due Nov 25

Summary by RFP Detector

What this RFP is about

Internal Revenue Service (Department of Treasury IRS), part of the Department of the Treasury, posted a sources sought notice titled “Enterprise Inbound Email Retention and Forensic Analysis Solution” under solicitation number IT2027-06. It was first posted on Nov 13, 2026 and has been updated once since. Responses are due Nov 25, 2026, 3:00 PM EST. It is classified under NAICS 513210 (Software Publishers) and product/service code 7A21. No set-aside is listed. The place of performance is New Carrollton, Maryland. The listed point of contact is Jessica Camunez.

Key facts

Sector
Federal
Notice type
Sources sought
As posted: Sources Sought
PSC
7A21
Place of performance
New Carrollton, MD
Value
Not statedTypical award in this market ≈ $729.0K
Solicitation #
IT2027-06
Listing
Official federal notice

RFP Detector Score

Score breakdown

Every RFP starts at 50. Each factor adds or subtracts points compared with a typical RFP; unknown data counts as neutral.

Starts at 50

  • Value+1.8estimated

    No value published. Typical award is about $729K: the median of 42 Internal Revenue Service contracts over $25K awarded in NAICS 513210, FY24–FY26.

  • Competition & access−7.7measured

    Full and open competition. The largest recipient took 53% of these dollars in FY24–FY26, so expect a strong incumbent.

  • Issuer & market−8.5measured

    Internal Revenue Service obligated $186M on NAICS 513210 across 54 contracts in FY24–FY26.

  • Time & stage−1.7measured

    Sources sought (market research, not a bid): 5 days to respond (due Nov 25, 2026, 3:00 PM EST). Tight.

  • Clarity & completeness+3.9estimated

    Documents not listed, named contact with email, 1,420-word description.

  • Freshness+5.4measured

    Updated yesterday (scope change).

50 + contributions = 43 (D, Limited)

Score trend, last 30 daysScore history: 68, 54, 53, 50, 48, 45, 43

Informational, not advice to bid or not bid. Score version 1.0.0, evaluated Nov 20, 2026.

Requirements & submission

Eligibility · Full and open competition

Full and open competition means the notice states no set-aside: any responsible business can respond, subject to the requirements in the notice.

Not stated in a form we could extract. See the official solicitation for requirements, evaluation criteria and submission steps.

From the official notice

Description

1,420 words

NOTICE UPDATE – NOVEMBER 18, 2026 The Government has updated this Sources Sought Notice to clarify the requirements in Sections 1, 2.A, and 2.C regarding downstream email delivery, Cisco IronPort integration, and the secure handling of potentially malicious emails. All other requirements remain unchanged. The response deadline remains November 25, 2026, at 3:00 PM Eastern Time. Enterprise Inbound Email Retention and Forensic Analysis Solution Sources Sought Notice / Request for Information (RFI) This is a Sources Sought Notice (SSN) for market research purposes only. This notice is issued solely for information and acquisition planning purposes and does not constitute a Request for Quotation (RFQ), Request for Proposal (RFP), or a commitment to issue a solicitation in the future. The Internal Revenue Service (IRS) does not obligate itself to contract for any supply or service as a result of this notice. The Government is not currently seeking quotations or proposals and will not accept unsolicited quotations. The purpose of this notice is to identify potential vendors and commercially available solutions capable of meeting the IRS's enterprise email retention, search, and forensic analysis requirements. 1. BACKGROUND The Department of the Treasury, Internal Revenue Service (IRS), is seeking information on existing Commercial-Off-the-Shelf (COTS) solutions capable of providing enterprise-wide inbound email visibility, retention, centralized search, and forensic analysis capabilities for both legitimate (clean) and malicious emails. The IRS currently utilizes Cisco IronPort email security infrastructure and an existing Blind Carbon Copy (BCC) method to receive and retain copies of inbound email messages. The IRS is seeking a solution that can integrate with this existing infrastructure and preserve complete, unaltered copies of inbound emails, including message headers, content, metadata, and attachments. The IRS requires an enterprise-level solution that operates independently of individual Microsoft Outlook clients and does not rely on Outlook add-ons, plug-ins, or client-side software for enterprise email collection, retention, search, and forensic analysis. The proposed solution is not intended to perform downstream email delivery to Microsoft Exchange. Its primary function is to receive and securely retain inbound email copies for centralized search and forensic analysis. Interested vendors should identify any dependencies on downstream email systems associated with their proposed solutions. The IRS is interested in commercially available on-premises, virtual, cloud-based, or hybrid solutions. The Government is also interested in alternative technical approaches that can provide equivalent capabilities while meeting applicable federal security and operational requirements. The IRS does not have a predefined solution or architecture and welcomes information on commercially available products capable of meeting its operational needs. The results of this market research will assist the Government in identifying potential sources, assessing available commercial capabilities, and determining an appropriate acquisition strategy. The IRS anticipates a target implementation date of June 2027. Interested vendors should identify their estimated delivery and implementation timelines. 2. TECHNICAL CAPABILITIES Interested vendors are requested to describe their ability to meet the following anticipated technical and operational capabilities. Vendors should identify any capabilities that cannot be met or would require additional configuration, integration, or development. The Government welcomes information on alternative approaches that achieve equivalent operational outcomes. A. Cisco IronPort Integration and Email Collection Support integration with Cisco IronPort to receive and retain complete, unaltered copies of inbound email messages made available through the existing BCC method, including legitimate (clean) and potentially malicious emails, or an alternative collection method that provides equivalent functionality. Vendors should identify any collection limitations or integration dependencies associated with their proposed solutions. Preserve original message headers, content, metadata, and attachments for forensic investigations. Provide enterprise-wide email collection independent of Microsoft Outlook add-ons, plug-ins, or client-side applications. Identify any additional infrastructure, software, or configuration required for integration. B. Enterprise Email Volume and Retention The solution should be capable of supporting the following estimated email volumes: Up to approximately 1 million inbound emails per day. Peak email volume of approximately 150,000 emails per hour. Approximately 22 TB of inbound email data per month. Configurable retention periods ranging from 30 to 180 days for both legitimate and malicious emails. Vendors should describe the scalability, storage architecture, and performance capabilities of their proposed solutions. C. Email Search and Forensic Analysis Provide centralized search and investigation capabilities for both legitimate and malicious inbound email messages. Allow authorized analysts to search, retrieve, and review complete email messages, including headers, metadata, and attachments. Describe the solution's capabilities for identifying and classifying potentially malicious email messages, including any integration with existing email security tools. Describe available quarantine or equivalent isolation capabilities, whether provided directly by the solution or through integration with existing security infrastructure. Allow authorized analysts to view and download attachments for forensic investigations. Maintain message integrity throughout the retention and investigation process. Describe how the proposed solution securely receives, processes, retains, and supports forensic analysis of potentially malicious email messages and attachments while maintaining message integrity and protecting the system from malicious content. D. Third-Party Integration Support integration with Splunk for forwarding system logs, events, and email metadata. Support integration with Splunk SOAR for investigation and response automation. Provide APIs or equivalent interfaces for integration with additional security tools and automated workflows. E. Administration and System Management Provide secure command-line interface (CLI) access or equivalent administrative capabilities. Support high availability, redundancy, and automatic failover. Provide centralized system configuration, administration, and monitoring. For physical on-premises appliances, support IPMI or equivalent out-of-band hardware management. F. Security and Federal Compliance The solution must be capable of supporting applicable federal cybersecurity and audit requirements, including: IPv6 compatibility. Applicable FIPS 140-2 or FIPS 140-3 validated cryptographic modules. Encryption of data at rest and in transit. Role-based access control (RBAC). Audit logging and monitoring. Configurable security warning banners. Secure input validation. Secure remote configuration backups. Active Directory integration, including LDAP and SAML-based authentication, as applicable. For cloud-based solutions, vendors shall identify their FedRAMP authorization status, authorization level, and any limitations or additional requirements associated with federal deployment. Vendors shall also identify the country of product development, hosting locations, data storage locations, and any applicable federal security or supply-chain considerations. G. Technical Support and Maintenance Provide information regarding 24x7 technical support availability. Identify whether technical support can be provided by U.S.-citizen personnel. Describe regular software updates, security patches, and vulnerability remediation procedures. Identify available maintenance agreements, support response times, and escalation procedures. 3. SUBMISSION INSTRUCTIONS a) Point of Contact The point of contact for this notice is: Contracting Officer: Jessica Camunez Email: Jessica.r.camunez@irs.gov Responses shall be submitted electronically no later than November 25, 2026, at 3:00 PM, Eastern Time. Vendors shall reference "Enterprise Inbound Email Retention and Forensic Analysis Solution" in the subject line of their response. The Government is not requesting formal quotations, proposals, or general marketing materials. b) Requested Vendor Information The Government requests that interested parties submit the following information: 1. Company name, Unique Entity ID (UEI), business address, point of contact, telephone number, and email address. 2. Business size and socioeconomic status (e.g., large business, small business, small disadvantaged business, HUBZone, woman-owned small business, service-disabled veteran-owned small business). 3. Name and manufacturer of the proposed commercially available solution, including whether the solution is currently available. 4. Describe how the proposed solution addresses the technical capabilities identified in Section 2. For each capability, indicate whether it is currently supported, requires configuration or integration, requires additional development, or is not supported. Identify any alternative approaches that provide equivalent functionality. 5. Describe how the proposed solution integrates with Cisco IronPort using the existing BCC method or an alternative collection method capable of preserving complete, unaltered copies of inbound email messages made available through the collection method. 6. Describe the solution's ability to support the estimated enterprise email volumes, storage requirements, and retention periods. 7. Identify any dependencies on Microsoft Outlook, Microsoft 365, Exchange Online, Microsoft Purview, or other third-party products. 8. Identify applicable federal security certifications, FedRAMP authorization status (if applicable), hosting locations, and availability of U.S.-citizen technical support. 9. Provide an estimated implementation timeline and indicate whether the solution could be delivered and operational by June 2027. 10. Identify available Government contract vehicles, including GSA Multiple Award Schedule contracts, applicable Special Item Numbers (SINs), contract numbers, and suggested NAICS codes. 11. Identify the vendor's level of interest in a potential future requirement: highly likely to submit a quotation or proposal, may submit a quotation or proposal, or unlikely to participate. 12. Provide any additional information regarding alternative products, capabilities, or approaches that may satisfy the Government's requirements. Responses should be limited to 10 pages, excluding supporting technical documentation. The Government may contact respondents for clarification or additional information as necessary. Thank you for your interest.

Documents

No documents are listed for this notice.

Contacts

Points of contact as published on the notice.

Timeline & history

1 change since posting.

  1. Sources Sought posted

  2. Sources Sought posted

  3. Description updated

  4. Responses dueNext · in 5 days

  5. Archive date on the official notice

Federal award history

Market context

Internal Revenue Service · NAICS 513210 · FY24–FY26

Typical award (over $25K)
$729.0K
Contracts awarded
54
Total obligated
$185.6M
Award size, Internal Revenue Service · NAICS 513210 contracts, FY24–FY26 (log scale)
P25 $35.1KMedian $211.2KP75 $5.8MP90 $11.4M

Largest recipients in this market

  • PALANTIR TECHNOLOGIES INC.$98.1M53%
  • INTACT TECHNOLOGY INC$18.8M10%
  • FEDTRIBE LLC$13.0M7%

Recipients of past awards in this market, not the incumbent of this RFP.

View as table
Fiscal yearObligated ($)
FY20220
FY20233,399,896.24
FY202427,261,357.88
FY202562,012,178.77
FY202696,305,116.03

Federal contract award records, award types A–D, FY24–FY26. Updated Nov 15, 2026.

Similar open RFPs

Same NAICS group or IT & Software, nearby first, ranked by score.

Limited

Sonnet Software and Maintenance Support

National Institute of Standards and Technology · Gaithersburg, MD

FederalSpecial noticeIT & Software
Posted Nov 13Due Nov 28, 2026, 8:00 AM EST (in 8 days)Federal notice
Not competed

Intent to Sole Source – SOFT COMPUTER CONSULTANTS INC

National Institutes of Health · Bethesda, MD

FederalPresolicitationIT & Software
Posted Nov 18Due Nov 30, 2026, 12:00 PM EST (in 10 days)Federal notice
Poor

Globus Data Transfer System

Office of the Assistant Secretary for Financial Resources (Asfr) · Bethesda, MD

FederalSpecial noticeIT & Software
Posted Nov 18Due Nov 20, 2026, 2:30 PM EST (in 2 h)Federal notice

RFP Detector Scores are informational.How we score →

More from Internal Revenue Service

1 open RFP from this issuer and its offices.

At publication

Tax Software and Support

Internal Revenue Service · Lanham, MD

FederalClosedRFPIT & Software
Posted Oct 19Due Nov 18, 2026, 4:00 PM EST (2 days ago)Federal notice

RFP Detector Scores are informational.How we score →

About this notice

Official federal notice. Updated Nov 18, 2026.

Official solicitation:Sign in free to open the official solicitation

RFP Detector is an independent service and is not affiliated with any government agency. Scores are informational.

RFP Detector is not affiliated with the organization that issued this RFP. Always rely on the official notice and confirm every date and requirement with the issuer.