github/confidential-containers
1
0
Fork 0
mirror of https://github.com/confidential-containers/confidential-containers.git synced 2025-08-27 11:48:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: fix dead link in overview

Browse Source 
Due to recent events, this US government page is no longer available.

Signed-off-by: Tobin Feldman-Fitzthum <tobin@ibm.com>
This commit is contained in:
Tobin Feldman-Fitzthum 2025-01-22 13:41:50 -05:00 committed by Tobin Feldman-Fitzthum
parent 1a93fb6ccb
commit 9d1293af13
2 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
overview.md
View File

@ -31,9 +31,8 @@ Cloud Computing adoption continues to accelerate whether it be Public, Private o
common a Hybrid approach and with it the trust boundaries change. Consideration of insider threats common a Hybrid approach and with it the trust boundaries change. Consideration of insider threats
needs to now consider the cloud provider, infrastructure provider, and managed service provider. needs to now consider the cloud provider, infrastructure provider, and managed service provider.
Certain industries are heavily focused on compliance to standards. Governments, too, are concerned Certain industries are heavily focused on compliance to standards. Governments are also
both [collectively](https://www.un.org/counterterrorism/cybersecurity) and [interested](https://www.un.org/counterterrorism/cybersecurity).
[individually](https://www.whitehouse.gov/briefing-room/presidential-actions/2021/05/12/executive-order-on-improving-the-nations-cybersecurity/).
The standards expected to protect software solutions continue to evolve towards a concept of The standards expected to protect software solutions continue to evolve towards a concept of
Confidential Computing. Confidential Computing.

2
releases/v0.12.0.md
View File

@ -65,7 +65,7 @@ This release has been tested on the following stacks:
## Limitations ## Limitations
The following are known limitations of this release: The following are limitations and known issues with this release.
* SEV(-ES) does not support attestation. * SEV(-ES) does not support attestation.
* Credentials for authenticated registries are exposed to the host. * Credentials for authenticated registries are exposed to the host.