Skip to content

Commit 5b4a59d

Browse files
Update Rules.md
1 parent 59c9c41 commit 5b4a59d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

wiki/Rules.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -252,7 +252,7 @@ If you want to restrict it further, under the `Addresses` tab you can review wha
252252

253253
If `/proc/sys/kernel/unprivileged_userns_clone` is set to 1, change it to 0. Until we obtain the checksum of a binary, it's better to set it to 0.
254254

255-
- Don't allow connections opened by binaries located under certain directories: `/dev/shm`, `/tmp`, `/var/tmp`
255+
- Don't allow connections opened by binaries located under certain directories: `/dev/shm`, `/tmp`, `/var/tmp` or `/memfd`
256256

257257
Why? If someone gets access to your system, usually these directories are the only ones where they can write files, thus it's usually used to drop malicious files, that download remote binaries to escalate privileges, etc.
258258

@@ -264,7 +264,7 @@ If you want to restrict it further, under the `Addresses` tab you can review wha
264264

265265
```
266266
(*) Deny
267-
[x] From this executable: ^(/tmp/|/var/tmp/|/dev/shm/|/var/run|/var/lock).*
267+
[x] From this executable: ^(/memfd|/tmp/|/var/tmp/|/dev/shm/|/var/run|/var/lock).*
268268
```
269269

270270
**Note** that the default policy should be deny everything unless explicitely allowed. But by creating a rule to deny specifically these directories, you can have a place where to monitor these executions.

0 commit comments

Comments
 (0)