Difference between pages "Incident Response" and "Google Chrome"

From ForensicsWiki
(Difference between pages)
Jump to: navigation, search
(Kill Chain)
 
(Open Source)
 
Line 1: Line 1:
{{Expand}}
+
Google Chrome is a [[Web Browser|web browser]] developed by Google Inc.
  
Incident Response is a set of procedures for an investigator to examine a computer security incident. This process involves figuring out what was happened and preserving information related to those events. Because of the fluid nature of computer investigations, incident response is more of an art than a science.  
+
== Configuration ==
 +
The Google Chrome configuration can be found in the '''Preferences''' file.
  
== Tools ==
+
On Linux
 +
<pre>
 +
/home/$USER/.config/google-chrome/Default/Preferences
 +
</pre>
  
Incident response tools can be grouped into three categories. The first category is '''Individual Tools'''. These are programs designed to probe parts of the operating system and gather useful and/or volatile data. The tools are self-contained, useful, discrete, and do not create a large footprint on the victim system.
+
On MacOS-X
 +
<pre>
 +
/Users/$USER/Library/Application Support/Google/Chrome/Default/Preferences
 +
</pre>
  
Standalone tools have been combined to create '''Script Based Tools'''. These tools combine a number of standalone tools that are run via a script or batch file. They require minimal interaction from the user and gather a fixed set of data. These tools are good in that they automate the incident response process and provide the examiner with a standard process to defend in court. They also do not require the first responder to necessarily be an expert with the individual tools. Their weakness, however, is that they can be inflexible. Once the order of the tools is set, it can be difficult to change. Some script based tools allow the user to pick and choose which standalone tools will be used in a given examination.
+
On Windows XP
 +
<pre>
 +
C:\Documents and Settings\%USERNAME%\Local Settings\Application Data\Google\Chrome\User Data\Default\Preferences
 +
</pre>
  
The final category of tools are '''Agent Based Tools'''. These tools require the examiner to install a program on the victim which can then report back to a central server. The upshot is that one examiner can install the program on multiple computers, gather data from all of them, and then view the results in the aggregate. Finding the victim or victims can be easier if they stand out from the crowd.
+
On Windows Vista and later
 +
<pre>
 +
C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\Default\Preferences
 +
</pre>
  
== See Also ==
+
Or for '''Chrome SxS''' (Chrome side-by-side)
* Obsolete: [[List of Script Based Incident Response Tools]]
+
  
== External Links ==
+
<pre>
* [http://dfrws.org/2002/papers/Papers/Jesse_Kornblum.pdf Preservation of Fragile Digital Evidence by First Responders], by [[Jesse Kornblum]], DFRWS 2002
+
C:\Users\%USERNAME%\AppData\Local\Google\Chrome SxS\User Data\Default\Preferences
* [https://labs.mwrinfosecurity.com/system/assets/131/original/Journey-to-the-Centre-of-the-Breach.pdf Journey to the Centre of the Breach], by Ben Downton, June 2, 2010
+
</pre>
* [http://blog.handlerdiaries.com/?p=325 Keeping Focus During an Incident], by jackcr, January 17, 2014
+
  
=== Emergency Response ===
+
Or for '''Chromium'''
* [http://www.mdchhs.com/sites/default/files/JEM-9-5-02-CHHS.pdf Addressing emergency response provider fatigue in emergency response preparedness, management, policy making, and research], Clark J. Lee, JD, September 2011
+
  
=== Kill Chain ===
+
On Linux
* [http://www.lockheedmartin.com/content/dam/lockheed/data/corporate/documents/LM-White-Paper-Intel-Driven-Defense.pdf Intelligence-Driven Computer Network Defense Informed by Analysis of Adversary Campaigns and Intrusion Kill Chains], by Eric M. Hutchins, Michael J. Clopperty, Rohan M. Amin, March 2011
+
<pre>
* [http://www.emc.com/collateral/hardware/solution-overview/h11154-stalking-the-kill-chain-so.pdf Stalking the kill chain], by RSA
+
/home/$USER/.config/chromium/Default/Preferences
* [http://blog.cassidiancybersecurity.com/post/2014/04/APT-Kill-chain-Part-1-%3A-Definition-Reconnaissance-phase APT Kill chain - Part 1 : Definition], by Cedric Pernet, April 28, 2014
+
</pre>
* [http://blog.cassidiancybersecurity.com/post/2014/04/APT-Kill-chain-Part-2-%3A-Global-view APT Kill chain - Part 2 : Global view], by Cedric Pernet, May 7, 2014
+
* [http://blog.cassidiancybersecurity.com/post/2014/05/APT-Kill-chain-Part-3-%3A-Reconnaissance APT Kill chain - Part 3: Reconnaissance], by Cedric Pernet, May 23, 2014
+
  
=== Incident Lifecycle ===
+
On MacOS-X
* [http://www.itsmsolutions.com/newsletters/DITYvol5iss7.htm Expanding the Expanded Incident Lifecycle], by Janet Kuhn, February 18, 2009
+
<pre>
* [https://www.enisa.europa.eu/activities/cert/support/incident-management/browsable/workflows/incident-lifecycle Incident lifecycle], by [[ENISA]]
+
/Users/$USER/Library/Application Support/Chromium/Default/Preferences
 +
</pre>
  
=== Intrusion Analysis ===
+
On Windows XP
* [http://www.threatconnect.com/files/uploaded_files/The_Diamond_Model_of_Intrusion_Analysis.pdf The Diamond Model of Intrusion Analysis], by Sergio Caltagirone, Andrew Pendergast, Christopher Betz
+
<pre>
 +
C:\Documents and Settings\%USERNAME%\Local Settings\Application Data\Chromium\User Data\Default\Preferences
 +
</pre>
  
=== Product related ===
+
On Windows Vista and later
* [http://middleware.internet2.edu/idtrust/2009/papers/05-khurana-palantir.pdf Palantir: A Framework for Collaborative Incident Response and Investigation], Himanshu Khurana, Jim Basney, Mehedi Bakht, Mike Freemon, Von Welch, Randy Butler, April 2009
+
<pre>
 +
C:\Users\%USERNAME%\AppData\Local\Chromium\User Data\Default\Preferences
 +
</pre>
  
== Tools ==
+
=== Plugins ===
=== Individual Tools ===
+
* [http://technet.microsoft.com/en-us/sysinternals/0e18b180-9b7a-4c49-8120-c47c5a693683.aspx Sysinternals Suite]
+
  
=== Script Based Tools ===
+
Information about plugins can be found under the "plugins section" of the Preferences file.
* [[First Responder's Evidence Disk|First Responder's Evidence Disk (FRED)]]
+
* [[COFEE|Microsoft COFEE]]
+
* [[Windows Forensic Toolchest|Windows Forensic Toolchest (WFT)]]
+
* [[Regimented Potential Incident Examination Report|RAPIER]]
+
  
=== Agent Based Tools ===
+
=== DNS Prefetching ===
* [[GRR]]
+
* [[First Response|Mandiant First Response]]
+
  
== Books ==
+
DNS is prefetched for related sites, e.g. links on the page.
There are several books available that discuss incident response. For [[Windows]], ''[http://www.windows-ir.com/ Windows Forensics and Incident Recovery]'' by [[Harlan Carvey]] is an excellent introduction to possible scenarios and how to respond to them.
+
This behavior is controlled by the setting "Predict network actions to improve page load performance", which is enabled by default.
 +
 
 +
If enabled the Preferences file contains:
 +
<pre>
 +
  "dns_prefetching": {
 +
      "enabled": true,
 +
</pre>
 +
 
 +
If disabled the Preferences file contains:
 +
<pre>
 +
  "dns_prefetching": {
 +
      "enabled": false,
 +
</pre>
 +
 
 +
== Start-up DNS queries ==
 +
 
 +
When Chrome starts it queries for several non-existing hostnames that consists of a 10 random characters, E.g.
 +
<pre>
 +
ttrgoiknff.mydomain.com
 +
bxjhgftsyu.mydomain.com
 +
yokjbjiagd.mydomain.com
 +
</pre>
 +
 
 +
This is used to determine if your ISP is hijacking NXDOMAIN results [http://www.google.com/support/forum/p/Chrome/thread?tid=3511015c72a7b314&hl=en].
 +
 
 +
== Disk Cache ==
 +
Google Chrome uses multiple caches, from [http://src.chromium.org/viewvc/chrome/trunk/src/net/base/cache_type.h?view=markup]:
 +
<pre>
 +
// The types of caches that can be created.
 +
enum CacheType {
 +
    DISK_CACHE,  // Disk is used as the backing storage.
 +
    MEMORY_CACHE,  // Data is stored only in memory.
 +
    MEDIA_CACHE,  // Optimized to handle media files.
 +
    APP_CACHE,  // Backing store for an AppCache.
 +
    SHADER_CACHE, // Backing store for the GL shader cache.
 +
    PNACL_CACHE, // Backing store the PNaCl translation cache
 +
};
 +
</pre>
 +
 
 +
<b>Note that $PROFILE (or %PROFILE%) the paths below is the profile dependent subdirectory which is normally Default but also could be Profile1, Profile2, etc.</b>
 +
 
 +
The Google Chrome disk cache uses the [[Chrome Disk Cache Format]] and can be found in:
 +
 
 +
On Linux
 +
 
 +
<pre>
 +
/home/$USER/.cache/chromium/$PROFILE/Cache/
 +
/home/$USER/.cache/google-chrome/$PROFILE/Cache/
 +
/home/$USER/.config/chromium/$PROFILE/Cache/
 +
/home/$USER/.config/google-chrome/$PROFILE/Cache/
 +
</pre>
 +
 
 +
<pre>
 +
/home/$USER/.cache/chromium/$PROFILE/Media Cache/
 +
/home/$USER/.cache/google-chrome/$PROFILE/Media Cache/
 +
/home/$USER/.config/chromium/$PROFILE/Media Cache/
 +
/home/$USER/.config/google-chrome/$PROFILE/Media Cache/
 +
</pre>
 +
 
 +
<pre>
 +
/home/$USER/.config/chromium/$PROFILE/Application Cache/Cache/
 +
/home/$USER/.config/google-chrome/$PROFILE/Application Cache/Cache/
 +
</pre>
 +
 
 +
<pre>
 +
/home/$USER/.config/chromium/$PROFILE/GPUCache/
 +
/home/$USER/.config/google-chrome/$PROFILE/GPUCache/
 +
</pre>
 +
 
 +
<pre>
 +
/home/$USER/.cache/chromium/PnaclTranslationCache/
 +
/home/$USER/.cache/google-chrome/PnaclTranslationCache/
 +
</pre>
 +
 
 +
On MacOS-X
 +
<pre>
 +
/Users/$USER/Library/Caches/Chromium/$PROFILE/Cache
 +
/Users/$USER/Library/Caches/Google/Chrome/$PROFILE/Cache
 +
</pre>
 +
 
 +
<b>TODO confirm the following paths</b>
 +
<pre>
 +
/Users/$USER/Caches/Chromium/$PROFILE/Cache/
 +
/Users/$USER/Caches/Google/Chrome/$PROFILE/Cache/
 +
</pre>
 +
 
 +
<pre>
 +
/Users/$USER/Library/Caches/Chromium/$PROFILE/Media Cache
 +
/Users/$USER/Library/Caches/Google/Chrome/$PROFILE/Media Cache
 +
</pre>
 +
 
 +
<pre>
 +
/Users/$USER/Library/Application Support/Chromium/$PROFILE/Application Cache/Cache/
 +
/Users/$USER/Library/Application Support/Google/Chrome/$PROFILE/Application Cache/Cache/
 +
</pre>
 +
 
 +
<pre>
 +
/Users/$USER/Library/Application Support/Chromium/$PROFILE/GPUCache/
 +
/Users/$USER/Library/Application Support/Google/Chrome/$PROFILE/GPUCache/
 +
</pre>
 +
 
 +
<pre>
 +
/Users/$USER/Library/Caches/Chromium/PnaclTranslationCache/
 +
/Users/$USER/Library/Caches/Google/Chrome/PnaclTranslationCache/
 +
</pre>
 +
 
 +
On Windows XP
 +
 
 +
<b>TODO confirm the following paths</b>
 +
<pre>
 +
C:\Documents and Settings\%USERNAME%\Local Settings\Application Data\Chromium\User Data\Cache\
 +
C:\Documents and Settings\%USERNAME%\Local Settings\Application Data\Google\Chrome\User Data\Cache\
 +
</pre>
 +
 
 +
On Windows Vista and later
 +
<pre>
 +
C:\Users\%USERNAME%\AppData\Local\Google\Chromium\%PROFILE%\Cache\
 +
C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\%PROFILE%\Cache\
 +
</pre>
 +
 
 +
<pre>
 +
C:\Users\%USERNAME%\AppData\Local\Google\Chromium\%PROFILE%\Application Cache\Cache\
 +
C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\%PROFILE%\Application Cache\Cache\
 +
</pre>
 +
 
 +
<pre>
 +
C:\Users\%USERNAME%\AppData\Local\Google\Chromium\%PROFILE%\Media Cache\
 +
C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\%PROFILE%\Media Cache\
 +
</pre>
 +
 
 +
<pre>
 +
C:\Users\%USERNAME%\AppData\Local\Google\Chromium\%PROFILE%\GPUCache\
 +
C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\%PROFILE%\GPUCache\
 +
</pre>
 +
 
 +
The Chrome Cache contains different files with the following file names:
 +
* index
 +
* data_#; where # contains a decimal digit.
 +
* f_######; where # contains a hexadecimal digit.
 +
 
 +
== History ==
 +
Chrome stores the history of visited sites in a file named '''History'''. This file uses the [[SQLite database format]].
 +
 
 +
The '''History''' file can be found in same location as the '''Preferences''' file.
 +
 
 +
There is also '''Archived History''' that predates information in the '''History''' file.
 +
Note that the '''Archived History''' only contains visits.
 +
 
 +
=== Timestamps ===
 +
The '''History''' file uses the different timestamps.
 +
 
 +
==== visits.visit_time ====
 +
 
 +
The '''visits.visit_time''' is in (the number of) microseconds since January 1, 1601 UTC
 +
 
 +
Some Python code to do the conversion into human readable format:
 +
<pre>
 +
date_string = datetime.datetime( 1601, 1, 1 )
 +
            + datetime.timedelta( microseconds=timestamp )
 +
</pre>
 +
 
 +
Note that this timestamp is not the same as a Windows filetime which is (the number of) 100 nanoseconds since January 1, 1601 UTC
 +
 
 +
==== downloads.start_time ====
 +
 
 +
The '''downloads.start_time''' is in (the number of) seconds since January 1, 1970 UTC
 +
 
 +
Some Python code to do the conversion into human readable format:
 +
<pre>
 +
date_string = datetime.datetime( 1970, 1, 1 )
 +
            + datetime.timedelta( seconds=timestamp )
 +
</pre>
 +
 
 +
=== Example queries ===
 +
Some example queries:
 +
 
 +
To get an overview of the visited sites:
 +
<pre>
 +
SELECT datetime(((visits.visit_time/1000000)-11644473600), "unixepoch"), urls.url, urls.title FROM urls, visits WHERE urls.id = visits.url;
 +
</pre>
 +
 
 +
Note that the visit_time conversion looses precision.
 +
 
 +
To get an overview of the downloaded files:
 +
<pre>
 +
SELECT datetime(downloads.start_time, "unixepoch"), downloads.url, downloads.full_path, downloads.received_bytes, downloads.total_bytes FROM downloads;
 +
</pre>
 +
 
 +
How the information of the downloaded files is stored in the database can vary per version of Chrome as of version 26:
 +
<pre>
 +
SELECT datetime(((downloads.start_time/1000000)-11644473600), "unixepoch"), downloads.target_path, downloads_url_chains.url, downloads.received_bytes, downloads.total_bytes \
 +
FROM downloads, downloads_url_chains WHERE downloads.id = downloads_url_chains.id;
 +
</pre>
 +
 
 +
== Cookies ==
 +
Chrome stores the cookies in a file named '''Cookies'''. This file uses the [[SQLite database format]].
 +
 
 +
=== Extension Cookies ===
 +
Chrome stores the cookies used by extensions in a file named '''Extension Cookies'''. This file uses the [[SQLite database format]].
 +
 
 +
<pre>
 +
SELECT datetime(((cookies.creation_utc/1000000)-11644473600), "unixepoch"), cookies.host_key, cookies.name, cookies.value, cookies.path, \
 +
datetime(((cookies.expires_utc/1000000)-11644473600), "unixepoch"), cookies.secure, cookies.httponly, datetime(((cookies.last_access_utc/1000000)-11644473600), "unixepoch"), \
 +
cookies.has_expires, cookies.persistent, cookies.priority FROM cookies;
 +
</pre>
 +
 
 +
== See Also ==
 +
* [[Chrome Disk Cache Format]]
 +
* [[SQLite database format]]
 +
 
 +
== External Links ==
 +
* [http://en.wikipedia.org/wiki/Google_Chrome Wikipedia article on Google Chrome]
 +
* [http://www.chromium.org/user-experience/user-data-directory The Chromium Projects - User Data Directory]
 +
* [http://www.chromium.org/developers/design-documents/network-stack/disk-cache Chrome Disk Cache]
 +
* [http://www.google.com/support/forum/p/Chrome/thread?tid=3511015c72a7b314&hl=en Chrome support forum article random 10 character hostnames on startup]
 +
* [http://www.useragentstring.com/pages/Chrome/ Chrome User Agent strings]
 +
* [http://computer-forensics.sans.org/blog/2010/01/21/google-chrome-forensics/ Google Chrome Forensics] by [[Kristinn Guðjónsson]], January 21, 2010
 +
* [http://linuxsleuthing.blogspot.ch/2013/02/cashing-in-on-google-chrome-cache.html?m=1 Cashing in on the Google Chrome Cache], [[John Lehr]], February 24, 2013
 +
* [http://www.obsidianforensics.com/blog/history-index-files-removed-from-chrome/ History Index files removed from Chrome v30], by Ryan Benson, October 2, 2013
 +
* [https://hindsight-internet-history.googlecode.com/files/Evolution_of_Chrome_Databases.png Evolution of Chrome Databases], by Ryan Benson, November 12, 2013
 +
 
 +
== Tools ==
 +
=== Open Source ===
 +
* [https://code.google.com/p/hindsight-internet-history/ hindsight-internet-history]
 +
* [[plaso]]
  
[[Category:Incident Response]]
+
[[Category:Applications]]
 +
[[Category:Web Browsers]]

Latest revision as of 04:45, 22 June 2014

Google Chrome is a web browser developed by Google Inc.

Configuration

The Google Chrome configuration can be found in the Preferences file.

On Linux

/home/$USER/.config/google-chrome/Default/Preferences

On MacOS-X

/Users/$USER/Library/Application Support/Google/Chrome/Default/Preferences

On Windows XP

C:\Documents and Settings\%USERNAME%\Local Settings\Application Data\Google\Chrome\User Data\Default\Preferences

On Windows Vista and later

C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\Default\Preferences

Or for Chrome SxS (Chrome side-by-side)

C:\Users\%USERNAME%\AppData\Local\Google\Chrome SxS\User Data\Default\Preferences

Or for Chromium

On Linux

/home/$USER/.config/chromium/Default/Preferences

On MacOS-X

/Users/$USER/Library/Application Support/Chromium/Default/Preferences

On Windows XP

C:\Documents and Settings\%USERNAME%\Local Settings\Application Data\Chromium\User Data\Default\Preferences

On Windows Vista and later

C:\Users\%USERNAME%\AppData\Local\Chromium\User Data\Default\Preferences

Plugins

Information about plugins can be found under the "plugins section" of the Preferences file.

DNS Prefetching

DNS is prefetched for related sites, e.g. links on the page. This behavior is controlled by the setting "Predict network actions to improve page load performance", which is enabled by default.

If enabled the Preferences file contains:

   "dns_prefetching": {
      "enabled": true,

If disabled the Preferences file contains:

   "dns_prefetching": {
      "enabled": false,

Start-up DNS queries

When Chrome starts it queries for several non-existing hostnames that consists of a 10 random characters, E.g.

ttrgoiknff.mydomain.com
bxjhgftsyu.mydomain.com
yokjbjiagd.mydomain.com

This is used to determine if your ISP is hijacking NXDOMAIN results [1].

Disk Cache

Google Chrome uses multiple caches, from [2]:

// The types of caches that can be created.
enum CacheType {
    DISK_CACHE,  // Disk is used as the backing storage.
    MEMORY_CACHE,  // Data is stored only in memory.
    MEDIA_CACHE,  // Optimized to handle media files.
    APP_CACHE,  // Backing store for an AppCache.
    SHADER_CACHE, // Backing store for the GL shader cache.
    PNACL_CACHE, // Backing store the PNaCl translation cache
};

Note that $PROFILE (or %PROFILE%) the paths below is the profile dependent subdirectory which is normally Default but also could be Profile1, Profile2, etc.

The Google Chrome disk cache uses the Chrome Disk Cache Format and can be found in:

On Linux

/home/$USER/.cache/chromium/$PROFILE/Cache/
/home/$USER/.cache/google-chrome/$PROFILE/Cache/
/home/$USER/.config/chromium/$PROFILE/Cache/
/home/$USER/.config/google-chrome/$PROFILE/Cache/
/home/$USER/.cache/chromium/$PROFILE/Media Cache/
/home/$USER/.cache/google-chrome/$PROFILE/Media Cache/
/home/$USER/.config/chromium/$PROFILE/Media Cache/
/home/$USER/.config/google-chrome/$PROFILE/Media Cache/
/home/$USER/.config/chromium/$PROFILE/Application Cache/Cache/
/home/$USER/.config/google-chrome/$PROFILE/Application Cache/Cache/
/home/$USER/.config/chromium/$PROFILE/GPUCache/
/home/$USER/.config/google-chrome/$PROFILE/GPUCache/
/home/$USER/.cache/chromium/PnaclTranslationCache/
/home/$USER/.cache/google-chrome/PnaclTranslationCache/

On MacOS-X

/Users/$USER/Library/Caches/Chromium/$PROFILE/Cache
/Users/$USER/Library/Caches/Google/Chrome/$PROFILE/Cache

TODO confirm the following paths

/Users/$USER/Caches/Chromium/$PROFILE/Cache/
/Users/$USER/Caches/Google/Chrome/$PROFILE/Cache/
/Users/$USER/Library/Caches/Chromium/$PROFILE/Media Cache
/Users/$USER/Library/Caches/Google/Chrome/$PROFILE/Media Cache
/Users/$USER/Library/Application Support/Chromium/$PROFILE/Application Cache/Cache/
/Users/$USER/Library/Application Support/Google/Chrome/$PROFILE/Application Cache/Cache/
/Users/$USER/Library/Application Support/Chromium/$PROFILE/GPUCache/
/Users/$USER/Library/Application Support/Google/Chrome/$PROFILE/GPUCache/
/Users/$USER/Library/Caches/Chromium/PnaclTranslationCache/
/Users/$USER/Library/Caches/Google/Chrome/PnaclTranslationCache/

On Windows XP

TODO confirm the following paths

C:\Documents and Settings\%USERNAME%\Local Settings\Application Data\Chromium\User Data\Cache\
C:\Documents and Settings\%USERNAME%\Local Settings\Application Data\Google\Chrome\User Data\Cache\

On Windows Vista and later

C:\Users\%USERNAME%\AppData\Local\Google\Chromium\%PROFILE%\Cache\
C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\%PROFILE%\Cache\
C:\Users\%USERNAME%\AppData\Local\Google\Chromium\%PROFILE%\Application Cache\Cache\
C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\%PROFILE%\Application Cache\Cache\
C:\Users\%USERNAME%\AppData\Local\Google\Chromium\%PROFILE%\Media Cache\
C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\%PROFILE%\Media Cache\
C:\Users\%USERNAME%\AppData\Local\Google\Chromium\%PROFILE%\GPUCache\
C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\%PROFILE%\GPUCache\

The Chrome Cache contains different files with the following file names:

  • index
  • data_#; where # contains a decimal digit.
  • f_######; where # contains a hexadecimal digit.

History

Chrome stores the history of visited sites in a file named History. This file uses the SQLite database format.

The History file can be found in same location as the Preferences file.

There is also Archived History that predates information in the History file. Note that the Archived History only contains visits.

Timestamps

The History file uses the different timestamps.

visits.visit_time

The visits.visit_time is in (the number of) microseconds since January 1, 1601 UTC

Some Python code to do the conversion into human readable format:

date_string = datetime.datetime( 1601, 1, 1 )
            + datetime.timedelta( microseconds=timestamp )

Note that this timestamp is not the same as a Windows filetime which is (the number of) 100 nanoseconds since January 1, 1601 UTC

downloads.start_time

The downloads.start_time is in (the number of) seconds since January 1, 1970 UTC

Some Python code to do the conversion into human readable format:

date_string = datetime.datetime( 1970, 1, 1 )
            + datetime.timedelta( seconds=timestamp )

Example queries

Some example queries:

To get an overview of the visited sites:

SELECT datetime(((visits.visit_time/1000000)-11644473600), "unixepoch"), urls.url, urls.title FROM urls, visits WHERE urls.id = visits.url;

Note that the visit_time conversion looses precision.

To get an overview of the downloaded files:

SELECT datetime(downloads.start_time, "unixepoch"), downloads.url, downloads.full_path, downloads.received_bytes, downloads.total_bytes FROM downloads;

How the information of the downloaded files is stored in the database can vary per version of Chrome as of version 26:

SELECT datetime(((downloads.start_time/1000000)-11644473600), "unixepoch"), downloads.target_path, downloads_url_chains.url, downloads.received_bytes, downloads.total_bytes \
FROM downloads, downloads_url_chains WHERE downloads.id = downloads_url_chains.id;

Cookies

Chrome stores the cookies in a file named Cookies. This file uses the SQLite database format.

Extension Cookies

Chrome stores the cookies used by extensions in a file named Extension Cookies. This file uses the SQLite database format.

SELECT datetime(((cookies.creation_utc/1000000)-11644473600), "unixepoch"), cookies.host_key, cookies.name, cookies.value, cookies.path, \
datetime(((cookies.expires_utc/1000000)-11644473600), "unixepoch"), cookies.secure, cookies.httponly, datetime(((cookies.last_access_utc/1000000)-11644473600), "unixepoch"), \
cookies.has_expires, cookies.persistent, cookies.priority FROM cookies;

See Also

External Links

Tools

Open Source