OpenText Webroot Unity - Kentico Integration and Automation

Common Integration Use Cases Between OpenText Webroot Unity and Kentico

OpenText Webroot Unity and Kentico serve very different but complementary enterprise needs. OpenText Webroot Unity secures endpoints and helps IT teams detect and respond to threats, while Kentico powers websites, campaigns, and digital customer experiences. Integrating them can improve security governance around digital properties, reduce operational risk, and support coordinated workflows between security, marketing, and web operations teams.

1. Secure Access to Kentico Admin and Authoring Environments

Data flow: OpenText Webroot Unity to Kentico

Use endpoint security signals from OpenText Webroot Unity to control or flag access to Kentico administration portals and content authoring workstations. If a device is identified as infected, compromised, or out of compliance, access to Kentico editing or publishing functions can be restricted until the issue is resolved.

• Prevents compromised endpoints from being used to publish malicious content
• Reduces risk of unauthorized access to CMS administration
• Supports security policies for marketing and web content teams

2. Threat-Based Alerting for Web Content and Campaign Teams

Data flow: OpenText Webroot Unity to Kentico

When OpenText Webroot Unity detects phishing, malware, or suspicious activity on devices used by content editors, campaign managers, or eCommerce administrators, alerts can be surfaced to Kentico workflow owners or IT service teams. This helps teams pause publishing activity, review recent changes, and investigate whether malicious content or credentials may have been exposed.

• Improves response time to endpoint security incidents affecting digital operations
• Helps marketing teams avoid publishing from compromised devices
• Creates a clearer handoff between security and business teams

3. Protect Customer-Facing Web Operations from Compromised Internal Devices

Data flow: OpenText Webroot Unity to Kentico

Integrate endpoint risk data into Kentico operational controls so that users with high-risk devices cannot approve, schedule, or publish website changes until remediation is complete. This is especially useful for organizations with distributed content teams, agencies, or remote contributors.

• Reduces the chance of malicious code or unauthorized edits reaching production
• Supports governance for distributed publishing teams
• Helps enforce least-privilege publishing practices

4. Incident-Driven Content Freeze for High-Risk Campaigns

Data flow: OpenText Webroot Unity to Kentico

If OpenText Webroot Unity identifies a security incident on a device used in a live campaign or eCommerce operation, Kentico can automatically place related content workflows into a hold state. This prevents further edits, approvals, or launches until the incident is reviewed and cleared.

• Limits exposure during active security events
• Protects campaign integrity and customer trust
• Gives security teams time to assess whether credentials or assets were compromised

5. Security-Aware User Segmentation for Personalized Experiences

Data flow: Bi-directional

Use OpenText Webroot Unity to provide endpoint trust signals that can influence how Kentico delivers internal or partner-facing experiences. For example, users accessing a portal from a high-risk device can be routed to limited functionality, additional verification, or a restricted content set.

• Improves risk-based access control for portals and self-service sites
• Supports differentiated experiences for employees, partners, and contractors
• Helps balance usability with security requirements

6. Audit and Compliance Reporting for Digital Publishing Controls

Data flow: Bi-directional

Combine Kentico publishing logs with OpenText Webroot Unity endpoint security events to create a more complete audit trail for compliance reviews. Security teams can see which devices were involved in content changes, while web teams can verify whether publishing actions occurred from trusted endpoints.

• Strengthens auditability for regulated industries
• Supports investigations into suspicious content changes
• Improves visibility across IT security and digital operations

7. Secure Agency and Contractor Collaboration for Website Management

Data flow: OpenText Webroot Unity to Kentico

For external agencies or contractors who contribute to Kentico-managed websites, endpoint security status from OpenText Webroot Unity can be used to validate whether their devices meet security requirements before granting access to staging or production workflows. This is useful for organizations that rely on distributed content production.

• Reduces third-party risk in content operations
• Helps enforce security standards for external contributors
• Supports safer collaboration across internal and external teams

Together, OpenText Webroot Unity and Kentico can help organizations protect the systems and users involved in digital experience delivery while improving governance, publishing control, and incident response coordination.