Cylance, the innovator in AI-based threat prevention, professed “prevention is possible” with the introduction of its next-gen anti-malware solution CylancePROTECT®, which leverages machine learning models to prevent malicious code from executing on endpoints.
With no signatures or constant updates required, Cylance provides superior prevention with minimal impact on the endpoint. Now almost four years and thousands of satisfied customers later, we are proud to say that Cylance delivers reliable, consistent threat prevention which has catalyzed a pivot in how all security vendors talk about security: prevention is possible.
One of the key capabilities of CylancePROTECT is its uncanny ability to prevent threats that have yet to even be created. In fact, in a recent commissioned lab test we found that on average our model prevented threats up to 2.5 years before they were detected in the wild.
That is astounding proactive protection when compared to reactive, signature-based security solutions that falter significantly when even a single update is not applied. We say this to illustrate one point: at Cylance, we are good at predicting the future of threats. It’s built into our products and our culture. So, it should come as no surprise that are continually working on new ways to use AI to solve security problems.
To that end, this week at RSA we will be previewing an industry-first AI security implementation: AI-driven incident prevention in our CylanceOPTICS™ Endpoint Detection and Response (EDR) solution.
The Case for AI-Driven Incident Prevention
There is no doubt that organizations can benefit from EDR products, which enable faster response and remediation to security incidents. However, as with most security technologies, attackers have worked hard to develop tactics, techniques, and procedures (TTPs) to defeat legacy rule-based technologies, making them less effective over time.
The evolution of TTPs and their impact (Read more...)
This is a Security Bloggers Network syndicated blog post authored by The Cylance Team. Read the original post at: Cylance Blog