REQUEST FOR INFORMATION - 11-9-26 (Clean).docx

DOCX document 58 KB Posted

Attached to
Department of Defense Secure Access File Exchange Modernization
Solicitation number
622673683
Issued by

About this file

This is a Request for Information (RFI) issued by the Defense Information Systems Agency (DISA) for market research regarding the modernization of the Department of Defense Secure Access File Exchange (SAFE) system under the authority of 10 U.S.C. 4022. The Government seeks information on commercially available, commercial-off-the-shelf (COTS), and reasonably adaptable software capabilities to support secure, policy-controlled file transfer and data movement across designated network environments. SAFE currently serves over 4 million users globally, providing managed file transfer tools to DoD personnel and mission partners. The modernization effort aims to address limitations in scalability, security, usability, authentication, data loss prevention, content inspection, policy enforcement, integration with external systems, user experience, and data-retention policies. The Government is assessing the viability of using an Other Transaction Agreement (OTA) to design, develop, test, demonstrate, and evaluate an operational prototype, with potential transition to a follow-on, non-competitive production contract under 10 U.S.C. 4022(f).

Respondents must address system architecture and deployment flexibility, high-performance transport for files ranging from 100 GB to multiple terabytes, zero trust security with DoD Enterprise Identity, Credential, and Access Management (E-ICAM) federation (SAML 2.0/OIDC), disconnected/denied, degraded, intermittent, and limited-bandwidth (DDIL) operations, and cross-domain integration capabilities. The solution must operate within DoD Impact Level 5 and 6 security boundaries, support FIPS 140-3 encryption, multi-factor authentication, FedRAMP Moderate compliance, and native Data Loss Prevention (DLP) scanning for personally identifiable information and controlled unclassified information. Required deployment support includes containerized Kubernetes/Helm, virtual machine images, and native support for x86_64 and ARM64 architectures across enterprise, cloud, on-premises, and tactical-edge environments. White paper responses cannot exceed 20 pages, single-spaced, 11-point type with one-inch margins (excluding cover page, table of contents, and appendices), and must not exceed 5 MB. Responses must include business information, relevant experience, past performance examples, and non-binding Rough Order of Magnitude pricing for a representative deployment of 5 strategic hubs and up to 500 tactical edge instances. OTA eligibility information is required, including small business or Nontraditional Defense Contractor status or partnership arrangements. Responses are due by December 10, 2026, at 4 PM eastern time via email to elizabeth.a.bono.civ@mail.mil and shawn.m.dostie.civ@mail.mil. This RFI is for information and planning purposes only and does not constitute a solicitation, commitment, or authorization to incur costs; no payment will be made for responses, and all submissions become Government property.

View the file

Other files

File Type Posted
RFI DoD SAFE Modernization AMD01.docx DOCX document
DoD SAFE RFI QA 01092026.xlsx XLSX spreadsheet
RFI_DoD SAFE Modernization_FINAL12-22.docx DOCX document
SAFE Technical Characteristics Attachment FINAL 12-22.docx DOCX document
RFI_DoD SAFE Modernization_FINAL.docx DOCX document
SAFE Technical Characteristics Attachment.docx DOCX document

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

REQUEST FOR INFORMATION (RFI)

Defense Information Systems Agency (DISA), Portfolio Acquisition Executive Command, Control, Communications & Enterprise / Services Division (PAE C3E/SD), is modernizing a large file transfer system. The modernized solution will update the Department of War’s (DoW) Secure Access File Exchange (SAFE). SAFE is a DoW Common Access Card (CAC)-enabled, DISA enterprise secure file exchange platform hosted on Non-classified Internet Protocol Router Network that is also accessible via the Secret Internet Protocol Router Network.

THIS IS A REQUEST FOR INFORMATION (RFI) NOTICE ONLY. THIS IS NOT A REQUEST FOR PROPOSALS (RFP). NO SOLICITATION IS AVAILABLE AT THIS TIME.

1. Overview/Purpose/ Description of Procurement This RFI is issued for market research, planning, and information-gathering purposes in support of potential prototype development under 10 U.S.C. 4022.

