OpenText Directory Services - OpenText Webroot Unity Integration and Automation

Common Integration Use Cases Between OpenText Directory Services and OpenText Webroot Unity

1. Automated User Provisioning for Endpoint Security Administration

OpenText Directory Services can serve as the authoritative source for user identities, groups, and role assignments, while OpenText Webroot Unity consumes that data to automatically create and maintain security administrator and analyst accounts. This reduces manual onboarding effort for IT and security teams, ensures new employees receive the correct endpoint protection access on day one, and removes stale accounts when users leave the organization.

Data flow: OpenText Directory Services to OpenText Webroot Unity

2. Group-Based Policy Assignment for Endpoint Protection

Security teams can map directory groups from OpenText Directory Services to specific protection policies in OpenText Webroot Unity. For example, finance users, executives, and remote workers can each receive different malware prevention, web filtering, or device control settings based on their directory membership. This improves policy consistency and reduces the risk of misconfiguration across large user populations.

Data flow: OpenText Directory Services to OpenText Webroot Unity

3. Automated Deprovisioning When Employees Leave the Organization

When a user account is disabled or removed in OpenText Directory Services, that change can trigger OpenText Webroot Unity to revoke access to the security console, remove the user from privileged roles, and disable any associated endpoint management permissions. This helps close security gaps quickly during employee exits, contractor offboarding, or role changes, reducing the chance of unauthorized access.

Data flow: OpenText Directory Services to OpenText Webroot Unity

4. Synchronization of Organizational Structure for Security Reporting

OpenText Webroot Unity can use directory attributes such as department, location, manager, and business unit from OpenText Directory Services to organize endpoint protection reporting. Security leaders can then view incidents, infection trends, and policy compliance by business unit or region, making it easier to identify high-risk areas and prioritize remediation efforts.

Data flow: OpenText Directory Services to OpenText Webroot Unity

5. Role-Based Access Control for Security Operations Teams

OpenText Directory Services can manage security operations roles such as help desk, SOC analyst, and security administrator, and pass those roles to OpenText Webroot Unity. This allows organizations to enforce least-privilege access to endpoint protection functions, such as viewing alerts, isolating devices, or changing policies, while keeping access aligned with job responsibilities.

Data flow: OpenText Directory Services to OpenText Webroot Unity

6. Centralized Identity Governance for Security Tool Access Reviews

Identity data from OpenText Directory Services can be used to support periodic access reviews in OpenText Webroot Unity. Managers and application owners can validate who has administrative access to endpoint security controls, which groups they belong to, and whether access still matches current responsibilities. This supports audit readiness and strengthens governance over security operations.

Data flow: OpenText Directory Services to OpenText Webroot Unity

7. Incident Escalation Based on User and Device Ownership

When OpenText Webroot Unity detects a threat on an endpoint, it can reference identity and group information from OpenText Directory Services to determine the user, department, and manager associated with the device. This enables faster escalation to the right business owner, more accurate incident routing, and better coordination between IT support, security, and line-of-business teams.

Data flow: Bi-directional, with OpenText Webroot Unity sending incident data and OpenText Directory Services providing identity context

8. Faster Onboarding for New Sites, Teams, and Acquisitions

During organizational growth, OpenText Directory Services can standardize user and group structures for new employees, acquired teams, or new locations, and OpenText Webroot Unity can immediately apply endpoint protection policies based on those structures. This shortens deployment timelines, reduces manual setup work, and helps ensure consistent security coverage across the expanded environment.

Data flow: OpenText Directory Services to OpenText Webroot Unity