> For the complete documentation index, see [llms.txt](https://cyber-reaper.gitbook.io/my-malware-analysis-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cyber-reaper.gitbook.io/my-malware-analysis-guide/guide/safety-procedures/safety-checklist.md).

# Safety Checklist

{% hint style="danger" %}
The time that you will be mostly vulnerable is during the **transit** of the malware inside your testing environment
{% endhint %}

***

## Checklist

If your answer to all the questions below is yes, then you are dealing with the malware safely :)

* [x] Am I transferring the malware in a password protected compressed file?
* [x] Does the extension of the file defang (dis-arm) the malware?
* [x] Is my Lab environment isolated from the physical host?
* [x] Do I have a snapshot for the lab environment before and after setting up the tools?

Below is why and how you will apply or have these questions answered by **YES!**

***

## Transferring Malware Safely

It is recommended to have the malware compressed and protected by password (the standard password if `infected` and not extracted until in the lab environment.

While transferring malware, there is always a chance that you (**double-click**) on it and detonate it, to avoid such thing we need to append another extension like `.malz` or `.xyz` or any file format that does not detonate the malware.

#### These apply for any malware type

## Physical Host Safety

Always make sure that the lab environment is isolated of your physical host from network.

## Lab environment Safety

Make sure you have snapshots of the lab:

1. For the clean lab
2. For the lab after installing and configuring the tools

And of course, you will go back to the configured lab after finishing the analyzing the malware.