by Lawrence Pingree | March 10, 2017 | Comments Off on Threat Intelligence Interest areas of Gartner clients
Been a while since I’ve blogged, so I figured I’d update you on what I’m digging into in Q217 with Ruggero Contu (my awesome teammate). He and I are collaborating on a threat intelligence competitive landscape note. As part of this process, I’ve been digging into our Gartner.com search analytics data to identify interest areas of our client base. The way I went about this is a bit interesting, so we have a large list of threat intelligence providers that cover a range of different threat intelligence services. I took that list (which is categorized, then used the Gartner search analytics tool to search for company names in each category) which allowed me to arrive at a search count by category. For example: Threat intelligence company x was in category y, then I queried how many searches on our website there were for company x, iterated across all the companies in each of these categories then charted the results omitting the companies in each category. The result was quite interesting and demonstrates a nice demand/interest graph. Below is the output of my search query analysis.
Note: I did not search these exact search terms above and they are not “official” Gartner published categories, these were the categories I had drafted for each of the companies in the list and how the client searches ranked by category (I inferred the category). If you are confused, you can do an inquiry with me for a better explanation!
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.