{"id":201,"date":"2013-11-05T13:11:54","date_gmt":"2013-11-05T17:11:54","guid":{"rendered":"http:\/\/blog.uvm.edu\/whysecurity\/?p=201"},"modified":"2013-11-08T14:17:04","modified_gmt":"2013-11-08T18:17:04","slug":"traveling-abroad-without-making-the-news-mobile-tech-edition","status":"publish","type":"post","link":"https:\/\/blog.uvm.edu\/whysecurity\/2013\/11\/05\/traveling-abroad-without-making-the-news-mobile-tech-edition\/","title":{"rendered":"Traveling Abroad without Making the News (Mobile Tech Edition)"},"content":{"rendered":"

Occasionally, a member of the community approaches the ISO Team to ask for our advice on traveling safely with mobile technology. While individual circumstances (including the nature of the mobile technologies\/data in play, the nature of the trip, the particular destination) will dictate specifics, our general recommendations (below) will cover a lot of ground for a lot of folks.<\/p>\n

    \n
  1. Unless there is a tremendously-compelling reason to do otherwise, leave your normal work machine (with your years of research data, UVM\/previous employer’s email, grant proposals, intellectual property, personal finances, countercultural rantings, etc.) at home and take a loaner machine (provided by your Helpful IT Folks) containing only the materials necessary for the trip.<\/li>\n
  2. This loaner should be wiped and get a fresh OS install to keep from leaking data belonging to the *last* person who traveled with it…and to keep the new traveler from picking up any *ahem*<\/em> latent “gifts” acquired by the last user. Set all installed browsers to clear all private data on session termination, and disable (browser-based) password storage.<\/li>\n
  3. Make liberal use of webmail.uvm.edu<\/a>, webfiles.uvm.edu<\/a>, and sslvpn.uvm.edu<\/a> while abroad.<\/li>\n<\/ol>\n

    These suggestions apply to smartphones\/tablets\/Google Glass\/smart watches\/any other device that stores data which could be 1) a liability to the university if lost or 2) embarrassing to the user if confiscated. Or data the export of which is controlled under ITAR rules<\/a>. (Yes, that applies to Higher Ed.<\/a>)<\/p>\n

    [Edit 8 November, 2013: It’s worth considering, too, that not all travel destinations feature the robust freedoms of expression that we enjoy in the U.S., so feel free to substitute\/append “…or could precipitate your detention if confiscated and found to be at variance with local law.”]<\/em><\/p>\n

    Why incur this much potential inconvenience? One reason is that humans have a tendency to (subconsciously) downplay the risks inherent in the data they tote around on a daily basis, and while “safe” might cost them an extra few hours over their two-week trip, “sorry” can manifest in more…time-consuming ways.<\/p>\n

    Incidentally: Simply having the storage encrypted doesn’t suffice in a number of travel zones, as customs officials may be invested with the authority to compel the owner to unlock\/decrypt it. (And encryption is illegal in certain jurisdictions.)<\/p>\n

    Want to share your own tips\/travel-tech stories? Got questions? Need to chat about your specific circumstances? Please let us know! As usual, we can be reached at iso@uvm.edu.<\/p>\n

     <\/p>\n

    Cheers,<\/p>\n

    Sam Hooker, for the ISO Team<\/p>\n","protected":false},"excerpt":{"rendered":"

    Occasionally, a member of the community approaches the ISO Team to ask for our advice on traveling safely with mobile technology. While individual circumstances (including the nature of the mobile technologies\/data in play, the nature of the trip, the particular destination) will dictate specifics, our general recommendations (below) will cover a lot of ground for … <\/p>\n

    Continue reading “Traveling Abroad without Making the News (Mobile Tech Edition)”<\/span><\/a><\/p>\n","protected":false},"author":16,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-201","post","type-post","status-publish","format-standard","hentry","category-uncategorized","entry"],"featured_image_src":null,"featured_image_src_square":null,"author_info":{"display_name":"Sam","author_link":"https:\/\/blog.uvm.edu\/whysecurity\/author\/sthooker\/"},"_links":{"self":[{"href":"https:\/\/blog.uvm.edu\/whysecurity\/wp-json\/wp\/v2\/posts\/201","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.uvm.edu\/whysecurity\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.uvm.edu\/whysecurity\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.uvm.edu\/whysecurity\/wp-json\/wp\/v2\/users\/16"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.uvm.edu\/whysecurity\/wp-json\/wp\/v2\/comments?post=201"}],"version-history":[{"count":11,"href":"https:\/\/blog.uvm.edu\/whysecurity\/wp-json\/wp\/v2\/posts\/201\/revisions"}],"predecessor-version":[{"id":212,"href":"https:\/\/blog.uvm.edu\/whysecurity\/wp-json\/wp\/v2\/posts\/201\/revisions\/212"}],"wp:attachment":[{"href":"https:\/\/blog.uvm.edu\/whysecurity\/wp-json\/wp\/v2\/media?parent=201"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.uvm.edu\/whysecurity\/wp-json\/wp\/v2\/categories?post=201"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.uvm.edu\/whysecurity\/wp-json\/wp\/v2\/tags?post=201"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}