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.
====== SQLite App Databases ======

===== Definition =====
SQLite App Databases 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, sqlite app databases 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.
Good analysis keeps the artifact in its lane: useful, limited, and not allowed to perform intent for the room. 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 =====
  * **Timeline reconstruction:** SQLite App Databases 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.
  * **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 sqlite app databases looks interesting but not conclusive.

===== Evidence Sources =====
^ Evidence source ^ What it may show ^ Reliability limits ^ What it cannot prove alone ^
| Mobile app databases | May show messages, usage records, settings, cache entries, or account identifiers. | Schemas change and deleted rows can be partial. | Do not prove who held the device. |
| Backup records | May preserve app data, manifests, media, and system state. | Backup scope may omit protected, cloud-only, or volatile data. | Do not equal a full device image. |
| Notification and usage records | May show previews, interaction timing, or foreground activity. | Retention is short and platform-dependent. | Do not prove message content in full. |
| Cloud-linked records | May confirm sync, account activity, or server-side retention. | Can arrive delayed or normalized. | Do not prove local device action alone. |

===== Interpretation Limits =====
The most common error is treating sqlite app databases 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 =====
  * Treating sqlite app databases as proof that a specific user acted, when the artifact only supports system or account context.
  * Treating a timestamp as exact truth without checking timezone, clock drift, and source semantics.
  * 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.

===== Example Scenario =====
A reviewer sees mobile app databases in the case file and asks whether it actually supports the written conclusion.
The artifact may explain part of the sequence, but ordinary system behavior still needs to be ruled in or out.
The careful next step is to normalize the time source, compare independent artifacts, and write the finding as support rather than proof.

===== Analysis Workflow =====
  - Define the question before opening another parser: what should SQLite App Databases help answer?
  - Preserve the source evidence and document how the mobile app databases 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 sqlite app databases 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 mobile app databases are consistent with activity related to sqlite app databases, 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 | Mobile app databases exist, but collection scope, time source, or surrounding context is limited. | State the observation and keep interpretation narrow. |
| Moderate | Mobile app databases align with Backup records, 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:account_login_history|Account Login History]] - Compare this concept when testing sequence and corroboration.
  * [[wiki:digital_forensics:browser_mobile_cloud:android_app_data|Android App Data]] - Useful when checking whether another artifact supports the same interpretation.
  * [[wiki:digital_forensics:browser_mobile_cloud:android_browser_artifacts|Android Browser Artifacts]] - Compare this concept when testing sequence and corroboration.
  * [[wiki:digital_forensics:browser_mobile_cloud:android_downloads|Android Downloads]] - Helps keep the finding grounded in a wider evidence pattern.
  * [[wiki:digital_forensics:browser_mobile_cloud:android_notifications|Android Notifications]] - Often appears nearby in reviews of the same system or behavior.
  * [[wiki:digital_forensics:browser_mobile_cloud:android_usage_stats|Android Usage Stats]] - Often appears nearby in reviews of the same system or behavior.

===== 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: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:digital_forensics:browser_mobile_cloud:android_usage_stats|Android Usage Stats]]
  * [[wiki:digital_forensics:browser_mobile_cloud:apple_icloud_artifacts|Apple iCloud Artifacts]]
  * [[wiki:digital_forensics:browser_mobile_cloud:autofill_artifacts|Autofill Artifacts]]
  * [[wiki:digital_forensics:browser_mobile_cloud:browser_cache|Browser Cache]]
  * [[wiki:digital_forensics:browser_mobile_cloud:browser_cookies|Browser Cookies]]
  * [[wiki:tools:start|Forensic Tools]]
  * [[wiki:resources:start|Project Resources]]

===== Reader Takeaway =====
SQLite App Databases is useful when it helps explain what the evidence can support and where the limits begin. Treat sqlite app databases as one part of a corroborated record, not a shortcut to intent. Cloud logs often arrive normalized, delayed, and very pleased with themselves.

===== 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.