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.
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?
-----Original Message-----
From: Gene Kim-Eng
Sent: October-04-13 3:32 PM
To: Dan Goldstein
Cc: TECHWR-L (techwr-l -at- lists -dot- techwr-l -dot- com)
Subject: Re: Adobe was hacked
Depends on whether its archival or active. For archival that you upgrade every 90 days or so, I'd choose encrypted media, either shipped or carried by bonded messenger, depending on volume, distance and sensitivity.
For active data, I'd do a first ship as above and then use data transmission for incremental updates (also encrypted).
Saw a news article recently that said the NSA routinely archives all encrypted online traffic. No political statement intended, but someone in the government is overlooking a potential revenue stream from offering people accounts that would allow them to access their own stuff for a fee. Because once my data is in the NSA database, I think I could probably depend on them to not accidentally overwrite it with a pirated copy of "Blade Runner" (that actually happened to someone I know, btw, hence my rather low opinion of offsite clouds).
Gene Kim-Eng
On 10/4/2013 10:51 AM, Dan Goldstein wrote:
> If an offsite vendor maintains encrypted backups of your onsite data, would you ship it to them on physical media? Or would you rely on them for data transmission? I prefer the former: You burn it, you ship it, they sign for receipt, and it's easy to maintain physical media in a vault.
The information contained in this electronic mail transmission
may be privileged and confidential, and therefore, protected
from disclosure. If you have received this communication in
error, please notify us immediately by replying to this
message and deleting it from your computer without copying
or disclosing it.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.
