OpenText Core Transformation Publication Service - OpenText Webroot Unity Integration and Automation

Common Integration Use Cases Between OpenText Core Transformation Publication Service and OpenText Webroot Unity

1. Secure Distribution of Regulated Documents to Endpoints

Data flow: OpenText Core Transformation Publication Service → OpenText Webroot Unity

Published documents such as policy notices, compliance statements, and customer correspondence can be distributed to managed endpoints only after security checks are applied through Webroot Unity. This helps ensure that sensitive content generated by the publication service is delivered to protected devices with current threat defenses in place.

• Reduces risk of malware interception during document delivery
• Supports controlled release of regulated communications
• Improves confidence for legal, compliance, and operations teams

2. Security-Aware Publishing for High-Risk Content

Data flow: OpenText Webroot Unity → OpenText Core Transformation Publication Service

Webroot Unity can flag endpoints or user groups with elevated security risk, allowing the publication service to adjust how content is rendered and distributed. For example, sensitive documents can be routed to more secure channels, watermarked, or restricted to approved formats when delivered to devices with higher threat exposure.

• Enables risk-based content delivery policies
• Helps prevent exposure of sensitive documents on compromised devices
• Supports security and publishing teams with shared controls

3. Automated Quarantine of Published Files Linked to Threat Events

Data flow: Bi-directional

If Webroot Unity detects suspicious activity involving a published file, it can trigger a workflow to quarantine the document or suspend further distribution from the publication service. This is useful when a published output is suspected to be part of a phishing campaign, malware attachment, or unauthorized document use.

• Speeds incident response for security operations
• Limits spread of potentially harmful content
• Creates a closed-loop process between publishing and endpoint protection

4. Controlled Release of Security Communications and Remediation Notices

Data flow: OpenText Core Transformation Publication Service → OpenText Webroot Unity

Security teams often need to send standardized remediation notices, policy updates, and user guidance to employees after a threat event. The publication service can generate consistent, approved documents while Webroot Unity helps target the right endpoints and user populations for delivery.

• Ensures consistent formatting and approved messaging
• Improves speed of security communications during incidents
• Supports enterprise-wide awareness and remediation efforts

5. Publishing Audit Evidence for Security and Compliance Reviews

Data flow: OpenText Core Transformation Publication Service → OpenText Webroot Unity

Organizations can publish audit-ready reports, endpoint protection summaries, and compliance evidence from managed content repositories and make them available to security administrators through Webroot Unity workflows or linked portals. This reduces manual effort when preparing evidence for internal audits or regulatory reviews.

• Streamlines compliance reporting
• Reduces manual document preparation
• Improves traceability of published security records

6. Endpoint-Specific Delivery of Policy Documents and Acceptable Use Agreements

Data flow: OpenText Core Transformation Publication Service → OpenText Webroot Unity

When employees enroll devices or when security posture changes, the publication service can generate device-appropriate policy documents, acceptable use agreements, or security acknowledgements. Webroot Unity can help identify the endpoint context so the correct version is delivered to the right user or device group.

• Supports policy acknowledgment workflows
• Improves consistency in employee communications
• Reduces administrative overhead for IT and HR security processes

7. Threat-Informed Document Distribution Controls

Data flow: OpenText Webroot Unity → OpenText Core Transformation Publication Service

When Webroot Unity identifies a device as infected, non-compliant, or at elevated risk, the publication service can restrict or delay delivery of sensitive documents to that endpoint. This is especially valuable for finance, legal, and HR content where unauthorized access could create business or regulatory exposure.

• Prevents sensitive content from reaching risky devices
• Supports conditional access decisions
• Aligns document distribution with security posture