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
I do not think the ruling is that wrong altho I think the motivation given is not a very good one.

The first issue here is that two weeks are ample time for creating a new offsite backup, and is also enough for disinfecting the laptop and restoring the sources on it.

The primary motivation for the rulign should have been that the loss was caused by neglecting the laptop and offsite backup issues.

The lesson should be that having stored a backup offsite in itself is not enough. You will have to check periodically if this backup is still indeed a workign backup, and if it can be restored. Also, virus incidents should not be neglected, and infected machines should be recovered.

This company allowed all their backups to reside on one single location for way longer then needed, and that is what has bitten them.



[ reply ]

Link to this comment: http://www.securityfocus.com/comments/columns/276/29094#29094
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
Possibility for recovery... 2004-11-23
hanzie







 

Privacy Statement
Copyright 2008, SecurityFocus