Setting up Cybereason was straightforward. However, if you don't have an IT team that can program the exceptions you need or run the automatic installation,  it might take some time to figure out how it all works. Cybereason offered us some support during deployment. They have a forum, and if we had any questions, Cybereas support could offer customized solutions or guide us through the process. 

The deployment didn't take too long because we didn't have many endpoints. It was maybe a couple of days. We can automatically deploy the sensors on our new machines, so it's quick and easy to expand. The policies are set automatically when we onboard employees and the sensors run pretty smoothly.

The initial setup process is straightforward. We have to install the agent, create a package, and deploy it on servers. It has a prebuilt console managed by the cloud team of Cybereason. We don't have to worry about the console and concentrate on endpoint implementation. It takes ten days to deploy it on 10,000 devices.

The initial setup was pretty straightforward. Deployment took two or three months. 

We started with a few machines in monitor-only mode to see what kind of noise we had. Then, we expanded the number of machines and continued monitoring. Once we had everything in monitoring mode, we were then able to start turning on some of the blocking and automated actions. 

The initial setup was straightforward. You just install the client and as long as it has internet access, you're pretty much already working at that point, and then it's just fine-tuning your policies or your groupings after that.

We had the majority of our assets done, probably 20,000 in a month for our office. So it was very quick.

We have an automation tool that we use for patching and installing software, and we just did a phased approach of rolling it out to end clients and servers.

We manually set up Cybereason Endpoint Detection & Response. We also have a deployment tool, so it depends on the situation. Sometimes we can do it via automation, and sometimes we have to involve the local agent. As for how long it took, for automation, it would still depend on the size of the company, for example, if one site has a hundred and ten, it would take one week. For manual deployment, it would require three manpower. For our company, deployment took one month.

The initial deployment was very straightforward for Windows, Linux, and Mac. On the mobile side, the deployment has still been very slow. I think their VPN has some compatibility issues with Android or specific versions of Android.

On Windows machines, the deployment took around two and a half months. Part of it was very much due to us wanting to dip our toes first and not go full speed, because we didn't know how our machines were going to react or its compatibility with the system. It was a very wide deployment to various different systems. We were mostly worried about our servers. 

It has done very well with our servers. We haven't really seen many negatively affected assets.

We had a lot of issues when the the tool went online, it was consuming too much results on the machines, especially on servers. It is not very difficult to maintain the solution.

On a scale of one to ten, where one is difficult, and ten is easy, I rate the setup phase a nine.

The solution is deployed on the cloud.

For around 100 employees, we need three to five days for the deployment of the product.

We need three people for the deployment.

It's very straight forward to implement the solution. It's not complex at all. The solution provides you with a package once, tailored to how your network is working. They provide you with a dedicated package for your own organization and it's ridiculously simple to install.

Technically, the solution is already deployed, however, it's not on all servers yet. I'm deploying the machine servers worldwide while also making sure that the grid version of the sensors is set up. I would estimate that, at this point, the company has deployed the solution 90-95%. We're in the process of finishing off what's left.

The initial setup was straightforward with plenty of issues.

It took between a few weeks and a few months to deploy.

The setup was completely fast-paced and extremely straightforward. 

We were under a somewhat constrained timeline for rollout. It usually takes us six to eight weeks to roll something of this magnitude out to the organization, but having the pandemic upon us, we actually got it fully deployed in under three weeks. That's how easy it was to roll out and deploy.

The deployment was done all internally. It was a little bit more than just our security team. It was help from our tier-one support analyst as well, but we got it rolled out with a handful of people. Six people were involved in the project in deploying over 2,900 sensors.

We are currently looking at their mobile device management solution or their protection solution to expand usage.

It’s easier to set up that Cybereason Connect. It’s pretty straightforward. It didn’t take too long to deploy.

The set up is a bit complex. We were using cloud when we setup the solution. As we implemented the product, we had to tell them what are the requirements so they understand and they are creating the package. It initially took some time to deploy.

This is a product that requires a lot of resources when it is set up.

Some of our customers ask that Cybereason be installed with an air gap.

The initial setup was easy and straightforward. It took about two months. 

The initial setup is pretty much straightforward. Simply follow the onboarding process as instructed by the vendor. The vendor is available to guide and assist with the onboarding process, and training for using the solution is also provided.

The setup is straightforward, provided you have the required infrastructure support as prerequisites.

The initial setup was easy.