Bromium Initial Setup

Hugh Percy
Manager of Cyber Security Operations at a healthcare company with 1,001-5,000 employees
The setup was pretty straightforward. They make it really easy to install this particular product and you give it various avenues. You can do it remotely, through the BEC (Bromium Enterprise Controller), or you can do it on the endpoint, and the endpoint would actually reach back out to the BEC. It's pretty simple, pretty smooth. We just added two more Bromium administrators here and they were pleasantly pleased by how easy it was to manage and install. The initial deployment didn't take that long at all. Installing the enterprise controller and installing on our first several PCs, took no more than an hour, if that. It was three years ago, roughly, when we did that, but I don't remember it taking more than an hour. Each additional machine literally takes five to ten minutes, tops. I hesitate to say ten minutes, not even that long. It's really easy and it's really simple. Staff, on our side, for the deployment was two people: One setting up the Bromium Enterprise Controller, and the other who was over the radiology department, the technical control person there. That was so we could coordinate things, but it didn't take a lot of folks at all. As far as to manage Bromium on a day-to-day basis, we only had one Bromium administrator, but we've expanded that to three. That's not because of the workload requirement but because everybody has to take vacation or gets sick once in a while. We just need a backup administrator for Bromium. View full review »
Director of Information Security with 1,001-5,000 employees
It was definitely very difficult to implement but that was over three years ago. If not for their support and their follow through on getting it up and running and going... The endpoint protection you get from it is phenomenal but there's definitely some overhead and there are some bumps in the road from time to time. You may have to do some work when a website doesn't operate correctly or you have to whitelist it because again it doesn't run well in a micro VM. The deployment took around six months or so. We did a slow roll at first because a lot of websites did not render properly. We had some internal things that didn't work properly with it. There were some enhancements that they did and some whitelisting that went on. It was not a simple process to get up and running. Our implementation strategy was to start with a small pilot group and grow as we felt comfortable with the usability. In terms of the number of staff it took for deployment, we have a very small staff. There are only four IT security people here. At the peak of implementation, it was taking two of us a good deal of our time, between getting it going and trying to get with Bromium and resolve issues. Now that it's fully implemented it takes a fraction of one person's time to maintain it. We'll still have a one-off issue now and then where there will be an issue with a website that somebody is going to, or they are trying to download a file from that may not work. But, we have pretty good expertise within our staff now for dealing with those problems. View full review »
Director of IT Security, Risk and Compliance. at a pharma/biotech company with 1,001-5,000 employees
The setup is complex. It's a solution that forces behavior changes throughout the environment. Because you're isolating processes individually within a host, things behave a little bit differently. The set-up part of it is: * Understanding where you need, and how you want, to define boundaries of trust; to define what is isolated and what is no isolated. * Going back and making sure that, where you have isolation established, the process will still function and people will understand the differences in how they interact with simple things like downloading a PDF from a website that's not trusted. There are some different behavior issues that the users will see, and that was really where the majority of the time and effort went in getting the solution up and running. To truly to get where we wanted to be it took some nine to ten months. Our initial implementation strategy was to start rolling it out quietly. But we paused that and actually started going on more of a very active awareness campaign. We had to start marketing what we were doing more, so people would understand the little nuances that were changing and not react negatively to them. That's a big part of why it took us a little bit longer to actually get rolled out. View full review »
Find out what your peers are saying about HP, Cylance, Sophos and others in Endpoint Protection (EPP) for Business. Updated: February 2020.
398,050 professionals have used our research since 2012.
Product Lead at a retailer with 1,001-5,000 employees
The initial setup was very straightforward, very basic policies, not a lot of complicated policies involved. We found it pretty straightforward. The deployment, on a scale of one to ten, with one being the hardest and ten being the easiest, was about a six. There are a few reasons. First, it requires a reboot, so it is very intrusive for the end-user, and it also requires an initialization period, which is usually about 20 minutes of slowdown to a workstation. So when you deploy, not only is the user asked to reboot their computer, they are also asked to wait for 20 minutes while it sits there and initializes. It definitely impacts the end-user. It takes time away from their day. We try to minimize that impact by scheduling our deployments right before lunch so that they can reboot and then it can initialize while they are at a lunch break. But, of course, not everybody works the same hours. A lot of other agents do not require a reboot and are pretty invisible to the end-user. This is definitely "in your face" to the end-user. View full review »
Director with 51-200 employees
The initial setup was straightforward. We followed the deployment methodology that they outlined and it pretty much worked the way it was supposed to. Regarding the deployment, on a scale of one to ten, with one being the hardest and ten being the easiest, it's a ten. We didn't have any challenges. View full review »
Find out what your peers are saying about HP, Cylance, Sophos and others in Endpoint Protection (EPP) for Business. Updated: February 2020.
398,050 professionals have used our research since 2012.