nobeastsofierce - Fotolia

UC blogs: Approaches to public cloud security monitoring

In UC blogs, analysts discuss how enterprises approach public cloud security monitoring and the different categories of contact center chat vendors.

Gartner Inc. analyst Anton Chuvakin discusses his latest research on public cloud security and the approaches enterprises take to security monitoring. He writes that security requirements and monitoring often lag behind, as the cloud changes how enterprises use technology.

Chuvakin writes that enterprises report spending more time dealing with traditional threats that affect their cloud environment. These threats include malicious software, denial-of-service (DoS) attacks and unsafe access credentials. However, a proper security monitoring approach has not emerged. Enterprises reported using a mix of traditional tools, such as security information and event management, and cloud-specific tools, such as cloud access security brokers.

Read more for Chuvakin's advice on cloud security monitoring.

The contact center chat vendor categories

Forrester Research Inc. analyst Kate Leggett discusses how to select a chat vendor for the contact center. She writes that customers are increasingly using chat to communicate with customer service agents; but organizations can face difficulties in choosing a chat vendor that meets their contact center needs.

Leggett writes that chat vendors fall under several categories that can help organizations evaluate potential vendors. One category is standalone chat vendors that offer full-featured, easy-to-deploy chat products. While these vendors, which include Olark and Velaro, are good for small businesses, they are rarely deployed by larger enterprises.

Another category is online engagement vendors, which include LogMeIn's BoldChat and Needle. These vendors offer proactive and personalized customer interactions that support customers in pre- and post-purchase situations.

Read more about three other categories of chat vendors.

Why WebRTC needs IP addresses

Consultant Tsahi Levent-Levi delves into WebRTC basics to explain why it needs IP addresses and how the technology uses them. He writes that WebRTC uses peer-to-peer technology that allows Web browsers to communicate with each other without a Web server. However, IP addresses are needed to support communication.

Levent-Levi writes that messages between browsers also contain session description protocol, which contains IP addresses for the exchange of data between browsers. This helps to facilitate future communication between browsers.

Read more about why peer-to-peer communication is preferable to a Web server for WebRTC.

Next Steps

Minimizing public cloud security threats

A primer on WebRTC basics

Collaboration boosting contact center technology

Dig Deeper on Unified Communications Security