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
6 8 Steps To An Effective Mobile Device Policy pay for all or a portion of the hardware, data access plan and support costs. Other financial areas to spell out include the specific costs for which a BYOD device owner will be responsible and, if applicable, the international calling and international roaming plans that will be offered for voice and data traffic. STEP 5: ADDRESS LIABILITY ISSUES. Liability considerations home in on data that's subject to government security and privacy regulations and the organization's own best practices. "You don't want to wind up with a Sarbanes-Oxley problem because of mobile usage," warns Craig J. Mathias, principal with the Farpoint Group, a consulting firm. But there may be some knotty issues to sort out when it comes to liability. For If there are other apps users or groups of users need, then an approval would need to come from the mobile policy overseers. e policy also can state that the organization won't support user-added software. STEP 4: SPELL OUT FINANCIAL TERMS. ere are three basic financial models an organization can adopt. e first is direct billing, where the organization buys the device and assumes all expenses. e second is to provide a fixed monthly reimbursement for device support. Finally, some organizations choose to reimburse based on worker expense reports. e model chosen depends on the answers to a handful of important questions. ese questions range from whether the organization or worker will example, every organization has a right to regulate how its data is accessed and used, but policymakers must decide how to handle users' personal information, including contacts that are stored on entity-provisioned devices. Is that data private? e policy committee must hash out questions such as these to create a system that minimizes the exposure of personal information. Finally, mobile users should clearly understand the penalties for failing to adhere to any of the required mobile policies. is includes whether different types of violations will carry different penalties. For example, will the consequences for violating eligibility rules be treated differently than security or acceptable-use requirements? STEP 6: LOCK DOWN SECURITY. Security will likely require the most time and effort from the mobile policy writers. e influx of new mobile equipment, including personal devices, is adding complexity to security operations while also loosening some of the tight controls the IT department had been able to exert in the past. " e paradigm has changed. In the past, end users were bound by what the IT department required. But it's not a one-way street anymore," Kotikalapudi says. "If you want to put security software on a mobile device, you must first get user buy-in." To get users on board, IT managers must accept a couple of ground rules, he adds. "You can't do anything to mess up the native end-user experience. People buy an Android device, for example, for specific reasons." at shouldn't be compromised by security controls. Hammering out security rules begins with setting the broad outlines in Step 3 about the data that should be accessible via mobile devices. Follow that rule with having the steering committee drill down into specific security technologies and use policies. An important goal is to protect internal data when it travels outside the VISIT CDWG.com/mobile-policy FOR MORE INFORMATION ABOUT DEVELOPING A MOBILE DEVICE POLICY FOR YOUR ORGANIZATION.
August 30, 2013
September 30, 2013