OpenText Core Content - Metadata - OpenText Webroot Unity Integration and Automation

Common Integration Use Cases Between OpenText Core Content - Metadata and OpenText Webroot Unity

1. Security-Aware Content Classification for Sensitive Documents

Flow: OpenText Core Content - Metadata ? OpenText Webroot Unity

When content is classified in OpenText Core Content using metadata such as document type, department, sensitivity level, or retention category, that metadata can be shared with OpenText Webroot Unity to help security teams apply tighter endpoint controls for users handling high-risk content. For example, finance, legal, or HR documents tagged as confidential can trigger stricter device monitoring or elevated threat alerts for endpoints accessing those files.

Business value: Reduces the risk of data exposure by aligning content classification with endpoint security posture.

2. Threat-Driven Metadata Tagging for Incident Tracking

Flow: OpenText Webroot Unity ? OpenText Core Content - Metadata

When OpenText Webroot Unity detects malware, phishing, or ransomware activity on a device, incident details can be written back into OpenText Core Content as metadata on related case files, investigation records, or affected documents. This creates a structured audit trail that links security events to business content for compliance, legal review, and post-incident analysis.

Business value: Improves incident documentation and makes security investigations easier to search, report, and audit.

3. Automated Quarantine Workflow for Compromised Content

Flow: Bi-directional

If Webroot Unity identifies a compromised endpoint that recently accessed specific content, OpenText Core Content can update metadata to mark those files as under review, restricted, or quarantined. In return, Core Content can provide file identifiers, owners, and classification details to Webroot Unity so security teams can prioritize remediation based on the sensitivity of the affected content.

Business value: Speeds containment and helps security teams focus on the most business-critical content first.

4. Policy Enforcement Based on Content Sensitivity

Flow: OpenText Core Content - Metadata ? OpenText Webroot Unity

Metadata rules in OpenText Core Content can define content sensitivity levels such as public, internal, confidential, or regulated. These classifications can be used to inform endpoint security policies in Webroot Unity, such as requiring stricter device checks, limiting access from unmanaged devices, or increasing monitoring for users accessing regulated content.

Business value: Supports risk-based access and security controls without relying on manual decisions.

5. Security Reporting for Regulated Content Repositories

Flow: OpenText Webroot Unity ? OpenText Core Content - Metadata

Security events from Webroot Unity can be captured as metadata against content repositories, folders, or records in OpenText Core Content. Compliance teams can then report on which repositories were accessed from infected devices, which users were exposed to threats, and which documents were involved in suspicious activity.

Business value: Strengthens compliance reporting and provides a clearer view of content risk exposure.

6. User and Device Risk Context for Content Access Reviews

Flow: OpenText Webroot Unity ? OpenText Core Content - Metadata

Webroot Unity can provide endpoint risk indicators such as device health, malware status, or recent threat events to OpenText Core Content. That information can be stored as metadata on access logs or review queues, enabling content owners to prioritize review of files accessed from high-risk devices or by users with recent security incidents.

Business value: Helps content governance teams make faster, better-informed access review decisions.

7. Audit-Ready Evidence Collection for Security and Compliance Teams

Flow: Bi-directional

OpenText Core Content can store structured metadata for evidence packages, including document classification, retention status, and case ownership. Webroot Unity can contribute endpoint threat details, remediation timestamps, and device identifiers. Together, the platforms create a complete evidence record for audits, investigations, and regulatory reviews.

Business value: Reduces manual evidence gathering and improves traceability across security and content governance teams.