Anti-Forensics Field Manual

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Cloud Recycle Bins ======

===== Definition =====
Cloud Recycle Bins is a cloud, account, or synchronization artifact family used to interpret remote activity, shared content, device relationships, or server-side audit history.
In a forensic report, cloud recycle bins should be treated as a source of evidence and uncertainty, not as a shortcut to intent. The useful question is what the record supports, what it does not support, and what another source says when asked the same question.

===== Background =====
Cloud evidence is where local timelines go to argue with server clocks. Sometimes the cloud record clarifies the case. Sometimes it arrives late, normalized, and smug about it.
For practitioners, the value is not drama; it is knowing which facts can survive review and which ones need to stay in the notes. A sync conflict is not drama. It is a small argument between devices that the report has to referee.

===== Technical Description =====
Cloud review compares audit logs, account events, device lists, recycle bins, sharing records, mailbox events, exports, and local sync artifacts.
A careful review starts with the source format and collection method before it argues about meaning.

===== Forensic Relevance =====
  * **User activity review:** It may support account or profile context, but only when independent artifacts point the same direction.
  * **Contradiction testing:** It is useful for finding places where logs, metadata, storage behavior, or accounts disagree.
  * **Reporting decisions:** It helps decide how narrow the finding should be when cloud recycle bins looks interesting but not conclusive.
  * **Timeline reconstruction:** Cloud Recycle Bins can help place activity in sequence when the time source and collection conditions are understood.
  * **Recovery analysis:** It can explain why data was recovered, missed, corrupted, or only partially reconstructed.

===== Evidence Sources =====
^ Evidence source ^ What it may show ^ Reliability limits ^ What it cannot prove alone ^
| Cloud audit logs | May show account actions, access times, client identifiers, and administrative events. | Retention, licensing, and tenant configuration affect what exists. | Do not prove local user intent alone. |
| Sync client artifacts | May show local paths, conflict records, downloads, uploads, and device identifiers. | Can be delayed, retried, or performed automatically. | Do not prove manual file handling. |
| Account security records | May show logins, MFA events, OAuth grants, and device state. | IP addresses and devices can be shared, proxied, or incomplete. | Do not prove a person beyond the account context. |
| Export files | May provide structured data for review. | Exports can omit fields, normalize timestamps, or lose original context. | Do not replace platform logs. |

===== Interpretation Limits =====
The most common error is treating cloud recycle bins as proof of motive. It may support a technical event, a sequence, or a contradiction, but motive needs stronger ground.
Another bad leap is treating absence as intent. Missing data can come from retention, configuration, collection scope, sync behavior, overwriting, media behavior, or ordinary use.
A tool result should be described as a parsed or recovered record, not as the tool's opinion about what happened. Tools surface evidence; they do not understand it.
Cloud logs often arrive normalized, delayed, and very pleased with themselves.

===== Common Misinterpretations =====
  * Ignoring benign explanations because the suspicious explanation is easier to write.
  * Treating account activity as proof of a local device action.
  * Ignoring sync delay, retries, server-side retention, and export normalization.
  * Treating an IP address as a person.
  * Reporting cloud deletion without checking recycle bins, audit policy, and local sync artifacts.

===== Example Scenario =====
A responder notices cloud audit logs that appear to line up with a disputed timeline.
The record may be meaningful, but it has to be compared with sync client artifacts before the report gets confident.
The report should state the observed record, the collection limits, and the alternative explanations that were tested.

===== Analysis Workflow =====
  - Define the question before opening another parser: what should Cloud Recycle Bins help answer?
  - Preserve the source evidence and document how the cloud audit logs were collected.
  - Record tool versions, input paths, output paths, time settings, and errors.
  - Identify observed facts before writing any interpretation.
  - Normalize time sources and document timezone, clock drift, and collection-time effects.
  - Compare at least two independent artifact families before raising confidence.
  - Consider benign explanations, automated behavior, retention, sync, and storage-device behavior.
  - Write conclusions proportionally: observed fact first, inference second, uncertainty always visible.

===== Reporting Guidance =====
Reporting on cloud recycle bins should be precise enough that another analyst can retrace the claim without inheriting the original examiner's confidence.
Avoid wording that converts possibility into intent. The report should not say a user deliberately deleted, hid, wiped, or tampered with evidence unless the evidence actually supports that conclusion.
Report-ready wording:
  * The available cloud audit logs are consistent with activity related to cloud recycle bins, but they do not independently establish motive or user intent.
  * Recovery was limited under the examined conditions; additional corroboration would be required before concluding deliberate destruction.
  * The finding should be read with the collection scope, time-source limits, and alternate explanations described in this report.

===== Confidence and Reliability =====
^ Confidence level ^ What it looks like for this topic ^ How to report it ^
| Low | Cloud audit logs exist, but collection scope, time source, or surrounding context is limited. | State the observation and keep interpretation narrow. |
| Moderate | Cloud audit logs align with Sync client artifacts, but attribution or intent remains unresolved. | Say the artifacts support the finding, not that they prove it. |
| High | Multiple independent sources agree on sequence, source system, account context, and collection conditions. | Use stronger language, but still separate observed facts from inference. |

