Print

Print


Thank you, everyone, for the advice! I'll pass all of this along to our Systems department.

Sarah
------------------
Sarah Coates, MA, MLIS, CA
Archives
204 Edmon Low Library
Oklahoma State University
Stillwater, OK 74078
405.744.6076
[log in to unmask]



-----Original Message-----
From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of Jason Bengtson
Sent: Thursday, August 24, 2017 10:40 AM
To: [log in to unmask]
Subject: Re: [CODE4LIB] Non-networked computer advice -

My desktop support unit will be using a flash drive to deliver those. A little more trouble, but completely doable. We can manage the OS updates, and the anti-virus updates that way as well. I'm actually not as worried about updating the virus definitions super-frequently . . . besides that technology becoming obsolete, that machine should mostly be encountering legacy bugs that have long-since been identified.

Best regards,

*Jason Bengtson*


*http://www.jasonbengtson.com/ <http://www.jasonbengtson.com/>*

On Thu, Aug 24, 2017 at 10:34 AM, Kari R Smith <[log in to unmask]> wrote:

> Jason,
> How do you plan to deal with necessary software updates?
>
> Kari R. Smith
> Digital Archivist and Program Head for Born-digital Archives Institute 
> Archives and Special Collections Massachusetts Institute of Technology 
> Libraries, Cambridge, Massachusetts
> 617.253.5690   smithkr at mit.edu   http://libraries.mit.edu/archives/
> @karirene69
>
>
> -----Original Message-----
> From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of 
> Jason Bengtson
> Sent: Thursday, August 24, 2017 11:17 AM
> To: [log in to unmask]
> Subject: Re: [CODE4LIB] Non-networked computer advice - HD docking 
> Station
>
> We're setting  up a digital forensic machine for Special Collections 
> which we want quarantined from the rest of our network due to the risk 
> of viruses on older media. Our precautions have been pretty basic. The 
> machine has no wireless card, and while it has ethernet through the 
> motherboard we will have that functionality disabled by the time the 
> machine is deployed. It's also being located in a space with no 
> network drops, which, given the bulkiness of the computer, makes it 
> unlikely that anyone would even try to plug it into the network.
>
> Best regards,
>
> *Jason Bengtson*
>
>
> *http://www.jasonbengtson.com/ <http://www.jasonbengtson.com/>*
>
> On Thu, Aug 24, 2017 at 10:05 AM, Kari R Smith <[log in to unmask]> wrote:
>
> > Hi Sarah,
> > I suggest that you also ask this question to the BitCurator Users 
> > Group (Archivists using digital forensics tool and techniques for 
> > archival
> > processing) www.bitcuratorconsortium.org
> >
> > One solution I'm using at MIT Institute Archives is having a Dual 
> > Bay Hard Drive Docking Station (in my case, a Sabrent USB 2.5" and 
> > 3.5") along with two 3.0TB NAS Hard Drives.  This allows me to have 
> > a primary drive with the digital material that I'm processing on it 
> > and then the Docking Station has a Clone feature that allows me to 
> > clone that drive to a second NAS HD for back-up until processing is 
> > complete and I then move the digital packages for preservation into 
> > our
> Preservation storage area.
> >
> > I connect the Docking station to a computer that is disconnected 
> > from the Ethernet (and no WiFi) during processing.  This keeps the 
> > files separate from the computer and gives me some peace of mind 
> > that I've got redundancy.  A further step is to store the 2nd HD 
> > (copy/clone) in our Vault or other separate location to avoid 
> > location-specific disasters (water leaks, power surge, etc.)
> >
> > Thanks to Dorothy Waugh, digital archivist, at Emory Special 
> > Collections and Archives who shared this approach with me.
> >
> > Kari
> >
> > Kari R. Smith
> > Digital Archivist and Program Head for Born-digital Archives 
> > Institute Archives and Special Collections Massachusetts Institute 
> > of Technology Libraries, Cambridge, Massachusetts
> > 617.253.5690   smithkr at mit.edu   http://libraries.mit.edu/archives/
> > @karirene69
> >
> > -----Original Message-----
> > From: Code for Libraries [mailto:[log in to unmask]] On Behalf 
> > Of Scancella, John
> > Sent: Thursday, August 24, 2017 10:11 AM
> > To: [log in to unmask]
> > Subject: Re: [CODE4LIB] Non-networked computer advice
> >
> > Hi Sarah,
> >
> > Does it really need to be a completely separate network/standalone 
> > computer? The reason I ask is because it sounds like you just want a 
> > firewall setting that won't allow a computer (or groups of 
> > computers,
> i.e.
> > subnet) to not be able to access the internet. By leaving the 
> > computer attached to the network you get all the benefits of 
> > automatic updates from your central configuration management system 
> > (in the case of
> windows SCCM).
> >
> > John
> > Opinions expressed in this email are my own
> >
> > -----Original Message-----
> > From: Code for Libraries [mailto:[log in to unmask]] On Behalf 
> > Of Coates, Sarah
> > Sent: Wednesday, August 23, 2017 11:44 AM
> > To: [log in to unmask]
> > Subject: [CODE4LIB] Non-networked computer advice
> >
> > Hello!
> >
> > Asking on behalf of our library's Systems department: Does anyone 
> > have any best practices for a non-networked/quarantined computer for 
> > confidential information/sensitive information? We are looking for 
> > ways to get more potential donors of digital material, but some of 
> > these donors do not want their work to be on a networked computer.
> >
> > Our Systems department is looking for a methodology or best 
> > practices for a computer that can be backed up/connected to an 
> > internal-only network (with no public access) but that cannot access 
> > networked resources and the internet. If your archives has something 
> > like this set up, would you be willing to share your set-up?
> >
> > Please feel free to respond off-list to Scott Lewis at 
> > [log in to unmask] Scott can also answer any questions if 
> > you have any.
> >
> > Thank you so much in advance!
> >
> > Sarah
> > ------------------
> > Sarah Coates, MA, MLIS, CA
> > Archives
> > 204 Edmon Low Library
> > Oklahoma State University
> > Stillwater, OK 74078
> > 405.744.6076
> > [log in to unmask]
> >
>