{"id":94670,"date":"2013-11-05T04:45:08","date_gmt":"2013-11-05T09:45:08","guid":{"rendered":"http:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/uncategorized\/nasa-mobile-security-requirements-why-now.php"},"modified":"2013-11-05T04:45:08","modified_gmt":"2013-11-05T09:45:08","slug":"nasa-mobile-security-requirements-why-now","status":"publish","type":"post","link":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/nasa\/nasa-mobile-security-requirements-why-now.php","title":{"rendered":"NASA Mobile Security Requirements: Why Now?"},"content":{"rendered":"<p><p>    On August 29, 2013, NASA Chief Information Officer Larry Sweet    sent out an Agency message to all NASA employees entitled    \"Bring Your Own Device (BYOD) and Mobile Computing at NASA,\"    which included a memorandum of minimum security requirements    for personal mobile devices (available     online). The memo alerted employees to the    enforcement of several requirements regarding the NASA e-mail    system that would begin on September 10.  <\/p>\n<p>    Many have asked, \"Where did these requirements come from, and    why are they coming out now?\" Well, as we all know, mobile    devices (e.g., smartphones, tablets, etc.) are playing an    increasingly important role in our lives. As we start to use    these new and exciting technologies at home, we often want to    use them in all aspects of our life--including at work.    However, the introduction of such devices into the marketplace    and then into the workplace often precedes NASA's ability to    test and secure them. As a result, they present unique    technological, legal, and security challenges for you and for    our IT staff.  <\/p>\n<p>    Historically, NASA has not blocked or prevented the use of    mobile devices to access NASA e-mail and resources. However,    due to the exponential growth of these unmanaged systems in the    NASA environment over the past few years, it has become    imperative for NASA to acknowledge and address the risk they    present to our resources and data.  <\/p>\n<p>    So, instead of simply \"turning access off\" and forbidding the    use of mobile devices (which would have certainly addressed the    risk), the NASA CIO decided to implement a minimum set of basic    security requirements and capabilities to support NASA    employees while a broader BYOD effort is pursued. Many of these    security requirements are general best practices that are    already in use by employees on their personal devices.  <\/p>\n<p>    That being said, we did want to address a few questions and    concerns that have been raised, particularly those related to    using a personal mobile device to connect to the NASA e-mail    system:  <\/p>\n<p>    Does NASA now have the ability to access any information on my    personal device?  <\/p>\n<p>    No, absolutely not. NASA cannot access any data on your    personal device; it can only confirm that your device exists    and has connected to our system.  <\/p>\n<p>    Did NASA install any software on my device?  <\/p>\n<p>    No. Any changes in the security configuration of your personal    device to support NASA's minimum requirements take place within    the device's own native capabilities. No software or additional    \"profiles\" have been installed.  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>Original post: <\/p>\n<p><a target=\"_blank\" href=\"http:\/\/www.spaceref.com\/news\/viewsr.html?pid=44921\" title=\"NASA Mobile Security Requirements: Why Now?\">NASA Mobile Security Requirements: Why Now?<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> On August 29, 2013, NASA Chief Information Officer Larry Sweet sent out an Agency message to all NASA employees entitled \"Bring Your Own Device (BYOD) and Mobile Computing at NASA,\" which included a memorandum of minimum security requirements for personal mobile devices (available online). The memo alerted employees to the enforcement of several requirements regarding the NASA e-mail system that would begin on September 10 <a href=\"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/nasa\/nasa-mobile-security-requirements-why-now.php\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"limit_modified_date":"","last_modified_date":"","_lmt_disableupdate":"","_lmt_disable":"","footnotes":""},"categories":[20],"tags":[],"class_list":["post-94670","post","type-post","status-publish","format-standard","hentry","category-nasa"],"modified_by":null,"_links":{"self":[{"href":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/wp-json\/wp\/v2\/posts\/94670"}],"collection":[{"href":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/wp-json\/wp\/v2\/comments?post=94670"}],"version-history":[{"count":0,"href":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/wp-json\/wp\/v2\/posts\/94670\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/wp-json\/wp\/v2\/media?parent=94670"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/wp-json\/wp\/v2\/categories?post=94670"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/wp-json\/wp\/v2\/tags?post=94670"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}