<?xml version="1.0" encoding="UTF-8" ?>
<rss xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
        <channel>
        <title>byod - ReadWrite</title>
        <link>http://readwrite.com</link>
        <description />
        <language>en</language>
        <copyright>Copyright 2012 SAY Media, Inc.</copyright>
        <managingEditor>readwriteweb@gmail.com</managingEditor>
        <docs>http://blogs.law.harvard.edu/tech/rss</docs> 
        <lastBuildDate>Thu, 23 May 2013 07:06:00 -0700</lastBuildDate>
        <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://rww.superfeedr.com/" />

                    <item>
                <title><![CDATA[Bring Your Own Device (BYOD) Saves Companies Money - But Could Cost Users Big]]></title>
                <description><![CDATA[
                                        <img src="http://readwrite.com/files/styles/800_450sc/public/fields/Apps_Iphone45.jpg" />
                                        <p>Bring Your Own Device (BYOD) polices are increasingly popular as a way for companies to let workers use the hardware they like best and are most productive with. But <a href="http://blogs.cisco.com/news/new-analysis-comprehensive-byod-implementation-increases-productivity-decreases-costs/">according to a new study from Cisco</a>, that not be the best way to think about BYOD.</p>
<p>Implement a strong BYOD policy, Cisco says, and your organization could save $1,300 per year per mobile user. Users meanwhile, report that they are happier and more productive - even though they may end up paying more out of their own pockets!</p>
<p><strong>(See also <a href="http://readwrite.com/2012/12/06/pause-economy-linked-to-bring-your-own-device-use" target="_blank">Worried Workers: BYOD Or You're SOL [Infographic]</a>)</strong></p>
<h2>Happier, More Productive, But Poorer?</h2>
<p>The survey, released Wednesday by <a href="http://www.cisco.com/web/about/ac79/index.html" target="_blank">Cisco's Internet Business Solutions Group (IBSG)</a> consulting unit, polled 2,415 users in six countries to determine the effects of letting employees bring their own devices into the office.&nbsp;The results indicate that employees around the world were very interested in BYOD, and they were even willing to pay for it: On average, workers said they would spend $965 out of pocket for their own devices and another $734 annually for the data plans to go with them.</p>
<p>Here's why: Workers with their own devices said they were happier and (more objectively) reported significant productivity gains. In the U.S., BYOD participants saved 81 minutes of time per week - just over 70 hours a year.</p>
<p>Not every country noted such productivity increases, and use of employee devices also had negative effects, such as increased administration, downtime and distractions that dragged the overall efficiency down,&nbsp;explained Jeff Loucks, senior manager at IBSG.&nbsp;</p>
<p>Most of the devices in question were phones: 81% of device bringers reported they uses smartphones, 56% brought tablets and 37% brought their own laptops. On average, each of the&nbsp;estimated 198 million BYOD users around the world&nbsp;had 1.7 devices, said Loucks.</p>
<h2>BYOD Keeps Growing</h2>
<p>The number of BYOD users is expected to swell to 406 million by 2016. Even though the U.S. leads in BYOD use right now, by 2016, China alone is expected to have 166 million alone, compared to the 106 million in the U.S. and 76 million in India.</p>
<p>Companies fared best, Cisco discovered, when they implemented a strategic BYOD plan, rather than stick than just trying to keep up with devices coming into the organization.&nbsp;Such reactive policies tend to make users figure everything out for themselves, often working with an IT department that only grudgingly allows such devices into the organization.</p>
<p>Want to realize those promised cost benefits? Get ahead of users with a proactive BYOD policy that enables employees to quickly access corporate tools and data, perhaps featuring a self-service help system. Such policies also help organizations keep better security on corporate data.</p>
<p><strong>(See also <a href="http://readwrite.com/2013/01/18/readwrite-survey-results-what-a-typical-byod-program-really-looks-like" target="_blank">ReadWrite Survey Results: What A Typical BYOD Program Really Looks Like</a>.)</strong></p>
<h2>Be Careful What You Wish For - BYOD Edition</h2>
<p>As much as workers seem willing to pay their own way to get the devices they want without their employers'&nbsp;interference (only 30% said they would be willing to work with corporate-provisioned devices - often called <a style="line-height: 1.538em;" href="http://readwrite.com/2012/10/19/forget-bring-your-own-device-try-corporate-owned-personally-enabled" target="_blank">Corporate Owned, Personally Enabled, or COPE</a>), it's hard to shake the feeling that even though employees are more satisfied and productive, there's something unsettling if they end up footing the bill for this innovation.&nbsp;</p>
<p><strong>(See also <a href="http://readwrite.com/2012/10/19/forget-bring-your-own-device-try-corporate-owned-personally-enabled" target="_blank">Forget Bring Your Own Device - Try Corporate Owned, Personally Enabled</a>.)</strong></p>
<p>It's not an idle question: A recent&nbsp;Gartner&nbsp;survey of CIOs found that 38% said their companies planned stop providing employees with devices by 2016.&nbsp;Gartner also expects that nearly 50% of employers will demand employees provide their own devices for work purposes - out of pocket - by 2017.</p>
<p>Companies are increasingly willing to explore BYOD policies - but it seems that the reasons may not be entirely altruistic. Letting employees use the tools they prefer is clearly a good idea, but making them pay for the privilege doesn't seem right.&nbsp;</p>
<p>&nbsp;</p>
                    ]]></description>
                <link>http://readwrite.com/2013/05/23/bring-your-own-device-byod-saves-companies-money-but-could-cost-users-big</link>
                <guid>http://readwrite.com/2013/05/23/bring-your-own-device-byod-saves-companies-money-but-could-cost-users-big</guid>
                <category>BYOD</category>
                <pubDate>Thu, 23 May 2013 07:06:00 -0700</pubDate>
                <author>Brian Proffitt</author>
            </item>
                    <item>
                <title><![CDATA[The Consumerization Of The Enterprise Is Over]]></title>
                <description><![CDATA[
                                        <img src="http://readwrite.com/files/styles/800_450sc/public/fields/flickr-gerrydincher-shell-gas.jpg" />
                                        <p>At the point that a trend becomes obvious and mainstream, it is no longer a trend. It is historical fact.</p>
<p>So it is with the consumerization of the enterprise, a buzzy phrase for the infiltration into workplaces of gadgets and services purchased on the sly or openly by employees.</p>
<p>These renegade tools arrived without the sanction of traditional IT departments, upending everything from the design of networks and security protocols to the very hierarchy of corporations. Also known as BYOD, or "bring your own device," it's less of a deliberate move than a belated acceptance of reality.</p>
<p>Now Shell, the energy giant, has announced it is <a href="http://www.v3.co.uk/v3-uk/news/2263243/shell-plans-to-move-135-000-staff-to-byod" target="_blank">allowing its 135,000 employees to bring their own devices to work</a>, and offering them access to the tools and technologies they need over the Internet—the cloud, if you prefer.</p>
<p>Ken Mann, Shell's enterprise information security architect, explained this as a recruiting decision as much as a technology move—an acknowledgement of the inevitability of the consumerization movement.</p>
<p>“We’re going to have a lot of people turning over, and we want to be able to attract and retain talented and young staff," Mann said at the CA World conference in Las Vegas earlier this week, V3 reports. "They don’t want to come into a locked corporate environment.”</p>
<p>Shell has always been something of a future-forward organization, employing futurists long before many technology companies did. So consider it a harbinger of what will happen to other companies of its size. They will either embrace similar strategies or find themselves unable to compete for talent or customers.</p>
<p>The consumerization of the enterprise is no longer an open question. It's a fait accompli. Which makes it, for me, not a very interesting thing to think about.</p>
<p>What's next? I think it may be the flip side of this trend, what I call the enterprisification of the consumer. Business-class tools, gigantic "big-data" databases, and massive amounts of computing power will be in the reach of the smallest of businesses, sole proprietors, and ordinary technology users. Just as consumer tools are bleeding into the business world, technology that we've classically thought off as walled off in the enterprise world will become cheap, accessible, and widespread.</p>
<p>The consumerization trend will keep happening, and we'll note its progress from time to time. But we need to start thinking about what's next, not what's done. And with Shell's full embrace, the hard work for advocates of consumerization is done.</p>
<p><em>Photo by Flickr user <a href="http://www.flickr.com/photos/gerrydincher/6825083518/">Gerry Dincher</a>, CC 2.0</em></p>
                    ]]></description>
                <link>http://readwrite.com/2013/04/23/consumerization-of-the-enterprise-is-over</link>
                <guid>http://readwrite.com/2013/04/23/consumerization-of-the-enterprise-is-over</guid>
                <category>BYOD</category>
                <pubDate>Tue, 23 Apr 2013 11:22:00 -0700</pubDate>
                <author>Owen Thomas</author>
            </item>
                    <item>
                <title><![CDATA[BYOD By The Numbers [Infographic]]]></title>
                <description><![CDATA[
                                        <img src="http://readwrite.com/files/styles/800_450sc/public/fields/Intel%20BYOD%20infographic%20lede%20image%202013-03-25%20at%204.44.jpg" />
                                        <p><a href="http://intel.ly/XoL2jP" target="_blank"><img style="display: block; margin-left: auto; margin-right: auto;" src="http://readwrite.com/files/Intel_contributed_300x60.jpg" alt="" /></a></p>
<p>Earlier pieces in this series on "<a href="http://readwrite.com/series/byod-grows-up/" target="_blank">BYOD Grows Up</a>" have explained how bring-your-own-device policies can be productivity enhancers, employee morale boosters and even, counterintuitively, security enhancers (because new policies can allow IT departments to push through long-overdue upgrades).</p>
<p>But enough with the logical arguments. Let's have a look at the hard numbers behind the BYOD trend, as laid out in this handy infographic jointly produced by Intel and ReadWrite. Be sure to let us know what you think in comments.&nbsp;</p>
<p><span class="embedded-Media-image img-caption-c">
				<img src="http://readwrite.com/files/RW_BYOD_Info_v2b_Blue.png" style="" />
			</span>
</p>
<p><strong>Read more in the series "BYOD Grows Up":</strong></p>
<ul>
<li><a href="http://readwrite.com/2013/03/05/why-processor-choice-matters-to-byod" target="_blank">Why Processor Choice Matters To BYOD</a></li>
<li><a href="http://readwrite.com/2013/02/26/security-basics-of-byod" target="_blank">Yes, It IS Possible To Have A Secure BYOD Program</a></li>
<li><a href="http://readwrite.com/2013/02/12/10-tips-to-make-byod-a-success-in-your-enterprise" target="_blank">10 Tips to Make BYOD A Success In Your Enterprise</a></li>
<li><a href="http://readwrite.com/2013/02/04/why-bring-your-own-device-byod-is-so-hot-right-now" target="_blank">Why Bring Your Own Device (BYOD) Is So Hot Right Now</a></li>
</ul>
<p><a href="http://intel.ly/XoL2jP" target="_blank"><img style="display: block; margin-left: auto; margin-right: auto;" src="http://readwrite.com/files/Intel_contributed_300x60.jpg" alt="" /></a></p>
                    ]]></description>
                <link>http://readwrite.com/2013/03/26/intel-byod-by-the-numbers</link>
                <guid>http://readwrite.com/2013/03/26/intel-byod-by-the-numbers</guid>
                <category>BYOD Grows Up</category>
                <pubDate>Tue, 26 Mar 2013 06:00:00 -0700</pubDate>
                <author></author>
            </item>
                    <item>
                <title><![CDATA[No More Wild West For Bring Your Own Devices]]></title>
                <description><![CDATA[
                                        <img src="http://readwrite.com/files/styles/800_450sc/public/fields/shutterstock_cowboy.jpg" />
                                        <p>In June 2007, Apple launched the first iPhone, marking a new era in corporate mobility. Before the fashionable mini-computer, people used smartphones for voice, texting and email. With the iPhone and its remarkable touchscreen users could also be entertained with music, video and games. Corporate executives became so attached to their hip device, they wanted to use it for business, so they bullied IT departments into providing access to email and corporate data. Employees soon joined their bosses and the bring-your-own-device trend began.</p>
<p>Six years later, what started out with one smartphone has grown into an army - far too much for the Wild West atmosphere of BYOD to continue as it has been. Many companies that have allowed BYOD will soon be pulling back on such freedoms. While BYOD may not die altogether, it will carry stricter restrictions meant to finally get this trend under control.</p>
<h2><strong>The Fate Of BYOD</strong></h2>
<p>"BYOD is clearly an important trend, but we expect it to plateau in the coming one to two years as enterprises decide that the cost and security issues associated with unlimited BYOD do not warrant the anarchy and increased support costs it has often caused," a recent report from tech analyst <a href="http://jgoldassociates.com/" target="_self">J.Gold Associates</a> said.</p>
<p>Where the iPhone use to be in a class by itself, the smartphone now competes with Android phones from Samsung, HTC, LG, Sony and <a href="http://www.android.com/devices/" target="_self">10 other vendors</a>.&nbsp; In addition, there is the BlackBerry and multiple devices running Microsoft's Windows Phone.</p>
<p>In 2010, Apple added the iPad to the chaos, creating a whole new market for tablet computers that brought lots of competitors from manufacturers in the Android camp.</p>
<p>From the beginning, BYOD was a challenge for IT departments, which had to wrestle with data security, device manageability, support and app control. Nevertheless, enterprises went along with the trend and the majority allowed at least some workers to use their personal devices for business.</p>
<p>But configuration, workflow and security issues were always making things difficult for IT. For instance, cyber-criminals saw an easy target in Android - with so many devices running older versions of the OS, hackers could target known vulnerabilities that were left unpatched by manufacturers and wireless carriers.</p>
<h2><strong>BYOD Limits</strong></h2>
<p>A survey of enterprises that allow employees to use their own notebooks, smartphones and tablets found that nearly half had experienced a security breach. As a result, more than 40% of the companies either restricted mobile data access or installed security software, <a href="http://www.trendmicro.com/cloud-content/us/pdfs/rpt_decisive-analytics_mobile_consumerization_trends_perceptions.pdf" target="_self">according to the poll</a> of more than 400 IT professionals and chief executives conducted by Decisive Analytics and released in August 2012.</p>
<p>Despite the breaches, only 12% of companies outright cancelled BYOD programs, an indication that most remained committed to providing flexibility to employees, while moving toward imposing rules.</p>
<p>Indeed, Gold found that companies are realizing "the current mostly wide-open,&nbsp;<em>laissez fare</em> approach to BYOD is not sustainable longer term, and that more controls and better strategy are needed."</p>
<p>As companies clamp down on BYOD, employees will likely find they will have to surrender their devices in order for IT departments to install technology to protect corporate data and communications. At the same time, manufacturers are providing more enterprise features in order to ensure their products get approved for work and play.</p>
<p>Samsung <a href="http://readwrite.com/2013/03/14/samsung-galaxy-s4-unveiled-spectacular-specs-innovative-features#feed=/search?keyword=samsung%20safe" target="_self">recently launched</a> technology called <a href="http://www.samsung.com/us/business/samsung-for-enterprise/index.html?cid=omc-mb-cph-1112-10000022" target="_self">SAFE</a> that the vendor boasts brings enterprise-class security to selected devices. People who buy the Galaxy S III or S 4 smartphones, the Galaxy Note II smartphone/tablet hybrid or the Note 10.1 tablet have the option of including SAFE, which provides a container for corporate data and email in order to separate it from personal applications.</p>
<p>BlackBerry, which has always been considered the gold standard in device security, has added similar data-separating technology in the <a href="http://readwrite.com/2013/01/30/years-in-the-making-blackberry-announces-two-new-devices#feed=/search?keyword=blackberry%20z10" target="_self">new Z10</a>.</p>
<p>In time, enterprises are likely to give the nod to those devices that can meet the demands of consumers and businesses and shun those that don't. So instead of BYOD, the policy of the future will be BYODA, or bring-your-own-device-for-approval.</p>
<p><em>Image courtesy of <a href="http://www.shutterstock.com">Shutterstock</a>.</em></p>
                    ]]></description>
                <link>http://readwrite.com/2013/03/25/byod-losing-steam</link>
                <guid>http://readwrite.com/2013/03/25/byod-losing-steam</guid>
                <category>Samsung</category>
                <pubDate>Mon, 25 Mar 2013 06:00:00 -0700</pubDate>
                <author>Antone Gonsalves</author>
            </item>
                    <item>
                <title><![CDATA[Why Processor Choice Matters To BYOD]]></title>
                <description><![CDATA[
                                        <img src="http://readwrite.com/files/styles/800_450sc/public/fields/_shutterstock_112366412.jpg" />
                                        <p><a href="http://intel.ly/XoL2jP" target="_blank"><img style="display: block; margin-left: auto; margin-right: auto;" src="http://readwrite.com/files/Intel_contributed_300x60.jpg" alt="" /></a></p>
<p class="p1">When IT managers build a Bring Your Own Device (BYOD) plan, chip architecture usually isn't high on their list of considerations. At first glance, it's easy to see why. After all, processors work or they don't – there isn't a lot of support to be done, right?</p>
<p class="p1">But there's more here than meets the eye. Thinking about the silicon that powers your supported devices can pay off big, providing better performance, security and manageability. It might even keep your legal department happy.&nbsp;</p>
<h2 class="p2"><span class="embedded-Media-image img-caption-r">
				<img src="http://readwrite.com/files/_shutterstock_110228837.jpg" style="" />
			</span>
Simplicity First</h2>
<p class="p2">There are plenty of exciting consumer devices to catch your employees' eyes, each with its own combination of processor, operating system and form factor. The task of a BYOD program is not necessarily to support <em>all</em> of them, but to choose the devices that best match customer needs, security concerns, business demands and available resources.&nbsp;</p>
<p class="p2">New devices introduce risk and complexity to every aspect of your ecosystem, from provisioning and training to security and support. The more varied the range of devices you allow, the greater the stress on your operations. The keys to meeting your goals are platform simplicity and consistency. Choosing to minimize deviation simplifies&nbsp;administration&nbsp;and allows IT to leverage as much existing infrastructure as possible. That choice starts with the processor.</p>
<h2 class="p2">The Processor Market</h2>
<p class="p2">Intel and ARM Holdings are the two primary competitors in the mobile chipset market. Intel's high-performing Core-series processors power the majority of laptops, Ultrabooks and notebooks, and its low-power Atom processors are gaining market share in tablets, smartphones and hybrid devices. ARM-based chips – most commonly found in tablets and smartphones – have recently begun to appear in laptops and hybrid devices.</p>
<p class="p2">Intel and ARM take very different approaches to chip production. ARM licenses its designs to semiconductor manufacturers, which then fabricate their own processors based on those designs. This flexibility is attractive to hardware companies, and allows ARM-based chips to power a wide assortment of devices, from appliances to servers.</p>
<p class="p2">The downside of that flexibility is inconsistency among ARM-based designs. Samsung and AMD both manufacture ARM-based chips, but their processors are substantially different. Intel follows a different business model, designing <em>and</em> producing all of its own silicon. This approach establishes a baseline across multiple manufacturers. This consistency is the reason Intel-powered Apple MacBooks are capable of running Windows natively, for example.&nbsp;</p>
<h2 class="p2">Application And OS Support</h2>
<p class="p2">Businesses run on applications, and processor choice can impact how (or whether) those applications run. The most obvious example is as basic as the operating system itself - most notably in Microsoft Windows.</p>
<p class="p2">When it launched Windows 8, Microsoft decided to support ARM-based chips for the first time. Windows RT, an operating system targeted at lower-cost consumer devices, like the Microsoft Surface, is the company's first ARM-based OS.</p>
<p class="p2"><span class="embedded-Media-image img-caption-c">
				<img src="http://readwrite.com/files/arm_intel_0.png" style="" />
			</span>
</p>
<p class="p2">While RT shares many of the same features as Windows 8 and Windows 8 Pro, it is not fully compatible with the entire Windows ecosystem.&nbsp;On its website, Microsoft <a style="line-height: 1.538em;" href="http://windows.microsoft.com/en-US/windows/compare">outlines the major differences</a> between RT and its other operating systems.&nbsp;For a consumer starting from scratch, Windows RT and applications available through the Windows Store may be more than enough.&nbsp;For enteprise IT managers, though, the differences become more troubling.</p>
<p class="p2"><span class="embedded-Media-image img-caption-l">
				<img src="http://readwrite.com/files/compatible.png" style="" />
			</span>
The most significant IT concern is the lack of support for "legacy" applications. Windows RT simply cannot run applications designed for previous versions of Windows. Depending on your existing investment in Windows apps and their business necessity, this can be an annoyance - or an absolute showstopper.</p>
<p class="p2">Other missing features, like Remote Desktop and Domain Join, may be less essential, but still add to the support burden for RT devices and could complicate efforts to create a simple, comprehensive management solution. In an all-Intel, Windows 8 environment, IT managers can leverage time-tested, existing management applications to extend their reach without writing custom software. As soon as one RT device is added to the mix, custom coding is required.</p>
<p class="p2">Not all consequences of a heterogeneous environment are technical. Employee-owned devices are already notorious for violating enterprise software licenses. When classes of employee devices come stocked with different software than your other devices, your existing license agreements may not provide coverage. For example, Windows RT comes pre-loaded with Office Home &amp; Student 2013 RT Preview. Unless a business anticipated supporting that device and took the necessary legal steps, using that program in a business setting could violate the software's licensing provisions.</p>
<h2 class="p2">Hardware-Based Assistance</h2>
<p>Chipsets rarely fail, for good reason. Once it's pressed and placed into a computer, a processor is essentially untouchable by applications, the operating system, or overzealous users. That's why hardware is the perfect place to store low-level security, management, and networking features.</p>
<p><span class="embedded-Media-image img-caption-r">
				<img src="http://readwrite.com/files/deepsafe.jpg" style="" />
			</span>
All Intel processors are built with management in mind, allowing administrators to reach below the operating system level for additional security and accessibility. For example, all current Intel Core processors support remote device locking through Intel Anti-Theft (AT) Technology. Unlike pure software Mobile Device Management (MDM) solutions, this approach will work even if a device is corrupted or rooted.</p>
<p>Newer third-generation Intel Core vPro processors (found in newer enterprise and small-business laptops, Ultrabooks and even some tablets)&nbsp;add two-factor PKI-based authentication with Intel Identity Protection Technology, and pre-boot system integrity verification through Intel Trusted Execution Technology (TXT). By using devices themselves as authentication tokens, IT can remove a layer of complexity and cost created by third-party tokens.</p>
<p>Intel builds on this hardware foundation with tightly integrated software. For example, on the security front, <a href="http://www.mcafee.com/us/solutions/mcafee-deepsafe.aspx">McAfee DeepSAFE</a> leverages vPro's TXT to install security monitoring software below the operating system, while <a href="http://www.mcafee.com/us/products/epo-deep-command.aspx">Deep Command</a> provides endpoint management tools for AT and other low-level features.</p>
<p>In some cases, security or management software can run only on complementary processors. In other situations, those processors simply run the software better. For example, Intel has tuned its newer Core processors to support the <a href="http://en.wikipedia.org/wiki/AES_instruction_set" target="_blank">AES-NI</a> instruction set, which speeds encryption products like <a href="http://www.mcafee.com/us/products/endpoint-encryption.aspx" target="_blank">McAfee Endpoint Encryption</a> to near real-time. Other compatible systems can certainly run the same program, but processors without AES-NI support could incur up to a 10X slowdown.</p>
<p>The processor is the heart of any device. It may not be the flashiest part of your BYOD strategy, but it's the foundation. A bit of time considering processor choice during your planning phase can save a lot of money and headaches down the road.</p>
<p>&nbsp;</p>
<p><em>Top two images courtesy of <a href="http://www.shutterstock.com" target="_blank">Shutterstock</a>.</em></p>
<p><a href="http://intel.ly/XoL2jP" target="_blank"><img style="display: block; margin-left: auto; margin-right: auto;" src="http://readwrite.com/files/Intel_contributed_300x60.jpg" alt="" /></a></p>
                    ]]></description>
                <link>http://readwrite.com/2013/03/05/why-processor-choice-matters-to-byod</link>
                <guid>http://readwrite.com/2013/03/05/why-processor-choice-matters-to-byod</guid>
                <category>BYOD Grows Up</category>
                <pubDate>Tue, 05 Mar 2013 10:30:00 -0800</pubDate>
                <author></author>
            </item>
                    <item>
                <title><![CDATA[BYOD Security: Yes, It IS Possible To Have A Secure Bring Your Own Device Program]]></title>
                <description><![CDATA[
                                        <img src="http://readwrite.com/files/styles/800_450sc/public/fields/shutterstock_126605534.jpg" />
                                        <p><a href="http://intel.ly/XoL2jP" target="_blank"><img style="display: block; margin-left: auto; margin-right: auto;" src="http://readwrite.com/files/Intel_contributed_300x60.jpg" alt="" /></a></p>
<p class="p1"><span style="line-height: 1.538em;"><span style="line-height: 1.538em;">Securing a Bring Your Own Device (BYOD) program means more than hoping endpoint authentication will keep out the bad guys.</span><span style="line-height: 1.538em;">&nbsp;</span></span></p>
<p class="p1">BYOD security is a big deal.&nbsp;In 2012, Intel&nbsp;<a style="line-height: 1.538em;" href="http://www.intel.com/content/dam/www/public/us/en/documents/white-papers/consumerization-enterprise-byod-peer-research-paper.pdf" target="_self">surveyed 3,000 IT decision makers and 1,300 end users</a>&nbsp;from Australia, Germany, South Korea and the United States to better understand their BYOD challenges. In three of the four countries, IT Managers considered a lack of security features the most important factor inhibiting device adoption. German IT managers ranked it second, after only government compliance.</p>
<p class="p1"><span class="embedded-Media-image img-caption-c">
				<img src="http://readwrite.com/files/byod_barriers.png" style="" />
			</span>
</p>
<p class="p1">BYOD may be inevitable, but the security concerns around it are well-founded.&nbsp;Some of IT's top BYOD security issues are beyond the ability of software-management tools to handle alone. These include</p>
<ul>
<li><strong>Unlicensed Software</strong>: Owner-installed applications on personal devices can violate enterprise license agreements, and others could compromise the integrity of your network.</li>
<li><strong>Unsecured Third-Party Connections</strong>: All smartphones and most tablets can connect to unsecured wireless networks, offering an unmonitored back channel.</li>
<li><strong>Malware</strong>: Devices can become infected outside the firewall through non-work usage.</li>
<li><strong>Rooted Devices</strong>: By gaining root access to mobile devices, users can bypass security restrictions and, in some cases, install rogue apps.</li>
<li><strong>Lost, Stolen, Or Damaged Devices</strong>: When devices disappear or go out of service unexpectedly, businesses can lose access to critical data. Furthermore, in addition to compromising local data, stolen devices can expose the entire network.</li>
</ul>
<p class="p1">Each device class and user type brings unique security challenges. To address them all, IT needs to leverage software&nbsp;<em style="line-height: 1.538em;">and</em> hardware solutions to lock down and manage devices while simultaneously securing the data itself. Here are three steps to help make the BYOD environment as secure as it can be.</p>
<h2 class="p1"><span class="embedded-Media-image img-caption-c">
				<img src="http://readwrite.com/files/BYOD.png" style="" />
			</span>
</h2>
<h2 class="p1">1: Educate Employees</h2>
<p class="p1">Curbing dangerous behavior is the first step toward reducing risk. Personal device management policies and procedures help reduce your company's risk with very low cost and complexity.&nbsp;In a review of <a style="line-height: 1.538em;" href="http://www.intel.com/content/dam/www/public/us/en/documents/best-practices/improving-security-and-mobility-for-personally-owned-devices-paper.pdf">its own, internal BYOD program</a>, Intel noted three types of employee education necessary to minimize risk:</p>
<ul>
<li><strong>User Training:</strong> Training end users about the content and ramifications of the employee service agreement and sharing best practices for data protection inside and&nbsp;outside&nbsp;of the office.</li>
<li><strong>Security-Desk Training</strong>: Training the Help Desk to answer questions quickly, efficiently, and within the allowable legal scope created by the program.</li>
<li><strong>Developer Training</strong>: Training developers to build secure data access and storage into their application code.</li>
</ul>
<p>With its favorable cost-benefit ratio, education is low-hanging fruit. In the IT manager survey referenced earlier, managers from all four participating countries that had begun securing their BYOD systems had most commonly implemented device management rules and an employee code of conduct. Employee education is a rewarding place to start, but – based on the fact that security concerns persist – it is obviously not a standalone solution.</p>
<h2 class="p1">2. Secure Your Data</h2>
<p>Tomorrow's devices could be completely different, future applications may handle data in entirely new ways and users will always find ways to use devices inappropriately. Future-proofing your network against the unknown requires a shift from protecting <em>devices</em> to protecting the <em>data</em> they use. Encrypting and backing up data is essential, but IT should also consider other, complementary methods of making sensitive information less accessible.</p>
<p>One popular software-based security method gaining steam in BYOD environments is the <em style="line-height: 1.538em;">Virtual Hosted Desktop</em>&nbsp;(VHD). VHD (sometimes&nbsp;known as Virtual Desktop Infrastructure, or VDI) creates a&nbsp;complete&nbsp;desktop image that includes an operating system, all applications and settings. The hosted desktop can be accessed from any compatible machine, and processing and storage take place on a central server.&nbsp;With enough network bandwidth and powerful hardware, this type of virtualized environment can combine acceptable performance with high-levels of security.</p>
<p>For high-security environments in which manageability and recovery trump everything else, it is often the default computing paradigm. But for most BYOD workers, VHD's drawbacks usually outweigh its advantages. VHD cannot take full advantage of all the features of local hardware, and it performs poorly on marginal networks – a major issue for remote workers. Furthermore, the desktop paradigm may break down on non-PC devices, limiting the available audience.</p>
<p class="p3"><em><span class="embedded-Media-image img-caption-r">
				<img src="http://readwrite.com/files/cotainerization.png" style="" />
				<span class="embedded-Media-image-caption">Example showing multiple containers on a single device.</span>
		</span>
Containerization</em>&nbsp;is way to address VHD's issues by placing native applications inside a safe zone on a device. A virtual machine manager (VMM) abstracts the container from the client hardware, boosting performance and reducing server strain by allowing client-side execution - while still improving security by isolating the container from certain functions, such as wireless network connections, USB ports or device cameras. Some virtual containers contain an entire operating system and productivity application suite, while others are purpose-built, single-function virtual devices that provide services like compliance monitoring or highly secure applications.</p>
<p class="p3">IT can create or purchase containerized applications for every platform, including smartphones, providing a much broader client base than VHD. Containerized applications also run at or close to the speed of fully native applications, and caching lets users continue working through network disruptions. However, containerization can compound development and administrative burdens, and since containerized apps require client-side storage, they are inherently less secure than fully virtualized solutions.</p>
<h2 class="p1">3. Use <em>Your</em> Hardware&nbsp;</h2>
<p class="p1">Selecting the right subset of hardware to support will bolster software-based security measures while lowering management costs. For example, if a company chooses to&nbsp;support&nbsp;a variety of Intel-based devices, IT could implement a 100% Windows-based environment. This would reduce the cost of developing and securing applications for different platforms while allowing IT to leverage Windows' existing security infrastructure, virtualization tools and anti-malware. And it would still allow employees a wide choice of devices to meet their individual needs.</p>
<p class="p1">On an application level, properly chosen hardware can augment your management tools. Mobile Device Management (MDM) software can identify devices that are out of compliance, but it has limited reach into rooted, broken, hacked or otherwise compromised systems.</p>
<p class="p1">Chipset-level security technologies like <a style="line-height: 1.538em;" href="http://www.intel.com/content/www/us/en/architecture-and-technology/vpro/vpro-technology-general.html">Intel VPro</a>&nbsp;(found in 3rd-generation Intel Core processors) allow MDM to reach underneath a managed device's operating system, performing remote wipes and pre-boot virus scans, regardless of the device's status.&nbsp;By providing access below the operating system, VPro allows&nbsp;administrators&nbsp;to correct problems by loading software patches and virus definitions, and its integrated support for <a href="http://en.wikipedia.org/wiki/Public-key_infrastructure" target="_blank">Public Key Infrastructure (PKI)</a> allows IT to use the devices themselves to authenticate users, removing the need for third-party software tokens or hardware-based authentication devices.&nbsp;<a style="line-height: 1.538em;" href="http://www.intel.com/content/www/us/en/architecture-and-technology/anti-theft/anti-theft-business-technology.html">Intel Anti-Theft</a>&nbsp;technology extends security features such as remote, OS-independent device locking and unlocking to earlier processors, as well as newer, VPro-compatible chipsets.</p>
<p class="p1">Finally, selecting the right hardware can make other software options more viable. For example, VHD's biggest drawback is performance. <a href="http://www.intel.com/content/www/us/en/virtualization/intel-virtualization-transforms-it.html">Hardware that accelerates common virtualization tasks</a> can mitigate that sluggishness, making the security of VHD more acceptable to users.</p>
<p class="p1">Securing BYOD will always be a challenge, but with the right planning and proper device selection, IT can make users' hardware work <em>for</em> the cause, rather than against it.</p>
<p class="p1">&nbsp;</p>
<p class="p1"><a href="http://intel.ly/XoL2jP" target="_blank"><img style="display: block; margin-left: auto; margin-right: auto;" src="http://readwrite.com/files/Intel_contributed_300x60.jpg" alt="" /></a></p>
<p class="p1">&nbsp;</p>
<p class="p1"><em>Lead image courtesy of <a href="http://www.shutterstock.com" target="_blank">Shutterstock</a>.</em></p>
                    ]]></description>
                <link>http://readwrite.com/2013/02/26/security-basics-of-byod</link>
                <guid>http://readwrite.com/2013/02/26/security-basics-of-byod</guid>
                <category>BYOD Grows Up</category>
                <pubDate>Tue, 26 Feb 2013 10:01:00 -0800</pubDate>
                <author></author>
            </item>
                    <item>
                <title><![CDATA[Box CEO Aaron Levie On Finding Mentors & Mixing Enterprise/Consumer Cultures [Video]]]></title>
                <description><![CDATA[
                                        <img src="http://readwrite.com/files/styles/800_450sc/public/fields/levie%202.jpg" />
                                        <p>Last Wednesday, ReadWrite Editor-in-in-Chief Dan Lyons sat down with 27-year-old&nbsp;<a href="https://www.box.com/" target="_blank">Box</a>&nbsp;CEO&nbsp;<a href="https://twitter.com/levie" target="_blank">Aaron Levie</a>&nbsp;to discuss the complex market of enterprise cloud technology in the third&nbsp;<a href="http://readwrite.com/series/readwrite-mix/" target="_blank">ReadWrite Mix</a>&nbsp;event in San Francisco.</p>
<p><strong>(See also <a href="http://readwrite.com/2013/02/18/readwrite-mix-box-ceo-aaron-levie-on-the-uncertain-landscape-of-enterprise-software-video" target="_blank">Box CEO Aaron Levie On The Uncertain Landscape Of Enterprise Software [Video]</a>)</strong></p>
<p>In the one-hour sit-down, Lyons and Levie covered surprisingly diverse topics, from Levie's personal life&nbsp;<a href="http://www.inc.com/magazine/201211/reshma-memon-yaqub/the-way-i-work-aaron-levie-box.html">as a&nbsp;notorious&nbsp;workaholic</a> to what it means to sit in the middle of the enterprise and consumer software landscape that has steadily begun to merge. Levie also showcased his sense of humor with descriptions of the companies he started as a teenager (Zazap, the fastest search engine on the Internet - except for Google), and spot-on caricatures of stuffy enterprise types to illustrate how he keeps his company loose and fast-moving.&nbsp;</p>
<p>This 2:28 video touches on Levie's thoughts on having grown up in the startup landscape with his high school friends, the laughable&nbsp;stereotype&nbsp;of enterprise software culture and seeking out mentors in Silicon Valley (Hint: There's no risk to to sending an email. So what if you don't get a response, he says).&nbsp;</p>
<p><iframe src="http://www.youtube.com/embed/Kij5fwww88Q" frameborder="0" width="853" height="480"></iframe></p>
                    ]]></description>
                <link>http://readwrite.com/2013/02/20/box-ceo-aaron-levie-on-seeking-out-mentors-mixing-enterprise-consumer-cultures-video</link>
                <guid>http://readwrite.com/2013/02/20/box-ceo-aaron-levie-on-seeking-out-mentors-mixing-enterprise-consumer-cultures-video</guid>
                <category>ReadWrite Mix</category>
                <pubDate>Wed, 20 Feb 2013 14:41:00 -0800</pubDate>
                <author>Nick Statt</author>
            </item>
                    <item>
                <title><![CDATA[The 5 Big Questions Dell Will Have To Answer To Survive]]></title>
                <description><![CDATA[
                                        <img src="http://readwrite.com/files/styles/800_450sc/public/fields/rsz_mike_dell_0.jpg" />
                                        <p>On Tuesday, Dell faced Wall Street analysts for what could be the last time, as <a href="http://readwrite.com/2013/02/05/dell-goes-private#feed=/author/markhachman" target="_self">Michael Dell and a collection of investors prepare to take the company private</a>. And though Dell Inc. reportedly exceeded Wall Street's expectations, the results were disappointing overall. And in some ways, that's a good thing.</p>
<p>Dell revenues fell 11% to $14.3 billion. Profits were down, too: 31% to $534 million. Dell's consumer business fell by a whopping 24% to $2.8 billion; The slogan "Dude, you're getting a Dell" is now a distant memory.</p>
<p>The earnings call is a unique event in American business; although chief executives occasionally deign to hear questions from business reporters, rarely do they sit down with their upper management and submit to questions about their past and future financial and operational performance. Calls following quarters in which a business dramatically exceeds expectations, taking a drink each time an analyst congratulates execs ("Great quarter, guys!") will usually result in a long nap under one's desk.</p>
<p>After a lousy quarter, on the other hand, analysts feel unusually liberated to ask the pointed questions that should always be asked. And - hurray! - some of them did their jobs on Tuesday.</p>
<p>Here are the five questions that Dell will need to answer going forward:</p>
<h2>1. Does Dell Belong In The PC Market?</h2>
<p>In many ways, this is the same question that Hewlett-Packard faced in the wake of Leo Apotheker's decision to shop the PC business, Meg Whitman's decision to retain it, and then the ultimate&nbsp;reorganization&nbsp;into a combined printer/PC business. With very little room for adding value besides bundling a printer with a PC, adding the crapware software that users hate, and striking out into relatively untested waters such as ultraportables and tablets, the answer seems to be: "Yes, but barely."</p>
<p>Dell's strengths are its XPS tier and its Latitude line of business PCs. But as Dell chief financial officer Brian Gladden noted, the growth continues to be in tablets and in the low-value desktop and notebook space - both areas where Dell, seeking higher profits, has consciously avoided.</p>
<h2>2. Is There An Opportunity To Refresh Older Corporate PCs?</h2>
<p>Yes, definitely. And that's the primary reason Dell won't bail out of the PC market any time soon - it has established longstanding ties with corporate America. This was one of the most telling quotes of the call:</p>
<p>"I think that’s really tough to get at, but the data that we’ve seen would suggest there’s still somewhere in the range of 40% of the corporate installed base for PCs that is XP or Vista that needs to be upgraded," <a href="http://seekingalpha.com/article/1204961-dell-management-discusses-q4-2013-results-earnings-call-transcript" target="_blank">Gladden said</a>. "So that’s, I think, pretty consistent with the data that we see for our installed base, and for what we hear from our corporate customers."</p>
<p>Corporate IT departments rarely, if ever, update a PC operating system without refreshing the hardware, too. Microsoft may have to worry about corporate customers turning to Windows 7 rather than 8, but Dell doesn't care either way. And with support ending for Windows XP in April 2014, Dell knows there's a windfall ahead.</p>
<p>"All the data that we’ve seen, all the conversations we’ve had with customers, would lead us to believe that there’s still a significant refresh activity that has to happen in the next 12-14 months," Gladden said.</p>
<h2>3. Is BYOD (Bring Your Own Device) The Answer?</h2>
<p>Yes. Or it was in December, when <a href="http://readwrite.com/2012/12/12/dell-says-byod-driving-corporate-interest-in-windows-8" target="_self">Michael Dell said exactly that</a>.&nbsp;</p>
<p>"And in the customer conversations that we’ve been having, the interest in Windows 8 is quite high, even with commercial customers, who would normally wait a few releases to adopt the new versions," Dell said. "What we’re seeing here is really an immediate need, because CIOs are worried about the ramifications of a BYOD world. With Windows 8 products... we’re pleased with the incredible experience that they expect, while you get the security and versatility and reliability that your enterprise really requires."</p>
<p>Since then, <a href="http://readwrite.com/2013/01/25/why-microsofts-earnings-report-doesnt-reveal-how-windows-8-is-doing" target="_self">Microsoft has reported terrific Windows 8 numbers</a>, although there has been some suspicion that the company hid behind previouslysold Windows 8 licenses. Still, Dell and the rest of the PC industry will certainly help try and make Windows 8 a success. Ultimately, however, Michael Dell has bet his farm on Windows, while other hardware makers, like Samsung, have diversified into Android and phones. Time will tell who made the right choice.</p>
<h2>4.) Will Server Customers Keep Buying From Dell, Or Roll Their Own?</h2>
<p>If you're not following the datacenter market that runs the cloud services we use and love, you're may be unaware that <a href="http://readwrite.com/2011/04/07/what-facebooks-opencompute-mea" target="_blank">Facebook has pioneered an industry-wide program called Open Compute</a>, which publishes detailed specifications on building your own servers via components from no-name manufacturers. Facebook recently said that a major European datacenter would be constructed entirely from these "white box" servers, and companies like <a href="http://www.rackspace.com" target="_blank">Rackspace</a> have also signed on.</p>
<p>Revenue-wise, Dell’s Server and Networking Business unit grew 11% in the last quarter, to $9.3 billion. But <a href="http://www.isigrp.com/main/index.html" target="_blank">ISI Group</a>'s Brian Marshall asked one of the key questions: given the Open Compute model, will the trend continue? Gladden waved off the question.</p>
<p>"It is relatively isolated to a few number of large-scale customers who can make the economics work, and given that, we’re still seeing strong growth in that business, and significant opportunities to continue to grow the hyperscale business," Gladden said. "So I don’t think it’s a new dynamic."</p>
<p>Gladden's right; <em>most</em> companies are not going to exert the time and effort to design their own servers, Open Compute or no. But over time, this may eat into the server businesses of Dell and others.</p>
<h2>5.) What Effects Will Virtualization, Consolidation and the Cloud Have On Servers?</h2>
<p>Virtualization, where a number of "virtual servers" can share computing resources, helps effectively consume underutilized servers, especially older hardware. Some of the older hardware can be retired, as data centers "consolidate" their hardware and run virtual machines on top of them to maximize their use. At the same time, as more cloud services are deployed, the number of servers they require goes up. Unfortunately, analysts have reported that the <a href="http://slashdot.org/topic/datacenter/dell-wins-in-servers-during-bland-q3/" target="_blank">number of servers sold has flattened</a> - the trends of consolidation and virtualization are holding down sales, and revenues are actually decreasing.</p>
<p>For a long time, notebooks became the escape route out of the quicksand of commoditization that has dragged the industry down. Then servers were the answer. Now, they're apparently sinking into the mud, too.</p>
<p>Dell may in fact continue to provide updates to Wall Street as it goes private; it hinted as much when it talked about a fiscal first-quarter earnings release. But as the company moves into the financial shadows, away from public scrutiny, it did not provide any guidance for the future. One can wonder whether its outlook is equally cloudy.</p>
                    ]]></description>
                <link>http://readwrite.com/2013/02/20/the-5-big-questions-dell-will-have-to-answer-to-survive</link>
                <guid>http://readwrite.com/2013/02/20/the-5-big-questions-dell-will-have-to-answer-to-survive</guid>
                <category>Dell</category>
                <pubDate>Wed, 20 Feb 2013 12:02:23 -0800</pubDate>
                <author>Mark Hachman</author>
            </item>
                    <item>
                <title><![CDATA[10 Tips to Make BYOD A Success In Your Enterprise]]></title>
                <description><![CDATA[
                                        <img src="http://readwrite.com/files/styles/800_450sc/public/fields/shutterstock_107609315.jpg" />
                                        <p><a href="http://intel.ly/XoL2jP" target="_blank"><img style="display: block; margin-left: auto; margin-right: auto;" src="http://readwrite.com/files/Intel_contributed_300x60.jpg" alt="" /></a></p>
<p class="p1"><a href="http://readwrite.com/2013/02/04/why-bring-your-own-device-byod-is-so-hot-right-now" target="_blank">Bring Your Own Device (BYOD)</a> is more than a fad. It's a movement toward a different kind of enterprise computing. BYOD requires a lot of planning and work, but businesses that embrace the change can find new efficiencies and actually increase security. Here are 10 tested tips to make your transition as smooth and productive as possible:&nbsp;</p>
<h2 class="p2">1. Engage Stakeholders In Discovery</h2>
<p class="p3">The biggest benefit of BYOD is a happier, more productive workforce. But that can't happen if your workers don't support the process. To get everyone on board, start with these four steps:</p>
<ul>
<li><strong>Identify Stakeholders</strong>: Create a manageable-but-representative committee of key influencers from all relevant departments. Be sure to include the CEO or a designated representative so you have buy-in and visible support from the top.</li>
<li><strong>Identify Targets:</strong>&nbsp;Using your committee, create and prioritize a list of necessary applications and desired use cases for personal devices.</li>
<li><strong>Take A Pulse:</strong> IT will ultimately decide which devices to support, but a quick poll of your committee (or your entire workforce, if that's possible) can identify promising places to start the evaluation.</li>
<li><strong>Work With Legal &amp; HR:</strong> Throughout the process, you'll need to work with your Legal and Human Resources departments to build your policies, service and support agreements and other procedures. Having a representative on the committee will help you identify potential complications before they become problems.</li>
</ul>
<h2 class="p2">2. Think TCO, Not ROI</h2>
<p class="p3">BYOD will not usually show cost-savings up-front. Don't plan on offsetting development costs with hardware savings, as personal devices will typically supplement your existing work devices, rather than replace them. That also means you should think twice before offering device stipends to employees.</p>
<p class="p3">Properly implemented BYOD can expand your device footprint at close to zero cost. In 2010, Intel implemented a personal device program. Three years later, it supports nearly 25,000 employee-owned smartphones, eliminating unsecured devices, increasing job satisfaction, and adding nearly an hour of productivity per employee, per day, with little to no increase in IT Service Desk calls. With no net impact to Intel's ongoing costs, initial investments in a well-designed BYOD program have been well worth it.</p>
<h2 class="p3">3. Think Users, Not Devices</h2>
<p class="p4">Traditional IT operations focus on maintaining and securing the PC device image, including the operating system, applications, data and personal settings. In a BYOD environment full of disparate devices, this strategy crumbles. On a conceptual level, the goal of a BYOD program should be a security model that follows the user across multiple device classes in a variety of situations. On a practical level, that requires a shift from securing device images to securing data, at rest and in transit.&nbsp;</p>
<h2 class="p4"><span class="embedded-Media-image img-caption-r">
				<img src="http://readwrite.com/files/shutterstock_88037794.jpg" style="" />
			</span>
4. Create BYOD Policies</h2>
<p class="p3">Even if you don't have plans to use personally identifiable information gleaned from your users' personal devices, it's a good idea to document your plans in a privacy policy. If you do plan to use such information, be very clear about how you plan to do so, how and where you plan to store the data, and when and how you will dispose of it. Your legal department will help you create the policy, and your HR representative will help implement procedures to keep your employees apprised of changes.</p>
<p class="p3">You should enlist the help of both departments in the creation of your usage policy, which will outline safe usage practices and prohibit any behavior that could put the company at risk. This policy will inform the content of the education program detailed in Step #9.</p>
<h2 class="p2">5. Evaluate Operating Systems First, Then Devices</h2>
<p class="p3">Giving users choices doesn't mean you have to support <em>everything</em>. In fact, if you're going to get the most out of your BYOD system, you shouldn't support everything.</p>
<p class="p3">Since devices change constantly and new form factors are continuing to emerge, beginning the selection with specific devices can be tricky and expensive. IT should first evaluate which operating systems it chooses to support, and work toward device support based on that decision. Selecting a dominant, uniform operating system (OS) environment can allow IT to leverage existing security and performance benefits. For example, most businesses use Intel-based Windows systems for their desktop and laptop systems. Extending that combination to other device types can help IT leverage existing security features (for example, Secure SMB, used by Windows 2012 and Windows 8), share common applications, and reduce support and training costs.</p>
<p class="p3">Within the subset of devices that support a chosen OS, IT should then select models with the most management-friendly hardware. For example,&nbsp;Intel Core vPro processors found in business-level laptops, Ultrabooks and other devices provide&nbsp;chipset-level device locking, auditing, and wiping. Embedded management features can increase security and eliminate the need to build or integrate redundant systems in software.&nbsp;</p>
<h2 class="p3"><span class="embedded-Media-image img-caption-r">
				<img src="http://readwrite.com/files/remote.gif" style="" />
			</span>
6. Maximize Commonalities</h2>
<p class="p2">Commonalities provide efficiencies. Wherever possible, strive to use the smallest possible number of tools. Sharing applications, hardware and vendors will save additional costs and minimize the number of integration points in your system. In descending order, IT should look to:</p>
<ul>
<li><strong>Shared Platforms:</strong> A common operating system and hardware configuration (for example, Intel-based processors running Windows 8) produces an almost identical support and maintenance case, even across multiple form factors. In situations where duplicating hardware is impossible, look for compatible systems from the same vendors, if possible. For example, a smartphone running Windows Phone 8 on an Intel Atom processor will still be able to share many of the same applications and remote management tools as Windows 8-based Ultrabooks running Intel Core processors.</li>
<li><strong>Mobile Application Management:</strong>&nbsp;MAM tools such as Microsoft ActiveSync can provide secure synchronization between servers and non-Windows devices, allowing users to access corporate assets through their native applications, while still enforcing your internal business and security rules. While these tools don't provide the full set of options available in a shared platform, this type of synchronization can allow&nbsp;participation&nbsp;of other device types, if necessary.</li>
<li><strong>Virtualization:</strong>&nbsp;With proper hardware, virtualization can provide a level playing field across many classes of devices and a number of disparate operating systems. It is not a panacea, since many form factors cannot support virtualization, and performance can suffer versus native environments, but it can be an effective method to pull other devices into the fold.</li>
</ul>
<h2 class="p3">7. Address Compliance</h2>
<p class="p2">Properly implemented BYOD can actually <em>help</em> businesses enhance their compliance efforts. Poorly implemented BYOD can destroy them. The key to BYOD compliance is understanding the weaknesses and exploiting the strengths of each device. For example, a smartphone's unsecured 3G or 4G connection could be considered a liability, but with properly implemented Mobile Device Management (MDM) locking down that feature and allowing access to the filesystem, the phone could be as secure as any PC on the network. Low-level hardware functionality that provides system control below the operating system layer is extremely helpful, as it allows&nbsp;IT to manage, wipe and potentially recover sensitive data from hardware that has fallen out of compliance or may not be properly functioning.</p>
<h2 class="p3">8. Evaluate Management And Deployment Tools</h2>
<p class="p2">Once you've selected supported devices and platforms, you can begin building your tools. Each project will require a different blend of security controls, but at a minimum, IT should evaluate:</p>
<ul>
<li>Two-factor authentication</li>
<li>Secure storage using encryption</li>
<li>Secure policy settings and restrictions</li>
<li>Secure data transmission to and from the network</li>
<li>Remote wipe capabilities (where possible)</li>
<li>Server-side virus protection</li>
<li>Mobile Device Management (MDM) software to secure monitor, manage and support mobile devices over the network</li>
</ul>
<p class="p2">Wherever possible, IT should leverage hardware-embedded&nbsp;options for greater reliability and enhanced security. For example, Intel Core vPro processors' embedded PKI tokens eliminate the need for third-party devices or software.</p>
<h2 class="p3">9. Create An Employee Education Program</h2>
<p class="p3">Employees understand their own devices and your corporate network, but they may be unaware of how to manage the union of the two. It's important to provide initial and ongoing education on new security risks and the proper conduct required to minimize them.&nbsp;For example, an employee's child may use work tablets in off-hours to view videos. In this case, simple steps, such as creating user profiles on the device and avoiding password-sharing can dramatically reduce the likelihood of accidental data loss.</p>
<h2 class="p3"><span class="embedded-Media-image img-caption-l">
				<img src="http://readwrite.com/files/shutterstock_114198172_sm.jpg" style="" />
			</span>
10. Assess Feedback</h2>
<p class="p2">User needs and consumer hardware continue to evolve, and so should your BYOD program. You won't get everything done in your first iteration, and you'll want to engage your user committee to review hits and misses to plan Phase Two. Having everyone involved keeps everyone accountable, and it ensures that IT will be seen as a critical business partner - not a roadblock.</p>
<p class="p2">&nbsp;</p>
<p class="p1">&nbsp;</p>
<p class="p1">&nbsp;</p>
<p><a href="http://intel.ly/XoL2jP" target="_blank"><img style="display: block; margin-left: auto; margin-right: auto;" src="http://readwrite.com/files/Intel_contributed_300x60.jpg" alt="" /></a></p>
<p class="p2"><em>Images courtesy of <a href="http://www.shutterstock.com" target="_blank">Shutterstock</a>&nbsp;and <a href="http://www.microsoft.com/" target="_self">Microsoft.com</a>.<br /></em></p>
                    ]]></description>
                <link>http://readwrite.com/2013/02/12/10-tips-to-make-byod-a-success-in-your-enterprise</link>
                <guid>http://readwrite.com/2013/02/12/10-tips-to-make-byod-a-success-in-your-enterprise</guid>
                <category>BYOD Grows Up</category>
                <pubDate>Tue, 12 Feb 2013 06:00:00 -0800</pubDate>
                <author></author>
            </item>
                    <item>
                <title><![CDATA[The Consumerization Of IT: 7 Ways To Seize The Business Opportunity]]></title>
                <description><![CDATA[
                                        <img src="http://readwrite.com/files/styles/800_450sc/public/fields/Powertothepeople.png" />
                                        <!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:TrackMoves/>
  <w:TrackFormatting/>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:DoNotPromoteQF/>
  <w:LidThemeOther>EN-US</w:LidThemeOther>
  <w:LidThemeAsian>JA</w:LidThemeAsian>
  <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
   <w:SplitPgBreakAndParaMark/>
   <w:EnableOpenTypeKerning/>
   <w:DontFlipMirrorIndents/>
   <w:OverrideTableStyleHps/>
  </w:Compatibility>
  <m:mathPr>
   <m:mathFont m:val="Cambria Math"/>
   <m:brkBin m:val="before"/>
   <m:brkBinSub m:val="&#45;-"/>
   <m:smallFrac m:val="off"/>
   <m:dispDef/>
   <m:lMargin m:val="0"/>
   <m:rMargin m:val="0"/>
   <m:defJc m:val="centerGroup"/>
   <m:wrapIndent m:val="1440"/>
   <m:intLim m:val="subSup"/>
   <m:naryLim m:val="undOvr"/>
  </m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"
  DefSemiHidden="true" DefQFormat="false" DefPriority="99"
  LatentStyleCount="276">
  <w:LsdException Locked="false" Priority="0" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Normal"/>
  <w:LsdException Locked="false" Priority="9" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="heading 1"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 1"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 2"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 3"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 4"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 5"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 6"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 7"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 8"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 9"/>
  <w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption"/>
  <w:LsdException Locked="false" Priority="10" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Title"/>
  <w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font"/>
  <w:LsdException Locked="false" Priority="11" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtitle"/>
  <w:LsdException Locked="false" Priority="22" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Strong"/>
  <w:LsdException Locked="false" Priority="20" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Emphasis"/>
  <w:LsdException Locked="false" Priority="59" SemiHidden="false"
   UnhideWhenUsed="false" Name="Table Grid"/>
  <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text"/>
  <w:LsdException Locked="false" Priority="1" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="No Spacing"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 1"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 1"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 1"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 1"/>
  <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision"/>
  <w:LsdException Locked="false" Priority="34" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="List Paragraph"/>
  <w:LsdException Locked="false" Priority="29" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Quote"/>
  <w:LsdException Locked="false" Priority="30" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Quote"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 1"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 1"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 1"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 1"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 1"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 2"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 2"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 2"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 2"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 2"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 2"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 2"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 2"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 2"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 3"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 3"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 3"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 3"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 3"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 3"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 3"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 3"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 3"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 4"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 4"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 4"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 4"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 4"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 4"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 4"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 4"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 4"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 5"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 5"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 5"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 5"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 5"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 5"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 5"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 5"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 5"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 6"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 6"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 6"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 6"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 6"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 6"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 6"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 6"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 6"/>
  <w:LsdException Locked="false" Priority="19" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis"/>
  <w:LsdException Locked="false" Priority="21" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis"/>
  <w:LsdException Locked="false" Priority="31" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference"/>
  <w:LsdException Locked="false" Priority="32" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Reference"/>
  <w:LsdException Locked="false" Priority="33" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Book Title"/>
  <w:LsdException Locked="false" Priority="37" Name="Bibliography"/>
  <w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading"/>
 </w:LatentStyles>
</xml><![endif]-->
<p><em style="line-height: 1.538em;">Guest author Christian Buckley is product evangelism director at </em><a style="line-height: 1.538em;" href="http://www.axceler.com/"><em>Axceler</em></a><em style="line-height: 1.538em;">, a designer of collaboration solutions.</em></p>
<p class="p1">Users have wrested more control from the information technology department than ever before. Now that they have become tech-savvy in their off-hours, they're demanding work products with the same degree of usability as their home devices. Better yet, they want to bring their home gear to work (Bring Your Own Device, or BYOD).</p>
<p class="p1">The consumerization of IT means empowerment for users, a (potential) headache for tech professionals, and an opportunity for third parties that offer products and services that increase the productivity of non-technical consumers.</p>
<p class="p1">Here are seven tips for third parties who looking to jump on the trend:</p>
<p class="p1"><strong>1. Data Anytime, Anywhere.</strong> Ten years ago, controlling data access was the central piece of intellectual property management. Today, companies are weighing the legal and competitive risks against the productivity benefits of allowing data to flow more freely to employees, partners and customers. Enterprises will need products that allow the protection of the most highly sensitive data while letting subsets of the rest of it to become more accessible.&nbsp;</p>
<p class="p1"><strong>2. Pick A Tool, Any Tool.</strong> Today’s world is app-centric. Companies hoping to break into the enterprise market should look to use apps as an entry point - the most common categories are mobile apps, browser add-ons or&nbsp;some flavor of Web service. But beware, the vibrancy of the third-party app market means that users can find three or four different competitive offerings in just about any category. To be successful, third parties have to find a way to distinguish themselves from the pack - either through technical innovation, superior user experience or brilliant marketing.</p>
<p class="p1"><strong>3. Bring Your Own Device (BYOD).</strong> Users are no longer married to a single device. They’ve become polygamous: depending on circumstances, they'll use smart phones, tablets, laptops or PCs. And they want to use device they’re most comfortable with - often one they’ve purchased themselves – at work. Smart organizations caught on early to the BYOD trend and have expanded the array of devices they support. To do that, they’ll need tools able to work across multiple platforms, applications and services &nbsp;to help them manage the newly expanded variety of devices they've pledged to support.</p>
<p class="p1"><strong style="line-height: 1.538em;">4. Let Me In</strong>. Users expect to connect to work, while at the same time staying plugged into their private circle of friends and activities. And they want to do it with a minimum of hassle. Personal and corporate applications should be designed with a minimum of security checkpoints so users can toggle easily between them. And applications should be able operate independently without either impinging on the other.</p>
<p class="p1"><strong>5. Be Social.</strong> This means more than using Facebook-like features for workplace chat. Applications and networks should be designed so that data can be shared across environments and conversations can take place between users on competing platforms. An interconnected world will prove challenging. And that opens up a myriad of opportunities for tool providers and integrators to differentiate their products with innovative social features.</p>
<p class="p1"><strong>6. The Business Proposition.</strong> The next generation of IT tools will be built for lay users, not techies. Increasingly, complex business tools offer easy-to-navigate, intuitive interfaces. Keep in mind that the person who now writes checks for new gear is a line of business manager and will expect the same level of usability that consumers do.</p>
<p class="p1"><strong>7. I Can Do It Myself, Thank You</strong>. Much of the consumerization wave has to do with self-service. The IT team decides which piece of hardware the company purchases, but have little control over what is installed and how those machines are configured. Smart solution providers will create tools with the individual user in mind. Make a user happy and the eventual result may be an enterprise sale. or the effective equivalent as users bring it into the enterprise from the bottom up.</p>
<h2 class="p1">Power To The People</h2>
<p class="p1">The consumerization of IT is the ultimate in user empowerment. Increasingly tech-savvy users want their managers to tell them what they need to do, but <em>not</em> how to do it. They want to pick the tools and processes they believe will best help them to meet goals. Those offering products and services that let them do that with a minimum of fuss will be the biggest winners.</p>
<p class="p1"><em>Image courtesy of <a href="http://www.shutterstock.com/" target="_blank">Shutterstock</a>.</em></p>
                    ]]></description>
                <link>http://readwrite.com/2013/02/06/the-consumerization-of-it-7-ways-to-seize-the-business-opportunity</link>
                <guid>http://readwrite.com/2013/02/06/the-consumerization-of-it-7-ways-to-seize-the-business-opportunity</guid>
                <category>enterprise IT</category>
                <pubDate>Wed, 06 Feb 2013 06:00:00 -0800</pubDate>
                <author>Christian Buckley</author>
            </item>
                    <item>
                <title><![CDATA[Why Bring Your Own Device (BYOD) Is So Hot Right Now]]></title>
                <description><![CDATA[
                                        <img src="http://readwrite.com/files/styles/800_450sc/public/fields/shutterstock_87232645.jpg" />
                                        <p><a href="http://intel.ly/XoL2jP" target="_blank"><img style="display: block; margin-left: auto; margin-right: auto;" src="http://readwrite.com/files/Intel_contributed_300x60.jpg" alt="" /></a></p>
<p>Since the invention of the laptop, employees have been trying to bring their personal devices to work. And ever since that first employee-owned laptop crossed the corporate threshold, the IT department has almost always said "No way you're bringing that un-supported, un-secure, un-productive <em>consumer</em> machine into my nice clean business network."</p>
<p>Until recently, the idea that you might Bring Your Own Device (BYOD) to work has filled IT folks with fears of: &nbsp;&nbsp;</p>
<ul>
<li>Rootkits and other malware</li>
<li>New operating systems to support</li>
<li>Proprietary, insecure applications</li>
<li>No remote management</li>
<li>Incompatibility with enterprise security and encryption</li>
</ul>
<p>For the vast majority of businesses, securing, managing, and supporting user-sourced devices just wasn't worth the potential upside. In some heavily regulated environments, it wasn't even a <em>possibility</em>.</p>
<h2 class="MsoNormal" style="margin-top: 12.0pt; margin-right: 0in; margin-bottom: 12.0pt; margin-left: 0in; line-height: 15.0pt;">BYOD Grows Up</h2>
<p>But times have changed.&nbsp;As shifting cultural norms and new devices have increased employee pressure for BYOD, the industry has finally responded with the tools IT needs to safely open its doors to personal devices.</p>
<p>Let's not kid ourselves. BYOD is&nbsp;still a major undertaking. But over the past few years, companies like Intel have made huge improvements to consumer technologies that make BYOD a very real, manageable possibility. Low-level hardware&nbsp;enhancements&nbsp;have extended the reach of operating systems and device-management applications, making it possible for IT to maintain order while still letting users have the machines they want.</p>
<p>With a bit of planning and work, IT can now allow employees to use many of the personal devices they actually enjoy - without sacrificing security or causing too much disruption. Here's a look at some of the most important factors turning BYOD from an IT pain-in-the-neck into an opportunity.</p>
<h2 class="MsoNormal" style="margin-top: 12.0pt; margin-right: 0in; margin-bottom: 12.0pt; margin-left: 0in; line-height: 15.0pt;">The Case for BYOD</h2>
<p>BYOD isn't just about "cool" anymore. For many workers, it's a necessity.</p>
<p>Many Gen X and Millennial workers and customers prefer video chat, social networks, and text messages to email. They expect near-constant availability and immediate responses, and even office-based employees are doing more remote work at off-hours. Businesses support this, expecting workers to be available at all times, yet most employers issue only a desktop or laptop PC. That disconnect is precisely why groups like Field Sales tend to bypass established procedures, and it's dangerous for everyone involved.</p>
<p>The mobile device landscape changes every day. Tablets, Ultrabooks, and an evolving line of hybrid devices fill the gap between laptops and smartphones. With constant media coverage of consumer technology rivaling or surpassing the capabilities of enterprise hardware and software, many employees are convinced that they, not IT, can identify the best tools for their jobs. Modern workers know exactly what they want, but traditional enterprise provisioning and purchasing systems often can't keep up. Managing employee devices can bridge that gap and rein in rogue behavior before it starts.</p>
<h2 class="MsoNormal" style="margin-top: 12.0pt; margin-right: 0in; margin-bottom: 12.0pt; margin-left: 0in; line-height: 15.0pt;">The Hardware Industry Responds</h2>
<p><span class="embedded-Media-image img-caption-r">
				<img src="http://readwrite.com/files/shutterstock_87368453_0.jpg" style="" />
			</span>
Simply put, consumer mobile devices have gotten better during the last few years, and IT doesn’t have a good reason to dismiss them anymore.</p>
<p>Consumer devices have long outperformed equally priced business machines, but they've usually sacrificed stability, reliability and security to do so.&nbsp;In the last few years, though, the hardware industry has made up a lot of that ground.&nbsp;</p>
<p>Features that used to require specialized, custom hardware are now supported in off-the-shelf devices. Mobile device processors now offer low-level features that protect against malware and reduce the complexity of implementing a secure environment. For example, all current Intel Core processors support remote device locking through Intel Anti-Theft Technology. Newer Intel Core vPro processors (found in newer enterprise and small-business laptops, Ultrabooks and even some tablets)&nbsp;add two-factor PKI-based authentication with Intel Identity Protection Technology, and pre-boot system integrity verification through Intel Trusted Execution Technology. These features offload a large amount of the complexity needed to build and maintain a secure system. And since they're embedded at the chipset - applications, malware and nosy users can't alter them.</p>
<h2>Software Reduces Complexity</h2>
<p>Consumer operating systems have matured, too. For example, we've moved beyond the days of the single enterprise smartphone or tablet operating system. There are now several viable options for each device class, allowing IT departments to base their choices on synergies across multiple platforms, the ease of integration with other devices and total cost of ownership (TCO) calculations.</p>
<p><span class="embedded-Media-image img-caption-r">
				<img src="http://readwrite.com/files/windows-microsoft.png" style="" />
			</span>
As the mobile device market has exploded with new manufacturers and form factors, operating system vendors have provided platform consistency. For example, it's now completely plausible for an enterprise to run Windows across all of its servers, desktops, tablets, smartphones, and hybrid devices, while still retaining user choice. A common OS allows IT to share applications from desktops to smartphones, lower training and management costs, and extend the security and performance advantages of a shared infrastructure without having to sacrifice device variety.&nbsp;</p>
<p>At the same time, its easier than ever to mix operating systems as needed.</p>
<h2 class="MsoNormal" style="margin-top: 12.0pt; margin-right: 0in; margin-bottom: 12.0pt; margin-left: 0in; line-height: 15.0pt;">The BYOD Payoff</h2>
<p>Of course, writing a BYOD policy and building the systems and procedures to support it still takes work. Is it justified?</p>
<p>If you’re willing to expand your thinking beyond this year’s balance sheet, the answer can be a definite “yes.”</p>
<p>Quantifying return on investment for BYOD implementations can be tough. IT should not plan to recoup the costs of a BYOD project through immediate hardware or staff savings. On the other hand, BYOD can create happier, more productive workers and a more secure workplace.&nbsp;</p>
<p>According to an <a href="http://www.intel.com/content/dam/www/public/us/en/documents/best-practices/improving-security-and-mobility-for-personally-owned-devices-paper.pdf">internal review of Intel's own BYOD program</a>, BYOD creates a huge boost in employee productivity. In 2011, the 17,000 Intel employees bringing personal devices to work reported an average productivity increase of 57 minutes per day. That helps create a halo for IT, positioning the department as a productivity enabler instead of a roadblock, which can help smart CIOs collect political capital for other projects.</p>
<p>While it may sound counterintuitive, a properly implemented BYOD program can actually <em>increase</em> enterprise security by locking down corporate assets and forcing overdue security updates. In the case study above, Intel assigned higher security scores to employee-owned mobile devices than to many of its internal PCs, since all of the mobile devices were subject to rigorous compliance monitoring.</p>
<p>BYOD is here because it needs to be, and because IT finally has the tools to make it make sense.</p>
<p>&nbsp;</p>
<p><em>Hybrid image courtesy of Microsoft. Other images courtesy of <a href="http://www.shutterstock.com" target="_blank">Shutterstock</a>.</em></p>
<p><!--EndFragment--></p>
<p><a href="http://intel.ly/XoL2jP" target="_blank"><img style="display: block; margin-left: auto; margin-right: auto;" src="http://readwrite.com/files/Intel_contributed_300x60.jpg" alt="" /></a></p>
                    ]]></description>
                <link>http://readwrite.com/2013/02/04/why-bring-your-own-device-byod-is-so-hot-right-now</link>
                <guid>http://readwrite.com/2013/02/04/why-bring-your-own-device-byod-is-so-hot-right-now</guid>
                <category>BYOD Grows Up</category>
                <pubDate>Mon, 04 Feb 2013 14:15:00 -0800</pubDate>
                <author></author>
            </item>
                    <item>
                <title><![CDATA[ReadWrite Survey Results: What A Typical BYOD Program Really Looks Like]]></title>
                <description><![CDATA[
                                        <img src="http://readwrite.com/files/styles/800_450sc/public/fields/shutterstock_107808977_tablet-smartphone.jpg" />
                                        <p class="p1"><a href="http://readwrite.com/search?keyword=byod" target="_blank">BYOD</a> - Bring Your Own Device - is one of the hottest trends in IT right now. The idea is to let employees use their own preferred smartphones, tablets and/or laptops, and have the company's technology department allow them to connect to company networks and applications, as well as make sure they're secure and supported.</p>
<p class="p1">But what are companies <em>really</em> doing about BYOD?</p>
<p class="p1">To find out, ReadWrite ran a survey of our readers. (See <a href="http://readwrite.com/2012/12/18/is-bring-your-own-device-byod-changing-your-company-survey">Is Bring Your Own Device - BYOD - Changing Your Company?</a>)</p>
<p class="p1">The survey attracted 261 responses, and 176 completed every question. While this is far from a scientific or statistically valid study, the results do offer some intriguing data points as to how BYOD is being used.</p>
<p class="p1">The results painted a remarkably clear picture of how and why companies are using BYOD:</p>
<p class="p1"><strong>1. BYOD Is Popular Among Companies.</strong> Half (49%) of the companies responding let all employees use personal devices for work purposes. Another 33% let some employees do so. Only 18% don't support BYOD. Of course, this was a BYOD survey, so it's no surprise that this group was interested. But the percentages were higher than I'd expected.</p>
<p class="p1"><strong>2. BYOD Is Less Popular Among Employees.</strong> At 44% of companies, fewer than 25% of employees participate in the BYOD program. A quarter to one half of employees BYOD in 27% of companies. More than 50% participate in a fifth of the BYOD companies, and the policy is mandatory for everyone at 10% of companies.</p>
<p class="p1"><strong>3. BYOD Isn't New.</strong> Surprisingly, 41% of the BYOD companies began their programs more than two years agao. Another 22% started more than a year ago. Despite the hype heating up, only 12% have moved to BYOD in the last 3 months.</p>
<p class="p1"><strong>4. BYOD Has Widespread Benefits.</strong> Asked what the prime justification for BYOD, respondents were fairly evenly split among Employee Satisfaction (29%), Employee Productivity (29%) and Saving Money for the Company (23%). The rest didn't know or weren't sure.</p>
<p class="p1"><strong>5. Paying For BYOD Is Up To The Employees.</strong> Companies pay for the BYOD devices at less than 10% of the companies responding. Workers and the company share costs at another quarter (27%) of responding organizations. Only 10% of companies buy the devices for their employees.</p>
<p class="p1"><strong>6. Employees Who BYOD Are On Their Own For Support.</strong> Support is one of BYOD's big issues, but most companies (56%) simply leave it up to employees. Another third (31%) supply internal IT support, while just 6% employ outsourced support for employee-owned devices.</p>
<p class="p1"><strong>7. BYOD Is All About Smartphones.</strong> At the vast majority of BYOD companies (82%), smartphones are the most popular employee-owned devices. Tablets are often BYOD at half of the companies, while laptops get the BYOD treatment at about a third of companies (33%).</p>
<p class="p1"><strong>8. Security Is The Biggest BYOD Concern.</strong> This one wasn't a surprise. Almost half (49%) named security as the biggest BYOD issue - and another 5% worried about lost or stolen devices. Management and support were the top issues for 16% of respondents, while performance problems troubled 7%. Not surprisingly based on Number 5 above, cost was a concern for less than 5% of companies.</p>
<p class="p1"><strong>9. Ensuring BYOD Security Is A Multi-Dimensional Job.</strong> Usage of various security measures were all over the map, with multiple responses showing that many comapnies were using more than one approach. Top security tactics included limiting device access to networks (38%), requiring employees to lock screens (37%) and VPNs and virtual desktops (31%). Security software (24%), enforced updates (24%) and mobile application management software (21%) were also widely used. There was less enthusiasm for making employees report issues quickly (17%), restricting downloads (11%) and building a internal app store (7%). In a victory for employee privacy, only 6% of respondents said they installed location tracking software on employee devices.</p>
<p class="p1">What does it all add up to? BYOD isn't some Johnny-come-lately concept being pushed on reluctant IT departments by gadget-loving workers. Instead, it seems more like a viable business strategy for letting workers have access to the right tools without having to spend a fortune.</p>
<p class="p1">There are plenty of concerns, but overall, BYOD participants seem pretty happy about how things are going.</p>
<p class="p1"><em>Image courtesy of <a href="http://www.shutterstock" target="_blank">Shutterstock</a>.</em></p>
                    ]]></description>
                <link>http://readwrite.com/2013/01/18/readwrite-survey-results-what-a-typical-byod-program-really-looks-like</link>
                <guid>http://readwrite.com/2013/01/18/readwrite-survey-results-what-a-typical-byod-program-really-looks-like</guid>
                <category>BYOD</category>
                <pubDate>Fri, 18 Jan 2013 05:00:00 -0800</pubDate>
                <author>Fredric Paul</author>
            </item>
                    <item>
                <title><![CDATA[January 2 = BYOD’s Big Day: How Will IT And The Cloud Keep Up?]]></title>
                <description><![CDATA[
                                        <img src="http://readwrite.com/files/styles/800_450sc/public/fields/Fusion-io.png" />
                                        <p class="p1"><em>Guest author Mat Young is senior technical director at <a href="http://www.fusionio.com/" target="_blank">Fusion-io</a>.</em></p>
<p class="p1">Many enterprise employees no doubt received new tablets this Holiday season. And many are likely to bring them to work on Wednesday, January 2, 2013 - perhaps the biggest day ever for the Bring Your Own Device (BYOD) trend.</p>
<p class="p1">Will corporate IT be prepared for the challenge?</p>
<p class="p2">Managing BYOD devices like tablets poses many security and compliance challenges. <a href="http://blogs.forrester.com/frank_gillett/12-04-23-why_tablets_will_become_our_primary_computing_device">Forrester has predicted that that tablets would become the primary computing devices in 2013</a>, so it will be instructive to watch how corporate IT policies evolve to support or discourage BYOD with tablets. (Of course, some lucky workers will end up with tablets provided to them by their employers!)</p>
<p class="p1">Recent research has noted that - not surprisingly -&nbsp;<a href="http://blog.hubspot.com/blog/tabid/6307/bid/27932/30-New-Tablet-Usage-Stats-Marketers-Should-Know-Infographic.aspx" target="_blank">many tablet users use their devices for email</a>. With traditional data-storage infrastructure, the added workload of all these new tablets connecting into corporate networks could create quite a strain on applications like <a href="http://www.microsoft.com/exchange/en-us/default.aspx" target="_blank">Microsoft Exchange</a>. If organizations are running virtualized infrastructure or <a href="http://en.wikipedia.org/wiki/Desktop_virtualization" target="_blank">virtual desktops (VDI)</a>, delivering consistent performance gets even more complicated.</p>
<p class="p1">Easy-to-use apps with data served from the cloud make tablets especially attractive to mobile workers. This has led to a boom in mobile applications. It will also be interesting to track how download and adoption rates for mobile apps delivered through the cloud are impacted by the BYOD influx in 2013.</p>
<p class="p1">Keeping on top of network performance will be a critical requirement for IT teams watching to see how the BYOD influx affects their infrastructure. One possibility is to boost the use of flash memory on the server side as well as on the device side.</p>
<p class="p1">From cell phones to tablets, NAND flash powers just about every mobile device. But investing in flash on the server-side as well can help improve performance of specific applications and remove overall bottlenecks.</p>
<p class="p1">As BYOD brings ever-more mobile devices into corporate environments, IT faces a very real challenge to keep up. The proud owners of all those new tablets will demand nothing less.&nbsp;</p>
                    ]]></description>
                <link>http://readwrite.com/2013/01/02/january-2-byod-big-day-how-will-it-and-the-cloud-keep-up</link>
                <guid>http://readwrite.com/2013/01/02/january-2-byod-big-day-how-will-it-and-the-cloud-keep-up</guid>
                <category>BYOD</category>
                <pubDate>Wed, 02 Jan 2013 03:00:00 -0800</pubDate>
                <author>Mat Young</author>
            </item>
                    <item>
                <title><![CDATA[The 6 Technologies That Mattered Most To Small Business In 2012]]></title>
                <description><![CDATA[
                                        <img src="http://readwrite.com/files/styles/800_450sc/public/fields/shutterstock_93522841.jpg" />
                                        <p class="p1">Even though 2012 was a tough year overall for small businesses - the stubbornly slow economy didn't help - technology improvements continued to offer hope of lowering costs, boosting efficiency, increasing sales and opening new markets. To the extent that they could find the cash, investing in technology remained a top priority for savvy smaller companies.</p>
<p class="p1">These half-dozen technologies are the ones small businesses were most involved with in 2012:</p>
<h2 class="p1">1. Social Media Surged</h2>
<p class="p1">In a survey by VerticalResponse, more than one-third of small business owners wished they could spend <em>less</em> time on social media (nearly half spend 6+ hours per week). But they can’t, because that’s where the customers are. A recent <a href="http://nmincite.com/download-the-social-media-report-2012/">report by NM Incite</a> found Internet users spend more time on social networks than on any other type of website. 2012’s breakout star, Pinterest, showed a whopping 1,047% increase in unique visitors — so if you haven’t gone there yet, you might want to. However, Facebook is still the top site, used by 90% of entrepreneurs, according to VerticalResponse, and 152.2 million unique visitors, according to NM Incite.</p>
<h2 class="p1">2. Consumers Went All-In On Mobile</h2>
<p class="p1">The rabid adoption of tablets over the 2011 holiday season gained even more momentum in 2012. Smart retailers took advantage of the tablet’s leisure-time nature to create customized mobile shopping experiences for couch-surfers. On Black Friday, <a href="http://www.prnewswire.com/news-releases/early-promotions-drive-record-online-sales-for-thanksgiving-fuels-black-friday-retail-surge-reports-ibm-180691231.html">IBM reports</a>, mobile sales topped 16%, up from 9.8% last year, with the iPad dominating. Small businesses also took advantage of mobile marketing to reach customers on their smartphones. <a href="http://www.pewinternet.org/Reports/2012/Cell-Activities/Main-Findings/Cell-Phone-Activities.aspx">The Pew Internet &amp; American Life Project</a> reports 56% of mobile users go online with their phones and 50% use them for email; both figures more than doubled compared to two years ago. Some 84% of small businesses that used mobile marketing found it increased new business, a <a href="http://www.smallbusinesscomputing.com/News/Marketing/small-business-mobile-marketing-attracts-new-customers.html">Web.com and Lab42 study</a> found.</p>
<h2 class="p1">3. Mobile Dominated Business</h2>
<p class="p1">In 2012 savvy businesses of all sizes incorporated tablets into the workplace as presentation tools, payment devices or simply to entertain customers (for example, providing iPads for customers to place orders or entertain kids in restaurants). In The Mobility Edge: CDW’s 2012 Small Business Mobility Report, 75% of mobile users report mobile devices have become “critical” to their jobs, and 67% say without mobile devices, their businesses would be less competitive.</p>
<h2 class="p1">4. BYOD Arrived</h2>
<p class="p1">Bring Your Own Device has long been business as usual for cash-strapped startups, but in 2012 the trend took hold at companies of all sizes. Since many job seekers consider being able to bring their own device a workplace perk, BYOD could even give your small small business an edge in competing with bigger companies whose IT managers don’t like BYOD.</p>
<h2 class="p1">5. Crowdsourcing Continued</h2>
<p class="p1">Technological changes sped the growth of crowdsourcing, a boon to many small startups, this year, the <a href="http://content.dell.com/us/en/corp/d/corp-comm/the-evolving-workforce">Dell Evolving Workforce reports</a>. Contractors and even customers increasingly contributed to small business solutions, doing everything from coding to innovating new product and service ideas.</p>
<h2 class="p1">6. The Clouds Rolled In</h2>
<p class="p1">2012 was the year cloud services went from mysterious to mainstream—or as <a href="http://www.smb-gr.com/wp-content/uploads/2011/pdfs/2012_SMB_Group_Predictions.pdf">SMB Group</a> put it, “as normal rather than cutting edge.” More and more, small businesses and startups turned to cloud storage and solutions to streamline operations and save money. At the same time, consumers’ increasing comfort level with the cloud opened up a whole new world of startup possibilities.</p>
<p class="p1">What mattered to your small business most in 2012?</p>
<p class="p1">&nbsp;</p>
<p class="p1"><em>Image courtesy of <a href="http://www.shutterstock.com" target="_blank">Shutterstock</a>.</em></p>
                    ]]></description>
                <link>http://readwrite.com/2012/12/19/the-6-technologies-that-mattered-most-to-small-business-in-2012</link>
                <guid>http://readwrite.com/2012/12/19/the-6-technologies-that-mattered-most-to-small-business-in-2012</guid>
                <category>2012 Trends</category>
                <pubDate>Wed, 19 Dec 2012 11:00:00 -0800</pubDate>
                <author>Rieva Lesonsky</author>
            </item>
                    <item>
                <title><![CDATA[Is Bring Your Own Device - BYOD - Changing Your Company? [Survey]]]></title>
                <description><![CDATA[
                                        <img src="http://readwrite.com/files/styles/800_450sc/public/fields/shutterstock_47716741_bottles.jpg" />
                                        <p>The growing trend of Bring Your Own Device (BYOD) to the workplace is having dramatic effects on corporate IT plans, policies and staffing. That's the conventional wisdom, anyway.</p>
<p>But ReadWrite wants to know what's really happening. How is <em>your</em> company dealing with employees using their own devices for work purposes? Why did you decide to do it? What are your biggest concerns? How is it working out so far?</p>
<p>That's why we put together this little 9-item questionnaire: <a href="https://www.surveymonkey.com/s/PGV5B6R" target="_blank">ReadWrite BYOD Survey</a>. (There are also a few demographic questions at the end, so we can better analyze the results.)</p>
<p>Once we have enough responses, we'll put together a post detailing the insights we gained, so if you'd like to share additional BYOD thoughts in the comments, we're all ears.</p>
<h2>Take the <a href="https://www.surveymonkey.com/s/PGV5B6R" target="_blank">ReadWrite BYOD Survey</a> now!</h2>
<div id="surveyMonkeyInfo">&nbsp;</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div><em>Image courtesy of <a href="http://www.shutterstock.com" target="_blank">Shutterstock</a>.</em></div>
                    ]]></description>
                <link>http://readwrite.com/2012/12/18/is-bring-your-own-device-byod-changing-your-company-survey</link>
                <guid>http://readwrite.com/2012/12/18/is-bring-your-own-device-byod-changing-your-company-survey</guid>
                <category>BYOD</category>
                <pubDate>Tue, 18 Dec 2012 06:00:00 -0800</pubDate>
                <author>Fredric Paul</author>
            </item>
            </channel>
</rss>

