From 1fa024fc085ff61561dd272fc4cd245e22593c85 Mon Sep 17 00:00:00 2001 From: Adam Langley Date: Thu, 5 Jun 2025 09:58:51 -0700 Subject: [PATCH] Fix link to FedRAMP policy. They moved the page and broke the old link. Change-Id: I797fe4357d1cf911dfb1aa8836d695c7f6985da1 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/79667 Commit-Queue: David Benjamin Commit-Queue: Adam Langley Auto-Submit: Adam Langley Reviewed-by: David Benjamin --- crypto/fipsmodule/FIPS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/crypto/fipsmodule/FIPS.md b/crypto/fipsmodule/FIPS.md index 354f4a6db..091c0f004 100644 --- a/crypto/fipsmodule/FIPS.md +++ b/crypto/fipsmodule/FIPS.md @@ -19,7 +19,7 @@ BoringCrypto has undergone the following validations: ## Update stream -On 2025-01-16, the FedRAMP Board published an [updated policy](https://www.fedramp.gov/updates/docs/cryptographic-module/) on cryptographic modules. That policy suggests that module vendors should “promote the use of update streams over the use of validated module streams”. An _update stream_ “contains the latest patches and updates to be applied to software, regardless of the FIPS-validation status of the changed software”. +On 2025-01-16, the FedRAMP Board published an [updated policy](https://www.fedramp.gov/rev5/fips/) on cryptographic modules. That policy suggests that module vendors should “promote the use of update streams over the use of validated module streams”. An _update stream_ “contains the latest patches and updates to be applied to software, regardless of the FIPS-validation status of the changed software”. BoringSSL's `main` branch is the update stream for the module. We intend to perform validations such that all major changes to the module are submitted to the CMVP within six months, as required by FRR7.