Protect your Identities with Azure AD Identity Protection (part 2)

By Ashwin Venugopal -

 


To read part 1 please click here


Multi-factor Authentication (MFA) Registration Policy

MFA adds an extra second layer of protection to your users' identities according to which the user has to go through an additional verification step after they successfully provide their username and password. This policy can also be configured so that you can enforce sign-in risk policies which allows the users to self-remediate after a sign-in risk is detected.

After you configure an MFA registration policy, the user is asked to register when they sign in and must complete the registration within 14 days, but they can also choose to skip signing in during that period. After 14 days, they'll have to complete the registration before they are allowed to sign in again.

Remediate risks detected by Azure AD Identity Protection

Investigate risks

Identity Protection provides the reports you can easily use to investigate identity-based risks detected for your organization's users. The reports also helps you to understand how to better prevent risks and improve your security stance for identities. 

You can also access risk detection type reports, which combines the information about the risky user detections as well as sign-in detections and use these reports how different risk types are related and take appropriate action. 

You can easily view and download all the reports from the Azure portal.

Remediate risks

When your investigation is complete, and you want to remediate the risk even if you are not already using the risk policies to automatically deal with them; the following ways and methods to remediate risks hugely depends on your organization's needs.

Remediation method

Description

Self-remediation

If you configure risk policies, you can let the users to self-remediate. When Identity Protection has detected a risk, the users either reset their password or go through the MFA to unblock themselves. After the self-remediation, these detected risks are considered closed.  

Reset passwords manually

For some organizations, the automated password reset might not be an option. In this case, the admin can manually enforce password resets.

Dismiss user risk detections

Sometimes, the password reset isn’t possible. In this case, you can dismiss the risk detections for the user and all the associated risk detections for the user will be closed.

Close individual detections

All detected risks contribute to an overall risk score for a user that represents the probability that a user account is compromised. The admin can also choose to close the individual risk detections, and lower the overall risk of a user’s account.

 

Unblock users

User accounts can be blocked by the risk policies or manually by the admin after an investigation, but their unblocking depends on the type of risk that caused the blockage:
  • Accounts blocked because of sign-in risk- It can be unblocked by excluding the user from the policy if the admin asks the user to sign-in from a familiar location or device. There might be an alert for any suspicious behavior based on what's known about the user account's sign-in patterns, but the policy can also be disabled if the admin found issues with it.

  • Accounts blocked because of user risk- An account might be blocked if the user was flagged because of a possible risky behavior and the admin can reset the password for the user to unblock the account as well as dismiss the particular activity identified as risky or exclude the user from the policy. If the policy is causing problems for many users, then the admin can also completely disable the policy itself. 


To read part 1 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

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

Threat Hunting in Microsoft Sentinel (part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Introducing the Microsoft Sentinel Hunting Page Threat hunting is a series activities performed while investigating and as there are no guidelines to perform it, the available tools on the Microsoft Sentinel can be introduced to perform better in your investigations. Firstly, you have to choose the Hunting link in the Microsoft Sentinel navigation menu to get to the Hunting page which is divided into the following sections: The header bar- It is located at the top of the page as usual and contains Refresh as well as timespan drop down menu. The New Query button can help you with creating a new query and the Run all queries button can run all the hunting queries in the background while also updating the hunting query list section with the number of results found.  The summary bar- Here, you can view the total number of queries available to run, the total number of bookmarks, the number of results from running live
Read more