by clicking on the page. A slider will appear, allowing you to adjust your zoom level. Return to the original size by clicking on the page again.
the page around when zoomed in by dragging it.
the zoom using the slider on the top right.
by clicking on the zoomed-in page.
by entering text in the search field and click on "In This Issue" or "All Issues" to search the current issue or the archive of back issues respectively.
by clicking on thumbnails to select pages, and then press the print button.
this publication and page.
displays a table of sections with thumbnails and descriptions.
displays thumbnails of every page in the issue. Click on a page to jump.
allows you to browse through every available issue.
FCW : June 30, 2014
QHow can agencies ensure that the mobile program they implement today will be able to handle future growth in users and resource demands? AAgencies must make pro- curement decisions that ad- dress immediate needs, yet allow for both the continued adoption of new capabilities and ongoing user growth. The resulting program should em- brace a range of things, such as ensuring that workers have access to mobile broadband and supporting the move of applications and data to the cloud. And it must be capable of accommodating re- motely applied security measures. QMobile involves a signi cant amount of change in back of ce and legacy systems. What steps should be taken to ease the integration? AThe change in back of ce and legacy systems is being driven by the nearly universal need to do more with less, and to increase end-user satisfac- tion and productivity. The ultimate goal is conver- gence, rather than integration. Agencies need to augment their own core competencies with the spe- cialized skillsets of experienced providers that can help them make changes that will stand the test of time. Such blended project teams must de ne and outline the agency architecture and security re- quirements and then take steps to ensure conver- gence will be effective. QWhen it comes to mobile security, most organiza- tions focus on the device itself. Is this suf cient? What else is needed? AMost of the security on the mobile devices is managed by enterprise-grade mobile device management (MDM) software, which is used to create policies for authenti- cation and the controls necessary to ensure that the devices coming onto the agency network or accessing its resources have not been jeopardized by viruses or malware, and have not been jail-broken. However, se- curing end users' devices by using MDM is only one piece of the security continuum. With the onset of bring-your-own-device (BYOD) policies in mind, enter- prises also must focus on building a trusted application ecosystem in which device, network and authentica- tion controls deliver secure backend access and pro- tect data, both at rest on the device and in transit. QSome agencies are still trying to get their heads around BYOD. Is this something that is simply too risky for government? AWhat's risky is not looking at BYOD deployments. That's because if agencies do not implement a BYOD solution, employees will skirt the rules and use their own devices anyway, with no management or over- sight. Each government organization has a different risk pro le or tolerance. Proper deployment of MDM/ MAM/MAS solutions, which containerize a device through a personal/business mode split, is necessary. Overall, the successful deployment of BYOD depends on the right mobile strategy, clearly-de ned policies, adoption among agency leadership, and the educa- tion of the agency's ranks down to the end user. QWhat are the key elements in an enterprise-wide mobile strategy? A First, mobile policies for access and use---including the education of management, technology groups and end users---must be well-de ned and in place. These will help agencies leverage and manage mobile solu- tions, such as BYOD. It's also important to offer a choice of devices, allowing workgroups to choose de- vice attributes---such as operating systems, user inter- faces and tools---that are suitable for their operation. Make agency resources available to the mobile work- force in the form of native apps or via HTML5/web- based portal access, by moving the enterprise mobile strategy up the value chain, well beyond e-mail. Finally, engaging with all relevant parties from the beginning, both to de ne the end goals and to iron out the steps needed to move in the desired direction, will help build a holistic mobile environment that encourages a more collaborate workforce thus a more productive agency. Chris Smith Vice President, Technology AT&T Government Solutions Sponsored Content To learn more about mobility solutions for the federal government, contact AT&T at Att.com/gov/mobility M : Th k h v f
May 30, 2014
June 15, 2014