Secure by Design Pledge
Fortra has signed CISA's Secure by Design Pledge because we believe that software should be safe to use on day one. That is why we are committed to developing software that is built securely, with secure components, and comes with secure defaults. This process is both forward looking for new development and backward facing, improving code and default configurations in the software our customers have used and trusted for years.
Focus Areas and Goals
The Secure by Design Pledge has seven focus areas and target goals:
Quarterly Report
For Q2 of 2025, Fortra will be seeking to close the gaps found during our Q4 survey and Q1 follow up activities to validate our Pledge Focus survey results. We discovered good coverage for the MFA focus and those products lacking MFA have other mitigating controls in place. Some may benefit from improvements to integrations with customer identity providers and those are being investigated. For the purposes of the Secure by Design Pledge, we are moving this goal area into “Maintain” status
That leaves us to focus on eliminating default passwords and ensuring that we include logging and other mechanisms to provide evidence of intrusions. There were fewer instances of these weaknesses in the products surveyed, so in Q2 we will focus on getting remediations into the backlogs and future releases.
At a Glance
Goal Area | Fortra's Updates at a Glance | Status |
| Multi-Factor Authentication (MFA) | Conducted an audit in Q4 2024 to identify products missing MFA. | Maintain |
| Default Passwords | Conducted an audit in Q4 2024 to identify products with default passwords. | Remediation Planning |
| Evidence of Intrusions | Conducted an audit in Q4 2024 to find software missing desired logging. | Remediation Planning |
| Reducing Entire Class of Vulnerability | Defining heatmap and prioritization. | In Progress |
| Security Patches | Conducting telemetry audit and developing plan of attack. | In Progress |
| Vulnerability Disclosure Policy | Policy was published December 2023. | Complete |
| Common Vulnerabilities and Exposures (CVE) | Fortra published 14 CVEs in 2024. | Maintain |
When we reviewed our survey answers with teams, we found a slight increase in products that used it (+2%), a modest decrease in those that don’t (-10%) and a modest increase where MFA was “N/A” (+10%), meaning we had respondents conservatively answering “False” when MFA was not applicable for their products (e.g., no interactive logins). For the remaining 22% of products that are not using MFA, there is not a strong use case for this control based on the context of the access. For instance, products running on IBM i may defer this control to the OS or integrate with Powertech Multi-Factor Authentication. We are considering this control in Maintenance status now.
Default Passwords
The use of default passwords in Fortra products is rare base on our survey, however, we did find instances where the practice was used (18% use default passwords). Several of those products now have backlog items to mitigate or remediate the weakness which will find their way into a future release. Throughout Q2 we will track the teams’ progress in replacing default passwords with safer options and ensure this pattern is not used in new development.
Evidence of Intrusions
Like default passwords, most of Fortra’s products provide logging to help defenders detect evidence of intrusion affecting the software. 70% of products provided evidence of intrusion while only 12% did not. We will assess the logging gaps in those products and determine how we can provide customers with the information they need to respond quickly to incidents in their environments. Logging strategies and configurations are being evaluated and updates are planned to close the gap.
Reducing Entire Class of Vulnerability
The current approach to this goal is to leverage existing patterns and frameworks that have built in mitigations against attacks such as XSS, and SQLi. Fortra also has an inner-source project underway to standard approaches to common problems and centralize good security hygiene. Benchmarking this goal is a challenge and we are testing ways we can scan or discover vulnerability hot-spots that could benefit from targeted approaches.
For customers in our cloud-hosted and SaaS environments such as Fortra Platform, Fortra VM, and Tripwire ExpertOps customers never have to worry about being on the latest version. Fortra deploys updates as soon as we are able to deploy them. The Platform even allows for real-time updates of the Fortra Agent.
With customers in air-gapped and isolated on-premises environments, ensuring they have the latest software can be a challenge. Fortra is committed to providing timely communication to our on-premises customers when updates are available and we are working to determine which products have the highest barriers to upgrades.
In December of 2023, Fortra became a CVE Numbering Authority (CNA) and as part of that effort published its vulnerability disclosure policy on Fortra.com. Fortra welcomes external researchers to contact us with any security issues they find in our products and our research teams are committed to responsible disclosure to better safeguard our digital world.
As a CNA, Fortra now publishes their own CVEs when discovered. In 2024 Fortra published 14 CVEs for its own products and two for an external vendor. Fortra-published CVEs can be found in the Security Advisories area on Fortra.com. We will continue to provide transparency and fixes so our customers can effectively manage their risk posture.