We performed a comparison between Secureworks Red Cloak Threat Detection and Response [EOL] and VMware Carbon Black Endpoint based on real PeerSpot user reviews.
Find out what your peers are saying about VMware, ServiceNow, IBM and others in Security Incident Response."The features that I have found most valuable are that the search capabilities are easy to use. The dashboards are good. The reports are good. It is just simple from a deployment standpoint - that was easy."
More Secureworks Red Cloak Threat Detection and Response [EOL] Pros →
"CB Defense is more powerful, and you can take more actions than others. Its security features and signatures are constantly updated, so it is more effective than other security solutions."
"The solution has a very nice API on the back end for remoting into a system and executing scripts or utilizing self automation."
"We can access computers remotely if we need to."
"The solution is extremely scalable."
"The biggest feature out of CarbonBlack is its ability to dive in with more depth. You can look at the entire kill chain and understand, not only if an alarm or identified incident is truly a true security issue versus a false positive, and it allows us to backtrack and figure out why it actually happened and how it got into the environment."
"The software uses very few resources; it is almost invisible to the end user."
"You can deploy it through the cloud so that even if your stuff is outside of your controlled environment, you are still under control, based on the policies you create. The policies are controlled through the cloud. For example, if I don't allow anyone to do a certain activity or to install a particular app, and a consultant or a partner who is not part of our environment is doing so, it will stop them as well."
"The initial setup is pretty straightforward."
"There are some automated network response portions that we want to turn up."
More Secureworks Red Cloak Threat Detection and Response [EOL] Cons →
"Right now, Carbon Black CB Defense doesn't support cloud computing and Kubernetes."
"I would like to see improvements made so that we can better see all of the processes."
"The local technical support is very poor, but the support from headquarters is very nice."
"In our company, we also wanted to have network detection, like a host-based IDS on VMware Carbon Black Endpoint, but we did not get it."
"They will most likely need to create or include a feature that checks the network."
"The product's reporting capabilities are an area of concern where improvements are required."
"This solution works well but needs lots of tuning and optimization."
"This solution could have greater granular control on how certain applications work."
Earn 20 points
Secureworks Red Cloak Threat Detection and Response [EOL] doesn't meet the minimum requirements to be ranked in Security Incident Response while VMware Carbon Black Endpoint is ranked 1st in Security Incident Response with 61 reviews. Secureworks Red Cloak Threat Detection and Response [EOL] is rated 8.0, while VMware Carbon Black Endpoint is rated 8.0. The top reviewer of Secureworks Red Cloak Threat Detection and Response [EOL] writes "Simple deployment with good reports and dashboard". On the other hand, the top reviewer of VMware Carbon Black Endpoint writes "Centralization via the cloud allows us to protect and control people working from home". Secureworks Red Cloak Threat Detection and Response [EOL] is most compared with Cisco SecureX, Splunk SOAR and VMware Carbon Black Cloud, whereas VMware Carbon Black Endpoint is most compared with CrowdStrike Falcon, Microsoft Defender for Endpoint, Trend Micro Deep Security, SentinelOne Singularity Complete and Symantec Endpoint Security.
See our list of best Security Incident Response vendors.
We monitor all Security Incident Response reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
