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

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning...
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can...
Read more