Application Security (part 2 of 3)

By Ashwin Venugopal -

 


To read part 1 please click here
To read part 3 please click here


Microsoft Graph Permissions

Microsoft graph exposes granular permissions that can control the access that apps have to resources, like users, groups, and mails and as a developer you can decide which permissions to request for Microsoft Graph, as well as the apps that don't take a signed-in user, permissions can be pre-consented to by an administrator when the app is installed.

Microsoft Graph has two types of permissions-

  1. Delegated Permissions are used  by apps that has a signed-in user present. Some delegated permissions can be consented by non-administrative users, but some higher-privileged permissions required administrator consent.
  2. Application Permissions are used by apps that runs without a signed-in user present. They can only be consented by an administrator.

Effective permissions are the permissions that your app will have when making requests to the Microsoft Graph and for the delegated permissions, the effective permissions of your app will be the intersection of the delegated permissions the app has been granted (via consent) and the privileges of the currently signed-in user. 

Whereas for application permissions, the effective permissions of your app will be the full level of privileges implied by the permission. 

Microsoft Graph API

You can use the Microsoft Graph Security API to connect the Microsoft security products, services, and partners to streamline security operations and improve threat protection, detection, as well as response capabilities. 

The Microsoft Graph Security API federates requests to all providers in the Microsoft Graph Security ecosystem. This is based on the security provider consent provided by the application, as shown in the following diagram:


The following is the description of the flow:

  1. The application user signs in to the provider application to view the consent form from the provider which is owned by the provider and applies to non-Microsoft providers only to get explicit consent from their customers to send requests to Microsoft Graph Security API.
  2. The client consent is stored on the provider side.
  3. The provider consent service calls the Microsoft Graph Security API to inform consent approval for the respective customer.
  4.  The application sends a request to the Microsoft Graph Security API.
  5. The Microsoft Graph Security API checks for the consent information for this customer mapped to various providers.
  6. The Microsoft Graph security API calls all those providers the customer has given explicit consent to via the provider consent experience.
  7. The response is returned from all the consented providers for that client. 
  8. The result set response is returned to the application.
  9. If the customer has not consented to any of the provider, no results from those providers are included in the response.

The Microsoft Graph Security API makes it easy to connect with the security solutions from Microsoft and partners.

Why use the Microsoft Graph Security API?

  • Write code- Find code samples in C#, Java, NodeJS, and more.
  • Connect using scripts- Find PowerShell samples.
  • Drag and drop into workflows and playbooks- Use Microsoft Graph security connectors for Azure Logic Apps, Microsoft Flow, and PowerApps.
  • Get data into reports and dashboards- Use the Microsoft Graph Security connector for power BI.
  • Connect using Jupyter notebooks- Find Jupyter notebook centers.

Unify and standardize alert tracking

Once connected it can integrate alerts from any Microsoft Graph-integrated security solution and keep alert status and assignments in sync across all solutions and you can also stream alerts to Security Information and Event Management (SIEM) solutions, like Splunk using Microsoft Graph Security API connectors. 

Correlate security alerts to improve threat protection and response

Correlate alerts across security solutions more easily with a unified alert schema. This not only allows you to receive actionable alert information but allows security analysts to pivot and enrich alerts with asset and user information, enabling faster response to threats and asset protection.

Update alert tags, status, and assignments

Tag alerts with additional context or threat intelligence to inform response and remediation. You can use Webhook subscriptions to get notified of changes.

Unlock security context to drive investigation

Dive deep into related security-relevant inventory (like users, hosts, and apps), then add organizational context from other Microsoft Graph providers to bring business as well as security contexts together and improve threat response.


To read part 1 please click here
To read part 3 please click here


Comments

Post a Comment

Popular posts from this blog

Query, Visualize, & Monitor Data in Azure Sentinel

By Ashwin Venugopal -
Image
  Azure Sentinel Workbooks Several ready for use templates are provided by the Azure Sentinel that can be used to create your own workbook and then modify them as needed for Contoso. Most of the data connectors it uses to ingest data come with their own workbooks, but better insight can be obtained by simply looking into the data that is being ingested by using tables and visualizations, including bar and pie charts. You can also make your own workbook easily by using this data from the beginning instead of using the predefined templates. Workbook Page You can easily access the workbook page from the Azure Sentinel from the navigation pane which consists of the: Workbook header- You can add a new workbook and review the saved workbooks as well as templates that are available on the workbook page. Templates section- You can access existing workbook templates on the Templates tab. You can save some of the workbooks for quick access and they will appear on the My Workbooks tab.  From the
Read more

Planning for Implementing SAP Solutions on Azure (Part 2 of 5)

By Ashwin Venugopal -
Image
  To read part 1 please click  here To read part 3 please click  here To read part 4 please click  here To read part 5 please click  here Load Balancing The load balancer uses probe ports to determine as well as route the traffic to an active DBMS node, but of there's any failover then the most common SAP application architecture can automatically reconnect against the private virtual IP address without the need for the SAP application to reconfigure it, while the load balancer redirect the traffic against the private virtual IP address without any need for the SAP application to reconfigure. The loaf balancer also offers an option of DirectServerReturn which if configured, can help in directing the traffic from the DBMS VM to the SAP application layer directly to the application layer without routing through the load balancer. But, if it isn't configured, then the return traffic to the SAP application layer is routed through the load balancer. You can also use Azure Load Balan
Read more

Work with String Data Using KQL Statements

By Ashwin Venugopal -
Image
  Extract Data from Unstructured String Fields Unstructured string fields often contains the Security log data and requires parsing to extract data. There are multiple ways of pulling information from string fields in KQL and the two primary operators used are extract and parse.  Extract It gets a match for a regular expression from a text string. You can convert the extracted substring to the indicated type.  Arguments regex- A regular expression. captureGroup- A positive int constant indicating the capture group to extract. 0 stands for the entire match, 1 for the value matched by the first '('parenthesis')' in the regular expression, 2 or more for subsequent parenthesis.  text- A string to search. typeLiteral- An optional type literal. If provided, the extracted substring is converted to this type.  Returns If regex finds a match in text- the substring matched against the indicated capture group captureGroup, optionally converted to typeLiteral. If there's no mat
Read more