Perform forensic acquisition and analysis of cloud storage services including Google Drive, OneDrive, Dropbox, and Box by collecting both API-based remote data and local sync client artifacts from endpoint devices.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Perform forensic acquisition and analysis of cloud storage services including Google Drive, OneDrive, Dropbox, and Box by collecting both API-based remote data and local sync client artifacts from endpoint devices.
Cloud storage forensic acquisition involves collecting digital evidence from services like Google Drive, OneDrive, Dropbox, and Box through both API-based remote acquisition and local endpoint artifact analysis. Modern investigations must address the challenge that cloud-synced files may exist in multiple states: locally synchronized, cloud-only (on-demand), cached, and deleted. Endpoint devices that have synchronized with cloud storage contain a wealth of metadata about locally synced files, files present only in the cloud, and even deleted items recoverable from cache folders. API-based acquisition using service-specific APIs provides direct access to remote data with valid credentials and proper legal authorization.
When to Use
When conducting security assessments that involve performing cloud storage forensic acquisition
When following incident response procedures for related security events
When performing scheduled security testing or auditing activities
When validating security controls through hands-on testing
Detection Gaps & Validation
API acquisition captures current state, not history. Items purged past retention are gone — Google Drive Trash and OneDrive recycle bin typically hold ~30 days (OneDrive site/second-stage up to 93), Dropbox version history varies by tier. A clean recyclebin/Trash listing does not mean nothing was deleted; note the retention window as a coverage limit.
Cloud-only files are absent on the endpoint. On-demand/"Files On-Demand" placeholders (OneDrive .cloud, DriveFS) are not stored locally, so disk imaging alone misses them — you need the API or the sync metadata DB.
Encrypted/opaque local stores: Dropbox filecache.dbx/config.dbx are obfuscated SQLite and need decryption; parsing them raw yields nothing. OneDrive SyncEngineDatabase/<account>.dat schemas change across client versions.
Anti-forensics seen in the wild: deleting individual file revisions (the worked example shows a malicious macro added then reverted) and unsharing links to hide exfil recipients.
Timezone: API metadata (createdTime, modifiedTime) and revision times are UTC ISO-8601 — convert before merging with endpoint local times.
Validate / cross-corroborate: verify each acquired file's API md5Checksum against the downloaded/hashed copy for chain of custody, and reconcile API metadata with endpoint sync logs, browser history (web uploads), and . Confirm external-sharing events against the provider , not just the file's permission list.
$MFT
admin/audit log
Prerequisites
Legal authorization (warrant, consent, or corporate policy) for cloud data access
Valid user credentials or administrative access tokens
Magnet AXIOM Cloud, Cellebrite Cloud Analyzer, or equivalent tool
KAPE with cloud storage target files
Python 3.8+ with google-api-python-client, msal, dropbox SDK