Is it time to BYOD?
If you let workers bring their particular device (BYOD) into the business? Itis a question that raises many others. Is the business data going to be in danger? Can the business save a huge number of dollars per year through not buying apparatus? Will the workers eventually get the latest gadget they desire?
The concept of workers using their particular gear at work isn't new. Using private vehicles for sales representatives, couriers, and truck drivers has a long history in industry. Similarly business freedom isn't new. Businesses like Intermec and Motorola have developed fit for purpose mobile devices since the 1970s. What's transformed and continues to progress quickly is the sophistication of consumer cellular devices. These are now more powerful and feature rich than ever before. With the explosion of mobile device technology early adopters promptly brought the latest apparatus into the office. Before the iPad was released in Australia, it was used in Aussie workplaces to reveal videos, take notes, and access e-mail. So the major question for businesses is not "should we let BYOD," but "how do we let BYOD"?
BYOD strategy success variables
If we further investigate the analogy of vehicles in the workplace you will find some regulating variables that ensure their successful use. Firstly there are scenarios (dare I say uses) where it might not be suitable to make use of a private vehicle. For specialist areas like mining, authorities, and well-being or where there's a demand for branding a business vehicle might be a better fit. Second there are mature policies that summarize how a private vehicle may be utilized. For example cycle couriers may get a fee per delivery whereas taxi drivers must prepare and service their vehicle following strict guidelines. Another challenge to consider is that workers expect in order to utilize their private vehicle in their particular time for their own functions. So what should the Enterprise do to get ready for the BYOD that's already occurring? A helpful technique would be to develop a BYOD strategy that encompasses the demands, threats, policies, and technology.
Present use of cellular technology
The very first variable to consider is how your business now uses cellular technology. The most frequent responses are phone calls, e-mails and related attachments, calendar, internet, and map services. These features possibly low hazard for most, yet consider the specific risk to your business and information. If a telephone was located by a rival what information could they get access to? Could a malicious user release commercially sensitive information or undermine a government regulation?
Increasingly, businesses already use or are intending to make use of cellular technology to get the corporate network and backend systems. These characteristics of freedom merit a closer review of the demands and threats. Usually these programs fall into the class of either Web Based or Abundant/Native programs. Consider carefully what information and attributes the cellular programs empower? Could a malicious user download all the customer information? Some rich cellular programs are similar to the police car in the automobile analogy and need special gear to run correctly (e.g. bar code scan, a particular Operating System, or utilise a printer). It can help record each kind of user as well as the characteristics and programs they need.
Handling other risks and variables
While loss of IP as well as corporate information is of utmost significance there are a selection of other variables your business should consider for BYOD including:
-- Price of support - how will you manage issues on BYOD devices?
-- Private information - what if worker information is wiped or obtained?
-- Who Is paying - for the apparatus, information, calls, and support?
-- Brief lifespan - with models switching every 6 months what'll your upgrade strategy be?
-- Workers leaving - clean up the Enterprise info?
The appropriate policies for your business
It is a real "horses for courses" question. I have worked with small businesses that adore technology and utilise every attribute including geo-fencing and remote control of apparatus for support, however do not need stringent regulations on their information. At the opposite end of the spectrum authorities controlled businesses that simply use technology when they've to and every attribute must be encrypted and locked down. In my opinion reasonable polices should shield the Business without hamstringing productivity and innovation.
When you are in possession of a great image of your necessities, information, and threats think about the policies that your business would wish to contain in regard to cellular devices. These policies may actually be suitable for both BYOD and corporate apparatus. Most Businesses have an acceptable use policy for their desktop computers or the internet and these may be a great starting point. Do not just consider the technical policies (for example security, authentication, password strength, and information segregation) also think about the commercial (that's who pays for the information, calls, and support).
Handling the cellular fleet
I have seen a variety of organisations where the mobile fleet is out of control and monthly fees are paid for dormant SIM cards sitting on a ledge. Consider all the apparatus versions, brands, and operating systems that you have outside in the field. Do you own a mix of old and new apparatus, iPhones for executives and ruggedized devices in the area?
Just because your business will support BYOD does not mean it wants support every kind of consumer apparatus. Look at the most popular consumer device versions and consider your business conditions and policies. It's possible for you to make a whitelist of apparatus which are acceptable.
Supporting tools and options
When you own a handle on the BYOD demands and policies you will need to consider a toolset like Mobile Device Management (MDM) to help together with the execution of your strategy. Typical MDM characteristics comprise:
-- Program direction
-- Asset & lifecycle management
-- Authentication, policy & security direction.
An MDM can help segregate private as well as corporate information, set a typical operating environment (SOE), and support fleets of apparatus more readily. Yet MDMs are reliant on the characteristics supplied by the operating system or hardware maker. For example you could have the ability to remotely see the display on a Windows mobile device however an Apple apparatus mightn't support this attribute. Also some MDM products are offered as a hosted service and others have to be set up on your own hardware. Inquire the toolsets; a great starting point is Gartner's magic quadrant for MDM. If you're thinking about IOS a great public resource is the Department of Defence IOS hardening guide.
Workers constantly need to utilise the most effective tools and cellular technology is a place that continues to evolve. Be prepared so that your business can really cost efficiently influence the advantages of freedom. Develop a BYOD strategy that considers the demands, threats, policies and technology. Consider that BYOD is occurring but might not be appropriate for each mobile business demand.
BYOD may satisfy:
-- Phone Calls
-- E-Mail
-- Web Based Applications
-- Easy Workflow fashion Programs
-- Reporting & Business Intelligence
BYOD might not satisfy:
-- Programs that rely on abundant apparatus integration like RFID, scanning, computer keyboard, or stylus
-- When a particular Operating System or API is needed.
-- Scenarios where a solid or IP rated apparatus is needed
-- Where the business process is fully reliant on the apparatus
CRA -
http://consultcra.com/services/cloud-solutions/