This is not a NASA Website. You might learn something. It's YOUR space agency. Get involved. Take it back. Make it work - for YOU.
IT/Web

NASA Bring Your Own Device Update

By Keith Cowing
NASA Watch
September 11, 2013
Filed under , ,

ActiveSync Security Policies to be Applied to Mobile Devices Connecting to NOMAD
“a. The use of your own mobile device (i.e., cell phone or tablet) to retrieve your NASA email/calendar or to conduct NASA business is entirely voluntary. Users should refrain from using a personal mobile device to access NASA information and systems if uncomfortable, unable, or unwilling to comply with these minimum security requirements. As the use of personal mobile devices is purely optional, employees cannot be expected to use their own devices to accomplish their assigned tasks if they choose not to do so. Your supervisor may not require you to do so. If a mobile device is required for you to perform your assigned duties, management will provide you with an appropriate NASA-owned device consistent with the Negotiated Agreement, unless you voluntarily choose to use your own device. You cannot be required to provide your personal email address or cell-phone number to management.
b. Employees using their own mobile device for downloading NASA email /calendar directly via their phone’s mail client should be aware that NASA has the ability to access your device and to erase (“wipe”) it. While the current NASA policy is that no such access or wiping will occur without the employee’s explicit permission, it remains possible that such adverse events could nonetheless occur inadvertently. Therefore, employees should backup their personal phones often to reduce their vulnerability of data loss.”

Do You Really Trust NASA Not to Ruin Your Mobile Device?, earlier post

NASA Watch founder, Explorers Club Fellow, ex-NASA, Away Teams, Journalist, Space & Astrobiology, Lapsed climber.

One response to “NASA Bring Your Own Device Update”

  1. Fred says:
    0
    0

    I wouldn’t trust any company with my personal data and try to keep that separated as much as possible.