Before choosing Carbon Black Cloud, we evaluated other options, including Microsoft Defender and a different version of the Fortinet environment. We ultimately decided on Carbon Black Cloud because of its seamless integration with our Workspace ONE platform, which is our client management system, and also from VMware. The collaboration between Carbon Black Cloud and Workspace ONE was a significant advantage. Additionally, the third-party support provided for Carbon Black Cloud was a positive aspect. Price-wise, it was comparable to the other options we considered.

The solution stopped doing development about two years ago. It was actually supposed to roll into Defense, but that never happened. Part of the reason is because Defense can't be made into an on-premises product. 

The solution still exists because government and other industries do not want to move to cloud-based environments so they need on-premises services for their networks. 

There wasn’t much similar to Response that I was familiar with at the time. Though some other vendors are starting to include similar features now, Response was a leader when we selected it. Now there is a growing number of open-source projects, such as TheHive, and other vendors are incorporating similar features into their general security products, so I believe the landscape has changed a bit and things are getting more competitive for the needs Response fills.

I was not part of the decision-making process. It was the engineers who decided.

Carbon Black is the leader in the market on many web boards.