Reducing software risk is at the top of every CIOs’ agenda this year -- just like it was last year, and the year before that. And like the old saying goes, “Those who cannot remember the past are condemned to repeat it.” If CIOs are trying to reduce their software risk the same way they did in 2013, they’re setting themselves up for another year of crashes, outages, and angry customers.
So to help you remember the sordid past you don’t want to repeat, we compiled an infographic of the costliest software disasters in 2013. Hopefully seeing all these catastrophes and their associated costs in one place will help you prioritize fixing the riskiest applications in your portfolio. If not, it will at least be a reminder of how much a relatively minor glitch can cost an organization.
Software Risk in The News
Since these glitches enabled serious security breaches that affected both organizations and consumers, PC Mag’s SecurityWatch featured this infographic in a piece they did about the future of security in 2014. And not one to be left out of the conversation, our founder and CEO Vincent Delaroche penned a post for Wired’s Innovation Insights about the true costs of these software failures.
Lastly, since we’re specialists in finding the riskiest glitches buried deep in complex software, we’ve assembled a Software Risk Management Kit to help you uncover and defuse time-bombs in your software. Make sure you register to get a kit for yourself and keep your application portfolio robust, resilient, secure -- and most importantly -- far away from brand-killing negative press.
Erik Oltmans, an Associate Partner from EY, Netherlands, spoke at the Software Intelligence Forum on how the consulting behemoth uses Software Intelligence in its Transaction Advisory services.
Erik describes the changing landscape of M & A. Besides the financial and commercial aspects, PE firms now equally value technical assessments, especially for targets with significant software assets. He goes on to detail how CAST Highlight makes these assessments possible with limited access to the targetâ€™s systems, customized quality metrics, and liability implications of open source components - all three that are critical for an M&A due diligence.