Forensic Discovery
Home > Cloud Forensics Services for Law Firms and Businesses

Cloud evidence starts with the right account and question.

Cloud forensics services help law firms and businesses preserve and examine available evidence from Microsoft 365, Google Workspace and other cloud accounts. Forensic Discovery helps define the account, tenant, records and questions that matter, then evaluates what the collected data supports and what remains uncertain.

A file can live in a shared drive, appear in several versions and connect to activity recorded elsewhere. A useful examination brings those sources together within an authorized scope. It can help explain access, sharing, changes and timing without treating an account name as proof of the person behind an action.

Cloud collection is part of our digital forensics services. Bring us the platform, relevant accounts, dates and the business or legal question. We can help identify the collection decisions you need to make before logs expire or accounts change.

Schedule a Free Consultation

Cloud forensics services we provide

We scope collection and analysis around available records and the agreed questions. Platform names identify potential sources, not a promise that every account, feature or historical record can be collected.

Microsoft 365 records

Scope OneDrive files, SharePoint libraries, Teams communications and available audit or sign-in records. Relevant versions and shared resources need explicit collection coverage. Licensing and roles affect access. Mailbox work is coordinated through forensic email collection.

Google Workspace records

Identify relevant Drive files, shared drives, Chat records and admin logs, subject to the account settings and available collection paths. Ownership and membership in shared drives can affect coverage. Coordinate mailbox needs with forensic email collection.

Collaboration and file sharing

Evaluate available Slack, Box, Dropbox and similar account records. Define channels, custodians, files and dates rather than assuming a workspace export contains everything. Private conversations, attachments and activity history may require separate access or export arrangements.

Audit and sign-in analysis

Compare available account activity, sharing events and file versions against the questions in dispute. Record time zones, event definitions and gaps. A download or sync event needs context; it does not alone establish onward transfer or receipt, or identify the person who acted.

Compromised accounts or suspicious sign-ins around changed payment instructions may be relevant to a wire fraud and business email compromise investigation.

Cloud account preservation

Assess retention, account status and available preservation options before routine changes remove evidence. Counsel sets legal preservation obligations; tenant administrators implement authorized platform changes. A hold and a collected copy serve different purposes, and neither automatically covers every workload.

Personal cloud and account backups

Assess authorized access to available iCloud or Google account data and cloud backups. Device settings, account security, encryption and provider restrictions can limit collection. A cloud backup may differ from current synced content and may exclude important app records.

Discuss your cloud evidence

When to bring in a cloud forensic examiner

An employee is leaving and the account may change

A license removal, account deletion or changed sharing permission can affect evidence. Before deprovisioning, identify relevant files, versions, chats and retained logs with counsel and IT. Suspected mass downloads or external sharing may also call for business data theft investigation or intellectual property theft investigation. The cloud work evaluates account records; it does not decide whether information is legally protected or misused.

A workplace complaint involves Teams, Slack or Chat

Preserve the relevant conversation context, participants, attachments and available edits or deletions within the authorized scope. A screenshot may omit a thread, time zone or linked file. Employee misconduct investigations can combine these records with other relevant sources. Counsel and HR address privacy, interviews and employment decisions; the forensic examination supplies technical findings.

A discovery request names cloud sources

Translate the request and protocol approved by counsel into specific accounts, workloads, dates and export requirements. Record shared resources, linked files and collection exceptions so downstream reviewers understand the dataset. Cloud evidence can support eDiscovery services for litigation support. Our discussion of remote and cloud-based discovery collection provides additional background.

A file access, change or sharing event is disputed

Compare retained file versions and event records to reconstruct the available sequence. Confirm what the platform means by an access, download, sync or sharing event. A sharing link may show permission was granted without proving that the recipient opened the file. Missing logs limit the answer; compare relevant records before drawing conclusions about a person or action.

Cloud platforms and data to scope

A platform name is not a collection specification. We identify the workloads and records needed, confirm available access and document exclusions before relying on an export.

