mirror of
https://github.com/overcuriousity/autopsy-flatpak.git
synced 2025-07-06 21:00:22 +00:00
76 lines
5.7 KiB
Plaintext
76 lines
5.7 KiB
Plaintext
/*! \page tree_viewer_page Tree Viewer
|
|
|
|
[TOC]
|
|
|
|
|
|
The tree on the left-hand side of the main window is where you can browse the files in the data sources in the case and find saved results from automated analyis (ingest). The tree has seven main areas:
|
|
- <b>Persons / Hosts / Data Sources:</b> This shows the directory tree hierarchy of the data sources. You can navigate to a specific file or directory here. Each data source added to the case is represented as a distinct sub tree. If you add a data source multiple times, it shows up multiple times.
|
|
- <b>File Views:</b> Specific types of files from the data sources are shown here, aggregated by type or other properties. Files here can come from more than one data source.
|
|
- <b>Data Artifacts:</b> This isone of the main places where results from running \ref ingest_page appear.
|
|
- <b>Analysis Results:</b> This is the other main place where results from running \ref ingest_page appear.
|
|
- <b>OS Accounts:</b> This is where you can see the results from both the automated analysis (ingest) running in the background and your search results.
|
|
- <b>Tags:</b> This is where files and results that have been \ref tagging_page "tagged" are shown.
|
|
- <b>Reports:</b> Reports that you have generated, or that ingest modules have created, show up here.
|
|
|
|
You can also use the "Group by Person/Host" option available through the \ref view_options_page to move the Views, Results, and Tags tree nodes under their corresponding person and host. This can be helpful on very large cases to reduce the size of each sub tree.
|
|
|
|
\section ui_tree_ds Persons / Hosts / Data Sources
|
|
By default, the top node of the tree viewer will contain all data sources in the case. The Data Sources node is organized by host and then the data source itself. Right clicking on the various nodes in the Data Sources area of the tree will allow you to get more options for each data source and its contents.
|
|
|
|
\image html ui_tree_top_ds.png
|
|
|
|
If the "Group by Person/Host" option has been selected in the \ref view_options_group "View Options", the hosts and data sources will be organized under any persons that have been associated with the hosts. Additionally, the rest of the nodes (Views, Results, etc) will be found under each data source.
|
|
|
|
\image html ui_tree_top_persons.png
|
|
|
|
\subsection ui_tree_persons Persons
|
|
|
|
If the "Group by Person/Host" option in the \ref view_options_group "View Options" has been set, the top level nodes will display persons. Persons are manually created and can be associated with one or more hosts. To add or remove a person from a host, right-click on the host and select the appropriate option.
|
|
|
|
\image html ui_person_select.png
|
|
|
|
You can edit and delete persons by right-clicking on the node.
|
|
|
|
\subsection ui_tree_hosts Hosts
|
|
|
|
All data sources are organized under host nodes. See the \ref host_page "hosts page" for more information on using hosts.
|
|
|
|
\subsection ui_tree_ds_node Data Sources
|
|
Under the hosts are the nodes for each data source.
|
|
|
|
Unallocated space is the chunks of a file system that are currently not being used for anything. Unallocated space can hold deleted files and other interesting artifacts. In an image data source, unallocated space is stored in blocks with distinct locations in the file system. However, because of the way carving tools work, it is better to feed these tools a single, large unallocated space file. Autopsy provides access to both methods of looking at unallocated space.
|
|
\li <b>Individual blocks in a volume</b> For each volume, there is a "virtual" folder named "$Unalloc". This folder contains all the individual unallocated blocks in contiguous runs (unallocated space files) as the image is storing them. You can right click and extract any unallocated space file the same way you can extract any other type of file in the Data Sources area.
|
|
\li <b>Single files</b> Right click on a volume and select "Extract Unallocated Space as Single File" to concatenate all of the unallocated space files in the volume into a single, continuous file. (If desired, you can right click on an image, and select "Extract Unallocated Space to Single Files" which will do the same thing, but once for each volume in the image).
|
|
|
|
An example of the single file extraction option is shown below.
|
|
\image html extracting-unallocated-space.PNG
|
|
|
|
\section ui_tree_views File Views
|
|
|
|
Views filter all the files in the case by some property of the file.
|
|
- <b>File Types</b> Sorts files by file extension or by MIME type, and shows them in the appropriate group. For example, files with .mp3 and .wav extensions end up in the "Audio" group.
|
|
- <b>Deleted Files</b> Displays files that have been deleted, but the names have been recovered.
|
|
- <b>File Size</b> Sorts files based on size.
|
|
|
|
\section ui_tree_results Data Artifacts
|
|
|
|
This section shows the data artifacts created by running ingest. In general, data artifacts contain concrete information extracted from the data source. For example, call logs and messages from communication logs or web bookmarks extracted from a browser database.
|
|
|
|
\section ui_tree_analysis_results Analysis Results
|
|
|
|
This section shows the analysis results created by running ingest. In general, analysis results contain information that the user has indicated they are interested in. For example, if the user sets up a list of \ref hash_db_page "notable hashes", any hash set hits will appear here.
|
|
|
|
\section ui_tree_os_accounts OS Accounts
|
|
|
|
This section shows the OS accounts found in the case. See \ref host_os_accounts for an example.
|
|
|
|
\section ui_tree_tags Tags
|
|
|
|
Any item you tag shows up here so you can find it again easily. See \ref tagging_page for more information.
|
|
|
|
\section ui_tree_reports Reports
|
|
|
|
Reports can be added by \subpage ingest_page or created using the \subpage reporting_page tool.
|
|
|
|
*/
|