How to Audit Cloud Storage Activity: Find Suspicious File Access, Sharing, and Deletions
audit-logsfile-activitycloud-securityincident-investigationGoogle-DriveDropboxOneDrive

How to Audit Cloud Storage Activity: Find Suspicious File Access, Sharing, and Deletions

RRecoverFiles Editorial Team
2026-11-09
7 min read

Learn how to audit Google Drive, Dropbox, and OneDrive activity, investigate suspicious access, and build a repeatable cloud review routine.

A cloud storage activity audit helps you determine who accessed, changed, shared, moved, or deleted a file. This guide explains what to review in Google Drive, Dropbox, and OneDrive, how to preserve useful evidence, and how to build a monthly review routine without assuming that every platform exposes the same level of detail.

Overview

When a sensitive document appears in the wrong folder, a former collaborator still has access, or files begin changing unexpectedly, the activity history can provide important context. It may show a file view, download, edit, rename, move, share-permission change, or deletion. However, an activity feed is not always a complete forensic record. The available events, timestamps, actor information, retention period, export options, and administrator controls depend on the provider, account type, subscription, and the way the file was accessed.

Start by defining the question you need to answer. “Who accessed my file?” is different from “Who downloaded a copy?” or “Which account changed the sharing settings?” Record the file name, URL or path, owner, approximate time window, and the first sign that something was wrong. Avoid editing or moving the affected file while you investigate unless necessary, because additional actions can make the timeline harder to interpret.

For an organizational account, preserve relevant records through the provider’s administrative or security console when available. For a personal account, capture screenshots and download available reports, but treat them as supporting evidence rather than a guaranteed complete history.

What to track

Core events

For each sensitive file, folder, shared drive, or team workspace, look for these event categories:

  • Access: views, previews, opens, downloads, and sync activity, where reported.
  • Content changes: edits, uploads, replacements, renames, moves, and version changes.
  • Sharing changes: new collaborators, link-sharing changes, permission changes, ownership transfers, and removals.
  • Deletion and recovery: moves to trash, permanent deletion, restoration, and changes to retention or recovery settings.
  • Account signals: unfamiliar sign-ins, devices, applications, locations, or authorization events associated with the account.

Do not focus only on file views. A suspicious sharing change may be more important than an individual preview, and a bulk rename or deletion can indicate accidental automation, a compromised session, or ransomware affecting a synchronized folder.

Platform comparison

The following comparison is intentionally high-level. Provider interfaces and feature availability change, so confirm the current menu names, retention rules, and plan requirements in the relevant help or administrator documentation before relying on a report.

PlatformWhere to lookUseful event typesExport and retention considerationsAlerts and access
Google DriveFile or folder activity panels for a quick check; organizational investigations may use the Google Workspace administrative investigation or audit tools.Edits, comments, shares, permission changes, moves, renames, uploads, downloads, and deletions where exposed.Detailed audit access, export formats, and retention can depend on the Workspace edition and administrator configuration. Personal Drive activity is generally narrower than an organizational audit.Account owners and Workspace administrators may have different visibility. Alerts can be configured through available security or activity controls, but coverage should be tested.
DropboxFile activity and sharing controls provide a user-level view; team administrators may have access to an admin activity or audit area.File changes, sharing and unsharing, link activity, membership changes, downloads, deletions, and logins where supported.Team plan, administrator role, export capability, and historical retention affect what can be retrieved. A file activity view is not necessarily the same as a team audit log.Team administrators may be able to review broader activity and configure notifications. Personal accounts have fewer central monitoring options.
OneDriveFile details and activity views help with individual files; Microsoft 365 administrators may use audit or compliance portals for broader investigations.Access, sharing, synchronization, edits, moves, renames, uploads, downloads, deletions, and restoration events where available.Audit search, export, retention, and event detail can depend on the Microsoft 365 tenant, licensing, permissions, and configured policies.Owners, site administrators, and tenant administrators may see different records. Alerting usually requires the appropriate security or compliance configuration.

