Anexet integrates with Active Directory, Microsoft Entra ID, and FreeIPA. At deployment it syncs your directory structure — users, groups, and organizational units — into the Administrator Console, so every intercepted event and monitoring record is tied to a real employee identity, department, and role rather than a bare hostname or IP address.
Schedule a Demo
Monitoring by machine name loses the context security teams actually need — Anexet pulls your directory structure in at the source so every event carries the name, department, and role of the person behind it.
Most monitoring tools capture data by machine: a workstation name, a network address, an agent ID. What security teams actually need is context — which person, which team, which manager, which policy — and that context lives in your directory service. Anexet pulls it in at the source, at deployment, and keeps it synchronised.
When a directory object changes — a user moves departments, a group is renamed, a new hire is added — Anexet reflects that change in the console. Intercepted communications, activity timelines, policy violations, and reports all carry the current organizational context: full name, department, job title, and the group memberships that determine which agent profile and monitoring scope applies to that person.
The same mechanism works for Linux-heavy environments. Where Windows environments rely on Active Directory and cloud tenants on Microsoft Entra ID, organizations running Linux servers and workstations connect through FreeIPA. One integration model covers all three, without requiring separate configuration workflows or platform-specific agents.
Every intercepted event, screenshot, and alert is tied to a named employee with department and role — not a raw device ID.
Assign agent profiles and monitoring scope to OUs, security groups, or individual accounts — adding a user to the right group configures them automatically.
New hires, movers, and leavers are reflected automatically so monitoring coverage tracks the live organizational structure.
Full Active Directory, Microsoft Entra ID, and FreeIPA integration is included from the Standard plan and is the foundation for every capability built on top.
User cards created and updated from your on-premise Active Directory domain controller.
Cloud and hybrid tenants: sync from Microsoft Entra ID (formerly Azure AD) for organizations on Microsoft 365.
Linux-native infrastructure covered through FreeIPA — same integration model, no separate workflow.
Display name, department, job title, email, manager, and group memberships synced into user cards in the Client Console.
Assign agent profiles and monitoring scope to OUs, security groups, or individual accounts — not per-machine lists.
Department, job title, and manager visible in profile cards; filter investigations, reports, and search results by team or role.
Directory changes — new accounts, department moves, leavers — reflected in Anexet so policy coverage stays current.
Directory-linked user identity used for policy targeting and alert routing.
Risk scores attributed to named employees; relations graph maps communication between known directory objects.
Security events forwarded to your SIEM platform already carry the directory-resolved user context.
The exact attribute mapping and sync scope is confirmed during the setup and demo process.
When an Anexet agent installs on a workstation, it resolves the logged-in user to their directory record and applies the matching agent profile and monitoring policy. From that point, all data flowing into the Client Console — intercepted communications, activity reports, security policy alerts, Risk Analysis scores — carries the resolved user identity and organizational context, so analysts can search, filter, and build cases by name, department, or group without any manual mapping step.
Anexet is deployed on-premise; the vendor has no access to your data. Directory credentials and synced user attributes stay entirely within your infrastructure and are never transmitted externally.
From a directory connection configured once to organizational context in every console event.
In the Administrator Console, configure a connection to your directory service — Active Directory, Microsoft Entra ID, or FreeIPA — by providing the domain controller address, bind credentials, and the scope of OUs or groups to synchronise.
1
Anexet reads the directory tree and creates or updates user cards in the Users and Privileges Server, storing display name, department, job title, email, group memberships, and manager hierarchy.
2
Agent deployment rules are written against directory objects — an OU, a security group, or an individual account — so adding a user to the right group automatically applies the correct monitoring configuration on their workstation.
3
All data flowing into the Client Console carries the resolved user identity and organizational context, enabling analysts to search, filter, and build cases by name, department, or group without any manual mapping.
4
In the Administrator Console, configure a connection to your directory service — Active Directory, Microsoft Entra ID, or FreeIPA — by providing the domain controller address, bind credentials, and the scope of OUs or groups to synchronise.
1
Anexet reads the directory tree and creates or updates user cards in the Users and Privileges Server, storing display name, department, job title, email, group memberships, and manager hierarchy.
2
Agent deployment rules are written against directory objects — an OU, a security group, or an individual account — so adding a user to the right group automatically applies the correct monitoring configuration on their workstation.
3
All data flowing into the Client Console carries the resolved user identity and organizational context, enabling analysts to search, filter, and build cases by name, department, or group without any manual mapping.
4
Common questions about Anexet's Active Directory, Entra ID, and FreeIPA integration.
Anexet integrates with Microsoft Active Directory (on-premise), Microsoft Entra ID (formerly Azure AD, for cloud and hybrid tenants), and FreeIPA (for Linux-native infrastructure). All three are supported from the Standard plan. The exact attribute mapping and sync scope is confirmed during the setup and demo process.
The integration syncs user identity attributes — display name, department, job title, email address, manager, and group memberships — along with the organizational unit structure. These appear in user cards in the Client Console and are used to filter reports, search results, and security policy views by team or role.
Yes. This is the primary operational benefit of directory integration. Agent profiles and monitoring scope are assigned to directory objects — security groups, OUs, or individual accounts — so that adding a user to the right group automatically applies the correct monitoring configuration on their workstation, without updating a list of machine names.
Changes in the directory — new accounts, moves between departments, leavers — are reflected in Anexet through synchronization, so monitoring coverage tracks the live structure. The sync interval and scope are configured in the Administrator Console. Specific sync cadence can be confirmed during the demo.
Yes. Directory integration — Active Directory, Entra ID, and FreeIPA — is included from the Standard plan. It is the foundation for everything else: Advanced policies, Premium risk analysis, and SIEM event export all rely on the user context this integration provides.
Anexet is deployed on-premise; the vendor has no access to your data. The directory credentials and synced user attributes stay entirely within your infrastructure and are never transmitted to Scinero or any external server.
SIEM integration is included in the Premium plan. It exports security events — already enriched with the directory-resolved user identity — to your SIEM platform.
Tell us about your directory infrastructure — Active Directory, Entra ID, or FreeIPA — and we'll show you how Anexet maps your organizational structure to monitoring policies in a demo or a free trial.
