RFI QUESTIONS 36C10B25Q0203.pdf

Request for Information VA Server Enterprise Endpoint Security (VASEES)

TAC Number: VA-25-00011736

1. Introduction

This RFI is for planning purposes only and shall not be considered an Invitation for Bid, Request for Task Execution Plan, Request for Quotation or a Request for Proposal.

Additionally, there is no obligation on the part of the Government to acquire any products or services described in this RFI. Your response to this RFI will be treated only as information for the Government to consider. You will not be entitled to payment for direct or indirect costs that you incur in responding to this RFI. This request does not constitute a solicitation for proposals or the authority to enter into negotiations to award a contract. No funds have been authorized, appropriated or received for this effort. Interested parties are responsible for adequately marking proprietary, restricted or competition sensitive information contained in their response. The Government does not intend to pay for the information submitted in response to this RFI.

The North American Industry Classification System (NAICS) for this requirement is 541519.

Be advised that set-aside decisions may be made based on the information provided in response to this RFI. Responses should be as complete and informative as possible.

2. Submittal Information:

All responsible sources may submit a response in accordance with the below information.

There is a page limitation for this RFI of 15 pages. The Government will not review any other information or attachments included, that are in excess of the 15 page limit. NO MARKETING MATERIALS ARE ALLOWED AS PART OF THIS RFI. Generic capability statements will not be accepted or reviewed. Your response must address capabilities specific to the services required in the attached PWS and must include the following:

a. Interested Vendors shall at a minimum, provide the following information in the initial paragraph of the submission:

Name of Company:

Address:

Point of Contact:

36C10B25Q0203

Phone Number:

Email Address:

Company Business Size & Status:

NAICS code(s)

Socioeconomic Data

Unique Entity Identifier (UEI):

Existing Contractual Vehicles (GWAC, FSS or MAC):

b. Provide a summary of your capability to meet the requirements contained within the draft PWS. In addition, please provide a response to the following:

1. In detail, describe the steps or additional components to the proposed solution would need to expand from the base requirement of 75,000 devices to 100,000, 250,000, 500,000, and 750,000 devices. Please explain hardware changes, staff changes, software deployments/distributions, etc that would be required to complete this growth effort and estimated timelines for each.

2. Provide in detail the ability to integrate with other security vendors and respond to cybersecurity threats within a large enterprise environment using data and/or providing threat data generated by the proposed solution from and to other technologies and vendors.

3. Provide details on the proposed solution to run in a “mixed device state” with multiple vendors running specific functions of endpoint protection on a managed device. (Example, Anti-virus and host firewall from a 3rd party vendor, and device control from this solution.)

4. Explain in detail the staffing plan necessary to support operations as outlined within but not limited to the PWS sections 5.1, 5.4, 5.5, 5.8, and

5.9 showing capacity to support 24x7x365 operations and Appendix A – VASEES Service Level Agreements.

5. Provide response to requirements within Appendix B, VASEES Solution

Requirements. Please mark whether your solution capability can/cannot meet the General requirements. In addition, please provide a response outlining gaps or deltas comparing all checked applicable OS versions that clearly describe how this requirement is met based on the solution used for the response and which vendor technology is used if the solution includes multiple. Please note that this document will not be included in the page count.

6. Detail your company’s capabilities and experience supporting federal agencies in providing a Software as a Service (SaaS) product, and how your SaaS product can satisfy the requirements listed in the PWS. Include examples of federal experience implementing your SaaS product (specific examples or references provided must include the agency, point of contact, dollar value, and contract number).

7. Please describe your company’s willingness and ability to adopt and incorporate customer feedback in the product roadmap of your proposed SaaS product.

8. Please describe your pricing model to include the threshold for named user subscriptions vs. an enterprise/site subscription. Is your pricing model driven by total users, concurrent users, transaction-based, number of records, etc? Are any additional services needed outside of the subscription model (e.g., configuration to meet functional requirements, data storage, data migration, additional features)? If so, please provide the items and proposed price for these additional services.

9. Please provide separate Rough Orders of Magnitude (ROMs) for the

SaaS product in accordance with PWS Paragraph 3.0, 5.0-5.10, and Appendix B – EDR_EPP Reqs. Please include SKU’s and brief product descriptions as well as licensing details specific to the SKU’s from PWS paragraph 5.9.

10. Is your company’s SaaS product FedRAMP Authorized (High)? If not, are you willing and ready to begin the processes and documentation required to become FedRAMP Authorized within 30 days of award? Based on the ROM, confirm if all the components of the intended solution are inclusive of the High rating for FedRAMP.

11. Following guidance from the Federal CIO, VA will utilize existing JAB ATO or agency ATO issued by another agency as a starting point for FedRAMP requirements. If neither of those exist, VA will sponsor FedRAMP ATO.

VA will be using the FedRAMP baselines as a starting point, since they are specifically tailored for cloud services. Does your company’s SaaS product have an ATO from any federal agency?

12. Detail your company’s support Service Level Agreements (SLAs) for all tiers of service.

13. What was your uptime rate during the past 12 months?

14. Describe your standard release and patch cycle.

15. Has the draft PWS provided sufficient detail to describe the technical/functional requirements that encompass the software development and production operations support services to be performed under this effort.

______ YES _______ NO (if No, answer the next question)

16. If “NO”, please provide your technical comments/recommendations on elements of the draft PWS that may contribute to a more accurate proposal submission and efficient, cost effective effort.

Responses are due no later than 12:00PM EST on Thursday, March 20, 2025, via email to Dana Seeler, Contract Specialist at dana.seeler@va.gov and Jason King, Contracting Officer at jason.king6@va.gov. Please note “36C10B25Q0203 VASEES” in the subject line of your response. Mark your response as “Proprietary Information” if the information is considered business sensitive. The email file size shall not exceed 5 MB.