The Government is seeking information regarding commercially available, commercial-off-the-shelf (COTS), potential prototype capabilities, or reasonably adaptable software capabilities to support secure, policy-controlled file transfer and data movement across designated network environments. The Government previously published an RFI to SAM.gov on December 17, 2025, under Tracking Number 622673683. The Government’s required capabilities have evolved since that time, and the Government is looking for updated industry responses.

The SAFE system facilitates the secure transfer of files for authorized users, including CAC holders and guest users with limited access privileges. These secure file transfer capabilities enable the expedited delivery of essential data to mission partners both within and external to the DoW. The implementation of SAFE mitigates the risks, costs, and logistical delays associated with the physical transmission of sensitive documentation.

The SAFE Program Management Office is conducting market research to modernize current capabilities. The Government is assessing the viability of utilizing an Other Transaction Agreement (OTA) under the authority of 10 U.S.C 4022 to design, develop, test, demonstrate, and evaluate an operational prototype modernization solution. In accordance with DoW OTA guidance, successful completion of a prototype developed under this authority may transition into a follow-on, non-competitive production contract or transaction under 10 U.S.C. § 4022(f).

SAFE currently provides enterprise secure-file-exchange services for authorized users in designated operating environments. The Government seeks information on modernization approaches that preserve required mission access while improving scalability, security, interoperability, usability, and lifecycle support.

The Government is particularly interested in application-layer software capabilities that can be deployed without requiring a proprietary hardware appliance or vendor-specific infrastructure ecosystem. The Government recognizes that some solutions may require integration with separately provided boundary-enforcement, inspection, identity, logging, or infrastructure components. Respondents should identify all such dependencies.

The Government is seeking information on modernization approaches that address potential limitations in:

· Performance and scalability during periods of peak demand;

· Authentication strength and identity-service integration;

· Data loss prevention, content inspection, and policy enforcement;

· Integration with external Government-approved systems and workflows;

· User experience, including file-size limitations and administrative burden; and

· Data-retention, expiration, deletion, and recovery policies.

The Government seeks information on potential approaches that may support both of the following operational profiles:

1. Enterprise and strategic environments. High-throughput data movement among cloud-hosted and on-premises environments, including large-scale enterprise data centers and distributed mission partners.

2. Tactical and edge environments. Lower-footprint deployments operating on COTS compute platforms in degraded, intermittent, or limited-bandwidth conditions, including extended periods without connectivity to enterprise management, licensing, or support services.

The modernized SAFE solution must operate within a Department of War (DoW) Impact Level 5 (IL5) and Impact Level 6 security boundary. Whether the proposed solution is hosted as a tenant within a Government-managed cloud environment (such as DISA Stratus) or delivered as an accredited commercial Software-as-a-Service platform, it must integrate seamlessly with DoW enterprise services. Under this shared-responsibility model, the solution is expected to utilize DoW’s centralized Enterprise Identity, Credential, and Access Management (E-ICAM) systems for user authentication. The Government seeks information on solutions that provide robust, native security capabilities—specifically regarding application access control, data rights management, and detailed audit log generation—while remaining compatible with broader DoW enterprise transport, boundary, and visibility layers.

This RFI does not establish final technical requirements. The Government welcomes information on integrated products, modular products, and architectures that combine Government-furnished or third-party components.

2. Scope of Effort SAFE currently supports over 4 million users globally, providing essential managed file transfer tools to DoW personnel in the Contiguous United States and abroad, as well as to internal and external mission partners. The scope of this modernization effort encompasses addressing limitations in scalability, security, and usability through architectural changes, enhanced security features, improved data management, and expanded user access options. The effort spans across file sharing, network operations, and access control functionalities. Please see the required technical characteristics in more detail below.

Scope of Need: The Government is exploring commercial software, hybrid, or Software-as-a-Service capabilities that address the following core areas:

· Security & Compliance: Compliance with Federal Risk and Authorization Management Program (FedRAMP) Moderate, Federal Information Processing Standards (FIPS) 140-3 encryption standards, and support for multi-factor authentication and Single Sign-On integration.

