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

tail best updates, pdf macro

Browse source
This commit is contained in:
anarsec 2023-07-09 14:59:19 +00:00
parent 11986c34cb
commit 0031e85f7a
No known key found for this signature in database
15 changed files with 62 additions and 22 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -10,6 +10,8 @@ tags = ["opsec", "easy"]
blogimage="/images/X230.jpg"
toc=true
dateedit=2023-05-10
a4="tamper-a4.pdf"
letter="tamper-letter.pdf"
+++
If police can ever have [physical access](https://www.csrc.link/threat-library/techniques/targeted-digital-surveillance/physical-access.html) 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 on the hardware, firmware, or software level. One way to minimize this risk is to make it tamper-evident. As the CSRC Threat Library [notes](https://www.csrc.link/threat-library/mitigations/tamper-evident-preparation.html), "Tamper-evident preparation will make it possible to discern when something has been [physically accessed](/glossary/#physical-attacks) - it's not possible to prevent a powerful enemy from obtaining physical access to your computer when you are away, but it should be possible to be able to detect when they do."