Adopt common approaches to accommodate consumerization


Stage: Active

Campaign: Ideas for the Mobility Strategy

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


Submitted by

Feedback Score

14 votes
Voting Disabled

Idea Details

Vote Activity (latest 20 votes)

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


  1. The idea was posted



  1. Comment

    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

      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

    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

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