Fortify Software

Fortify
former Independent Software Vendor
Industry Computer software
Genre Software Security Assurance
Founded 2003
Founder Ted Schlein of Kleiner, Perkins, Caufield & Byers, Mike Armistead, Brian Chess, Arthur Do, Roger Thornton
Headquarters San Mateo, California, United States
Key people
 John M. Jack (former CEO), Jacob West(head of Security Research Group), Brian Chess(former Chief Scientist), Arthur Do (former Chief Architect)
Owner Hewlett Packard Company
Website

HP Software Security web page and

HP Fortify Software Security Center Server

Fortify Software, known now as Fortify, was a California-based software security vendor, founded in 2003 and acquired by Hewlett-Packard in 2010.[1] Fortify is now part of HP Enterprise Security Products in the HP Software business, providing application security products and services for enterprise customers to assess, assure and protect enterprise software and applications from security vulnerabilities.[2][3]

On September 7, 2016, HPE CEO Meg Whitman announced that the software assets of Hewlett Packard Enterprise, including Fortify, would be spun out and then merged with Micro Focus to create an independent company of which HP Enterprise shareholders would retain majority ownership. Micro Focus CEO Kevin Loosemore called the transaction "entirely consistent with our established acquisition strategy and our focus on efficient management of mature infrastructure products" and indicated that Micro Focus intended to "bring the core earnings margin for the mature assets in the deal - about 80 percent of the total - from 21 percent today to Micro Focus's existing 46 percent level within three years."[4]


Technical advisory board

Fortify's technical advisory board was composed of Avi Rubin, Bill Joy, David A. Wagner, Fred Schneider, Gary McGraw, Greg Morrisett, Li Gong, Marcus Ranum, Matt Bishop, William Pugh and John Viega.

Security research

Fortify created a security research group that maintained the Java Open Review project[5] and the Vulncat taxonomy of security vulnerabilities in addition to the security rules for Fortify's analysis software.[6] Members of the group wrote the book, Secure Coding with Static Analysis, and published research, including JavaScript Hijacking,[7] Attacking the build: Cross build Injection,[8] Watch what you write: Preventing Cross-site scripting by observing program output[9] and Dynamic Taint Propagation: Finding Vulnerabilities Without Attacking.[10]

Offerings

Fortify offerings included Static Application Security Testing[11] and Dynamic Application Security Testing[12] products, as well as products and services to support Software Security Assurance, or repeatable and auditable secure behaviors, over the course of a software application's life cycle.[13]

In February 2011, Fortify also announced Fortify OnDemand, a static and dynamic application testing service.[14]

See also

References

  1. ↑ HP Press Release: "HP Completes Acquisition of Fortify Software, Accelerating Security Across the Application Life Cycle" September 22, 2010.
  2. ↑ Software Searches for Security Flaws (English), PCWorld.com, April 5, 2004
  3. ↑ A New Approach to Fortify Your Software , Internetnews.com, April 5, 2004
  4. ↑ Sandle, Paul; Baker, Liana B. (2016-09-08). "HP Enterprise strikes $8.8 billion deal with Micro Focus for software assets". Reuters. Retrieved 2016-09-13.
  5. ↑ "Quality and Solutions for Open source Community" Archived March 4, 2016, at the Wayback Machine.
  6. ↑ "Software security errors" Archived November 27, 2012, at the Wayback Machine.
  7. ↑ "JavaScript Hijacking" Archived June 23, 2015, at the Wayback Machine.
  8. ↑ "Attacking the Build through Cross-Build Injection"
  9. ↑ "Watch What You Write: Preventing Cross-Site Scripting by Observing Program Output"
  10. ↑ "Dynamic taint propagation"
  11. ↑ Fortify SCA
  12. ↑ Fortify Runtime
  13. ↑ HP Fortify Governance
  14. ↑ SD Times, “HP builds up its Security-as-a-Service .” February 15, 2011.
This article is issued from Wikipedia - version of the 11/18/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.