|By Shelly Palmer||
|April 13, 2014 08:58 PM EDT||
What seemed like good news has quickly turned bad, if not downright terrifying. Saturday’s disclosure by Web security firm CloudFlare that at least one worst-case scenario related to the Heartbleed vulnerability might be impossible has been proven wrong by independent researchers in less than a day. Two independent tests have proven CloudFlare’s initial findings wrong, which means that certain nasty possibilities involving the bug are indeed possible. The firm had determined that using the Heartbleed vulnerability to steal private server keys appeared impossible, which looked to be the first good news since the bug was revealed earlier this week. CloudFlare had set up a public challenge seeking outside validation of the results of its own testing. The challenge lasted until late Friday afternoon Pacific Time. The first to pull out an SSL private key, according to CloudFlare, was Fedor Indutny, a Russian security researcher.
In a recent research, analyst firm IDC found that the average cost of a critical application failure is $500,000 to $1 million per hour and the average total cost of unplanned application downtime is $1.25 billion to $2.5 billion per year for Fortune 1000 companies. In addition to the findings on the cost of the downtime, the research also highlighted best practices for development, testing, application support, infrastructure, and operations teams.
Jan. 16, 2017 01:00 PM EST Reads: 3,594
Updating DevOps to the latest production data slows down your development cycle. Probably it is due to slow, inefficient conventional storage and associated copy data management practices. In his session at @DevOpsSummit at 20th Cloud Expo, Dhiraj Sehgal, in Product and Solution at Tintri, will talk about DevOps and cloud-focused storage to update hundreds of child VMs (different flavors) with updates from a master VM in minutes, saving hours or even days in each development cycle. He will also...
Jan. 16, 2017 01:00 PM EST Reads: 1,002
When you focus on a journey from up-close, you look at your own technical and cultural history and how you changed it for the benefit of the customer. This was our starting point: too many integration issues, 13 SWP days and very long cycles. It was evident that in this fast-paced industry we could no longer afford this reality. We needed something that would take us beyond reducing the development lifecycles, CI and Agile methodologies. We made a fundamental difference, even changed our culture...
Jan. 16, 2017 12:45 PM EST Reads: 254
Jan. 16, 2017 12:30 PM EST Reads: 785
Jan. 16, 2017 12:30 PM EST Reads: 5,419
Jan. 16, 2017 12:30 PM EST Reads: 4,985
Jan. 16, 2017 12:30 PM EST Reads: 3,336
Jan. 16, 2017 12:00 PM EST Reads: 2,381
Jan. 16, 2017 12:00 PM EST Reads: 1,340
Jan. 16, 2017 11:30 AM EST Reads: 5,660
Jan. 16, 2017 11:30 AM EST Reads: 1,842
Jan. 16, 2017 11:30 AM EST Reads: 4,120
Jan. 16, 2017 11:27 AM EST Reads: 201
Jan. 16, 2017 11:15 AM EST Reads: 1,708
Jan. 16, 2017 10:15 AM EST Reads: 7,629