-
Notifications
You must be signed in to change notification settings - Fork 0
/
Anti-Forensics_Precautions.mw
150 lines (110 loc) · 8.47 KB
/
Anti-Forensics_Precautions.mw
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
{{Header}}
{{Title|
title=VM Live Mode: Anti-forensics Precautions
}}
{{#seo:
|description=Minimize what is written to the hard drive when using {{project_name_short}} VMs in Live Mode.
|image=Fornesic324234.jpg
}}
{{live}}
{{grub-live}}
[[File:Fornesic324234.jpg|thumb]]
{{intro|
Anti-forensics Precautions when using {{project_name_long}} VMs in Live Mode.
Minimize what is written to the hard drive when using {{project_name_short}} VMs in Live Mode.
This wiki page is inapplicable using host live mode.
}}
= Introduction =
[[{{non_q_project_name_short}}|{{non_q_project_name_short}}]] users have the option of booting into [[Live Mode]]. When using this feature in {{project_name_short}} VM, precautions should still be taken on trusted systems (like GNU/Linux hosts) to prevent leaving traces -- proprietary operating systems such as [[Windows_Hosts|Windows]] and [[Host_Operating_System_Selection#macOS_Hosts|macOS]] are a lost cause.
At the moment there is only one advantage of this configuration compared to using [[Live Mode]] as HOST -- achieving selective amnesia for some virtual machines (VM) while others remain persistent. This section is a work in progress and not exhaustive.
When {{project_name_short}} VM are run as a live system, all changes are written to non-persistent memory (RAM) by default. However, it is possible for this design to be bypassed by [[Malware and Firmware Trojans|malware]], swap files, core dumps and other relevant configurations that are in effect. Fortunately, most of these can be disabled. <ref>
{{whonix_wiki
|wikipage=https://www.whonix.org/wiki/Dev/Technical_Introduction#Forensics
|text=Forensics
}}
</ref> <ref>
[[Warning#Kicksecure_Persistence_vs_Live_vs_Amnesic|Kicksecure Persistence vs Live vs Amnesic]]
</ref> <ref>
[[Encrypted_Images#Other_Security_Considerations|Encrypted Guest Images: Other Security Considerations]]
</ref> <ref>
[[Core Dumps]]
</ref>
To prevent malware from remounting the hard drive as read-write it is highly recommended to use [[read-only|read-only hard drive mode]]. This raises the bar because malware would need to break out of the VM to gain persistence. In order to stymie disk forensics, it is suggested to apply [[Full Disk Encryption|full disk encryption]] on the host and the computer should be powered off when not in use.
Alternatively or in addition to full disk encryption, the entire host operating system could be run in live mode. This is called HOST [[Live Mode]]. In this configuration, all writes are redirected to the non-persistent memory (RAM). Running the host operating system in live mode would additionally benefit from a correctly implemented write protection switch; this is not required but highly recommended.
To make memory forensics harder, make sure you shutdown your computer normally <ref>
so the Linux kernel's memory erasing features (<code>page_poison</code>, <code>slub_debug</code> or <code>init_on_free</code>) and/or your firmware reset attack mitigation can kick in
</ref> and then remove the machine from any power source by pulling the power plug. In the case of notebooks, the battery should be removed. <ref>
And/or the memory should be wiped upon shutdown. This is a theoretical mechanism at present because it is [[undocumented]].
https://forums.whonix.org/t/is-ram-wipe-possible-inside-whonix/5596
</ref> See also [[Cold Boot Attack Defense]].
= Swap =
{{mbox
| image = [[File:Ambox_warning_pn.svg.png|40px]]
| text = Host swapping may be the biggest threat to anti-forensics on Linux when running in a VM. <ref>
Linux also uses swapping despite having apparent "free" memory. The kernel tends to swap out long-inactive and memory-consuming processes. This frees up RAM for caches and therefore improves responsiveness.
</ref>
}}
== Disabling Swap for an Entire System ==
Turning off swap for the whole system may cause system instability or crashes if the RAM hard limit is reached. However the ample RAM in new systems makes this unlikely and it is worth the tradeoff. <ref>
https://superuser.com/questions/243357/how-to-prevent-a-specific-program-from-swapping
</ref> Disabling swap also disables the hibernation functionality.
== Host ==
<u>On the host</u>
{{Box|text=
'''1.''' Disable swap either temporarily or persistently.
The following command will disable swap and delete the file during the life of this session.
{{CodeSelect|code=
sudo swapoff -a
}}
To disable swap in a persistent way, edit the <code>fstab</code> file and comment out the line (using <code>#</code>) with the swap partition.
{{CodeSelect|code=
sudoedit /etc/fstab
}}
'''2.''' Save and reboot.
'''3.''' Confirm swap is disabled.
To check it is off, run the <code>free</code> command. The swap line should show zeros.
{{CodeSelect|code=
free -h
}}
}}
TODO: the existing swap partition should be securely wiped since sensitive information like encryption keys might have already leaked there.
== KVM ==
<u>Disabling swapping selectively for KVM VM</u>
An alternative KVM-only solution is to set guest memory pages as 'locked'. <ref>https://serverfault.com/questions/561446/how-can-i-keep-important-vms-in-memory-without-disabling-swap</ref> <ref>https://libvirt.org/formatdomain.html#memory-backing</ref>
<pre>
<memoryBacking><locked/></memoryBacking>
</pre>
This option is not without disadvantages - it can be abused by malicious guests DoSing the host through RAM exhaustion. <ref>
When set and supported by the hypervisor, memory pages belonging to the domain will be locked in the host's memory and the host will not be allowed to swap them out, which might be required for some workloads such as real-time. For QEMU/KVM guests, the memory used by the QEMU process itself will be locked too: unlike guest memory, this is an amount libvirt has no way of figuring out in advance, so it has to remove the limit on locked memory altogether. Thus, enabling this option opens up to a potential security risk: the host will be unable to reclaim the locked memory back from the guest when it is running out of memory. This means a malicious guest allocating large amounts of locked memory could cause a denial-of-service attack on the host. Due to the risk, this option is discouraged unless your workload demands it. Even then, to mitigate these risks it is strongly recommended to set a `hard_limit` (see [https://libvirt.org/formatdomain.html#memory-tuning memory tuning]) on memory allocation suitable for the specific environment at the same time.
</ref>
Note: Setting <code>vm.swappiness = 0</code> does not completely prevent swapping. <ref>
https://superuser.com/questions/760102/why-do-i-get-swapping-even-if-i-set-vm-swappiness-to-0
</ref>
= Disabling Program Crash Dumps =
Besides swap there is the problem of disabling process memory dumping to disk.
<u>Kernel</u>
A user must go out of their way to enable kernel memory dumps since it is not enabled by default; kdump-tools is utilized in Debian. <ref>https://www.bentasker.co.uk/documentation/linux/312-installing-and-configuring-kdump-on-debian-jessie</ref>
<u>Userspace</u>
The default core dump file size is <code>0</code> on Debian Linux: <ref>https://nanxiao.me/en/enable-generating-core-dump-file-on-debian-linux/</ref>
{{CodeSelect|code=
ulimit -c
0
}}
This setting is enforced for systemd-coredump too and can be verified by inspecting the lack of core files in <code>/var/spool</code> or <code>/var/lib/systemd/coredump</code> when an intentional crash is induced (<code>/var/crash</code> does not exist in Debian but it may be available in other Linux distributions). <ref>https://linux-audit.com/understand-and-configure-core-dumps-work-on-linux/#linux-and-core-dumps</ref>
<u>Disable setuid processes dumping their memory</u>
Processes with elevated permissions (or the setuid bit) might still be able to perform a core dump, depending on your other settings. These processes usually have more access and might contain more sensitive data segments in memory, so they should be changed as well. The behavior can be altered with a sysctl key, or directly via the <code>/proc</code> file system. For permanent settings, the sysctl command and configuration is typically used. A setting is called a ‘key’, which has a related value attached to it (also known as a key-value pair).
To disable programs with the setuid bit to dump, set the fs.suid_dumpable to zero:
{{CodeSelect|code=
sudo su
}}
{{CodeSelect|code=
echo "fs.suid_dumpable=0" >> /etc/sysctl.conf
}}
Reload the sysctl configuration with the -p flag to activate any changes you made.
{{CodeSelect|code=
sysctl -p
}}
= Footnotes =
{{reflist|close=1}}
[[Category:Documentation]]
{{Footer}}