Written by 11:18 am Uncategorized

OpenAI gets a new CISO after its leadership exodus 

Dane Stuckey, previously the Chief Information Security Officer (CISO) at Palantir, a leading analytics firm, has now joined OpenAI as its new CISO, TechCrunch reported

 Dane will be working alongside Matt Knight, OpenAI’s Head of Security. Dane’s appointment is preceded by the dramatic departure of several executives at OpenAI, including its CTO Mira Murati. Currently, CEO Sam Altman is one of just two original members of the 11-person founding team who are still actively involved in OpenAI.

Dane while announcing his move on X a few hours ago, wrote: I’m thrilled to announce that I’ve joined as CISO, alongside @embeddedsec, at @OpenAI. Security is germane to OpenAI’s mission. It is critical we meet the highest standards for compliance, trust, and security to protect hundreds of millions of users of our products, enable democratic institutions to maximally benefit from these technologies, and drive the development of safe AGI for the world. I am so excited for this next chapter, and can’t wait to help secure a future where AI benefits us all.

Dane’s 10-year old association with Palantir Technologies ended on October 3rd. He started his journey with Palantir in 2014 on the information security team as a detection engineering and incident response lead.

He calls himself “an information security generalist passionate about detection engineering, incident response, security program development, and Windows platform security.” 

Welcoming Dane on board, Sam Altman wrote on X: “I am so excited about this; Dane is an example of one of those people you meet and 10 minutes in realize you are talking to a genuine expert and great leader.”

Dane’s appointment comes at a when safety issues having been looming large at OpenAI. There have been claims that ChatGPT stores user chats locally without encryption and that the company rushed through safety tests while launching the product. In early 2013, hackers reportedly infiltrated OpenAI, but the company chose not to disclose the breach. 

(Visited 4 times, 4 visits today)
Close