What is our primary use case?
My company is using Cynet for endpoint protection.
How has it helped my organization?
Before Cynet, we didn't have a good centralized solution. We had disparate solutions from different manufacturers, so we needed a system that would keep everybody on the same platform.
What is most valuable?
It's transparent, so it's not something where every user has to press a button to download or do the thing. It is centralized, in fact. Personally, I use Malwarebytes and other tools, which are fine for home use. Cynet is also relatively silent in terms of operation, except when it's required to act. Another advantage is the way it segregates the data. We had the opportunity to test their deception feature, and it works.
What needs improvement?
Cynet gives a few false positives. It would also be nice if Cynet added the ability to put comments on each device. I would love to be able to say, "This is a computer in the conference room. This is a computer at the Mac desk." That way, when you have an alarm, you don't have to go to a separate registry to see which device has an alert. We have offices worldwide, so sometimes having an alert inside one building is fine, but sometimes we don't know if it's coming into our office in Morocco or the US.
The inability to add contact information inside the Cynet is also an issue because it makes things more complicated. I would like to have a simple feature to enter a contact name and number for the person taking care of that unit or that server. Then I would know who has access to that server registry and so on. But, on the other hand, I understand why they have not done that because they don't want to ask for private information on who is using what and what phone number.
I can see both sides. I trust Cynet, so I don't have a problem sharing that information. However, some customers may have an issue. At the end of the day, it would be a field that the customer can choose to fill or not. So if there were one feature that I would like to improve, this would be at the top of the list.
I'd like to be able to personalize the device labels so I can say, "This is the IT desk in our Montreal office. This is the IT desk in Saint-Laurent. Patrick is a salesman in Toronto who has had his computer attacked." When it's giving a warning, it isn't always providing notice to the user because it lets us decide whether it's a threat or not. So when it solves a problem automatically, I don't have to call.
But some users are sensitive. And at the very least, we need to advise them that one of their files has been encrypted because the security software thought it might be a threat. So I think it's a valid request there, which will not take a long time. I mean, Cynet is already maintaining a database of the unit. So it's just setting a field that the IT can decide to use or not use. So it's a simple implementation of a modification as they had.
Another disadvantage I have found so far is the platform has to be based on a desktop PC or server. It does not deploy on a mobile unit, like a cell phone or something like this. But for our primary requirements, it is doing the job.
For how long have I used the solution?
I haven't been using Cynet for very long, only about five months.
What do I think about the stability of the solution?
So far, Cynet has been stable. There have been few errors.
What do I think about the scalability of the solution?
I am not concerned about scalability for the moment because we are already deploying the solution countrywide to telecom companies and offering it to 250,000 telecom resellers. We will probably respond to some RFPs in the United States as well. When we initially approached Cynet. It was at the request of a major Canadian law enforcement agency. We also provide security for various government ministers.
So I've spoken often to the personnel at high-level Canadian public safety agencies. We've gotten some good feedback about Cynet from them. I cannot go into detail, but we provide a specialized solution for public safety and can deploy Cynet in that unit. So we got a great reference from them. Not a lot of software companies can get a recommendation from a national law enforcement agency. But, of course, it was only an informal recommendation, not an official endorsement. They tried different solutions. I'm sure they are not exclusively using Cynet, or they may not be using it anymore. I have no idea.
We have a team that specializes in public safety. The director of this Canadian law enforcement agency can give a special designation to our team that grants us access to privileged information in a case where the investigation is ongoing. I would not say our team is made up of cybersecurity experts, but we provide cybersecurity and cybersecurity video solutions. That's not cybersecurity. We offer live video services over any IP network. So we have some specialized solutions. We developed a platform. And for telecom, we deploy platforms that are big enough to serve a quarter-million users per year for some companies or resellers.
On top of that, we provide about 400 million SIM cards every year. Some of the SIM cards that we manufacture have some interesting features, especially for public safety. For example, the SIM card, not the phone, will recognize the user's video. So the SIM card access or the biometric will verify if the person is an authorized user. If they are an authorized user, they will gain access to secure applications inside the phone. That's why we have some issues with mobility because we sell a lot of SIMs in the mobility field.
How are customer service and support?
Support is one of the reasons we chose Cynet. We were looking for a solution that would help us get our cybersecurity certification in Canada, and there are a lot of solutions on the market. To get a certificate, we have to have a contingency plan for when we are attacked, and our internal experts can't deal with it. So we have to know what to do and who we'll call when this happens. A subscription to Cynet ensures that a CSO-certified actor will intervene in an emergency. So Cynet has an excellent solution from a technical standpoint, but they also have a great support system that extends to the attack itself.
How was the initial setup?
The complexity of Cynet's installation is average. There might not be an easier way to deploy the solution because we are incredibly paranoid, so we don't have a centralized way to install the software. Technically, we have to install it unit by unit on PC, so that's slow. You have to go there. And sometimes, it's behaving erratically when you set it up. So if I restart the installation three times on my PC, I may get three different questions at the setup time. So it could be improved.
Once you have done this and everything works, it's one of the easiest installs. Each instance takes about a minute to install when it works. So you install the software, and after that, it automatically updates itself. It does everything by itself. And it does not ask you difficult questions. It only asks you to install it in administrative mode, which is a pretty common request for security software. The only issue is that, from time to time, you technically have a USB key trying to install the software, and it's trying to scan every user's PC around there. And every time it scans, it cannot access the other computer because we have security sync. So you need to restart two or three times. Eventually, it goes through and works nicely. So if it resolved that glitch, it would be the easiest software in the world to install.
One criticism is that the online documentation does not detail too much. Maybe I was just unable to find what I was looking for, or Cynet isn't trying to give too much information to anybody other than those doing the deployment. But aside from the hangups you encounter from time to time, it's an easy software to deploy.
What other advice do I have?
I rate Cynet eight out of 10. It's decent. It could be improved, but it's a complete solution for us, and they provide excellent technical support, which is a critical requirement for us. I can offer one piece of advice to Cynet that no one else will give them. Our company is based in Canada, but it sells to telecom providers worldwide. We have customers in Western Africa and North Africa where there is a potential market for Cynet. The only problem is that Cynet is known as an Israeli solution. Personally, I have no issues with the high-quality Israeli product, but some of our customers are sensitive in those markets. Suppose we had a separate version that is white label or branded for another market. In that case, we probably could sell a lot of Cynet software there because we have a unique connection with the telecom providers.
We are already on their list of certified solutions, and we provide about 400 million telecom security solutions in that market. So this is where we are and again. We are happy with the Cynet. We probably could sell a lot — I'm talking tens or even hundreds of thousands of seats — but some of our customers are extremely sensitive. On the one hand, they appreciate the Israeli solution, but on the other, they have to respond to public pressure.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.