Home > Networking News > Losing the war to lock down networks might help enterprises innovate
Networking News:
EMAIL THIS

Losing the war to lock down networks might help enterprises innovate

By Michael Morisy, News Writer
06 Mar 2008 | SearchNetworking.com

News on networking, mobility and voice
Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google

Experts at the Gartner Wireless and Mobile Summit in Chicago warned attendees that locking down and banning consumer technology can choke off innovation.

"Users want all their options," said Bob Hafner, vice president at Gartner. He said that oftentimes support teams would end up spending more time and money managing strict policies than if they allowed user flexibility. This was particularly true with communications, he said, where much of the innovation is happening on the consumer side and then creeping into the workplace.

How bad can it be when organizations try to keep things locked down? For one Australian government agency Gartner studied, call re-direction was the single largest mobile expense. Users dissatisfied with the agency's standard-issue mobile devices simply programmed them to forward calls to their personal devices.

In contrast, Hafner cited a case several years ago where a bank asked him to build a business case for company-wide email. He struggled with the task, but the benefits were often not obvious: Why learn and manage a new application when a phone works just as well at lower cost?

When Hafner stepped away from the executive office and started implementing small group deployments, however, the benefits became obvious, often in surprising ways. "Users will build the business case for you," he said.

While completely blocking all consumer technology is becoming impractical, opening the floodgates isn't a sound idea, either: If every user utilized a different email application, phone syncing solution, and Web 2.0 document manager, the security management scenario would quickly become nightmarish. But according to Hafner, there is a middle ground.

Most users, he said, will fall into different categories, based on their usage patterns, technical savvy, and job function. The majority of users in most organizations can probably be narrowed down to five to seven profiles, and then policies can be developed with those profiles in mind.

Monica Basso and Nick Jones, vice presidents with Gartner, laid out an "A to F" continuum of support that can help IT decide how to manage aspects of user-implemented technology:

  • Approve. Explicitly approve some technologies for use, without support. This could work well with cell phones in some environments: Users can buy any phone they want but must be willing to be on their own if they have trouble. Often, "approved" devices are in a different class from "supported" ones, so that some users can buy recommended phones, for example, and they will get technical support.
  • Block. Actively seek out and block unauthorized applications, devices and usage patterns. Often costly, there are some scenarios where this still makes sense. Heavily regulated environments might mean that consumer instant messaging clients, for example, are unacceptable.
  • Contain. Similar to "A," but work to promote best practices to ensure that consumer tech is a positive force on productivity while mitigating risks -- for example, allowing use of GMail but disallowing attachments, which can contain confidential information.
  • Disregard. Turning a blind eye is always a choice, but given the risks involved, probably not a good one.
  • Embrace. Active support and promotion of consumer technologies in the workplace. More than simply approving, this means training and support on these technologies.
  • Fix. At this point, failures have started to have an impact on the bottom line, and large investments of time and energy are needed to get usage back on track. Part of fixing that problem could be setting policies and precedents for future consumer technology, ensuring that failures are not repeated.

Depending on the business environment, a mix of these policies may make the most sense, but conscious decisions in each major area – email clients, Web usage, mobile phones – could head off major problems down the road, and could even help discover solid strategic benefits.

IT should, however, set firm guidelines where needed. Hafner said that phone numbers, for example, should be owned by the company. Otherwise, a sales agent who jumps ship could easily take his clients with him when they call to re-order.

Hafner also emphasized the importance of finding and cultivating relationships with power users to identify trends and potential innovations in the network.

"Valuable opportunities show up if you just let the people play with the technology," he said. He recommended finding these users by asking departments who their go-to guy is for tech problems before they file help-desk requests. Then, admins can see what is being done and how best to quantify the benefits – and risks – technologies can bring.

Tags: LANs (Local Area Networks)Network AdministrationVIEW ALL TAGS

Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google


RELATED CONTENT
LANs (Local Area Networks)
Q&A: Jim Metzler previews the networking track at Interop
Extreme's port extender can replace consumer devices at network edge
VLANs versus IP subnets: Why use a VLAN over IP subnetting?
Troubleshooting VLANs: How to monitor 802.1q tagged traffic
Top 10 networking advice of 2008
During a recession, align the network with business priorities
LANs vs. WLANs: Which network designs are used for each company size?
Best practices for securing your wireless LAN
HTTP error code troubleshooting, Part 1: HTTP status codes defined
How do I set up multiple VLANs on a single switch?

Network Administration
How server virtualization improves efficiency in a client-server model
Understand Windows tracert output to troubleshoot network connectivity
Why would a computer show drive letters for discs that don't exist?
Using tracert and TTL to troubleshoot network connectivity problems
Open source software for enterprise network management and monitoring
When do applications suffer from poor network performance?
Tight times? Organize your networking group to stay above the stress
Managing Network Problem Users: The make-it-so CEO
Checking IP configuration to troubleshoot Windows network connectivity
Bandwidth allocation: How can I give a download limit for each user?
Network Administration Research

RELATED GLOSSARY TERMS
Terms from Whatis.com − the technology online dictionary
32-bit IP addressing  (SearchNetworking.com)
ARCNET  (SearchNetworking.com)
master  (SearchNetworking.com)
master/slave  (SearchNetworking.com)
subnet  (SearchNetworking.com)
subnet mask  (SearchNetworking.com)
system administrator  (SearchNetworking.com)
Technical Office Protocol  (SearchNetworking.com)
Telnet  (SearchNetworking.com)
virtual systems management  (SearchNetworking.com)

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary



Comprehensive network management resources, expert solutions, and professional research informing your technology decisions
About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Site Map




All Rights Reserved, Copyright 2000 - 2009, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts