From 6c985654af173a7061c82d9e70f75c51be9786a7 Mon Sep 17 00:00:00 2001 From: nihilist Date: Thu, 6 Feb 2025 18:52:15 +0100 Subject: [PATCH] fix link --- opsec/cloud_provider_adversary/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/opsec/cloud_provider_adversary/index.html b/opsec/cloud_provider_adversary/index.html index f2625a5..19c8d43 100644 --- a/opsec/cloud_provider_adversary/index.html +++ b/opsec/cloud_provider_adversary/index.html @@ -195,7 +195,7 @@ in this post we are going to do a threat modelling exercise:

Bob makes a RAM snapshot of the virtual machine. on a VPS it is very easy and can be done without notice.

Countermeasures

- Can't be addressed without renting a bare-metal server instead. Alice would need the baremetal server's hardware to support RAM encryption (such as AMD SEV and Intel SGX, where the idea is to store the encryption keys in the CPU directly instead of storing it in the RAM). + Can't be addressed without renting a bare-metal server instead. Alice would need the baremetal server's hardware to support RAM encryption (such as AMD SEV and Intel SGX, where the idea is to store the encryption keys in the CPU directly instead of storing it in the RAM).

Malicious Libvirt or Xen Interception