Skip to content

Commit f016bc1

Browse files
committed
fix permissions and add risk scoring
1 parent 74b9a60 commit f016bc1

File tree

1 file changed

+14
-4
lines changed

1 file changed

+14
-4
lines changed

ATPDocs/okta-integration.md

Lines changed: 14 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -26,17 +26,27 @@ Your Okta environment must have one of the following licenses:
2626
- Enterprise
2727

2828

29+
> [!NOTE]
30+
> The **Identity details** page in the Microsoft Defender portal shows user risk scores only if the **Identity Threat Protection with Okta AI** feature is enabled. For more information, see [Risk scoring (Okta Identity Engine)](https://help.okta.com/oie/en-us/content/topics/security/security_risk_scoring.htm).
31+
32+
33+
2934
### Okta roles
3035

3136
The Super Admin role is required only to create the API token. After you create the token, remove the role and assign the Read-Only Administrator and Defender for Identity custom roles for ongoing API access.
3237

3338

34-
### Microsoft Entra roles
39+
### Microsoft Entra and Defender XDR role-based access options
40+
To configure the Okta connector in Microsoft Defender for Identity, your account must have either of the following access configurations assigned:
41+
42+
- **Microsoft Entra roles:**
43+
44+
- Security Operator
45+
- Security Admin
3546

36-
To successfully set up the Okta connector, ensure that your account has one of the following Microsoft Entra roles assigned:
47+
- **Defender XDR Unified RBAC permission:**
3748

38-
- Security Operator
39-
- Security Admin
49+
- Core security settings (manage)
4050

4151
### Connect Okta to Microsoft Defender for Identity
4252

0 commit comments

Comments
 (0)