Git-Mirrors/anarsec.guide
1
0
Fork 0
mirror of https://0xacab.org/anarsec/anarsec.guide.git synced 2025-07-28 09:04:24 -04:00
Code Issues Projects Releases Packages Wiki Activity

layout fr

Browse source
This commit is contained in:
anarsec 2024-11-22 13:04:27 -05:00
parent 65777895db
commit 05a1171289
No known key found for this signature in database
14 changed files with 88 additions and 42 deletions
Download patch file Download diff file Expand all files Collapse all files

4
content/posts/tamper/index.md
View file

@ -10,8 +10,8 @@ tags = ["opsec", "beginner"]
blogimage="/images/beads-pink.jpg"
toc=true
dateedit=2024-04-18
a4="tamper-a4.pdf"
letter="tamper-letter.pdf"
a4="tamper-a4-en.pdf"
letter="tamper-letter-en.pdf"
+++
If the police ever have [physical access](/glossary/#physical-attacks) to an electronic device like a laptop, even [for five minutes](https://www.vice.com/en/article/a3q374/hacker-bios-firmware-backdoor-evil-maid-attack-laptop-5-minutes), they can install hardware keyloggers, create images of the storage media, or otherwise trivially compromise it at the hardware, firmware, or software level. One way to minimize this risk is to make devices tamper-evident. As the Threat Library [notes](https://notrace.how/threat-library/mitigations/tamper-evident-preparation.html), "Tamper-evident preparation is the process of taking precautionary measures to make it possible to detect when something has been physically accessed by an adversary."