Salem Cyber Doc Site
  • 🏠Documentation Home
  • ✨Initiation Guides
    • Quickstart: Deploy Salem
    • Admin Guide
    • Installing Teams App
    • Installing Browser Extension
    • Feature Overview
  • ✨General Guides
    • Managing Alerts
    • Managing Questions
    • Threat Notification Management
    • Uploading Files
    • Logical Operations
  • ✨Configurations Specification
    • Configuration Home
    • Action Conf
      • "match" ActionConfs
      • "webhook" ActionConfs
      • "llm" ActionConfs
    • Action Definition
      • Azure Log Analytics
      • Microsoft Graph API
      • Splunk Search
      • Bring Your Own LLM
    • Parsing Conf
      • Summary Details
    • Report Conf
    • LLM Configuration
  • 💾Changelog
    • Dec 5th '24: Get cracking on your holiday shopping list
    • July 18th, ’24: Beat the heat and the hackers
    • Apr 17th, '24: Alert showers make analysts sour... no longer with Salem!
    • Mar 5, '24: They're after me (and your) secure systems! We're na-tur-ally suspicious
    • Jan 31, '24: New year, new me... and a new way to extract data from your alerts
    • Dec 21, '23: Jingle bells, WannaCry smells, your escalated alert just laid an egg
    • Nov 14, '23: Stuff the turkey or stuff cyber alerts with context... Why not both?
    • Oct 25, '23: Llama, llama on the wall which alert is scariest of them all
    • Sept 19, '23: Context building via true positive/false positive workflow
    • Sept 1, '23: Alert report UI, webhook actions, and question upgrades
Powered by GitBook
On this page
  • Microsoft Graph API - Webhook Action
  • Configuring Microsoft Graph API
  • 1. Credentials/Authentication
  • 2. Input Keys - User input
  • 3. Requests - HTTP requests
  1. Configurations Specification
  2. Action Definition

Microsoft Graph API

PreviousAzure Log AnalyticsNextSplunk Search

Last updated 1 year ago

Security analysts use the Microsoft Graph security API to investigate cyber alerts by consolidating and correlating security alerts from multiple sources, enriching security alerts with additional context, and automating security investigations.

Salem offers configurable integrations with a customer's Microsoft Graph API to automate the process of building context around alerts. Users can create webhook ActionConfs that accept query instructions from users and apply the information in the response to alert data to identify endpoints, system activity, or other context building activity.

Description: In the default case, Salem retrieves data from a Microsoft Graph API resource by authenticating using a secret stored in a digital key vault and returning data based on a user-defined query. The user can then process the output using an to build Salem .

Request Workflow:

  1. The user defines the Microsoft Graph API endpoint to query in the api_path input field.

  2. The user refines the results of the query by including optional query parameters in the select, search, and filter input fields.

  3. Salem retrieves a bearer token using the secret value uses this value to authenticate against the defined endpoint. An HTTP GET request is .

  4. The filters defined in step 2 are passed with the request to narrow the response data.

By default, the Microsoft Graph API ActionDefinition expects a key vault resource that contains a client secret. This secret is passed as part of the bearer token request. To match this configuration, create a secret value in a key vault resource Salem can access.

The default Microsoft Graph API ActionDefinition includes 4 fields for the user to define as part of the request generation:

  • api_path - The Microsoft Graph API endpoint that the user wants to query

  • select - Optional parameter to select which fields to return from the API. Not all fields are returned by default, so leaving this field blank is not always a good idea

  • search - Optional parameter to search for specific results from the API query

  • filter - Optional parameter to filter for specific results from the API query

The format/structure of requests made by Salem to the target resources (defined in other parameters) is defined in this object.

In the default case, Salem uses OAuth2 to authenticate using a key vault secret and then includes the resulting bearer token as part of the query to Microsoft Graph API. The user input, as described in the preceding section, is also passed as part of the request to Microsoft Graph API.

✨
1. Credentials/Authentication
2. Input Keys - User input
3. Requests - HTTP requests
ActionConfs
Microsoft Graph API - Webhook Action
Configuring Microsoft Graph API
eval string