OpenText Content Metadata Service - OpenText Webroot Unity Integration and Automation

Common Integration Use Cases Between OpenText Content Metadata Service and OpenText Webroot Unity

1. Security Classification Metadata for Content Repositories

Data flow: OpenText Webroot Unity ? OpenText Content Metadata Service

When Webroot Unity detects a device or user associated with a security incident, it can send risk indicators to the Content Metadata Service to tag related content with security classification metadata such as high risk, under investigation, or restricted access. This helps content teams apply consistent handling rules across repositories and reduces the chance of sensitive files being shared or processed during an active threat event.

2. Automated Metadata Updates for Quarantined or Suspicious Files

Data flow: OpenText Webroot Unity ? OpenText Content Metadata Service

When endpoint protection flags a file as malicious, suspicious, or quarantined, the event can be pushed into the metadata service to update the file record with standardized metadata such as threat type, detection date, endpoint name, and incident status. This gives records and content teams a single source of truth for tracking compromised documents and supports faster investigation and remediation.

3. Content Access Rules Based on Endpoint Security Posture

Data flow: OpenText Webroot Unity ? OpenText Content Metadata Service

Security posture data from Webroot Unity can be used to enrich user or device metadata in the content platform. For example, if a device is marked non-compliant, the metadata service can classify content access requests from that device differently, enabling downstream applications to enforce stricter access, review, or approval workflows. This reduces exposure from unmanaged or compromised endpoints.

4. Incident Response Workflow Linking Security Events to Content Owners

Data flow: Bi-directional

Webroot Unity can send threat alerts to the metadata service, which then maps affected content to business owners, departments, or document categories using standardized metadata. In return, the metadata service can provide context back to security teams, such as document sensitivity, retention class, or business criticality. This improves incident triage by helping security analysts prioritize incidents based on the value and classification of impacted content.

5. Metadata-Driven Retention and Legal Hold for Security Incidents

Data flow: OpenText Webroot Unity ? OpenText Content Metadata Service

When a ransomware or malware incident affects content repositories, Webroot Unity can trigger metadata updates that place affected content into special handling states such as preserve for investigation or legal hold. This ensures evidence is retained consistently and prevents accidental deletion or modification while security and compliance teams investigate the incident.

6. Standardized Threat Reporting Across Content and Security Teams

Data flow: OpenText Webroot Unity ? OpenText Content Metadata Service

Security events can be normalized into enterprise metadata fields so that dashboards and reports show consistent categories across content and endpoint environments. For example, malware detections can be tagged by business unit, content type, and severity. This allows operations, compliance, and IT leadership to analyze trends, identify repeat exposure points, and improve policy enforcement.

7. Enriched Audit Trails for Sensitive Content Activity

Data flow: Bi-directional

Webroot Unity can provide endpoint event data such as detection time, device identity, and user context, while the Content Metadata Service can store that information alongside content access or modification metadata. The result is a richer audit trail that connects endpoint security activity with content events. This is especially useful for regulated industries that need to demonstrate who accessed sensitive content, from which device, and under what security conditions.

8. Policy Enforcement for High-Risk Content Handling

Data flow: OpenText Content Metadata Service ? OpenText Webroot Unity

The metadata service can identify content that is highly sensitive, regulated, or business critical and pass that classification to Webroot Unity for policy alignment. Security teams can then apply tighter endpoint controls for users handling that content, such as stricter monitoring, alerting, or isolation rules. This creates a more coordinated defense between content governance and endpoint protection.