OERV-RUNTIME/boringssl
2
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix link to FedRAMP policy.

Browse Source 
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 <davidben@google.com>
Commit-Queue: Adam Langley <agl@google.com>
Auto-Submit: Adam Langley <agl@google.com>
Reviewed-by: David Benjamin <davidben@google.com>
This commit is contained in:
Adam Langley
2025-06-05 10:18:24 -07:00
committed by Boringssl LUCI CQ
parent 5ad1f83da1
commit 1fa024fc08
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
crypto/fipsmodule/FIPS.md
+1 -1
View File
@@ -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.