> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/detect-investigate-and-respond-to-threats/investigation-and-response/forensics/analysis-and-documentation.md). # Analysis and documentation ### Analysis and documentation Forensic investigations include additional data for analysis and documentation purposes. * Issues * Forensics Timeline * Key Assets & Artifacts #### Review Issues The issues table displays all the collections within the investigation that has identified suspicious or malicious activity within the forensics data sets. Refer to [Overview of the Issues page](/cortex-xsiam/detect-investigate-and-respond-to-threats/investigation-and-response/investigate-issues/overview-of-the-issues-page.md) for descriptions of the table fields. The following actions are available for a selected alert. * Change status * Change severity * Investigate causality chain * Run playbook * Manage alerts #### Investigation timeline The Timeline page enables you to view the list of forensic artifacts that were tagged. The tags display details of the forensic data collected from the endpoints. The **Timeline** table displays the following fields:

Field	Description
Hostname	Name of the host machine.
Timestamp	Timestamp associated with the artifact.
Type	Forensic artifact of which a tag was added.
Description	Name of the timestamp field.
Tags	There are three default tags to choose from. legitimate malicious suspicious You can also create your own tags.
User	User account associated with the forensic artifact.
Data	Data summary for the tagged item.
Mitre Att&ck Tactic	Displays the type of MITRE ATT&CK tactic of the tagged item.
Mitre Att&ck Technique	Displays the type of MITRE ATT&CK technique of the tagged item.
Notes	Displays notes entered by the user.

1. **Edit a timeline entry** You can edit a tag of an artifact in the **Timeline** table. 1. Locate the relevant item to update the tag. 2. Right-click and select **Edit timeline entry**. 3. In **Edit timeline entry**, update the information as required and then click **Save** to update the changes. 2. **Clear a timeline entry** You can remove a tag from the artifact in the **Timeline** table. 1. Locate the relevant item to remove the tag. 2. Right-click and select **Clear timeline entry**. The tag is removed from the artifact and the row is removed from the **Timeline** table. #### Key assets & artifacts Key assets & artifacts are automatically created based on the tagged data from the investigation timeline of the investigation and are divided among the categories: * **Data Access**: Displays all the items that have been tagged in the File Access tables. The following table for **Endpoints** displays the endpoints that have at least one or more items tagged:

Field	Description
Endpoint Name	Name of the endpoint.
Endpoint Type	Displays the endpoint type: Mobile Server Workstation Kubernetes Node
Endpoint Status	Displays the status of the endpoint: Connected Connected Lost Deleted Disconnected Uninstalled VDI Pending Login Forensics Offline Partial Registration
Earliest Activity	Timestamp of the earliest tagged item in the incident timeline for the endpoint.
Latest Activity	Timestamp of the last tagged item in the incident timeline for the endpoint.
IP Address	List of associated IP addresses.
IPv6 Address	List of associated IPv6 addresses.
First Seen	Timestamp of first seen.
Last Seen	Timestamp of last seen.
Endpoint Isolated	Displays the status of endpoint isolation: Pending Isolation Cancellation Pending Isolation Isolated Not Isolated
Isolation Date	Isolation date of the endpoint.

The following table for **Malware** shows all the items that have been tagged in the Process Execution or Persistence tables.

Field	Description
File Name	Name of the artifact collected from the endpoint.
Path	Executable path.
Tags	Assigned tags to the artifact.
SHA256	SHA256 value of the executable file.
Verdicts	WildFire verdicts.
User	User name of the person who ran the process.
Mitre ATT&CK Tactic	Tactic selected during tagging.
Mitre ATT&CK Technique	Technique selected during tagging.
Platform	Operating system of the endpoint: Windows macOS Linux Android
Created	Creation timestamp of the file accessed.
Accessed	Accessed timestamp of the file accessed.
Modified	Modified timestamp of the file accessed.

The following table for **Users** displays any artifact data with a non-null user field that has been tagged.

Field	Description
Username	Username of the person who ran the process.
Domain	Domain of the user's computer.
ID	Indicates the operating system: UID for macOS and Linux SID for Windows
Earliest Activity	Timestamp of the earliest tagged item in the Incident Timeline for the user.
Latest Activity	Timestamp of the last tagged item in the Incident Timeline for the user.

The following table for **Network Indicators** displays the event logs with the IP addresses that have been tagged.

Field	Description
Indicator	Data field that was tagged.
Type	IP Address Hostname URL
Country	Geolocation data for IP addresses.
Flag	Flag of the geolocated country.
Organization	Organization associated with the IP address.

The following table for **Data Access** displays all the items that have been tagged in the File Access tables.

Field	Description
Path	Path of the accessed file.
User	User name of the person who accessed the file.
Created	Creation timestamp of the file accessed.
Accessed	Accessed timestamp of the file accessed.
Modified	Modified timestamp of the file accessed.
Size	Size of the file.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-xsiam/detect-investigate-and-respond-to-threats/investigation-and-response/forensics/analysis-and-documentation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.