Cloud

6/8/2017
09:57 AM
Dark Reading
Dark Reading
Products and Releases
50%
50%

Former Execs from Cylance, Carbon Black Launch Obsidian Security

NEWPORT BEACH, Calif., June 8, 2017 Obsidian Security today disclosed that it raised $9.5M in Series A funding led by Greylock Partners.  The company will use the funding to grow its product team working at the intersection of security, artificial intelligence and hybrid-cloud technology.

The Obsidian founding team includes Glenn Chisholm, former EVP product organization and CTO at Cylance and CISO at Telstra; Ben Johnson, former co-founder and CTO at Carbon Black, and computer scientist at the NSA; and Matt Wolff, former Chief Data Scientist at Cylance and computer scientist at the NSA.

“Glenn, Ben and Matt are accomplished product innovators and executives, with strong industry backgrounds in security,” said Asheem Chandna of Greylock Partners. “We are excited to closely partner with them on their mission, and help build an important new company.”

Asheem Chandna and Sarah Guo from Greylock Partners will join Obsidian Security CEO Glenn Chisholm and CTO Ben Johnson, on the company’s board of directors.

“At Carbon Black and Cylance, Ben and I developed the industry’s leading next-generation endpoint solutions. In our work with hundreds of enterprises, we both independently saw an even bigger challenge around managing user security,” said Glenn Chisholm. “Our Series A financing and partnership with Greylock allows us to start building a world-class engineering and data science team, focused on user security for hybrid environments. We’re hiring.”

Obsidian Security is headquartered in Newport Beach, CA, adding to what is already a thriving cyber security community in Southern California. The company is focused on building out its initial product team, and adding leading customers as design partners.

About Obsidian Security

Obsidian Security is applying artificial intelligence to enable user security for enterprise hybrid-cloud environments. The company is backed by Greylock Partners and based in Newport Beach, CA. Learn more at http://www.obsidiansecurity.com, and follow Obsidian Security on Twitter, LinkedIn and Facebook.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Want Your Daughter to Succeed in Cyber? Call Her John
John De Santis, CEO, HyTrust,  5/16/2018
New Mexico Man Sentenced on DDoS, Gun Charges
Dark Reading Staff 5/18/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Flash Poll
[Strategic Security Report] Navigating the Threat Intelligence Maze
[Strategic Security Report] Navigating the Threat Intelligence Maze
Most enterprises are using threat intel services, but many are still figuring out how to use the data they're collecting. In this Dark Reading survey we give you a look at what they're doing today - and where they hope to go.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-11354
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, the IEEE 1905.1a dissector could crash. This was addressed in epan/dissectors/packet-ieee1905.c by making a certain correction to string handling.
CVE-2018-11355
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, the RTCP dissector could crash. This was addressed in epan/dissectors/packet-rtcp.c by avoiding a buffer overflow for packet status chunks.
CVE-2018-11356
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the DNS dissector could crash. This was addressed in epan/dissectors/packet-dns.c by avoiding a NULL pointer dereference for an empty name in an SRV record.
CVE-2018-11357
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the LTP dissector and other dissectors could consume excessive memory. This was addressed in epan/tvbuff.c by rejecting negative lengths.
CVE-2018-11358
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the Q.931 dissector could crash. This was addressed in epan/dissectors/packet-q931.c by avoiding a use-after-free after a malformed packet prevented certain cleanup.