ESET Partners with Alphabet’s Chronicle

0

ESET, announced it has partnered with Chronicle, an Alphabet company, to provide essential validation on security incidents and alerts within Backstory, Chronicle’s global cloud service where companies can privately upload, store, and analyze their internal security telemetry to detect and investigate potential attacks. ESET’s partnership with Backstory will provide customers enhanced insight enabling better protection from advanced persistent threats.

With more than 30 years of cybersecurity innovation, ESET protects over 110 million users in 200 countries and territories globally. Almost 40 percent of ESET’s employees work in research and development, keeping both ESET customers and the world at large safe from the latest and most advanced cyberthreats. ESET’s threat intelligence data blocks targeted attacks, protects against phishing, stops botnets and detects advanced persistent threats.

“Our partnership with Chronicle will lead to simpler, faster and more streamlined remediation of advanced persistent cyber threats,” said Tony Anscombe, global security evangelist and industry ambassador, ESET. “Together, customers will be able to quickly understand incidents in more detail, take the appropriate actions and stay one step ahead of bad actors. This truly will make the world a safer place,” added Anscombe.

“We are thrilled to bring onboard ESET as an Insight Partner,” said Ansh Patnaik, Chief Product Officer, Chronicle. “As a global platform designed to analyze enterprise security telemetry, Backstory provides more value to customers when it’s integrated with other key technologies within the customers’ networks. We believe our collaboration with ESET gives customers a broader, more accurate view of threats within their networks.”

 

 



Warning: Unknown: open(/home/79277/data/tmp/sess_0a306d1757173fc3b708d3a5824ad765, O_RDWR) failed: Disk quota exceeded (122) in Unknown on line 0

Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/home/79277/data/tmp) in Unknown on line 0