Protocol Free Encryption Device (PFED) for Sensitive But Unclassified (SBU) Networks Request for Information (RFI) W15P7T-26-R-PFED

Protocol Free Encryption Device (PFED) for Sensitive But Unclassified Networks Request for Information (RFI) 1. Description The Capability Program Executive Command (CPE) and Control Information Network (C2IN), Product Manager Communications Security (PdM COMSEC) is seeking information on available commercial-off-the-shelf (COTS) solutions for protocol-agnostic inline network encryption on the United States Army s Sensitive But Unclassified Encrypted (SBU-E) Networks. The goal is to secure high-speed, point-to-point data links by providing transparent, "bump-in-the-wire" encryption at the Physical or Data Link layer (OSI Layer 1/2). This RFI is to conduct market research on available PFEDs, to gauge industry interest for potential Bailment and Government evaluation. Information gathered will be used to collaborate with Subject Matter Experts (SMEs) and operational units to define possible use cases for these technologies. The ultimate objective is to gather sufficient data to determine whether adopting these items will improve or hinder the effectiveness and efficiency of current field operations. 2. RFI THIS IS A RFI ONLY. This RFI is issued solely for information and planning purposes it does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. A solicitation is not available at this time. Requests for a solicitation will not receive a response. This notice does not constitute a commitment by the United States Government (USG) to contract for any supply or service whatsoever. This RFI does not constitute sponsorship for National Security Agency (NSA) certification. All information submitted in response to this announcement is voluntary; the USG will not pay for information requested nor will it compensate any respondent for any cost(s) incurred in developing information provided to the USG. Not responding to this RFI does not preclude participation in any future RFP, if any is issued. If a solicitation is released, it will be published on the System for Award Management (SAM.gov) website. It is the responsibility of the potential offerors to monitor this site for additional information pertaining to this requirement. 3. Instructions to Vendors 3.1. Responses Vendors shall respond to this RFI with a white paper in Microsoft Word format compatible with Office 365 no later than fifteen (15) days from the date this was posted or June 10, 2026. The responses should not exceed fifteen (15) pages for the entire submission. This page limit does not apply to administrative sections. The initial section of the white paper shall consist of administrative information and, at a minimum, include the following: Designated Point of Contact: Name, mailing address, overnight delivery address (if different), phone number, fax number, and email address. Business Size and Classification: Indicate your company s business size and classification (e.g., large business, small business, small disadvantaged business, 8(a)-certified small disadvantaged business, HUBZone small business, woman-owned small business, very small business, veteran-owned small business, service-disabled veteran-owned small business) based on North American Industry Classification System (NAICS) code 334210 Telephone Apparatus Manufacturing. 3.2 Requested Information The responding vendor shall address the questions and topics of interest outlined in this paragraph of the RFI and is limited to fifteen (15) pages for the entire submission. This section shall provide evidence of vendor experience and briefly summarize the PFED s capabilities. Interested parties are requested to respond to this RFI with a white paper addressing the following questions. Potential respondents shall answer the questions in sections 3.2.1 and 3.2.2. If a question is not applicable to the device(s), simply respond to the question stating, Not Applicable . 3.2.1 Company and Device(s) Overview Provide an overview of your company and your experience in the field of network security and cryptography. Describe your primary device(s) that meet the description of a protocol-agnostic inline network encryptor. Include model names, target use cases, and key differentiators. Provide example deployment diagrams for common use cases (e.g., data center interconnect, secure campus link). Please provide a general, non-binding overview of your pricing model for your device(s). Is licensing based on hardware, throughput, features, or a subscription model? 3.2.2 Technical Information What are the supported throughput rates for your devices (e.g., 1 Gbps, 10 Gbps, 40 Gbps, 100 Gbps, etc.)? Is this throughput guaranteed at full duplex? What industry standard was used to determine throughput? What is the Size, Weight and Power (SWAP) of your device(s)? What are the power, cooling, and physical rack unit requirements for the device(s)? Are redundant power supplies available? Describe the management interface of the device (e.g., CLI, Web GUI, NETCONF/YANG). How is network management performed? What logging and auditing capabilities are available? What types of events are logged? How are software and firmware updates securely applied to the device? What is the typical latency added by the device at various throughput rates? Please provide specific metrics in microseconds (s). What physical network interfaces are supported and how are they to be replaced? Which Commercial National Security Algorithm (CNSA) Suite standards is your device compliant with? Do your devices hold any government or industry security certifications or other compliance? Please list all relevant, current certifications or compliances (e.g., FIPS, Common Criteria EAL4+). Please include any relevant IDs associated with the certifications or compliances. What cryptographic algorithms and modes of operation are used for data encryption (e.g., AES-256 GCM)? What PQC protocols are implemented on the device? Describe the key management architecture. How are cryptographic keys generated, distributed, stored, and rotated? Is an external Key Management Server required or supported? Are the cryptographic keys ephemeral, refreshing automatically for each session? What is the default key-life? 3.3 Responses White paper submissions, prepared in Microsoft Word format compatible with Office 365, are due 15 calendar days following the release of this RFI. Responses shall be formatted in Times New Roman, 12-point font, and include a Title Page (Section 1) and a synopsis (Section 2). Section 2 is limited to a maximum of fifteen (15) pages and must be submitted via email to Contracting Officer, Sharon A. Peterson, sharon.a.peterson15.civ@army.mil and Contract Specialist, Melody S. Thomas, melody.s.thomas.civ@army.mil. Any proprietary information or trade secrets contained within the submission must be clearly marked on all relevant materials. The Government will handle all information designated as Proprietary in accordance with applicable regulations. Please note that all submissions become the property of the USG and will not be returned. All USG and contractor personnel reviewing RFI responses will be bound by signed non-disclosure agreements and will adhere to the responsible use and protection of proprietary information, as outlined in 41 USC 423. The USG assumes no liability for damages incurred due to the failure to properly identify proprietary information. 4.0 Questions Questions regarding this announcement shall be submitted in writing via e-mail to Contracting Officer, Sharon A. Peterson, sharon.a.peterson15.civ@army.mil, and Contract Specialist, Melody S. Thomas, melody.s.thomas.civ@army.mil. Verbal questions will NOT be accepted. Questions will be answered by posting responses to the SAM.gov website. Accordingly, questions shall NOT contain proprietary or classified information.