Atlassian is now part of the Open Cybersecurity Schema Framework!

[#1]

We’re excited to be a part of the Open Cybersecurity Schema Framework, which is now generally available for all security teams to adopt! The OCSF is the first vendor-agnostic, open-source initiative of its kind led by Splunk, Amazon Web Services (AWS), and IBM.

By using the framework, security teams can save loads of time on data normalization, freeing them up to analyze data sooner and detect threats faster.

“The OCSF is the first vendor-agnostic, open-source initiative of its kind,” said Bala Sathiamurthy, Chief Information Security Officer, Atlassian. “At Atlassian, we know that detecting and stopping cyberattacks is impossible alone, but with more companies adopting the OCSF we’re confident that we’ll grow stronger together. We’re proud to contribute to the OCSF and collaborate with members to exchange solutions so that we can all begin speaking the same data language.”

A huge Kudos to our very own Zachary Schmerber, Benjamin James, Ben Thompson and the team for leading this initiative internally at Atlassian, collaborating with members, and helping us all speak the same data language! )Find out how you can join OCSF here: https://www.businesswire.com/news/home/20230808950553/en/OCSF-Celebrates-First-Anniversary-with-the-Launch-of-a-New-Open-Data-Schema

[Thomas L]

This is great news!

Security event taxonomy is a struggle, especially when communicating details across different departments - When I say "Actor", I don't mean Hollywood :).

Are there examples of how security teams could implement the OSCF schema in their atlassian products to track and manage security events?

For example, security events in Jira SM would be neat, but they wouldn't really 'fit' into any existing work categories without some creative repurposing. 

Excited to see where this could go!