Search: Home Bugtraq Vulnerabilities Mailing Lists Jobs Tools Vista
The Worst Case Scenario
Mark Rasch, 2004-11-15

The fine print in an insurance policy becomes an issue when a bizarre chain of IT disasters leaves a company without a single copy of the source code to its flagship product.

Comments Mode:
The Worst Case Scenario 2004-11-15
Anonymous
The Worst Case Scenario 2004-11-16
Anonymous
The Worst Case Scenario 2004-11-16
Anonymous (1 replies)
WORM Vs worm 2004-11-18
Nick
The Worst Case Scenario 2004-11-16
Anonymous
The Worst Case Scenario 2004-11-16
Anonymous (1 replies)
Yup... 2004-11-22
Anonymous
The Worst Case Scenario 2004-11-17
Anonymous (2 replies)
The Worst Case Scenario 2004-11-17
Anonymous
The Worst Case Scenario 2004-11-17
Anonymous
The Worst Case Scenario 2004-11-17
Anonymous
The Worst Case Scenario 2004-11-18
Anonymous
Linus quote 2004-11-19
Anonymous
human mistakes bite 2004-11-22
Anonymous (1 replies)
human mistakes bite 2004-11-24
Anonymous
I think the point is that a good backup plan is fairly obvious, yet they did not take that route. The decided a paper copy, an off site backup (on a server of some kind, it looks like), and an onsite backup (only on HDDs) was a viable plan.

Disaster recovery is the issue. It sounds like they had very little in the way of a disaster recovery plan.
A) Backups need to be on secured media as well as HDDs. Something like a CD, DVD, tape, USB thumb drive, etc.
B) Backups should come in three flavors:
i) quick restore (on site HDD)
ii) basic restore (on site (in a fireproof safe) and off site (in a fireproof safe) recent backups. These must be on some removable media that is stable (eg CD, DVD, tape, etc)
iii) archive (off site (fireproof safe) and seperated from ii)

A paper copy of source seems silly....I smell a scam.

[ reply ]

Link to this comment: http://www.securityfocus.com/comments/columns/276/29210#29210
Possibility for recovery... 2004-11-23
hanzie







 

Privacy Statement
Copyright 2007, SecurityFocus