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:<br><br>
                         Bob makes a RAM snapshot of the virtual machine. on a VPS it is very easy and can be done without notice.
 
                     <h3>Countermeasures</h3>
-                    <b>Can't be addressed without renting a bare-metal server instead.</b> Alice would need the baremetal server's hardware to support RAM encryption (such as <a href="developer.amd.com/wordpress/media/2013/12/AMD_Memory_Encryption_Whitepaper_v7-Public.pdf">AMD SEV</a> and <a href="https://www.intel.com/content/www/us/en/products/docs/accelerator-engines/software-guard-extensions.html">Intel SGX</a>, where the idea is to store the encryption keys in the CPU directly instead of storing it in the RAM).
+                    <b>Can't be addressed without renting a bare-metal server instead.</b> Alice would need the baremetal server's hardware to support RAM encryption (such as <a href="https://www.amd.com/content/dam/amd/en/documents/epyc-technical-docs/specifications/56860.pdf">AMD SEV</a> and <a href="https://www.intel.com/content/www/us/en/products/docs/accelerator-engines/software-guard-extensions.html">Intel SGX</a>, where the idea is to store the encryption keys in the CPU directly instead of storing it in the RAM).
 
                     <h2><b>Malicious Libvirt or Xen Interception</b></h2>