Home | Connectors | Google Drive | Google Drive - OpenText Webroot Unity Integration and Automation

Google Drive - OpenText Webroot Unity Integration and Automation

Integrate Google Drive Cloud Storage and OpenText Webroot Unity Security / Identity Access Management apps with any of the apps from the library with just a few clicks. Create automated workflows by integrating your apps.

Common Integration Use Cases Between Google Drive and OpenText Webroot Unity

1. Automatically scan newly uploaded files in Google Drive for malware and ransomware indicators

Data flow: Google Drive ? OpenText Webroot Unity

When employees upload documents, spreadsheets, or shared assets to Google Drive, the integration can trigger a security scan through OpenText Webroot Unity to detect malicious files, suspicious macros, or known threat signatures. This is especially valuable for shared folders used by finance, HR, legal, and project teams where external files are frequently received.

Business value: Reduces the risk of infected files spreading across the organization, improves file trust before collaboration, and supports a stronger zero-trust content handling process.

2. Quarantine or restrict access to compromised files stored in Google Drive

Data flow: OpenText Webroot Unity ? Google Drive

If OpenText Webroot Unity identifies a file as malicious or high risk, it can notify Google Drive administrators or trigger an automated workflow to move the file to a restricted folder, revoke sharing permissions, or flag it for review. This helps security teams respond quickly without relying on manual intervention.

Business value: Limits lateral spread of threats, shortens incident response time, and helps protect shared business content from accidental exposure.

3. Send security alerts and incident reports to a Google Drive case management folder

Data flow: OpenText Webroot Unity ? Google Drive

Security events detected by OpenText Webroot Unity, such as endpoint infections tied to a downloaded file from Google Drive, can be exported to a dedicated Google Drive folder for SOC, IT operations, or compliance teams. Reports may include affected device details, file names, timestamps, and remediation status.

Business value: Creates a centralized audit trail, improves collaboration between security and operations teams, and simplifies evidence collection for investigations and compliance reviews.

4. Correlate endpoint threats with file-sharing activity to identify risky collaboration patterns

Data flow: Bi-directional

Google Drive sharing activity can be correlated with OpenText Webroot Unity endpoint telemetry to identify users or devices repeatedly involved in suspicious file downloads, external sharing, or malware detections. For example, if a shared marketing asset is downloaded by multiple endpoints and one device later shows a threat alert, the integration can help determine whether the file or the endpoint was the source.

Business value: Improves root-cause analysis, helps security teams prioritize remediation, and reveals risky user behaviors or weak controls in file-sharing workflows.

5. Secure external file exchange with partners and contractors

Data flow: Google Drive ? OpenText Webroot Unity

Organizations often use Google Drive to exchange files with agencies, vendors, and contractors. The integration can automatically inspect incoming partner files before they are made available to internal teams. High-risk files can be blocked or isolated until cleared by security.

Business value: Enables safer external collaboration, reduces exposure from third-party content, and supports business continuity without slowing down partner workflows.

6. Enforce security review for sensitive documents before broad internal sharing

Data flow: Google Drive ? OpenText Webroot Unity

Files uploaded to sensitive folders, such as legal contracts, HR records, or merger documents, can be routed through OpenText Webroot Unity for additional inspection before they are shared across departments. If a file is flagged, the workflow can require security approval before access is expanded.

Business value: Adds a control point for high-value content, reduces accidental distribution of compromised files, and supports governance for sensitive business documents.

7. Maintain a secure archive of endpoint threat evidence and remediation artifacts

Data flow: OpenText Webroot Unity ? Google Drive

After an endpoint incident is resolved, OpenText Webroot Unity can export remediation logs, screenshots, and incident summaries into a structured Google Drive archive. This gives IT, security, and audit teams a consistent repository for post-incident review and trend analysis.

Business value: Improves documentation quality, supports audit readiness, and helps teams identify recurring threat patterns across departments or locations.

8. Support remote workforce protection for files accessed from managed devices

Data flow: Bi-directional

For distributed teams working from managed laptops and mobile devices, Google Drive access events can be paired with OpenText Webroot Unity device posture and threat status. If a device is flagged as compromised, access to sensitive Drive folders can be restricted until the endpoint is remediated.

Business value: Protects remote work environments, reduces the chance of data exposure from infected devices, and aligns file access with endpoint security posture.

How to integrate and automate Google Drive with OpenText Webroot Unity using OneTeg?