Azure AD Identity Protection (part 1 of 3)

By Ashwin Venugopal -

 




To read part 2, please click here
To read part 3, please click here





Azure AD Identity Protection Explained

Identity protection helps the organizations to achieve following tasks:

  • Automate the detection and remediation of identity-based risk.
  • Investigate the risks using data in the portal.
  • Export risk detection data to third-party utilities for further analysis.

Microsoft analyses 6.5 trillion signals per day generated by and fed to Identity Protection to identify as well as protect customers from the threats. These signals are also fed into tools like Conditional Access to make access decisions, or fed back to a security information and event management (SIEM) tool for further investigation according to your organization's enforced policies.  

Risk Detection & Remediation

Identity Protection can easily determine the risks in the following situations:

Risk Detection Type

Description

Atypical travel

Sign in from an atypical location based on the user’s recent sign ins.

Anonymous IP Address

Sign in from an anonymous IP address (like Tor browser, anonymizer VPNs).

Unfamiliar Sign-in Properties

Sign in with the properties we have not seen recently for the given user.

Malware Linked IP Address

Sign in from a malware linked IP address.

Leaked Credentials

This risk detection indicates that the user’s valid credentials have been leaked.

Azure AD Threat Intelligence

Microsoft’s internal and external threat intelligence sources have identified a known attack pattern.

 

The risk signals will trigger remediation efforts that will require the users to- perform Azure Multi-Factor Authentication, reset their password with the help of self-service password reset, or blocking until an administrator takes an action.

Risk Investigation

Administrators can review detections and take manual actions with the help of the following key reports for investigations in Identity Protection:

  1. Risky users
  2. Risky sign-ins
  3. Risk detections 

Exporting Risk Data

Data can exported to other tools for archive from Identity Protection for further investigation and correlation with the help of the Microsoft Graph based APIs to collect this data for further processing in a tool like SIEM. 

Permissions

Users must have one or more than one of the following roles if they want access: 
  1. Security Reader
  2. Security Operator
  3. Security Administrator
  4. Global Reader
  5. Global Administrator







To read part 2, 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