December 4, 2018

The following is provided from Microsoft Security and Compliance blogs at TechCommunity:

Today we announced the launch of the Microsoft Graph Security Hackathon. We invite you to join it and submit your creative applications that can help improve organizations’ cyber defenses. You’ll have the chance to win* a piece of the $15,000 cash prize pool as well as a speaking opportunity at Microsoft Build 2019.


Tap into the Microsoft Graph Security API and mash up with other APIs to build solutions that can help streamline security operations. The Microsoft Graph Security API connects multiple security solutions, with a unified schema, to enable easier correlation of alerts, provide access to rich contextual information, and simplify automation. This empowers organizations to quickly gain insights and take actions across their security products, while reducing the cost and complexity of building and maintaining multiple integrations.


What is the Graph Security Hackathon? 

Microsoft Graph Security Hackathon is an online Hackathon available at and is open to individuals, teams and organizations for participation. The goal is to build an application using the Microsoft Graph Security API – feel free to add Microsoft Graph and other APIs to the mix.

Why should I participate? 

In addition to positively impacting organizational security, you have an opportunity to win* a piece of $15,000 cash in prizes with some additional opportunities to be promoted on Microsoft blog channels.

When is this? 

Submission window for this Hackathon runs from December 1, 2018 until March 1, 2019

How to participate?

Further Details

Review the Microsoft Graph Security Hackathon blog post and visit the Hackathon website.

Why wait? Join the #graphsecurityhackathon and invite your friends to join the fun!


*No purchase necessary. Open only to new and existing Devpost users who are the age of majority in their country. Game ends March 1, 2019 at 5:00 PM Eastern Time. For details, see Official Rules.


The above was provided from Microsoft Security and Compliance blogs at TechCommunity

You May Also Like…