Collect evidence from Linux endpoints manually using the Trend Micro Incident Response Toolkit.
![]() |
ImportantEvidence archives use the same folder structures as the SANS Institute and the CyLR
tool.
|
Procedure
- Select .
- Click Collect Evidence.
- Configure the following settings for manual collection.SettingDescriptionEvidence typesThe types of evidence to collect.For Linux endpoints, you need the following information:Archive location on endpointLocation of the evidence package on the local endpoint.
Important
-
The local archive does not have encryption and remains on the endpoint until deleted. This might allow anyone with access to the file system to access sensitive information or reveal the presence of an ongoing investigation.
-
Evidence archives take up hard drive space which may impact endpoint performance.
- Click
to download the Trend Micro Incident Response Toolkit.
- Deploy the toolkit to the endpoints on which you want to collect evidence.
- Execute the toolkit.
- Extract the contents of the .zip archive.
- Execute
TMIRT.sh
as the root user.
- If you do not have privileges for executing scripts, execute the following commands.
- Identify the endpoint operating system (OS) architecture by executing the
uname -m
command.-
For AArch64 or ARM64 architecture, use the TMIRT-arm64.tgz toolkit.
-
For i386 or i686 architecture, use the TMIRT-x86.tgz toolkit.
-
For AMD64 or x86_64 architecture, use the TMIRT-x64.tgz toolkit.
-
- To extract the toolkit from the .tgz file, execute the
./tar -xf
command with the correct version of the Trend Micro Incident Response Toolkit based on your OS architecture. - To begin collecting evidence, execute
./TMIRT evidence --config_file ./config.json
.
- Identify the endpoint operating system (OS) architecture by executing the
- Upload the evidence packages that the toolkit generates to Forensics. You can upload multiple files at once. Each file must not exceed 4 GB.
Forensics begins processing the uploaded evidence packages.
![]() |
Important
|