· Performance & Scale: Reliable transmission of extremely large datasets (100GB+ files) over high-latency or restricted-bandwidth networks without session drops.

· Automation & Visibility: Low-code/no-code workflow automation builders, comprehensive central audit logs, and real-time transit telemetry dashboards.

Interoperability: Standard protocol support (Secure Shell File Transfer Protocol (FTP), Applicability Statement 2, Hypertext Transfer Protocol Secure) combined with modern Representational State Transfer Application Programming Interface known commonly as REST APIs to interact with cloud-based storage services (such as Amazon Web Services Simple Storage Service or Microsoft Azure Blob) and legacy applications.

The Government seeks information to:

· Identify vendors capable of providing software-based managed file transfer, data-routing, cross-domain integration, content-validation, and disconnected-operation capabilities.

· Understand maturity, availability, deployment model, performance limits, interoperability, and support requirements of available solutions.

· Determine whether the market can support a common software capability across enterprise, cloud, on-premises, and tactical-edge deployments without separate code branches or proprietary hardware dependencies.

· Assess approaches for secure movement, inspection, validation, sanitization, routing, queuing, and recovery of structured and unstructured data.

· Inform potential cost, schedule, licensing, sustainment, integration, cybersecurity, and authorization considerations.

3. Technical Characteristics:

The Government is requesting responses from industry to see if the following technical criteria are available in the commercial marketplace. The Government requires a comprehensive solution to replace the existing SAFE legacy system if implemented.

Capability Areas of Interest The following areas describe Government interests for market research. They are not mandatory requirements for this RFI. For each area, respondents should identify whether the capability is:

· Available as a current commercial product;

· Available through configuration or integration;

· Available through planned product development;

· Available only through custom development; or

· Not available.

Managed File Transfer Core Technical Requirements:

Technical Pillar
Key Characteristic / Core Capability Requirement
1. Deployment & Scaling
• Multi-Architecture: Native support for x86_64 and ARM64 architectures.

• Packaging: Standard containerized deployment (Open Container Initiative)-compliant, Kubernetes/Helm) and Virtual Machine images.

• Compute Footprint: Minimal resource overhead; must utilize a common codebase across enterprise and tactical edge deployments.

• Elasticity: Horizontal/vertical autoscaling based on concurrent user count and transfer volume.

2. Cross-Domain Operations
• Architecture Role: Must act as a transfer engine, orchestration layer, or inspection node within a multi-domain guard architecture.

• Enforcement Integration: Out-of-the-box API/protocol interfaces with hardware data diodes, guards, and one-way transfer systems.

• Data Isolation: Enforced protocol breaks, packet inspection, and schema validation.

3. Zero Trust Security & ICAM
• User Pillar: Native Security Assertion Markup Language (SAML) 2.0 / (OpenID Connect (OIDC)) federation with DoW E-ICAM; secure guest-user gating via transient passcodes.

• Data Pillar: FIPS 140-3 validated cryptographic modules (transit and rest); native inline Data Loss Prevention (DLP) to scan, block, or alert on sensitive data.

Personally Identifiable Information (PII), Protected Health Information, Controlled Unclassified Information (CUI); support for security classification metadata tags.

• Infrastructure Pillar: Development, Security, and Operations-aligned Software Development Lifecycle with verifiable machine-readable Software Bill of Materials (SBOM) (CycloneDX/ Software Package Data Exchange).

• Visibility Pillar: Log exporting in structured JavaScript Object Notation (JSON) or Common Event Format (CEF) format to central DoW Security Information and Event Management (SIEM) platforms.

4. High-Performance Transport
• Protocol Optimization: User Datagram Protocol (UDP) based acceleration, optimized TCP, compression, and automated checkpoint restart/resume.

• Scale: Reliable, high-speed transfer of single files ranging from 100 GB to multiple Terabytes.

• Resiliency: Guaranteed delivery and integrity over high-latency (>500ms) and high-packet-loss (>10%) networks.

