From 550c7f620e91a882d674d045f2e5a4630d82afb3 Mon Sep 17 00:00:00 2001 From: Amarnath N <117257033+AmarNathChary@users.noreply.github.com> Date: Mon, 11 Sep 2023 16:12:15 +0530 Subject: [PATCH] Update content/en/blog/_posts/2023-07-06-confidential-kubernetes.md Co-authored-by: Dipesh Rawat --- content/en/blog/_posts/2023-07-06-confidential-kubernetes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/_posts/2023-07-06-confidential-kubernetes.md b/content/en/blog/_posts/2023-07-06-confidential-kubernetes.md index b9203e3d55..4aaf3f9b3a 100644 --- a/content/en/blog/_posts/2023-07-06-confidential-kubernetes.md +++ b/content/en/blog/_posts/2023-07-06-confidential-kubernetes.md @@ -129,7 +129,7 @@ signature of the memory contents, which can be sent to the VM's owner as an atte the initial guest memory was not manipulated. The second generation of SEV, known as -Encrypted State +[Encrypted State](https://www.amd.com/content/dam/amd/en/documents/epyc-business-docs/white-papers/Protecting-VM-Register-State-with-SEV-ES.pdf) or SEV-ES, provides additional protection from the hypervisor by encrypting all CPU register contents when a context switch occurs.