Focus on Security



Email    print   
July 15, 2007 —  (Page 1 of 2)
First came the announcement last month that IBM would acquire Watchfire, which sells security assessment software. Then HP followed by announcing it would buy SPI Dynamics, another well-regarded software security company.

Industry pundits had been writing for some time that there would be consolidation in this market, which features companies such as Cenzic, Klocwork and Ounce Labs. Any or all of these concerns could be ripe for the picking by Microsoft or Oracle, which as of now do not offer a secure software solution to compete against IBM and HP.

These acquisitions are a signal that software tool providers acknowledge that firewalls, access control lists and other measures are not enough to stop the siege from hackers looking to exploit personal data or to simply lock up a system for the fun of it. These major companies are learning that security is something that needs to be addressed during the creation of code, not a feature to be slapped on at the end.

Preventing access only stops people from getting to your data in ways you expect; writing secure code can cover the entry points you don’t immediately think of, or even see.

IBM already had tight integration with Watchfire in its Rational development life-cycle tools, while HP will incorporate the SPI Dynamics functionality into its former Mercury testing and QA tools. That’s an excellent first step toward securing software, in addition to securing networks and servers.

The harder challenge remains: convincing the people who gather requirements, create models and write code that security is their responsibility as well. Analysts have cited an unchanging culture among developers as a roadblock to security. And vendors have said you can give developers all the tools in the world, but you can’t make them use them.

Well, their bosses can. Now that IBM and HP are providing enterprise-class tools for security assessment, it falls to the development managers and project managers to make sure security is considered at each step—requirements, modeling, code, build, test and QA. They have a harder job than the vendors, but software will always be vulnerable until they get buy-in all along the life cycle.




Pages 1 2 


Share this link: http://sdt.bz/30934
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Cigital Develops Ready-to-Use Tools for Securing the Smart Grid
Cigital Inc. announced the release of the Guide to Developing a Cyber Security and Risk Mitigation Plan Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb