Course contentsShow
← Security
Lesson 2405 of 3,05246. Incident ResponseFree lesson

Browser Forensics and Web Artifacts

Extract and analyze browser history, cookies, cache, downloads, and autofill data from Chrome, Firefox, Edge, and Safari.

Browser Forensics and Web Artifacts

What you'll learn: How to extract and analyze browsing history, cookies, cache, and other web artifacts from major browsers during an incident investigation.

Why Browser Forensics Matters

When investigating security incidents, browsers are goldmines of evidence. They record where users went, what they downloaded, credentials they saved, and sessions they maintained—critical for tracking attacker lateral movement, data exfiltration, phishing compromise, or insider threats.

Core Browser Artifacts

Each major browser (Chrome, Firefox, Edge, Safari) stores artifacts in SQLite databases and JSON files, though locations differ:

History

Records URLs visited, timestamps, and visit counts. Shows reconnaissance activity, malicious site visits, or C2 communications. Look for History (Chrome/Edge), places.sqlite (Firefox), or History.db (Safari).

Cookies

Small files tracking sessions and authentication. Critical for understanding active sessions during compromise. Found in Cookies databases—helps identify stolen session tokens or persistence mechanisms.

Cache

Stores downloaded web content locally. Can recover malicious scripts, phishing pages, or exfiltrated data staged for upload. Cache inspection reveals what the attacker saw or delivered.

Downloads

Lists files downloaded with timestamps and source URLs. Direct evidence of payload delivery or tool downloads. Check History tables or separate download databases.

Autofill and Form Data

Captures typed usernames, search queries, and form inputs. May reveal reconnaissance keywords, internal system names, or credential harvesting attempts.

Analysis Approach

Extract these artifacts from user profile directories (often under AppData\Local on Windows, ~/Library on macOS, ~/.config on Linux). Use forensic tools or direct SQLite queries. Always work on forensic copies, never live systems, to maintain evidence integrity and chain of custody as established in prior disk forensics lessons.

Cross-reference timestamps with network logs and memory artifacts to build complete attack timelines.

Key Takeaway: Browser artifacts provide rich evidence of web-based attacker activity—extracting and correlating history, cookies, cache, and downloads across Chrome, Firefox, Edge, and Safari is essential for reconstructing incident timelines and identifying compromise vectors.