What is our primary use case?
The reason why I choose SentinelOne right now is that I can fork timelines. I can create serialization or my own fingerprints for the use cases. Or I can actually look for unknown unknowns. Where in CylanceOPTICS, I don't have that functionality, but what you can do in Cylance is, like, you can create artifacts.
Cylance also lets you classify different severities of AV detections, while SentinelOne uses signatures. So, they work slightly differently. In my opinion, Cylance might be lighter, but both are competitors with similar functionality, just a different approach. That's about it.
What is most valuable?
It's the whole suite. Like, you can't really use one aspect of it without having to use the other. Unless you can resolve it using the built-in AV detector.
In future releases, I would like to see more features around analysis for remote devices.
What needs improvement?
CylanceOPTICS could benefit from more granular control in the timeline-building process. Ideally, users would be able to drill deeper into the analysis rather than have the machine dictate the direction.
For example, if you want to open and analyze a specific driver, SentinelOne allows you to do that, but CylanceOPTICS currently doesn't offer that flexibility.
For how long have I used the solution?
I used it more than two years ago. But then, once I started using SentinelOne, I got much more familiar with that. And then I seldom use it now.
I work with the latest because I'm grandfathered into a major distributor's program. I've been using it since practically the beginning before it was widely known. So, updates are automatic for us. Though I haven't used it recently, I'm sure logging into the cloud would show me the latest version.
What do I think about the stability of the solution?
I would rate the stability a nine out of ten. I would give it a close ten as possible because, like SentinelOne, I've seen incompatibility. Whereas Cylance, I've seen none. So I can play nice with products that are like Kaspersky or Bitdefender or something like that or even Windows Defender; it plays very nice with it. But it does not play nice with SentinelOne. I tried putting them both on the same machine once, and it actually killed it; the machine was, like, gone.
What do I think about the scalability of the solution?
It is a very scalable product. I can go from, like, five hundred to a million copies. So if I want, I'm not limited.
So, I would rate the scalability a nine out of ten. I plan on using it more on remote devices.
How are customer service and support?
The customer service and support were okay. The tier I support is not great, but the higher support is great.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I'm getting more familiar with SolarWinds, but it's more of a monitoring tool. I also use SentinelOne. CylanceOPTICS and SentinelOne Singularity are both Endpoint Detection and Response (EDR) solutions, but they differ in their technical approaches.
CylanceOPTICS is similar to SentinelOne's singularity, but it's a different pro. It's almost the same thing, but you can list artifacts and look at other correlation points within the actual, like AV. It communicates within all the agents; they communicate together to make this, like, big picture of, like, timelines and extrapolation of, like, anti-malware information.
So, you could find all the threats in your environment. But it's very similar to SentinelOne. It's using a different methodology, like deep machine learning for antivirus. And it's a component of the protection, but it's more geared towards, like, SIEM, right, where it collects information.
And then you can upload packages where, let's say, you get a solution for a virus. That's moving laterally. You can upload the solution to a product; let's say that the product, for whatever reason, lost capability and can't communicate on the network, but the virus can. Then, you can isolate the product and upload the packages. And then, with the packages, it's not upgrading the software. It's, like, the solution to the AV. Then, once you inoculate the AV using CylanceOPTICS, you can move from one machine that has been isolated to another that has been isolated. You get me in the environment. So CylanceOPTICS allows you to do something like that.
How was the initial setup?
The initial setup is easy peasy. I would rate my experience with the initial setup a nine out of ten, with ten being easy.
The only thing that's interesting that the configuration of it is has become a little bit more complex. But the initial setup is easier than anyone can imagine.
What about the implementation team?
I did it myself. I went out to a site. I also did a POC for Cylance because we were testing it. We found it worked in our environment, so my current company asked me to check out what was going on with this other company. They had been breached, and I was able to isolate the problem and inoculate it. They were impressed and wanted Cylance. So, in a way, we were the third party that took care of Cylance for them.
For the deployment process, we install an agent. Download it from the cloud or the tenant suite, deploy it with a remote tool, GPO, or even manually download and install it. Then, from the cloud, we can uninstall it without being present on the device. We can also remove it from the cloud, but that's one thing we have to do manually. We can't just delete it and forget it. We have to go in and remove that license, which would be nice to automate.
In SentinelOne, you delete it, and it's really gone. But here, it sits there. It might not do anything, but it'll still detect malware, even if it's not connected to the cloud. But you're still getting billed on the cloud because we have to manually go in there and remove it.
The product itself communicates to the cloud when it does deep analysis. It uses a mathematical algorithm to detect whether a product on our computer is malicious or not. We can log into a website portal that shows all the information collected by the agents we've installed in your environment.
So it's, like, a tenant collector, and we go there, and we can rate things, observe things, change things. It's a full-blown product. It's a website within their organization that extrapolates information from all the agents. We're basically using their software. So, imagine everything is using the cloud right now. We log into a website server, but rest assured; it's in the cloud.
The actual Cylance itself, the Protect, depends on how many machines there are. When I did it, I didn't have GPO functionality, so I did everything manually. It took a while. But with GPO, I could get it done in one afternoon. So it depends on the number of machines. I did it on 300-400 machines, which took about a week. But, with GPO, I can get it done in an afternoon.
For the OPTICS, once the Protect is on the machine, it's within seconds. I just download and flag it, and it creates a client and installs it. I can install it from the web interface for the machine or upload it directly from the interface. Basically, I create it like the main client. I can download it or be on the machine physically; it's the same.
It's like yet another small client that attaches to the main one. But they're very small, only 30-50 megabytes. These client installation files are very small.
That's basically it. It's very simple.
For the OPTICS, we don't need many people for maintenance. CylanceOPTICS has administrators who come in to make sure it's doing things as it should. We can't buy OPTICS an administrator overseeing things, like making sure signatures are being kept and updated.
The product itself updates automatically, but every six months, you'll get a new version regardless of whether you need it or not. We can choose to update, though, which is a feature I like. They have something called Test, Co-Pilot, and Absolute. The Absolute basically puts all your nodes in there, like user definitions, and the update or the Co-Pilot takes precedence over the Test.
So, if we have machines in Test, nothing gets updated. But we can update, maybe one or two machines. If we have Co-Pilot and you could test it out, say, "Oh, let me test the new version, see how it goes," then we can reverse it if we want to, like, reverse the patch or reverse the update if you find any bugs in it. So that's a really cool feature.
What's my experience with pricing, setup cost, and licensing?
The pricing for CylanceOPTICS is very good; I would rate it around a nine on a scale of one to ten, with ten being the lowest. It's one of the most affordable options I've seen.
For example, I pay around $4.50 per month for Protect and $1.50 for Optics. So for both, it would be around $6 per month per client. Under $100 per client makes it affordable for what it does.
Which other solutions did I evaluate?
I don't consider CylanceOPTICS as an EDR. It's more like a collector for events on a machine. EDRs allow you to dig deeper into identifying malware and provide more information than traditional AVs. Additionally, you can configure them to look for specific indicators of compromise.
While other AVs just do their basic function, CylanceOPTICS allows you to customize these detections. For example, you can tell it to scan for specific drivers or monitor the processor activity. No other product, including SentinelOne from what I know, offers this level of customization.
I started using CylanceOPTICS on my own because I'm a researcher who likes to analyze things in depth. When I transitioned to next-generation AV, CylanceOPTICS was one of the first options I tried, and I liked it so much that I kept using it. I also tried SentinelOne and compared them both, and CylanceOPTICS just allowed me to go deeper into the analysis, which is what I prefer.
What other advice do I have?
Overall, I would rate the solution a nine out of ten.
Which deployment model are you using for this solution?
Public Cloud