Potential sources, subject to confirmed access and collection scope
Platform familyRecords to assessLogs and limitations
Microsoft 365OneDrive and SharePoint files, available versions, Teams recordsAvailable audit, sign-in, sharing and file activity records; licensing and workload differences matter.
Google WorkspaceFiles in Drive and shared drives, available revisions, Chat recordsAvailable admin, login and Drive activity records; retention and access differ by service.
Slack, Box and DropboxAuthorized conversations, files and export packagesWorkspace or file activity where available; plan, roles and export approval affect coverage.
iCloud and Google accountsAvailable account data, synced files and cloud backupsAccount records specific to the provider; encryption, security settings and backup content limit access.
Salesforce and ServiceNowAgreed business records and supported exportsHistory or audit records where enabled and retained; custom objects need explicit scoping.
AWS, Azure and Google CloudSpecified storage objects and available versionsAvailable storage activity and audit logs; source configuration and retention must be checked.

How a cloud data collection works

  1. Define the source and questionIdentify platforms, custodians, dates, shared resources, deadlines and desired deliverables. Unlike a drive image, cloud evidence is distributed across changing services. Assess retention and access before deciding what to collect.
  2. Plan preservationCoordinate preservation directed by counsel with the authorized administrator. Review account status, licensing and hold options for each source before deprovisioning. Broader needs across multiple sources belong in data preservation and collection. Document chain of custody and preservation exceptions.
  3. Confirm authority and accessDocument authorized accounts, collection methods and approved permissions. Use appropriately scoped access where supported; some exports require administrator roles or application consent. Agree on access changes and how temporary permissions will be removed.
  4. Collect and document exceptionsUse appropriate supported exports or API-based methods. Capture native data, metadata, available versions and logs within scope. Record filters, time ranges, delays from rate limits, inaccessible items and hash values where applicable. Collection may itself create audit events.
  5. Analyze the available evidenceCompare file activity, sharing and sign-in records with relevant versions and the agreed timeline. Explain how time zones were normalized, alternate explanations and missing sources. A hash comparison checks integrity between measured points, not completeness of the collection.
  6. Report and support reviewPrepare the agreed written findings and supporting exhibits or review dataset. Identify sources, methods, observations and limits. Where needed, define further collection, declaration or testimony work before expanding the engagement.

For additional context, see five steps to remote data collection. A remote workflow still needs authority for each source, access and documented exceptions.

Reports, declarations and testimony

A report tied to the questions

An agreed report can explain access and sharing timelines, relevant versions and the records supporting each observation. Exhibits and native data can support counsel or downstream review. The report should identify collection gaps and avoid treating a technical event as a legal conclusion.

Support for legal proceedings

Where scoped, expert witness and testimony services may include a declaration, affidavit, deposition or trial testimony. Counsel determines the intended legal use and any disclosure requirements. The court decides admissibility; the judge or jury evaluates evidentiary weight.

Discuss your cloud collection and reporting scope

Why work with Forensic Discovery

Cloud work needs more than a downloaded folder. Our approach connects the collection plan to the question your team needs answered, with attention to what each source can and cannot establish.

  • Scoping for each sourceAccount, workload and retention decisions guide the collection rather than a generic platform checklist.
  • Examination in contextWe compare available records and explain alternate interpretations before drawing conclusions.
  • Useful reportingMethods, exceptions and evidence limits travel with the findings so counsel and reviewers can evaluate them.
  • Coordination with your teamWe work with counsel and authorized administrators on scope, access and collection decisions. Counsel addresses privacy and requirements for data across borders.

Who we work with

We work with outside counsel, litigation teams, internal legal teams, HR, compliance, IT, tenant administrators and business leaders. The right participants depend on who controls the account and the question under review.

Forensic Discovery works with law firms and businesses only and does not accept direct individual consumer matters. If a law firm represents an individual, the firm may contact Forensic Discovery about the matter. See our offices and service locations.

Scoping and pricing

The collection plan and estimate should address the number of accounts and custodians, platforms and workloads, available volume, depth of log analysis, access complications and deadlines. Shared drives, external accounts and testimony can add work beyond an initial export.