5. Data Validation & Inspection
• Format Processing: Native parsing/validation of structured (JSON, Comma-Separated Values, Parquet), unstructured (Portable Document Format, Office documents), and geospatial imagery (National Imagery Transmission Format, Geographic Tagged Image File Format).

• Sanitization: Archive expansion, nested-content inspection, automated malware scanning, and Content Disarm and Reconstruction (CDR) integrations.

6. Disconnected Denied, Degraded, Intermittent, and Limited-Bandwidth (DDIL) Operations
• Local Resiliency: 100% functional local queuing, routing, credential caching, and local audit logging during extended Wide Area Network (WAN) outages.

• Offline Licensing: No external "phone-home" or cloud licensing dependencies; must support air-gapped license management.

• Reconciliation: Automated queue synchronization and audit log merging upon network reconnection.

4. Requested Information

Respondents should provide a concise response addressing the following areas:

A. System Architecture & Deployment Flexibility Describe your core product offering, its assessed Technology Readiness Level (with supporting operational deployment history), and how the architecture deploys across diverse DoW environments (Cloud, On-Premises, and Tactical Edge).

· Please explicitly identify minimum compute/memory requirements, any mandatory dependencies on proprietary hardware or vendor-hosted cloud infrastructure, and what features require third-party software versus native capabilities.

· Please clarify the architectural openness of the proposed solution. Specifically, is the product designed as a proprietary, single-vendor ecosystem optimized primarily for your own product suite, or does it operate as an open-ecosystem platform with robust, fully documented APIs that support seamless integration with third-party and legacy DoW technologies?

B. High-Performance Transport & DDIL Resiliency Detail your solution’s performance limits and transport optimization techniques (e.g., UDP-based acceleration, checkpoint restart/resume) when transferring very large files (100GB to Terabytes).

· Explain how the transport engine maintains data integrity and bandwidth efficiency over degraded, high-latency, and high-packet-loss communication links.

C. Zero Trust Security & Cross-Domain Integration Explain how your solution aligns with DoW Zero Trust requirements, specifically detailing native support for DoW E-ICAM federation standards (SAML 2.0/OIDC), inline Data Loss Prevention (DLP) scanning, and malware/Content Disarm and Reconstruction (CDR) capabilities.

· Briefly describe your solution's role and operational experience within a certified Cross-Domain Solution or guard architecture.

D. Disconnected Identity & Edge Operations Describe the system's operational and licensing behavior when completely disconnected from external WAN networks, cloud license hosts, or enterprise identity services.

· Detail how the system handles locally cached credentials, user authorization, local queuing, and audit logging during an outage, and how it synchronizes and reconciles data upon reconnection.

E. Cost ROM, Licensing Models & Deployment Schedule Provide a non-binding Rough Order of Magnitude (ROM) for a representative deployment consisting of 5 strategic hubs and up to 500 tactical edge instances.

· Separately identify software subscription/licensing costs, maintenance, and training. Clearly define your primary licensing models (e.g., enterprise, per-user, or capacity-based) and outline an estimated timeline from initial integration to full-scale fielding.

F. OTA Statutory Eligibility Describe if you are able to participate in an OTA. Please identify if your company qualifies as a small business or a Nontraditional Defense Contractor (NDC) —defined as an entity with no Cost Accounting Standards-covered DoW contracts in the preceding year per 10 U.S.C. 3014—or if you are a traditional defense contractor intending to partner with an NDC, small business, or nonprofit research institution (briefly outlining how their role constitutes "significant participation" in key technologies or work share), or willing to participate in a one third cost share from industry partners.

RESPONSE GUIDELINES:

Interested parties are requested to respond to this RFI with a white paper. Submissions cannot exceed 20 pages, single spaced, 11-point type with at least one-inch margins on 8 1/2” X 11” page size (excluding a cover page, table of contents, and appendices containing product data sheets or architecture diagrams). The response should not exceed a 5 MB e-mail limit for all items associated with the RFI response. Responses must specifically describe the contractor’s capability to meet the requirements outlined in this RFI. Responses must follow the numbered format in Section 5 to facilitate Government review. Oral communications are not permissible. SAM.gov will be the sole repository for all information related to this RFI.

