FA8307_RFI_Elastic_Alternatives.docx
DOCX document 21 KB Posted
- Attached to
- FA8307_RFI_Elastic_Alternatives
- Solicitation number
- FA8307_RFI_Elastic_Alternatives
About this file
This document is a Request for Information (RFI) issued by the Department of the Air Force Materiel Command Lifecycle Management Center Joint Base San Antonio (AFLCMC JBSA) regarding alternative solutions to Elastic's SIEM, Filebeat, and Kibana software.
The RFI requests information on alternative licensing models, pricing, and features of solutions that can meet the government's requirements for log aggregation, real-time monitoring, incident response, compliance, and multi-environment visibility. Specifically, the RFI asks for details on enterprise, cloud-managed, and open-source/community edition options, including feature comparisons, scalability, support, and how each alternative meets the stated needs. The RFI also requests pricing information such as transition and training costs, as well as any additional features or value-added services associated with the different licensing tiers. No award will be made under this RFI; it is solely for information gathering purposes.
View the file
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
***Please submit all responses using the attached RFI Template to geoffrey.bender.1@us.af.mil, elijah.simmons.4@us.af.mil, and julie.mckillip.ctr@us.af.mil.*** Current Software: Elastic Requirement:
Elastic serves as a log aggregation and security monitoring platform that enables the P1 Value Streams to perform continuous monitoring of the cloud environment for P1 applications. By consolidating log data from various cloud resources, applications, and infrastructure components into a single, accessible platform, Elastic allows teams to:
Elastic consolidates logs from distributed cloud systems into a centralized view, enabling efficient monitoring, analysis, and incident response. Its real-time analytics support threat detection by identifying indicators of compromise, unusual access patterns, and potential vulnerabilities. Elastic’s search and filtering allow security analysts to rapidly investigate incidents, while its audit trail capabilities help meet compliance and forensic requirements. Additionally, machine learning features automate the detection of unusual patterns, enhancing proactive threat identification and reducing manual analysis.
Our organization leverages the Elastic SIEM, Filebeat, and Kibana to accomplish its mission.
P1 Elastic Use Cases:
· To aggregate and centralize logs from various applications and services across our environment, providing a single source of truth for log data that aids in troubleshooting and system analysis.
· To support real-time monitoring and alerting on key system metrics and logs, allowing teams to quickly detect anomalies or performance issues that could impact application availability or user experience.
· To enable detailed log analysis and correlation for incident response, providing the ability to trace issues across services and identify root causes through comprehensive log searching and filtering capabilities.
· To retain logs for compliance and audit purposes, ensuring that all critical log data is archived and easily accessible to meet regulatory requirements and support forensic investigations.
· To dynamically scale log storage and processing as data volumes grow, ensuring that our logging infrastructure remains responsive and capable of handling increased load without compromising performance.
· To provide role-based access control (RBAC) for log data, allowing different teams to access only the logs relevant to their work, enhancing security and minimizing unnecessary data exposure.
· For the ability to visualize and analyze data through customizable dashboards, enabling teams to monitor system health, track trends over time, and gain insights into operational efficiency and resource usage.
· To support multi-environment visibility, ensuring that logs from development, staging, and production environments are managed and accessible from a unified interface, which streamlines troubleshooting and analysis across all stages of the application lifecycle.
Please provide information on the following:
Alternative License Types:
1. What other licensing models or solutions do you offer for Elastic?
· Please provide details on available options, such as enterprise, cloud-managed, or open-source/community editions. For each licensing option/solution set, please provide how it differs from the listed license.
2. For each licensing option/solution set, please provide how it is similar from the listed license.
· Specify any feature restrictions, scalability limitations, or support differences among the licenses (e.g., data retention, search query limits, or alerting capabilities).
3. For each licensing option/solution set, please provide how it meets the above requirements.
· Identify core features or capabilities that are shared across all options, such as log aggregation, visualization tools, and monitoring capabilities, regardless of the license type.
4. For each licensing option/solution set, clarify how it meets the above requirements for our logging and monitoring needs.
· Please highlight specific ways in which each licensing tier can address our operational, security, and compliance needs, particularly in areas like multi-environment visibility, role-based access control, and support for compliance auditing.
Pricing Information:
1. For each license, please provide estimated transition and training costs and schedule for both transitioning to and from your proposed solution.
· Include details on onboarding costs, consulting, or configuration support required for a smooth transition. Specify any training options available, such as workshops, online courses, or documentation resources, and their associated costs.
2. For each license, please provide any price plans associated such as monthly, trial, annual.
· Indicate if discounts are offered for longer-term contracts or high-volume deployments. For cloud-managed options, provide cost breakdowns for storage, query processing, and other usage-based charges.
Other Considerations:
1. Are there any additional features or benefits associated with the different licenses that we should consider?
· For example, are advanced analytics, machine learning-based anomaly detection, or pre-built integrations with other monitoring tools included at higher licensing tiers? - Clarify any value-added services, such as dedicated account support, proactive health checks, or best-practice workshops, that come with certain licenses.
2. Is your company willing to enter into contracts with a base year with up to four one-year options? If not, how many years is your company willing to agree to?
· For longer-term contracts, specify any guarantees on pricing, renewal terms, or opportunities to adjust the contract scope to accommodate potential changes in our data volume or monitoring requirements.
We are eager to find a solution that will best support our needs and ensure continued productivity.
Please Note: No award will be made under this RFI. Only a warranted Contracting Officer can obligate on behalf of the United States Government and that will be executed through an official request for quote (RFQ). The Government reserves the right to cancel this RFI. In the event the Government cancels this RFI, the Government has no obligation to pursue procurement or to reimburse an Offeror for any costs.
File details come from the government source that posted it. Updated .