Collect Logs for the XDR Forensics Module

Available Languages

Download Options

  • PDF     (610.1 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (695.2 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (459.3 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:October 20, 2025
Document ID:225236

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Contents

Introduction

This document describes how to remotely fetch diagnostic data to troubleshoot the XDR Forensics module in its console.

Fetching logs remotely

note-icon

Note: Currently, DART logs do not contain XDR Forensics logs.

Step 1. Open XDR and navigate to Investigate > Forensics console.

Left side Menu, then, Investigate, then Forensics

Step 2. Verify the hostname of the endpoint is visible on the Assets page by navigating to Assets page. To do this:

a) Open CMD on the given machine and execute hostname command.

C:\Users\Admin\hostname
lenovo-laptop-amp

b) In XDR Forensics console main page click View all Assets (or use Assets menu on the left).

XDR Forensics console overview

c) Localize the endpoint on the list and click the Device name to enter its details.

Computer list in XDR Forensics console

Step 3. In the Asset info page, click More Actions > Collect Logs to start gathering information from the endpoint.

More Actions, then Collect Logs

note-icon

Note: If the asset is online, this takes a few seconds to complete.

Step 4. Go to Logs section to see if logs has been gathered already. In Asset Logs section, click the icon to start logs download.

Download button

Step 5. Acquired *.zip file contains three files required to troubleshoot the module:

- AIR.Log.txt

- AIR.Process.Log.txt

- TACTICAL-Legacy.Log.txt

Log files list

Revision History

Revision Publish Date Comments
1.0
21-Oct-2025
Initial Release
TAC Authored

Contributed by Cisco Engineers

  • Radek Olszowy
    TAC

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products