Confirm scope, pricing and the basis of the estimate in writing before authorizing work. If access limits or newly identified sources change the plan, agree on the next steps before expanding the engagement. No single price or turnaround fits every cloud account.

Frequently asked questions about cloud forensics

What is cloud forensics, and how is it different from an admin export?

Cloud forensics connects collection to defined questions, documents the method and evaluates the records in context. An admin export can be a useful source; it may still need separate logs, versions or coverage of shared resources. Neither an admin export nor an API collection automatically captures everything. Metadata, collection exceptions, chain of custody and hash verification where applicable help explain what was obtained and whether the measured output changed.

Which cloud platforms can you collect from?

The initial scope can assess Microsoft 365, Google Workspace, Slack, Box, Dropbox and authorized personal cloud sources. Business applications may need a custom export plan. Available workloads, licensing, roles and provider restrictions determine the supported method; confirm these before assuming access to all records. Our Microsoft 365 forensic collection and analysis overview offers context for Microsoft environments.

Can cloud forensics show who accessed, downloaded or shared a file?

Available audit, sign-in and sharing records may identify an account, event and time. Version history may help explain changes. Those records do not automatically identify the human user, establish receipt by another party or prove intent. Shared credentials, delegated access, sync activity and application behavior can affect interpretation. We assess event definitions and corroborating sources, and state where missing logs prevent an answer.

How far back do cloud audit logs go?

There is no single retention period for a tenant. The service, record type, license, settings and any prior export affect what remains. File versions and audit logs can have different windows. A new hold or license change should not be assumed to restore records already lost. Ask counsel and the administrator to assess preservation early, then confirm actual oldest and newest records during collection.

Do you need administrator credentials or full tenant access?

Not always. The required access depends on the workload and collection method. A path authorized by a custodian may cover some data; other exports need administrator roles or application permissions. We define the authorized scope with the responsible team and identify the access needed. Do not send credentials through the general inquiry form. Access arrangements and removal of temporary permissions belong in the agreed collection plan.

Can you preserve a departing employee account before deletion?

Contact us before the account is changed so the team can assess available options with counsel and IT. A hold specific to the platform, license decision or authorized export may be needed. Deleting an account can affect access to retained data, and a hold does not cover every source or survive every account change. Business data theft investigations can address the broader evidence questions concerning a departing employee.

How long does a cloud data collection take?

Time depends on access approvals, account count, data volume, workloads and provider rate limits. Export jobs, inaccessible items and retries may add delay; analysis and reporting are separate work. Tell us the deadline and any pending account changes during scoping. We can assess priorities and feasible next steps after reviewing those conditions. A general inquiry does not establish a preservation start time or collection deadline.

How much do cloud forensics services cost?

Cost follows the agreed questions and sources. Account count, platforms, shared resources, data volume, log depth, access obstacles, reporting and potential testimony all matter. A targeted collection and a broader tenant examination can require different work. Discuss the proposed scope, estimate and assumptions before authorizing the engagement, and address changes when new sources or collection limits affect the plan.

Is Microsoft 365 or Google Workspace email part of this service?

Mailbox preservation and collection are coordinated through forensically sound email collection. This page focuses on the surrounding tenant: files, shared drives, collaboration records and available account activity. The two scopes often connect. A link in an email may point to a cloud file outside the mailbox, so permission, version, availability and the intended collection time need separate attention.

Will cloud evidence hold up in court?

Collection records, relevant metadata, hash values where applicable and documented chain of custody can support authentication and explanation of the work. They do not guarantee admissibility or establish that every relevant record was collected. Counsel identifies the legal requirements for the matter. The court decides admissibility and the judge or jury evaluates weight. Expert testimony can explain the methods, findings and limitations.

Schedule a Free Consultation

Tell us the platform, relevant account or tenant, the question you need answered and any deadline. Forensic Discovery can help assess your cloud evidence collection options. Use the form for a general inquiry or call (866) 458-4993.

"*" indicates required fields