OpenText Webroot Unity - DeSL Integration and Automation

Common Integration Use Cases Between OpenText Webroot Unity and DeSL

1. Secure access control for product development teams

Data flow: OpenText Webroot Unity → DeSL

Use Webroot Unity security policies to validate and protect endpoints used by designers, merchandisers, sourcing teams, and external partners accessing DeSL. If a device is flagged for malware, phishing risk, or compromised status, access to DeSL can be restricted or stepped up for review.

• Reduces the risk of unauthorized access to product data and supplier information
• Protects PLM workflows from compromised laptops and remote devices
• Supports secure collaboration across distributed fashion and retail teams

2. Threat alerting tied to critical PLM user activity

Data flow: OpenText Webroot Unity → DeSL

When Webroot detects suspicious endpoint behavior on a user involved in product development, sourcing, or approvals, the alert can be pushed into DeSL as a security flag. This helps product and IT teams identify whether sensitive actions such as style approvals, BOM updates, or supplier data changes should be paused or reviewed.

• Improves visibility into security issues affecting business-critical workflows
• Helps prevent fraudulent or unauthorized product changes
• Creates a faster response path between cybersecurity and business operations

3. Device trust checks before supplier collaboration

Data flow: OpenText Webroot Unity → DeSL

Before allowing suppliers, agents, or contractors to upload tech packs, samples, or compliance documents into DeSL, Webroot Unity can provide endpoint trust status. Only devices meeting defined security standards can be permitted to interact with shared product development spaces.

• Protects intellectual property and confidential product designs
• Reduces risk from third-party endpoints and unmanaged devices
• Supports secure external collaboration without slowing down sourcing cycles

4. Security incident context for audit and compliance workflows

Data flow: Bi-directional

DeSL can send user, project, and workflow context to security teams when a Webroot incident occurs, such as which product line, supplier, or approval process was active on the affected device. In return, Webroot can provide incident status back to DeSL so business users know whether a workflow needs to be frozen, revalidated, or reassigned.

• Speeds root-cause analysis for security incidents
• Improves audit readiness for product and supplier operations
• Minimizes disruption by targeting only impacted workflows

5. Protection of digital assets used in product development

Data flow: OpenText Webroot Unity → DeSL

DeSL teams often work with sketches, images, specifications, and other sensitive files. Webroot Unity can monitor endpoints for malware or ransomware that could compromise these assets before they are uploaded, shared, or synchronized through DeSL.

• Reduces the chance of corrupted or encrypted design files entering the PLM process
• Protects high-value creative and technical content
• Supports continuity in seasonal product development timelines

6. Endpoint risk-based approval for workflow actions

Data flow: OpenText Webroot Unity → DeSL

High-risk endpoint events can trigger additional approval steps in DeSL for sensitive actions such as supplier onboarding, material substitution, cost changes, or final product sign-off. This adds a security checkpoint only when needed, rather than slowing all users.

• Balances security with operational speed
• Helps prevent business process abuse from compromised accounts
• Improves governance over high-impact PLM decisions

7. Centralized reporting for security and product operations

Data flow: Bi-directional

Webroot Unity security events and DeSL workflow activity can be combined into a shared operational dashboard for IT, product development, and compliance teams. This gives leaders a clearer view of how endpoint threats may affect product timelines, supplier collaboration, and data integrity.

• Connects cybersecurity metrics to business process impact
• Helps prioritize response based on affected products or teams
• Improves coordination between security, PLM, and supply chain stakeholders