Merge pull request #179597 from MicrosoftGuyJFlo/IPServicePrinciples

[Azure AD] Identity Protection - Service Principle Risk

Author: Court72

articles/active-directory/identity-protection/TOC.yml

@@ -15,6 +15,8 @@
     href: concept-identity-protection-policies.md
   - name: What is the sign-in experience?
     href: concept-identity-protection-user-experience.md
+  - name: Securing workload identities
+    href: concept-workload-identity-risk.md
   - name: Identity Protection and B2B users
     href: concept-identity-protection-b2b.md
 - name: How-to guides

articles/active-directory/identity-protection/concept-workload-identity-risk.md

@@ -0,0 +1,107 @@
+---
+title: Securing workload identities with Azure AD Identity Protection
+description: Workload identity risk in Azure Active Directory Identity Protection
+
+services: active-directory
+ms.service: active-directory
+ms.subservice: identity-protection
+ms.topic: conceptual
+ms.date: 02/07/2022
+
+ms.author: joflore
+author: MicrosoftGuyJFlo
+manager: karenhoran
+ms.reviewer: etbasser
+
+ms.collection: M365-identity-device-management
+---
+# Securing workload identities with Identity Protection
+
+Azure AD Identity Protection has historically protected users in detecting, investigating, and remediating identity-based risks. We're now extending these capabilities to workload identities to protect applications, service principals, and Managed Identities.
+
+A workload identity is an identity that allows an application or service principal access to resources, sometimes in the context of a user. These workload identities differ from traditional user accounts as they:
+
+- Can’t perform multi-factor authentication.
+- Often have no formal lifecycle process.
+- Need to store their credentials or secrets somewhere.
+
+These differences make workload identities harder to manage and put them at higher risk for compromise.
+
+> [!IMPORTANT]
+> In public preview, you can secure workload identities with Identity Protection and Azure Active Directory Premium P2 edition active in your tenant. After general availability, additional licenses might be required.
+
+## Prerequisites
+
+To make use of workload identity risk, including the new **Risky workload identities (preview)** blade and the **Workload identity detections** tab in the **Risk detections** blade, in the Azure portal you must have the following.
+
+- Azure AD Premium P2 licensing
+- One of the following administrator roles assigned
+   - Global administrator
+   - Security administrator
+   - Security operator
+   - Security reader
+
+## Workload identity risk detections
+
+We detect risk on workload identities across sign-in behavior and offline indicators of compromise. 
+
+| Detection name | Detection type | Description |
+| --- | --- | --- |
+| Azure AD threat intelligence | Offline | This risk detection indicates some activity that is consistent with known attack patterns based on Microsoft's internal and external threat intelligence sources. |
+| Suspicious Sign-ins | Offline | This risk detection indicates sign-in properties or patterns that are unusual for this service principal. <br><br> The detection learns the baselines sign-in behavior for workload identities in your tenant in between 2 and 60 days, and fires if one or more of the following unfamiliar properties appear during a later sign-in: IP address / ASN, target resource, user agent, hosting/non-hosting IP change, IP country, credential type. <br><br> Because of the programmatic nature of workload identity sign-ins, we provide a timestamp for the suspicious activity instead of flagging a specific sign-in event. <br><br>  Sign-ins that are initiated after an authorized configuration change may trigger this detection. |
+| Admin confirmed account compromised | Offline | This detection indicates an admin has selected 'Confirm compromised' in the Risky Workload Identities UI or using riskyServicePrincipals API. To see which admin has confirmed this account compromised, check the account’s risk history (via UI or API). |
+
+## Identify risky workload identities
+
+Organizations can find workload identities that have been flagged for risk in one of two locations:
+
+1. Navigate to the [Azure portal](https://portal.azure.com).
+1. Browse to **Azure Active Directory** > **Security** > **Risky workload identities (preview)**.
+1. Or browse to **Azure Active Directory** > **Security** > **Risk detections**.
+   1. Select the **Workload identity detections** tab.
+
+:::image type="content" source="media/concept-workload-identity-risk/workload-identity-detections-in-risk-detections-report.png" alt-text="Screenshot showing risks detected against workload identities in the report." lightbox="media/concept-workload-identity-risk/workload-identity-detections-in-risk-detections-report.png":::
+
+### Graph APIs
+
+You can also query risky workload identities [using the Microsoft Graph API](/graph/use-the-api). There are two new collections in the [Identity Protection APIs](/graph/api/resources/identityprotection-root?view=graph-rest-beta&preserve-view=true) 
+
+- riskyServicePrincipals
+- servicePrincipalRiskDetections
+
+### Export risk data 
+
+Organizations can export data by configurating [diagnostic settings in Azure AD](howto-export-risk-data.md) to send risk data to a Log Analytics workspace, archive it to a storage account, stream it to an event hub, or send it to a SIEM solution. 
+
+## Investigate risky workload identities
+
+Identity Protection provides organizations with two reports they can use to investigate workload identity risk. These reports are the risky workload identities, and risk detections for workload identities. All reports allow for downloading of events in .CSV format for further analysis outside of the Azure portal. 
+
+Some of the key questions to answer during your investigation include:
+
+- Do accounts show suspicious sign-in activity?
+- Have there been unauthorized changes to the credentials?
+- Have there been suspicious configuration changes to accounts?
+- Did the account acquire unauthorized application roles?
+
+The [Azure Active Directory security operations guide for Applications](../fundamentals/security-operations-applications.md) provides detailed guidance on the above investigation areas.
+
+Once you determine if the workload identity was compromised, dismiss the account’s risk or confirm the account as compromised in the Risky workload identities (preview) report. You can also select “Disable service principal” if you want to block the account from further sign-ins.
+
+:::image type="content" source="media/concept-workload-identity-risk/confirm-compromise-or-dismiss-risk.png" alt-text="Confirm workload identity compromise or dismiss the risk in the Azure portal." lightbox="media/concept-workload-identity-risk/confirm-compromise-or-dismiss-risk.png":::
+
+## Remediate risky workload identities
+
+1.	Inventory credentials assigned to the risky workload identity, whether for the service principal or application objects.
+1. Add a new credential. Microsoft recommends using x509 certificates.
+1. Remove the compromised credentials. If you believe the account is at risk, we recommend removing all existing credentials.
+1.	Remediate any Azure KeyVault secrets that the Service Principal has access to by rotating them. 
+
+The [Azure AD Toolkit](https://github.com/microsoft/AzureADToolkit) is a PowerShell module that can help you perform some of these actions.
+
+## Next steps
+
+- [Conditional Access for workload identities](../conditional-access/workload-identity.md)
+- [Microsoft Graph API](/graph/use-the-api)
+- [Azure AD audit logs](../reports-monitoring/concept-audit-logs.md)
+- [Azure AD sign-in logs](../reports-monitoring/concept-sign-ins.md)