Merge pull request #199963 from MicrosoftGuyJFlo/GitHubIssue93287

[Azure AD] Identity Protection - Git Hub Issue 93287

Author: BCS2022

articles/active-directory/identity-protection/overview-identity-protection.md

@@ -6,7 +6,7 @@ services: active-directory
 ms.service: active-directory
 ms.subservice: identity-protection
 ms.topic: overview
-ms.date: 06/15/2021
+ms.date: 05/31/2022
 
 ms.author: joflore
 author: MicrosoftGuyJFlo
@@ -31,16 +31,12 @@ The signals generated by and fed to Identity Protection, can be further fed into
 
 ## Why is automation important?
 
-In his [blog post in October of 2018](https://techcommunity.microsoft.com/t5/Azure-Active-Directory-Identity/Eight-essentials-for-hybrid-identity-3-Securing-your-identity/ba-p/275843) Alex Weinert, who leads Microsoft's Identity Security and Protection team, explains why automation is so important when dealing with the volume of events:
+In the blog post *[Cyber Signals: Defending against cyber threats with the latest research, insights, and trends](https://www.microsoft.com/security/blog/2022/02/03/cyber-signals-defending-against-cyber-threats-with-the-latest-research-insights-and-trends/)* dated February 3, 2022 we shared a thread intelligence brief including the following statistics:
 
-> Each day, our machine learning and heuristic systems provide risk scores for 18 billion login attempts for over 800 million distinct accounts, 300 million of which are discernibly done by adversaries (entities like: criminal actors, hackers).
->
-> At Ignite last year, I spoke about the top 3 attacks on our identity systems. Here is the recent volume of these attacks
->   
->   - **Breach replay**: 4.6BN attacks detected in May 2018
->   - **Password spray**: 350k in April 2018
->   - **Phishing**: This is hard to quantify exactly, but we saw 23M risk events in March 2018, many of which are phish related
+> * Analyzed ...24 trillion security signals combined with intelligence we track by monitoring more than 40 nation-state groups and over 140 threat groups...
+> * ...From January 2021 through December 2021, we’ve blocked more than 25.6 billion Azure AD brute force authentication attacks...
 
+This scale of signals and attacks requires some level of automation to be able to keep up.
 ## Risk detection and remediation
 
 Identity Protection identifies risks of many types, including:
@@ -53,7 +49,7 @@ Identity Protection identifies risks of many types, including:
 - Password spray
 - and more...
 
-More detail on these and other risks including how or when they are calculated can be found in the article, [What is risk](concept-identity-protection-risks.md).
+More detail on these and other risks including how or when they're calculated can be found in the article, [What is risk](concept-identity-protection-risks.md).
 
 The risk signals can trigger remediation efforts such as requiring users to: perform Azure AD Multi-Factor Authentication, reset their password using self-service password reset, or blocking until an administrator takes action.
 
@@ -69,17 +65,17 @@ More information can be found in the article, [How To: Investigate risk](howto-i
 
 ### Risk levels
 
-Identity Protection categorizes risk into three tiers: low, medium, and high. 
+Identity Protection categorizes risk into tiers: low, medium, and high. 
 
-While Microsoft does not provide specific details about how risk is calculated, we will say that each level brings higher confidence that the user or sign-in is compromised. For example, something like one instance of unfamiliar sign-in properties for a user might not be as threatening as leaked credentials for another user.
+While Microsoft doesn't provide specific details about how risk is calculated, we'll say that each level brings higher confidence that the user or sign-in is compromised. For example, something like one instance of unfamiliar sign-in properties for a user might not be as threatening as leaked credentials for another user.
 
 ## Exporting risk data
 
 Data from Identity Protection can be exported to other tools for archive and further investigation and correlation. The Microsoft Graph based APIs allow organizations to collect this data for further processing in a tool such as their SIEM. Information about how to access the Identity Protection API can be found in the article, [Get started with Azure Active Directory Identity Protection and Microsoft Graph](howto-identity-protection-graph-api.md)
 
 Information about integrating Identity Protection information with Microsoft Sentinel can be found in the article, [Connect data from Azure AD Identity Protection](../../sentinel/data-connectors-reference.md#azure-active-directory-identity-protection).
 
-Additionally, organizations can choose to store data for longer periods by changing diagnostic settings in Azure AD to send RiskyUsers and UserRiskEvents data to a Log Analytics workspace, archive data to a storage account, stream data to an Event Hub, or send data to a partner solution. Detailed information about how to do so can be found in the article, [How To: Export risk data](howto-export-risk-data.md).
+Additionally, organizations can choose to store data for longer periods by changing diagnostic settings in Azure AD to send RiskyUsers and UserRiskEvents data to a Log Analytics workspace, archive data to a storage account, stream data to Event Hubs, or send data to a partner solution. Detailed information about how to do so can be found in the article, [How To: Export risk data](howto-export-risk-data.md).
 
 ## Permissions
 
@@ -92,25 +88,25 @@ Identity Protection requires users be a Security Reader, Security Operator, Secu
 | Security operator | View all Identity Protection reports and Overview blade <br><br> Dismiss user risk, confirm safe sign-in, confirm compromise | Configure or change policies <br><br> Reset password for a user <br><br> Configure alerts |
 | Security reader | View all Identity Protection reports and Overview blade | Configure or change policies <br><br> Reset password for a user <br><br> Configure alerts <br><br> Give feedback on detections |
 
-Currently, the security operator role cannot access the Risky sign-ins report.
+Currently, the security operator role can't access the Risky sign-ins report.
 
 Conditional Access administrators can also create policies that factor in sign-in risk as a condition. Find more information in the article [Conditional Access: Conditions](../conditional-access/concept-conditional-access-conditions.md#sign-in-risk).
 
 ## License requirements
 
 [!INCLUDE [Active Directory P2 license](../../../includes/active-directory-p2-license.md)]
 
-| Capability | Details  | Azure AD Free / Microsoft 365 Apps | Azure AD Premium P1|Azure AD Premium P2 |
+| Capability | Details | Azure AD Free / Microsoft 365 Apps | Azure AD Premium P1 | Azure AD Premium P2 |
 | --- | --- | --- | --- | --- |
-| Risk policies | User risk policy (via Identity Protection)  | No | No |Yes | 
-| Risk policies | Sign-in risk policy (via Identity Protection or Conditional Access)  | No |  No |Yes |
-| Security reports | Overview |  No | No |Yes |
-| Security reports | Risky users  | Limited Information. Only users with medium and high risk are shown. No details drawer or risk history. | Limited Information. Only users with medium and high risk are shown. No details drawer or risk history. | Full access|
-| Security reports | Risky sign-ins  | Limited Information. No risk detail or risk level is shown. | Limited Information. No risk detail or risk level is shown. | Full access|
-| Security reports | Risk detections   | No | Limited Information. No details drawer.| Full access|
-| Notifications | Users at risk detected alerts  | No | No |Yes |
-| Notifications | Weekly digest| No | No | Yes | 
-| | MFA registration policy | No | No | Yes |
+| Risk policies | User risk policy (via Identity Protection) | No | No | Yes | 
+| Risk policies | Sign-in risk policy (via Identity Protection or Conditional Access) | No | No | Yes |
+| Security reports | Overview | No | No | Yes |
+| Security reports | Risky users | Limited Information. Only users with medium and high risk are shown. No details drawer or risk history. | Limited Information. Only users with medium and high risk are shown. No details drawer or risk history. | Full access|
+| Security reports | Risky sign-ins | Limited Information. No risk detail or risk level is shown. | Limited Information. No risk detail or risk level is shown. | Full access |
+| Security reports | Risk detections | No | Limited Information. No details drawer.| Full access |
+| Notifications | Users at risk detected alerts | No | No | Yes |
+| Notifications | Weekly digest | No | No | Yes | 
+| MFA registration policy |   | No | No | Yes |
 
 More information on these rich reports can be found in the article, [How To: Investigate risk](howto-identity-protection-investigate-risk.md#navigating-the-reports).