18-0068_BNjust_pt2_Redacted.pdf
PDF 191 KB Posted
- Attached to
- Elastic X Pack Software Federal contract opportunity
- Solicitation number
- N64267-18-T-0068
About this file
BN Justification part 2
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| 18-0068bn_Redacted_pt_1.pdf | ||
| 1449_N6426718T0068_redact.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
1. The additional plugins from Elastic are required because we currently are already using the core products from the company for our initial roll-out for enterprise logging of our systems. To become fully information assurance (IA) compliant, we will need to provide token authentication and additional security measures that the X-Pack package contains. In order for CCRN to do this function, we would need our senior Linux administrator to first research and learn the authentication stack for Elasticsearch, Logstash, and Kibana which will take a more than 6 months. Afterwards, we would then need software developers to implement the requirement from our senior Linux administrator to ensure the application can talk with our identity manager to authenticate users securely. With testing and deployment, this can be another year of several developers. Total cost of trying to run a proprietary implementation of an authentication stack would be 3 man years /year X 3) which is .
was looked at as a different product to solve our enterprise logging requirement. This brand is not acceptable because the system is cost-prohibitive to our operations. Splunk charges on a per gigabyte basis and with logs from all of our systems would not be able to afford to pay the monthly cost associated to this product. Also, Splunk does not integrate with our current Elastic core stack and is its own logging solution. Our system administrators would need to be trained on a brand new system which includes understanding the new graphical user interface (GUI), creating new dashboards and reports, and fixing current scripts to ingest the data correctly into Splunk instead of
Elastic. The cost of getting our administrators trained up on a brand new logging system would be
. The additional cost to creating new dashboards and fixing current scripts would be to add
1 full man year to a developer to test and deploy ingesting our current logs into the new system. We would then need the developer 25% time for maintenance of the system.
File details come from the government source that posted it.