===== Related Concepts =====
  * [[wiki:digital_forensics:browser_mobile_cloud:cloud_audit_logs|Cloud Audit Logs]] - Helps keep the finding grounded in a wider evidence pattern.
  * [[wiki:digital_forensics:browser_mobile_cloud:cloud_export_files|Cloud Export Files]] - Often appears nearby in reviews of the same system or behavior.
  * [[wiki:digital_forensics:browser_mobile_cloud:cloud_sharing_history|Cloud Sharing History]] - Helps keep the finding grounded in a wider evidence pattern.
  * [[wiki:digital_forensics:browser_mobile_cloud:cloud_sync_artifacts|Cloud Sync Artifacts]] - Useful when checking whether another artifact supports the same interpretation.
  * [[wiki:digital_forensics:browser_mobile_cloud:onedrive_cloud_artifacts|OneDrive Cloud Artifacts]] - Compare this concept when testing sequence and corroboration.
  * [[wiki:digital_forensics:browser_mobile_cloud:account_login_history|Account Login History]] - Useful when checking whether another artifact supports the same interpretation.

===== Tools =====
  * [[https://rclone.org/|Rclone]] - Cloud storage listing and collection support where authorized.
  * [[https://learn.microsoft.com/en-us/powershell/microsoftgraph/|Microsoft Graph PowerShell]] - Microsoft cloud audit and account data access where authorized.
  * [[https://jqlang.org/|jq]] - JSON parsing for logs, exports, and cloud evidence.
  * [[https://github.com/mikefarah/yq|yq]] - YAML, JSON, XML, and properties parsing during evidence review.
  * [[https://sqlitebrowser.org/|DB Browser for SQLite]] - Manual SQLite database review for browser and app artifacts.
  * [[https://www.sqlite.org/index.html|SQLite]] - Reference documentation for SQLite databases used by many applications.
  * [[https://www.foxtonforensics.com/browser-history-capturer/|Browser History Capturer]] - Browser history acquisition support.
  * [[https://www.foxtonforensics.com/browser-history-examiner/|Browser History Examiner]] - Browser artifact review support.
  * [[https://developer.android.com/tools/releases/platform-tools|ADB Platform Tools]] - Android device communication and collection support.
  * [[https://libimobiledevice.org/|libimobiledevice]] - Open tooling for iOS device interactions.
  * [[wiki:tools:start|Forensic Tools]] - Full tool directory for the wiki.

===== Limitations of Tools =====
Tools parse, surface, and organize evidence. They do not create conclusions.
Parser output can be affected by version differences, unsupported formats, corrupted records, timezone handling, partial collection, and storage behavior outside the tool's view.
When a tool produces a strong-looking result, validate it against another tool or source where the stakes justify it. A parser can recover a fragment; it cannot tell you whether the fragment deserves a paragraph in the report.

===== References and Further Reading =====
  * [[https://www.sqlite.org/docs.html|SQLite documentation]] - SQLite documentation for app and browser databases.
  * [[https://developer.android.com/tools/adb|Android Debug Bridge]] - Android collection and device communication context.
  * [[https://learn.microsoft.com/en-us/purview/audit-log-search|Microsoft Purview audit]] - Microsoft cloud audit log reference.
  * [[https://takeout.google.com/|Google Takeout]] - Google account export reference.
  * [[https://plaso.readthedocs.io/|Plaso documentation]] - Timeline generation documentation.

===== See Also =====
  * [[wiki:digital_forensics:browser_mobile_cloud:start|Browser Mobile Cloud]]
  * [[wiki:digital_forensics:browser_mobile_cloud:cloud_audit_logs|Cloud Audit Logs]]
  * [[wiki:digital_forensics:browser_mobile_cloud:cloud_export_files|Cloud Export Files]]
  * [[wiki:digital_forensics:browser_mobile_cloud:cloud_sharing_history|Cloud Sharing History]]
  * [[wiki:digital_forensics:browser_mobile_cloud:cloud_sync_artifacts|Cloud Sync Artifacts]]
  * [[wiki:digital_forensics:browser_mobile_cloud:onedrive_cloud_artifacts|OneDrive Cloud Artifacts]]
  * [[wiki:digital_forensics:browser_mobile_cloud:account_login_history|Account Login History]]
  * [[wiki:digital_forensics:browser_mobile_cloud:android_app_data|Android App Data]]
  * [[wiki:digital_forensics:browser_mobile_cloud:android_browser_artifacts|Android Browser Artifacts]]
  * [[wiki:digital_forensics:browser_mobile_cloud:android_downloads|Android Downloads]]
  * [[wiki:digital_forensics:browser_mobile_cloud:android_notifications|Android Notifications]]
  * [[wiki:tools:start|Forensic Tools]]
  * [[wiki:resources:start|Project Resources]]

===== Reader Takeaway =====
Cloud Recycle Bins is useful when it helps explain what the evidence can support and where the limits begin. Treat cloud recycle bins as one part of a corroborated record, not a shortcut to intent. A sync conflict is not drama. It is a small argument between devices that the report has to referee.

===== Use Notes =====
This article is for defensive education and technical reference. It should not be treated as legal, forensic, investigative, compliance, or operational advice without qualified professional judgment.