TL;DR: Google Workspace does not give administrators a single global view of files shared as “Anyone with the link,” leaving public Drive content easy to miss and hard to govern, according to Strac. The control gap is not discovery alone but continuous monitoring, classification, and rapid remediation before sensitive data becomes broadly exposed.
Editorial analysis by NHI Mgmt Group, based on content published by Strac: “How to Find Publicly Shared Files or Public Links in Google Drive?”.
Key questions
Q: What breaks when Google Drive files can be shared publicly without central visibility?
A: The break is governance, not storage.
Q: Why do public Drive links create privacy and compliance risk?
A: Because a public link can turn a controlled document into broadly reachable content with very little friction.
Q: How should teams detect risky public sharing in cloud collaboration tools?
A: Use continuous discovery across sharing events, then pair that telemetry with content-aware classification.
Practitioner guidance
- Implement continuous public-link discovery Monitor Google Drive sharing state in real time so every new "Anyone with the link" event is detected as soon as it appears.
- Classify exposed file contents before triage Prioritise public files that contain PII, credentials, financial documents, or other sensitive records instead of reviewing all public links equally.
- Automate public-access revocation Use policy-driven remediation to remove public sharing or tighten permissions immediately when a risky link is found.
Bottom line: Public Google Drive links create a control gap when administrators cannot centrally see every file shared as "Anyone with the link."
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Public-link governance is a data exposure problem before it is a collaboration problem. The core failure is not that users share files, but that organisations often lack continuous visibility into the resulting access state. Once public-link sharing exists, the question becomes whether the security programme can detect and reverse it before exposure becomes durable. Practitioners should treat public sharing as governed access, not informal convenience.
A few things that frame the scale:
- 24,008 unique secrets were exposed in MCP configuration files in 2025 alone, the protocol's first year of widespread adoption, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: Should organisations rely on manual Google Drive reviews or automated remediation?
A: Automated remediation should handle the highest-risk exposures because manual review is too slow for live sharing changes. Human review still has a role for exceptions and investigations, but the default control should be to shorten the exposure window automatically whenever public access is created.
👉 Read our full editorial: Public Google Drive links create a hidden exposure gap in data security