Submission Details. Responses shall include:

1. Business name and address

2. Name of company representative and their business title

3. Company Business Size and Small Business Socio-economic status (if small)

4. Unique Entity Identifier and Commercial and Government Entity Code

5. A brief description of relevant experience supporting Federal, DoW, national-security, cybersecurity, data-transfer, or cross-domain missions.

6. Up to three relevant examples of past performance or comparable deployments. For each example, identify the customer type, general scope, deployment scale, and the respondent’s role. Do not provide sensitive customer information.

7. White paper should include ROM pricing information for executing the modernization requirements described in this notice.

Companies who wish to respond to this RFI should send responses via email no later than December 10, 2026, at 4 PM eastern time to and elizabeth.a.bono.civ@mail.mil and shawn.m.dostie.civ@mail.mil.

Respondents may include a capability matrix using the following format:

Capability Area
Available Now
Available Through Integration
Planned
Not Available
Dependencies / Limitations

E-ICAM-aligned federation

CAC/ Personal Identity Verification and Public Key Infrastructure authentication

Application-native authentication and authorization

Direct identity-provider integration without authentication proxy

Authorized third-party authenticator integration

Disconnected identity and authorization operations

Deployment flexibility

Cross-domain integration

Large-file transfer

Disconnected operations

Licensing in disconnected environments

Content validation / CDR

Respondents may include a Zero Trust Compliance matrix using the following format:

Zero Trust Capability (Application & Data Layers)
Native Capability
Requires Integration
Future Roadmap
Not Supported
Notes / Dependencies (e.g., FedRAMP/IL5 Status)

User: Granular Attribute-Based Access Control for application functions

User: Identity-assertion integration with E-ICAM

User: Granular policy gates for unauthenticated guests

Application: Provision of SBOM

Data: Native, content-level DLP (PII/CUI blocking)

Data: Secure cryptographic key management (Hardware Security Module / Bring Your Own Key)

Visibility: Standardized log exports (Syslog/CEF) to DoW SIEM

INDUSTRY DISCUSSIONS:

DISA representatives may choose to meet with potential offerors and hold one-on-one discussions. Such discussions would only be intended to obtain further clarification of potential capability to meet the requirements, including any development and certification risks.

QUESTIONS:

Questions regarding this announcement shall be submitted in writing by e-mail to elizabeth.a.bono.civ@mail.mil and shawn.m.dostie.civ@mail.mil. Verbal questions will NOT be accepted. Answers to questions will be posted to SAM.gov. The Government does not guarantee that questions received after December 10, 2026, at 4 PM eastern time will be answered. The Government may, at its discretion, publish consolidated questions and answers or otherwise communicate responses to all interested parties. The Government will not reimburse companies for any costs associated with the submissions of their responses.

DISCLAIMER:

This RFI is not a Request for Proposal (RFP) and is not to be construed as a commitment by the Government to issue a solicitation or ultimately award a contract. Responses will not be considered as proposals, nor will any award be made as a result of this synopsis.

This RFI is not a solicitation, request for proposal, request for quotation, commitment by the Government, or authorization to incur costs. All information contained in the RFI is preliminary as well as subject to modification and is in no way binding on the Government. This RFI is issued solely for market research, inforSmation, and planning purposes in support of potential prototype development under 10 U.S.C. § 4022. The Government does not intend to pay for information received in response to this RFI. Responders to this invitation are solely responsible for all expenses associated with responding to this RFI. This RFI will be the basis for collecting information on capabilities available. This RFI is issued solely for information and planning purposes. Proprietary information and trade secrets, if there are any, must be clearly marked on all materials. All information received in this RFI that is marked “Proprietary” will be handled accordingly. Please be advised that all submissions become Government property and will not be returned nor will receipt be confirmed. Responses to this RFI are not offers and cannot be accepted by the Government to form a binding contract.

Page | 1

File details come from the government source that posted it. Updated .