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

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

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
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