oxeo0/blog-contributions
1
0
Fork 0
mirror of http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/blog-contributions.git synced 2025-07-02 11:56:40 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

add ram extraction attack scenario

Browse source
This commit is contained in:
midas 2025-01-23 14:51:54 +01:00
parent 5c20cbe720
commit f86c5e1c7e
1 changed files with 12 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

12
opsec/cloud_provider_adversary/index.html
View file

@ -176,6 +176,18 @@ in this post we are going to do a threat modelling exercise:<br><br>
<div class="row">
<div class="col-lg-8 col-lg-offset-2">
<h1><b>Attack scenarii</b><h1>
Having finished her thread enumeration, Alice's decides to focus her efforts on three most probable/most damaging scenarii to protect herself and her organization.
<h2><b>Live RAM extraction</b></h2>
<h3>Attack</h3>
Bob powers down the serve hosting the vps and extracts its RAM, refrigerate it to analyze its contents
<h3>Countermeasures</h3>
This one is very tricky and can't be addressed without renting a bare-metal server instead. Alice would need hardware that supports RAM encryption (such as AMD SEV and SME).
<br><br>
This attack is both costly and obvious as it requires the server to go offline. Alice's decides to accept the risk for now and reevaluate based on the evolving sensitivity of the data stored on her VPS.
</div>
</div><!-- /row -->