Home
BYTE Newsletter
Keep up with all the BYTE News and Reviews

Subscribe
Jonathan Feldman

Jonathan Feldman

Contributing Editor

If Apple Walls Garden, IT Should Demand Keys

Comments | Jonathan Feldman, InformationWeek | May 07, 2012 11:11 AM


I wrote last week that I'm concerned that Apple and its copycats will use Flashback malware as an excuse to push a desktop walled garden model, raising IT costs while solving nothing. But if Apple and its groupies were to share control with IT, that approach would be palatable. Here's why.

But first, allow me to offer a comparison. I'm a frugal guy, which plays well with the CFOs I've worked with. I grew up with Depression-era parents and six siblings, so reuse and recycle were more than hipster terms in our house. To this day, I won't lease a vehicle. I buy cars used and drive them to 200,000+ miles, happily investing in maintenance and repairs from independent shops. Sadly, those days may be coming to an end now that auto makers are taking a page out of the software vendor playbook and pushing to make vehicle repairs proprietary.

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

My concerns about the cost of vehicle repairs will be replicated in the IT organization if the desktop walled garden and secure boot are implemented in a way that fails to recognize IT as an authority over that hardware. Under the current desktop model, IT leaders have their pick of "independent computer repair dealers," both from a software and hardware perspective.

Anybody who's been watching this industry knows that Apple's going to go walled garden on its desktops, whether or not it blames Flashback malware. And if other suppliers follow, it's just a matter of time until IT has fewer choices for repair and software distribution, all of which will mean higher prices.

But if IT organizations apply their considerable buyer power and influence to Apple's smaller competitors, those suppliers may relent and let IT control at least some of the walled garden--and thus Apple may be influenced through Michael Porter's "rivalry" force.

Which concessions should IT organizations pursue with Apple rivals? They need two important keys to the walled garden gates.

Part of Apple's walled garden is the notion of authorized or signed code. One reader of my column last week took me to task because he perceived that I was against signed code. I'm not. Signed code is OK, and can even be preferable, because if you don't know who someone is, you don't want his code running across 10,000 desktops at your organization.

What I'm against is creating conditions whereby only your desktop supplier can authorize a signer. If Apple would let IT organizations register "known good" code suppliers, that's the first key to a more acceptable desktop walled garden. Apple already lets enterprises registered with Dun & Bradstreet distribute their own enterprise apps for a mere $299 annually; they just don't let enterprises buy apps from anyone but Apple.

That model isn't good enough. We need to make it very clear to Apple's competitors (and thus to Apple) that CIOs will prefer hardware and operating system suppliers that provide conditions whereby IT organizations can, on an ad hoc basis, add a software supplier as an authorized signature for that enterprise's desktops.

Global CIO
Global CIOs: A Site Just For You
Visit InformationWeek's Global CIO -- our online community and information resource for CIOs operating in the global economy.

The other key to the walled garden is the approved and legal notion of jailbreaking a device. Nobody would ask manufacturers to provide warranty or support for a jailbroken product. But manufacturers that incite our lawmakers to make jailbreaking illegal should feel our collective buyer power wrath.

The stakes are high, as noted jailbreaker and open hardware advocate "Bunnie" Huang related to me earlier this year with this example. If a car maker such as Ford were to get locked down with secure boot on critical computers that run its manufacturing robots, and the robotics controller software maker were to go out of business, Ford would have a huge problem. It would be faced with either turning to a new support supplier that's breaking the law by reverse engineering or jailbreaking the software, or buying a new assembly line.

But plant managers don't know enough about computers to advocate for open systems and keys to walled gardens. They rely on us, the IT pros, who shouldn't fall for some mythical notion that wall gardens keep our equipment and data safe.

We work for our employers, not for our IT suppliers, and we're the experts our colleagues and bosses will turn to if something goes wrong critical systems. IT leaders at the table with suppliers would do well to remember which side they're on.

Jonathan Feldman is a contributing editor for InformationWeek and director of IT services for a rapidly growing city in North Carolina. Write to him at jf@feldman.org or at @_jfeldman.

From clouds to mobile to software development, threats may be everywhere, but they're not equally dangerous. The new, all-digital IT Strategic Security Survey issue of InformationWeek will help you prioritize. Also in this issue: IT must decide how to deal with consumer cloud storage being used in businesses. (Free registration required.)

Jonathan Feldman is a contributing editor for InformationWeek and CIO for a rapidly growing city in North Carolina. Write to him at jf@feldman.org or at @_jfeldman.



Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

COMMENTS

Tune In to BYTE
Facebook Twitter LinkedIn Newsletter RSS
Whitepapers
whitepaper
In this paper you will learn the five trends shaping the future of enterprise mobility. Learn how the rise of social media as a business application, the lurring between work and home, the emergence of new mobile devices, the demand for tech savvy employees and changing expectations of corporate IT will fundamentally change the workplace.
whitepaper
In a survey of more than 1,700 information workers (iWorkers) in North America, notebooks, desktops, and smartphones were found to be “must-have” devices, while tablets, slates, and netbooks were relegated to “nice-to-have” status, according to a commissioned study conducted by Forrester Consulting on behalf of Dell and Intel.
Sponsored by: Dell
Upcoming Events