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 : September 15, 2013
5 STEP 2: OUTLINE THE ORGANIZATION'S GOALS. Before the steering committee delves into policy specifics, it must define what challenges and opportunities the organization is trying to address with a modern mobile policy. "Considerations will range from helping the CEO, who just got a new tablet, to end users, who are pressuring the organization to support Android devices," Kotikalapudi says. "But then there's also the managers who want to put data in the hands of people in the field, which represents a true business model. A final consideration is the fact that if you don't have a system in place to support mobility, end users will find their own way." Multiple triggers may encourage organizations that the time has come to act. ese drivers may include a growing acceptance of the bring-your- own-device (BYOD) model --- both as an opportunity for cutting IT costs and as a potential productivity booster. Other incentives include the ability to better secure an organization's data and applications, as well as making sure that workers have ready access to the necessary tools to do their jobs. STEP 3: DEFINE THE POLICY DETAILS. ere aren't any one-size-fits-all templates for mobile policies, but all types of entities, no matter their size and industry segment, need to address some common core requirements. ese start with specifying the types of devices covered by the policy. In some cases, organizations may have to merge old and new policies. For example, most organizations will already have rules in place for managing notebooks. But unless they've been updated recently, the policies will likely assume that the devices are provisioned by the entity. at may still be the case, although some organizations are extending BYOD beyond smartphones and tablets to include notebooks and ultrabooks. > CDWG.com | 800.808.4239 e key is defining which types of devices and operating system platforms will be allowed to access data versus those that are restricted from use because of management and security considerations. "Different areas need different infrastructure and controls," Shey says. He suggests organizing worker groups into three broad categories. e first segment he calls "organization- liable," those who use entity- provisioned devices and data services to access organization databases. Examples include C-level executives, directors and administrators. "For this group, organizations will need a well-developed policy in place and a management infrastructure to control the devices and keep sensitive data safe from the bad guys," he says. " at may mean mobile device management [MDM] capabilities, plus data encryption and mobile virtual private networks [VPNs]." e second group also uses entity devices and services, but they might be authorized to access only the organization's email system, not databases directly. e controls can be somewhat looser, but the organization might still want an MDM solution to track the status and location of devices. " ese users may not have mobile access to databases, but there could still be access to sensitive data in emails," Shey points out. e third segment comprises BYOD users who tap their personal devices for work-related apps or to email and text other staff members, customers or constituents. Examples include a marketing manager or HR person who may work mostly in an office but wants to stay connected while in meetings or after hours. Wrapped up in these considerations are rules for whether some applications and data are off limits. For example, a policy might allow all devices to download approved software via a specified portal. But any additional software applications that users want must be on an organization-approved list.
August 30, 2013
September 30, 2013