Super Secure Gartner Security Blog Open to All

You have to be a paid Gartner client with GITL-Security level access rights to view the Gartner Security blog (here) – at least that was the case when my dribble was posted there – or you can just type in this URL and access the Gartner security blog directly. I am confident that the good folks at Gartner will resolve this quickly, in the meantime comment all you want, it’s free 🙂

In all seriousness it is a real shame that the security analysts are not allowed to share their blogging goodness with the general public. Get with the program Gartner it is 2007 and you cannot charge for everything an analyst says publicly. Now I am not one to gossip but rumor has it that more than one analyst resented the needless constraints placed on blogging by the Gartner internal blog police, and although we all make decisions to move on for different reasons this was one of those policies that made the decision to leave a little easier to make.

12 thoughts on “Super Secure Gartner Security Blog Open to All

  1. Amrit you know better than to post this “dribble.” I think you meant “drivel” but it’s too late to look it up.

    We give advise and perspectives on the market for a fee; that’s our business model. The model doesn’t really accomodate giving too much away. You worked here but I guess you forgot who signed your paycheck, and for what.

    When someone spends time building their personal brand in an outside blog on the topics they’re covering, it takes time away from providing “goodness” that should be shared with paying subscriber clients. Why would someone pay for something when it looks like they can get it for free? And when someone also complains that they think they’re working too hard and can’t get their work done while they’re maintaining an outside blog on the topics they cover as analysts, well, there’s a problem with that. The problem gets worse when Gartner is called upon to defend something someone wrote while working their second job. And so the higher ups established a policy prohibiting this conflict of interest. Those that can’t live with that policy are free to seek employment elsewhere, or to try to survive as independents. It’s funny (and sad) how many resumes we get from ex-analysts that really want to come back.

    Any analyst is free to speak or publish for “the general public” and we do — in the trades, in open and freely available First Takes and elsewhere. Those are just a taste of the goodness.

    My point is that there is nothing wrong with restricting officially sanctioned blogs to paying clients, and in disallowing Gartner-employed analysts from external blogging on the topics they’re covering. It’s just good business sense.


  2. Gee, I see that after I submitted this, I got a notice that “Your comment is awaiting moderation.” I resent this “needless constraint placed on blogging.”

    (smiley face goes here).

  3. I have to moderate comments, can’t just have every hippie with a computer posting willy nilly. Also you should see the mountain of porn links that come in through the spam filter – seriously you really should see it – just amazing stuff.

    Of course Gartner can implement whatever policy they feel is appropriate – and more power to them if they can pull in a couple extra bucks for the added service of the blog. But outside blogging aside the internally sanctioned Gartner security blog should really be made publicly available so as to break through the veil of delicate genius that permeates the halls or something like that.

    btw – I meant drivel, I was watching Hell’s Kitchen while typing the post (terrible show, Top Chef is much better) but now that I think about it most of the blog posts were dribble analysis, as in trickling in, as opposed to a flood of information

  4. Pingback: iloviT #1 | John M Willis - ESM BLOG

  5. What is so interesting about this thread and response from Gartner is that their entire business model is based on making observations about how other companies operate, which includes their policies (internal and external) and their technical skill. So it all seems so rather bizarre that when someone takes issue with one of their polices or points out an issue with their web administration skill they would get so bent around the axle – just goes to show that it is far easier to point out the flaws in others than to look at yourself.

  6. You know I love you Vic but I don’t know man you seem awfully annoyed in your original post, hardly what I would construe as simply explaining a policy – first you suggest one shouldn’t even post such things, and then you even toss in some anecdotal references to other analysts leaving and then having to come back and how sad it all is. Personally I wouldn’t know…in any case it is nice to see you visit my little slice of cyberia.

  7. This blog posting is now the first link when one Google’s “gartner security blog”, it is closely followed by a techtarget blog posting entitled “Gartner’s Security 3.0 theme falls flat” – funny!

  8. I think you raise an important issue Vic, that is analysts’ personal brand. There was a time at Gartner, slightly pre-dating my time there, when it was recognized that Gartner’s brand devolves from the the individual brands of its analysts. This, of course, was not something that a professional executive management team could stomach because you had all these over-inflated egos swaggering around the office.

    So one way of viewing your concerns about blogs leading to an analyst’s personal brand building and not doing anything for Gartner reveals a myopic stance. Times are changing, the way people get information is changing, bloggers are becoming more and more influential. One could argue that a large research factory can outperform the individual contributions from many experts. But I would hate to bet against something as big as the Internet and its social linking of knowledge, people and influence.

    As far as posting internal links: Bad form Amrit! Its almost like making vulnerabilities public before informing the vendor.

    Now here is an internal link that I *have* informed Gartner of. Apparently I am still a Gartner Analyst! Note the seven years seniority:

    I could argue that Gartner is co-opting *my* brand. But that’s silly.

    -R. Stiennon

  9. Good points!

    As for it being bad form, let’s be clear this is not an internal link, all Gartner blogs posted on the Gartner home page, which are not internal and are free to the public, use the following URL convention simply replacing x with the word security gets you into the so-called internal and pay blog – so please spare me the bad form and comparison to releasing information on previously unknown vulnerabilities

  10. Holy to Manny! I’m blogging. And on Amrit’s blog at that! I hope that doesn’t hurt my personal brand!

    Look Richard, Gartner offers it’s analysts blogs and podcasts as well as plenty of other highly visible opportunities to build their personal brand. Just today I came across your own branding as “Richard Steinnon, Author of the Gartner Magic Quadrant” for an event coming up next month. And as you’ve pointed out, you haven’t worked here in years. So….. what’s the brand again?

    As for the rest, yeah, the world is changing. Always has.

    I guess I’m saying we don’t want people expending their energy and intellectual capital on job related topics in outside channels. Is that so hard to understand? It dilutes Gartner’s value (in our corporate view), adds to Analyst workload (yeah, I know, everyone is entitled to hobbies) and it really isn’t our business model to give too much stuff away.

    Soooo if you guys want to go on continuing to criticise a business model that seems to work, carry on…


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s