Security and intra-agency collaboration. Those were two of the key barriers to Government mobility I focused on in my first blog. In this second part, I’m looking at how Huddle’s mobile solution breaks down those barriers, empowering government teams, departments, and agencies to share and work on content, internally and across the firewall—securely and confidentially.

The government mobility strategy has been fragmented until now. Some employees are allowed to bring their own device, while others have an agency assigned mobile device. The reason for this is a lack of confidence. All the advantages that a mobile device provides—including portability, access to information, and access to a plethora of productivity apps in the App Store—are doomed as concerns about mobile security threats in the government space prevail.

The US government is focused on developing a framework to bring a governance structure and foundation for cross-agency mobility services. It’s being driven by Bring Your Own Device (BYOD)—the mobile movement which is steadily revolutionizing employee output and productivity. Historically, work requirements drove innovation, but mobile has reversed this model. Though native apps on the mobile and tablets makes surfacing content possible, it does come with potential challenges that need to be addressed or solved prior to content enablement on mobile.

Huddle can help ensure every government mobility strategy is risk tolerant, allowing government agencies to share, store, and work on content in the cloud. Here’s how Huddle does it:

Data management

Security: Users are required to authenticate into Huddle to access their content. This is done over SSL to ensure that safeguards are in place to prevent unauthorized access or disclosure. In addition, all content stored on the device is stored in a secured cache and encrypted at rest. This will ensure that other applications cannot programmatically access Huddle content.

Access: Users are only able to interact with content that they have been explicitly permissioned to by the content owner.

Compliance: All interactions between the user and contents are to be recorded and auditable via the audit log within Huddle.

User experience via native applications

Being able to access content on the mobile device is definitely a huge barrier to overcome. The best user experience is provided via Huddle’s iOS native apps that captures the user’s attention and allows them to not only view content but to interact with it in a way that’s similar to the web experience.

Data ownership

Huddle’s philosophy is that the organization owns the content, not the user. As users join, leave, or move within departments, the government’s content owner (i.e. the organization) can control the type of interaction the user has.  If the user decides to part ways with the organization, the admin can invoke a remote wipe to ensure all Huddle data is removed from the secure cache within the device.

Mobile in the US government has morphed into an important channel that facilitates content distribution. End-users’ behavior and dependency on these devices has driven the US government to adopt and implement an overarching BYOD strategy. Content might be easier to access, however safeguards need to be in place to ensure the content is safe in the field where it is outside the control of IT. Huddle addresses those three issues of control: data management, user experience, and data ownership. Huddle is a FISMA compliant collaboration platform that not only provides the native apps for iOS that encompass these three safeguard controls, but also keeps security as the underlying framework to enable this functionality.

For the complete guide to cloud collaboration in the government, download this free white paper.

Download the white paper

Raj Agarwal


Request a Demo
trillatron

© 2006 - 2019. All Rights Reserved.