Gartner Blog Network


More On Security Monitoring of Public Cloud Assets

by Anton Chuvakin  |  January 14, 2012  |  3 Comments

This post is not a whine about how security in public cloud environments is lagging behind the traditional physical environments. There is nothing here to whine about since our experience with other IT advances – think PC, client-server, web applications, mobile devices – teaches us that it is ALWAYS the case for new technologies.  The cycle, that some people might call ‘vicious’, happens like this:

  1. Invent
  2. Deploy
  3. Popularize
  4. Disaster!!!
  5. Secure (and eventually even “build it securely”)

and then the next tech is invented and the cycle repeats. Let’s consider security monitoring of IT resources deployed on public clouds, whether SaaS, PaaS or IaaS. Such security monitoring includes logs (primarily), network traffic analysis, host activity monitoring as well as other well-known monitoring mechanisms (for a superb review of these, please review “Security Monitoring” template by Ramon Krikken). As my research project progresses, I am coming across various challenges to cloud asset security monitoring. Here is a quick list:

  • Often, unimportant assets move to the public cloud first, and the need to do security monitoring simply never appears.
  • Cloud (as well as virtual) assets are known to be transient and change more often than traditional physical systems, adding chaos to the attempts to monitor “who does what” to systems and data.
  • The familiar mechanisms – various network security appliances – do not map well to the cloud, and the new mechanisms (wherever available!) have a learning curve.
  • Similarly, lack of visibility into the lower layers of underlying infrastructure hampers many monitoring efforts as one might have to peek into the lower layers from the higher ones.
  • When lacking network data and system logs, a replacement monitoring method – application logs – comes with its own set of challenges, including working with application developers to engineer logs useful for security and not just for debugging.
  • “We just trust our CSP, they’d a great job securing and monitoring our assets!” This is admittedly more likely for users of SaaS providers, but more than a few people seem to confuse “cloud” with  “outsourcing”
  • Fragmented control over various cloud migration efforts leads to no security monitoring (and even “no security” sometimes); rogue cloud assets are by definition unmonitored by central IT.
  • Even when monitored, loss of the unified view of public cloud + virtual / private cloud + traditional makes noticing anomalous and malicious activities harder.

So, my journey continues – watch for more blog posts on cloud security monitoring as my project eventually culminates in architectural guidance for cloud security monitoring …

By the way, if you are a vendor with a technology helpful for security monitoring of public cloud assets, please brief me on your technology.

Previous cloud security monitoring related posts are:

Category: cloud  logging  security  siem  

Tags: cloud-security  security  security-monitoring  

Anton Chuvakin
Research VP and Distinguished Analyst
5+ years with Gartner
17 years IT industry

Anton Chuvakin is a Research VP and Distinguished Analyst at Gartner's GTP Security and Risk Management group. Before Mr. Chuvakin joined Gartner, his job responsibilities included security product management, evangelist… Read Full Bio


Thoughts on More On Security Monitoring of Public Cloud Assets


  1. […] more: More On Security Monitoring of Public Cloud Assets Comments […]

  2. […] Coverage Areas: ← More On Security Monitoring of Public Cloud Assets […]

  3. […] More On Security Monitoring of Public Cloud Assets […]



Comments are closed

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.