TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Think of worst case scenarios: fires, floods, earthquakes. How far is the nearest self-storage that's reasonably safe from that event? Copy the data yourself, verify the copy, drive it over there, and Bob's your uncle. If it's too far to conveniently drive, then ship it.
Remember, you only have to protect against an event that could destroy both buildings on the same day. For example, it doesn't matter if the offsite storage unit burns down, as long as your company's building is too far to be unaffected by that fire.
Meteors? Any meteor big enough to take out both buildings will probably send you to offsite storage as well, if you get my drift.
-----Original Message-----
From: McLauchlan, Kevin
Sent: Friday, October 04, 2013 4:17 PM
To: Gene Kim-Eng; Dan Goldstein
Cc: TECHWR-L (techwr-l -at- lists -dot- techwr-l -dot- com)
Subject: RE: Adobe was hacked
You, or the person(s) sending and receiving the traffic already own it once, and the routine archiving is being done with tax dollars, so you own it again.
Charging to let you see it would be double taxation at least.
On the other hand, how do you know that what they've got, attributed to you, is legitimately you/yours?
And that flag on it.... what does that mean? :-)
Similarly, in a commercial cloud-archive situation, I'd want to be able to verify occasionally that what I'm paying the vendor to archive is what (if anything) is being archived. I mean, BEFORE the frantic day when I need to urgently retrieve something.
Also, if I'm a contractor and entrust both my projects that I'm working on, and customers' source info, to a cloud, and the vendor :
- loses important material
- exposes sensitive material
do I want some boilerplate in my contract to keep the liability where it belongs?
And then, tying the concepts together, what if the NSA gets hacked and allows your data to be exposed?
Is there liability?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.
