Azure Graph Security Integration

Register a new application for the Logsign

These steps are needed to authenticate with the Microsoft Graph Security API.

Follow these steps to register a new application:

Sign in to the Azure Portal with your work account. Note: this stage does not require an AAD tenant admin.

  1. Select Microsoft Entra ID ( Azure Active Directory )
  2. Select App registrations
  3. Select New registration

    Figure 1. AAD App Registration screen

  4. In the new registration form that opens, enter an application name (4).
  5. Select Register (5).

  6. Next, you'll see the overview page (6) and your app ID (7), and Directory (tenant) ID (8). Copy and save these fields. You will need them later to complete the configuration process.
  7. Click on View API Permissions (9) to display the Graph permissions screen.

    Figure 3. Application overview page

  8. In the API Permission screen(10), click on the Add a permission button (11) and select Microsoft Graph (12).

     

    Figure 4. Application permissions

  9. Next, select Application permissions (13) in the Request API permission pane that opens.

    Figure 5. Application Auth mode (permissions)

  10. Under Request API permissions, select SecurityEvents.Read.All, SecurityAlert.Read.All and SecurityIncident.Read.All(14). Then click Add permissions (15).
  11. This step needs to be completed by the Azure Active Directory tenant admin Login to the Azure Portal as the Azure Active Directory Tenant Administrator for your organization and navigate to App registration/API permissions screen. Click on Grant admin consent for 'the AAD tenant' (16).

  12. Under Certificates & secrets (17), choose New client secret (18). A new secret will be displayed in the Value column. Copy this password – this is the only time you'll be able to. You will need it later to complete the configuration process.

     

    Figure 7. Create App secret

 

Logsign Configuration

A user with admin authority must log in to Logsign, then go to Settings -> Integrations -> Data Collection -> + Device, choose API as the method and Azure Graph Security as the Provider, and fill in:

Field Value
Client ID The app ID copied in step 6 above.
Client Secret The client secret copied in step 12 above.
Tenant ID The Directory (tenant) ID copied in step 6 above.
Base URL The Microsoft Graph API base address: https://graph.microsoft.com
Scope The OAuth client-credentials scope: https://graph.microsoft.com/.default. This tells Graph to issue a token for whatever application permissions were granted in step 10 above, rather than naming individual permissions here.

Click Save. If authentication fails, re-check that admin consent (step 11) was actually granted; a missing consent is the most common cause of a token request being rejected even when the Client ID/Secret/Tenant ID are correct.

 

Was this article helpful?
0 out of 0 found this helpful

Articles in this section

See more
Become a Certified Logsign User/Administrator
Sign-up for Logsign Academy and take the courses to learn about Logsign USO Platform in detail. Enjoy the courses, and get your badges and certificates. In these courses, you'll learn how to use Logsign in your work and add value to your career.
Visit Our Blog
Our Logsign USO Platform illustrate our expertise. So do the blog. Through our blog posts, deepen your knowledge on various SecOps topics or get updated about important news & modern approaches for cybersecurity. Get into the habit of reading valuable information provided by Logsign. Be a step ahead.