OpenText Webroot Unity - S-Drive Integration and Automation

Common Integration Use Cases Between OpenText Webroot Unity and S-Drive

1. Secure storage of security incident evidence in Salesforce

Data flow: OpenText Webroot Unity ? S-Drive

When Webroot detects malware, phishing, or suspicious endpoint activity, incident reports, alert logs, and forensic evidence can be automatically attached to the related Salesforce case, account, or support ticket in S-Drive. This gives service desks, security teams, and account managers a single place to review incident history and coordinate response.

Business value: Faster incident resolution, better auditability, and improved collaboration between cybersecurity and customer support teams.

2. Automated collection of endpoint remediation approvals and exception forms

Data flow: S-Drive ? OpenText Webroot Unity

Security teams can use Salesforce workflows to collect signed remediation approvals, device exception requests, or policy acknowledgment forms through S-Drive. Once submitted, the documents can be linked back to Webroot-managed endpoints to support policy enforcement decisions or exception handling.

Business value: Streamlined governance, reduced manual follow-up, and stronger compliance for security exceptions.

3. Centralized compliance recordkeeping for security audits

Data flow: OpenText Webroot Unity ? S-Drive

Webroot security reports, endpoint protection status summaries, and threat response documentation can be stored in S-Drive against Salesforce records for audit preparation. Compliance, risk, and internal audit teams can retrieve evidence directly from Salesforce without requesting files from IT security.

Business value: Simplified audit support, faster evidence retrieval, and improved regulatory readiness.

4. Customer-facing security incident documentation in Salesforce service cases

Data flow: Bi-directional

Support teams can upload customer communications, incident acknowledgments, and remediation instructions into S-Drive while Webroot provides threat details and endpoint findings. This creates a complete case file in Salesforce for customer service, managed services, or account teams handling security-related issues.

Business value: Better case visibility, more consistent customer communication, and reduced risk of missing critical incident documentation.

5. Endpoint onboarding documentation for new employees and devices

Data flow: S-Drive ? OpenText Webroot Unity

HR, IT, and onboarding teams can collect device acceptance forms, acceptable use policies, and onboarding checklists in S-Drive during employee setup. Once complete, the documents can be referenced by security operations to confirm that newly provisioned endpoints are covered by policy and protection requirements.

Business value: Faster onboarding, better policy compliance, and fewer gaps in endpoint protection readiness.

6. Security exception management for business-critical applications

Data flow: S-Drive ? OpenText Webroot Unity

When a business unit requests an exception for a blocked application, macro, or file type, the request can be submitted and approved in Salesforce using S-Drive. Approved exception documentation can then be associated with the relevant endpoint or policy review process in Webroot to ensure security teams have a clear record of the decision.

Business value: Faster exception approvals, stronger governance, and reduced friction between security and business teams.

7. Incident response case management with supporting documents

Data flow: Bi-directional

During a security incident, Webroot can provide threat intelligence, affected device details, and remediation status, while S-Drive stores response plans, customer approvals, legal notices, and post-incident reports in Salesforce. This supports coordinated action across security operations, legal, compliance, and customer success teams.

Business value: More organized incident response, improved cross-functional coordination, and a complete record for post-incident review.