Skip to main content
Version: 0.4 · current

Identity security

OverviewReviewed October 11, 2026
Applies to:Excubius 0.4Roles: Entity admin, Editor
PlansPro · EnterpriseDeploymentSelf-hosted

The identity security module checks who can administer your directory and how: privileged roles without multifactor authentication, risky sign-ins, changes in privileged Active Directory groups, stale accounts, and administrative sign-ins to Excubius itself. It only detects. What it finds is a finding with its evidence and a suggested action; Excubius never changes an account.

What it monitors​

AreaChecksWhy it matters
Privileged rolesActive holders of Global, Privileged Role, Security, Exchange, SharePoint or User Administrator who are not registered for multifactor authentication, one finding per role and userA privileged account protected by a password alone is the shortest path to the whole tenant
Risky sign-insIdentity Protection risk detections of the last 7 days still at risk, one finding per user and risk type at the highest level seen: high is critical, medium a warning, low informationA risky sign-in that nobody reviewed may be an attacker already inside. Remediating or dismissing it in Entra ID resolves the finding
Active DirectoryAdditions to or removals from Domain Admins, Enterprise Admins, Schema Admins, Administrators and AAD DC Administrators; enabled accounts without a logon in 90 days or with a password that never expiresUnreviewed privilege grants, and accounts nobody uses that attackers can
Excubius itselfEvery sign-in of a super administrator, read from the platform's own audit logAdministrative access to the monitoring platform should be rare and explained

Findings feed the identity area of the security score. A change in a privileged group is an event: it is reviewed and resolved by hand, not fixed. How findings, accepted risks and the score work: Security posture.

Every check, with its rule, cause and action, is in the reference for identity security checks.

Before you begin​

  • The security modules are on. A super administrator switches on the feature security in Settings › Instance.

  • An identity for Microsoft Graph: an app registration stored as an Azure service principal credential (client id, client secret and the tenant_id option), or the server's managed identity. Grant it these Microsoft Graph application permissions, all read-only, with admin consent:

    PermissionUsed for
    RoleManagement.Read.DirectoryRole definitions and active role assignments
    AuditLog.Read.AllMFA registration details of users
    IdentityRiskEvent.Read.AllIdentity Protection risk detections
  • Entra ID licences. Registration details need Entra ID P1 or P2. Full risk detections need P2; P1 gives basic risk events.

  • For the Active Directory checks, a read-only domain account over WinRM on a host with the Active Directory PowerShell module. WinRM collection is experimental; see Windows.

  • Sign-ins to Excubius need nothing more: the API reads its own audit log, without the collector.

Add a resource​

  1. Open Resources › Add resource and choose Entra ID tenant / domain services.
  2. Enter the tenant_id and, for the Active Directory checks, the domain.
  3. Choose the Azure service principal credential, or None to use the server's managed identity, and select Create resource.
  4. For the sign-ins to Excubius, add a Monitoring platform itself resource on the root entity, if you do not have one yet.

The full wizard: Add a resource.

Next steps​