Ideas for the Mobility Strategy

Adopt common approaches to accommodate consumerization

Create a Federal mobility reference architecture to enable adoption of common solutions (e.g., for BYOD).

Tags

Submitted by
Share this idea:

Stage: Active

Feedback Score

14 votes
Voting Disabled
Idea#24

Idea Details

Vote Activity (latest 20 votes)

  1. Upvoted
  2. Upvoted
  3. Upvoted
  4. Downvoted
  5. Upvoted
  6. Downvoted
  7. Upvoted
  8. Downvoted
  9. Downvoted
  10. Downvoted
  11. Upvoted
  12. Upvoted
  13. Upvoted
  14. Upvoted
  15. Upvoted
  16. Upvoted
  17. Upvoted
  18. Upvoted
  19. Upvoted
  20. Upvoted
(latest 20 votes)

Events

  1. The idea was posted

Comments

  1. Comment
    paglianobm

    More often users are demanding devices from the choices that they make in the consumer space. Enterprise IT needs to figure out ways to meet the security needs of the enterprise while making the customers happy with the device they are using.

  2. Comment
    Neil Bonner

    Couldn't agree more with this idea. TSA has built a mobile architecture for secure access to back-end web services that uses the standard Open Authentication (OAuth)to validate the user and mobile app. This approach could be used by other agencies.

    Why reinvent the wheel if we don't have to?

    Comments on this comment

    1. Comment
      sweerek

      The user and the app might be trusted, but the devices themselves we have today are horribly insecure... even with bolt-on 'security' apps.

  3. Comment
    wjhuie

    I've never seen a federal 'reference architecture' that's been very useful, and I've seen more than a few.

    Take for example the recent federal 'telework RA', which explicitly stated that it ignored mobility and not federally owned devices.

    Comments on this comment

    1. Comment
      wjhuie

      "not" - Non-federally owned devices... apparently you can Delete but not Edit a post.