A-Priori Avoidance:
The software environment hosting the automation may be prepared in order to generate as less unwanted evidence as possible.
Such a-priori avoidance may require a certain knowledge of the underlying operating system, features and services running on the machine. A naive approach consists of disabling any logging mechanisms and
other services that may record information about files and processes belonging to the automation. For example, features
like Virtual Memory, Prefetch and Volume Shadow Copy could be disabled on Windows.
Similarly, logging services such as syslogd can be disabled on Linux.
However, the presence of disabled features that are typically enabled by default may be considered suspicious by the DFA. Alternatively, the AM could temporarily disable these services, but also this solution might produce suspicious traces,
such as ``temporal holes'' in the system history.