A recorded event may identify an account without proving who was physically using the device. Shared credentials, delegated access, compromised sessions, VPNs, mobile networks, and synchronized clients can complicate attribution. Treat the log as a timeline to validate with sign-in records, device information, file versions, and user confirmation.

Cadence and checkpoints

A monthly review is a practical baseline for teams handling confidential material. Smaller personal accounts can use a quarterly review, while high-risk projects may need weekly or continuous monitoring. Set the cadence according to the sensitivity of the data, the number of collaborators, and the consequences of unauthorized access.

Monthly cloud storage activity checklist

  1. List active owners, editors, viewers, external guests, shared links, and connected applications for important folders.
  2. Review new sharing invitations, permission escalations, ownership changes, and links that no longer have a business purpose.
  3. Search activity for unusual downloads, bulk changes, repeated failed access attempts, deletions, or access outside the expected work pattern.
  4. Compare recent activity with project records, employee or contractor assignments, and approved automation.
  5. Check deleted or recently restored files when you are investigating missing content. If recovery is needed, avoid repeated changes and consult the provider’s recovery options.
  6. Export or securely record relevant logs before their available history changes, subject to your organization’s privacy and retention requirements.
  7. Remove obsolete collaborators and replace broad links with named access where practical.

Before a project changes hands, perform an additional checkpoint. Confirm the new owner, transfer needed files deliberately, remove departing users, rotate shared secrets, and document exceptions. A dedicated cloud storage offboarding checklist can help prevent access from surviving a role change.

How to interpret changes

Begin with the smallest reliable timeline: last known normal state, first observed problem, relevant activity events, containment action, and current state. Record timestamps with their displayed time zone. Compare the affected file with earlier versions, neighboring files, and account sign-in history.

Several patterns deserve prompt attention:

  • A new external collaborator or public link appears without an approved request.
  • A user who normally views files suddenly downloads many files or changes permissions.
  • Files are renamed, encrypted, overwritten, or deleted in a short period.
  • Activity occurs during an unusual time and matches an unfamiliar device or sign-in.
  • A deleted file returns with altered content or an unexpected owner.

Do not assume that every unusual event is malicious. Synchronization conflicts, automated workflows, mobile clients, bulk project maintenance, and a user working across time zones can produce surprising entries. Validate the event with the person or system responsible, but use an independent channel if an account may be compromised.

If compromise is plausible, preserve evidence first where possible, then revoke suspicious sessions or applications, reset credentials from a trusted device, require stronger sign-in protection, and review forwarding or sharing settings. For a broader response, follow the cloud account takeover recovery checklist. If files were deleted or overwritten, consult guidance on cloud storage retention and recovery before the available recovery window changes.

When to revisit

Revisit this audit process monthly or quarterly, depending on risk. Repeat it immediately after a suspected phishing incident, unexpected file-sharing notification, account takeover, ransomware-like synchronization event, employee or contractor departure, ownership transfer, or major change to a cloud subscription.

Review the article and your internal procedure whenever Google Drive, Dropbox, or OneDrive changes its administrator console, audit-event names, export formats, alert controls, or log-retention behavior. Menu labels are not permanent, and a feature visible to an administrator may not be available to a personal account. Keep a dated note of the console path, account role, plan or tenant context, and fields you confirmed during each review.

For the next audit, choose three sensitive folders and complete this short action plan:

  1. Confirm the owner and current collaborators.
  2. Review sharing, download, edit, move, and deletion activity.
  3. Compare unusual events with sign-in and device records.
  4. Remove unnecessary access and document approved exceptions.
  5. Preserve relevant evidence and test recovery only in a controlled manner.

Regular activity reviews will not prevent every cloud incident, but they reduce the time between an unsafe change and a useful response. Pair them with a secure document-sharing review, an independent backup strategy, and clear ownership for every sensitive workspace.

Related Topics

#audit-logs#file-activity#cloud-security#incident-investigation#Google-Drive#Dropbox#OneDrive
R

RecoverFiles Editorial Team

Cloud Security Editors

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.