Vulnerabilities / Threats

7/26/2016
07:30 AM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

SentinelOne Offers $1 Million Guarantee To Stop Ransomware

Jeremiah Grossman continues his crusade to make security vendors take responsibility for their own gear.

Endpoint security firm SentinelOne is now backing its ability to block or remediate ransomware attacks with a guarantee of $1,000 per endpoint or up to $1 million per organization, the company announced today.

This move is also a sign that SentinelOne's new chief of security strategy, Jeremiah Grossman, is continuing his crusade to make security companies take on more legal responsibility for the effectiveness of their products. It's a mission he started several years ago while still with White Hat Security, which offered breach loss coverage up to $500,000 and a full-refund warranty.  

Ransomware guarantee

Although the average cost of a ransom payment may still be below $1,000 per endpoint, the overall cost of an attack may be much higher once the costs of downtime, forensic investigations, compliance fines, replacement infrastructure is included, not to mention damaged reputation, are included. Many organizations have been stuck paying up ransoms because of a combination of increasingly sophisticated cryptoransomware and inadequate backup alternatives.

By the time ransomware attackers ask for payout, they may already have the victim organization in a chokehold. In some cases, security teams can crack the crypto; in others, they cannot. However, before ransomware gets to the point of loudly announcing intself to the unfortunate end user, it's banging around the endpoint rather noisily engaging in abnormal behavior -- like scanning full file systems and beginning to encrypt them. 

So, even if a new strain of ransomware has never been seen before and has no signature, the behavior is so common to it that SentinelOne feels confident its behavioral analysis technology can detect unknown ransomware by monitoring for this sort of behavior. (The old-fashioned "locker" ransomware that didn't encrypt files has fallen out of favor, says Grossman, and ransomware operators' "path forward is really good end-to-end crypto.")

The importance of liability 

Despite the confidence in the technology and the guarantee, Grossman doesn't expect that SentinelOne's product will catch every instance of ransomware every time, though.

That hasn't stopped him from pushing for security companies to provide more liability protection -- and for software companies to take more responsibility for their security. He's received some pushback, though. "The argument [against it] is that 'you can't guarantee security,'" Grossman says. "While that's true, can we guarantee it 99% of the time?"

Grossman's counterargument is that automakers and electronics companies don't expect that every one of their products will be perfect, either, but that doesn't stop them from providing customers with product warranties that exist to cover the times when their products are not perfect. His attraction to joining SentinelOne was that they were able to provide the kind of data that insurance providers would require in order to back the kind of guarantee SentinelOne will offer.

So, despite resistance of others in the infosec community, Grossman has been unwavering in his sentiments. "I heard them loud and and clear," he says, "I just wasn't hearing them."

"Customers are now asking for this," he says, and he urges end users to keep asking security vendors for more liability, because that will push the needle forward.

Black Hat USA returns to the fabulous Mandalay Bay in Las Vegas, Nevada July 30 through Aug. 4, 2016. Click for information on the conference schedule and to register.

When asked if skepticism about and resistance to guarantees was to be expected from an infosec industry, which is risk-averse, Grossman countered that they are "risk-averse only in relation to themselves" and don't mind if their customers are at-risk.

Grossman will be presenting a session at the Black Hat conference next week about cyber insurance and some how-tos about providing guarantees like this one. 

"Fifteen years ago I knew that appsec was a problem, and 'kicking and screaming, I dragged the industry along," he says. "It's time to do it again."

Related Content:

Sara Peters is Senior Editor at Dark Reading and formerly the editor-in-chief of Enterprise Efficiency. Prior that she was senior editor for the Computer Security Institute, writing and speaking about virtualization, identity management, cybersecurity law, and a myriad ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
'Hidden Tunnels' Help Hackers Launch Financial Services Attacks
Kelly Sheridan, Staff Editor, Dark Reading,  6/20/2018
Tesla Employee Steals, Sabotages Company Data
Jai Vijayan, Freelance writer,  6/19/2018
Inside a SamSam Ransomware Attack
Ajit Sancheti, CEO and Co-Founder, Preempt,  6/20/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-12538
PUBLISHED: 2018-06-22
In Eclipse Jetty versions 9.4.0 through 9.4.8, when using the optional Jetty provided FileSessionDataStore for persistent storage of HttpSession details, it is possible for a malicious user to access/hijack other HttpSessions and even delete unmatched HttpSessions present in the FileSystem's storage...
CVE-2018-12684
PUBLISHED: 2018-06-22
Out-of-bounds Read in the send_ssi_file function in civetweb.c in CivetWeb through 1.10 allows attackers to cause a Denial of Service or Information Disclosure via a crafted SSI file.
CVE-2018-12687
PUBLISHED: 2018-06-22
tinyexr 0.9.5 has an assertion failure in DecodePixelData in tinyexr.h.
CVE-2018-12688
PUBLISHED: 2018-06-22
tinyexr 0.9.5 has a segmentation fault in the wav2Decode function.
CVE-2018-10002
PUBLISHED: 2018-06-22
ruby-ffi version 1.9.23 and earlier has a DLL loading issue which can be hijacked on Windows OS, when a Symbol is used as DLL name instead of a String This vulnerability appears to have been fixed in v1.9.24 and later.