25RB033 RFI MicroFocus Fortify 2025.xlsx

XLSX spreadsheet 27 KB Posted

Attached to
FA830725RB033 MicroFocus Fortify FY25 RFI
Solicitation number
FA830725RB033_Microfocus_Fortify_FY25_RFI
Issued by

About this file

This RFI seeks information about MicroFocus Fortify software licenses and potential alternative solutions for the Department of the Air Force Materiel Command's Platform One (P1) Party Bus Value Stream. The RFI focuses on application security testing capabilities, specifically Static Application Security Testing (SAST) and Dynamic Application Security Testing (DAST) functionality that can scan mission applications during runtime and integrate with existing DevSecOps toolchains.

Vendors must provide details on alternative licensing models, including enterprise, cloud-managed, or open-source editions, along with pricing information for transition costs, training, and various subscription terms (monthly, trial, annual). Key technical requirements include ability to perform SAST and DAST, alignment with NIST/CWE/OWASP Top 10/DISA STIG standards, containerized deployment capability, SSO integration, and support for multiple programming languages including Java, JavaScript, Python, .NET, C++, Ruby, Golang, and PHP. Responses should be submitted to specified Air Force personnel using the provided Excel spreadsheet template, which is also posted on NASA SEWP under RFI number 337337.

View the file

Other files

File Type Posted
RFI_MicroFocus Fortify_v2.xlsx XLSX spreadsheet

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

RFI Excel version of Word sheet

MicroFocus Fortify harnesses the power of application security data across the software development life-cycle (SDLC) by measuring and improving the efficiency, accuracy, and value to an organization. MicroFocus Fortify helps to provide an accurate picture and scope of the application security posture across the enterprise.

MicroFocus Fortify delivers the advanced correlation, analytics, applications protection and data security Platform One (P1) requires to protect its software ecosystem from sophisticated cyber threats. Fortify supplies both Static Application Security Testing (SAST) and Dynamic Application Security Testing (DAST) to meet P1's rigorous security requirements.

MicroFocus Fortify (MFF) is a critical component of the Party Bus Value Stream's support to its customers security and software development. MFF scans the mission applications at run time during operation (i.e. as the application us being used) and highlights poorly written/unsecure code providing developer teams with suggestions for improvements/corrections for the unsecure code or highlighted security concern. MFF also links into other pipelines such as SD Elements. MFF is integrated into the Party Bus software development tool-chain, granting the developers the ability to find and fix security flaws at every stage of the Development Security Operations (DevSecOps) process in real time.

Alternative License Types:
1What alternate licensing models or solutions do you offer for MicroFocus Fortify?

(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:
1For 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:
1Are 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.)

Requirements Capability Sheet

MicroFocus Fortify ALTERNATIVE:[PUT NAME HERE]
Instructions:Please select Y/NPlease select Y if Yes, N if no plans, or N/A if ready on day 1Please insert # of days from award to build capability or a date if knownPlease insert comments, questions, or concerns for each requirement if needed
Requirement:Ready on Day 1Future CapabilityEstimated date of CapabilityComments
1Please enter Yes or No requirements that a possible alternative software vendor MUST meet.This Column is meant for the vendor to have space to answer the questions in more detail.
Must be able to perform Static Application Security Testing (SAST)
Must have rules that align with NIST, CWE, OWASP Top 10, and DISA STIG
Must be able to run scans in a containerized environment
If there is a server component for analysis, this must also run within a kubernetes stack, using helm charts for deployment
Must have functionality for whitelisting/adjudicating, and providing justification for findings
Must be able to perform taint analysis,
Must be able to run within CI workflows
Threshold for true positive rate as determined by https://github.com/OWASP-Benchmark/BenchmarkJava
Must have integrations with SDElements or other threat analysis tools
Should be able to show a call-graph deduced during taint analysis etc for analyzing source of code security findings
IF there is a server component for analysis/vulnerability management it must integrate into SSO using OIDC or SAML
Code Analysis must be performed in a self hosted environment. Findings/code cannot be sent to a SaaS solution
Server component Must have API for running programmatic calls to retrieve findings, create projects, and potentially manage findings
Must be able to scan the following languages:

- Java

- Javascript/TypeScript/React

- Python

- Dotnet/C#

- C++

- Ruby

- Golang

- PHP

Must provide recommendations for remediation
Must allow for tailoring of rulesets and vulnerability levels per organization standards and risk matrices
Must Detect CWE (Common Weakness Enumeration) vulnerabilities
Must Provide detailed compliance reports for audits and governance
Supports custom security policies for industry-specific standards
Must be able to Detect vulnerabilities across both source code and compiled binaries

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