From d04ebe135d621e18aaf0e7de7921170ff3bfdf4c Mon Sep 17 00:00:00 2001
From: midas <midas@mullsec>
Date: Thu, 23 Jan 2025 14:52:08 +0100
Subject: [PATCH] header for the BMC exploitation scenario

---
 opsec/cloud_provider_adversary/index.html | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/opsec/cloud_provider_adversary/index.html b/opsec/cloud_provider_adversary/index.html
index f78c1bd..1ebfe49 100644
--- a/opsec/cloud_provider_adversary/index.html
+++ b/opsec/cloud_provider_adversary/index.html
@@ -188,6 +188,13 @@ in this post we are going to do a threat modelling exercise:<br><br>
                     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.
+
+                    <h2><b>BMC Exploitation</b></h2>
+                    <h3>Attack</h3>
+
+
+
+
           
 	       </div>
 			</div><!-- /row -->