# Connect CyberArk Identity only with the required API roles and permissions > Use Connect CyberArk Identity to Microsoft Defender for Identity (Preview) to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/connect-cyberark-identity-with-required-api-roles/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:13:19+00:00 - Modified: 2026-08-27T13:01:32+00:00 - Last reviewed by DSE: 2026-08-26 - Resource type: Checklist - DSE priority: Advisory - Topics: Cybersecurity, IT, Microsoft 365 & Identity - Reading time: 3 minutes ## What you need to know Use Connect CyberArk Identity to Microsoft Defender for Identity (Preview) to review this narrow operational decision without extending the source beyond its stated scope. ## Potentially affected Teams, systems, services, or facilities within the stated scope of Connect CyberArk Identity to Microsoft Defender for Identity (Preview) ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Treat this document as a focused evidence review: Connect CyberArk Identity only with the required API roles and permissions. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [Connect CyberArk Identity to Microsoft Defender for Identity (Preview)](https://learn.microsoft.com/en-us/defender-for-identity/connect-cyber-ark) from Microsoft supports the following bounded statements: - The connection uses connector APIs to provide Defender for Identity visibility into and control over CyberArk identities. The research record locates this support at Opening overview. - Microsoft requires the documented CyberArk role plus Microsoft Entra or Defender role-based access permissions before connection. The research record locates this support at Prerequisites section. Keep the evidence boundary at these traced claims. They support a review of identity sensors, connected directories, cloud security services, event flows, roles, alerts, and investigation handoffs; they do not support conclusions outside the source’s stated conditions. ## What the source does not establish The connector is marked Preview; use least privilege, protect secrets, and validate API scope before production enablement. No current deployment state or change approval follows from the source alone. Validate Active Directory, Windows DNS, time, certificates, cloud identity, endpoint telemetry, network paths, and security operations, and treat examples or options as conditional inputs rather than defaults. ## Applicability questions - For source statement 1 at Opening overview, which observable configuration, record, or test can confirm applicability here? - For source statement 2 at Prerequisites section, which observable configuration, record, or test can confirm applicability here? - Which deployed instance of identity sensors, connected directories, cloud security services, event flows, roles, alerts, and investigation handoffs will be compared with the source, and why that instance? - How will the review distinguish a source mismatch from a failure in Active Directory, Windows DNS, time, certificates, cloud identity, endpoint telemetry, network paths, and security operations? - Who approves the conclusion, exception, test window, and rollback threshold? ## DSE recommendation: DSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of identity sensors, connected directories, cloud security services, event flows, roles, alerts, and investigation handoffs, observed and expected states, owner, and reason for deviation. Translate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include Active Directory, Windows DNS, time, certificates, cloud identity, endpoint telemetry, network paths, and security operations, while excluding secrets and sensitive personal or topology data from ordinary tickets. ## Verification and evidence Tie each conclusion back to Opening overview; Prerequisites section and to observable material such as integration configuration, connectivity tests, event timestamps, alert correlation, role assignments, and case records. Preserve provenance and stable identifiers without copying secrets into the evidence set. Retain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes. ## Official references - [Connect CyberArk Identity to Microsoft Defender for Identity (Preview)](https://learn.microsoft.com/en-us/defender-for-identity/connect-cyber-ark) — Microsoft ## Primary reference - Name: Connect CyberArk Identity to Microsoft Defender for Identity (Preview) - Authority: Microsoft Learn - URL: https://learn.microsoft.com/en-us/defender-for-identity/connect-cyber-ark - Source publication date: 2026-07-02 ## Citation and use Preferred citation: “Connect CyberArk Identity only with the required API roles and permissions,” DSE Security, https://update.dsesecurity.com/updates/connect-cyberark-identity-with-required-api-roles/ Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/ Usage and citation policy: https://update.dsesecurity.com/usage/ Copyright © 2026 Detection Systems & Engineering. All rights reserved.