LogRhythm and FireEye announce partnership

News

LogRhythm and FireEye announce partnership

Warwick Ashford

LogRhythm's next-generation security information and event management (SIEM) technology is to be integrated with FireEye's malware protection system (MPS).

The tightly integrated combined offering will provide enterprises with next-generation multi-dimensional big data security analytics with advanced malware protection, according to the two companies.

The integration will enable additional intelligence to be fed into LogRhythm by having standardised parsing rules for FireEye MPS.

The rules are distributed free of charge to existing customers and will be automatically included for any new customers.  

LogRhythm’s multi-dimensional security analytics capabilities will extend the value of FireEye’s threat intelligence platform by interpreting and correlating data from across an organisation, said Brent Remai, chief marketing officer at FireEye.

“We look forward to working with LogRhythm to provide joint customers with greater protection from today’s advanced threats and to enable them to respond more effectively to a rapidly evolving threat landscape,” he said.

Key benefits of the integrated offering include analytics for malware statistics, improved corroboration and risk-based prioritisation of security events, enhanced modeling of malware, and deep forensic visibility into malware attack vectors and patterns.

“The integration of FireEye and LogRhythm represents two next-generation solutions working together to combat today’s increasingly sophisticated cyber threats,” said Matt Winter, vice-president of corporate and business development at LogRhythm.


Email Alerts

Register now to receive ComputerWeekly.com IT-related news, guides and more, delivered to your inbox.
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
 

COMMENTS powered by Disqus  //  Commenting policy