Usage of 3rd party libraries for hashing and other cryptographic features make it difficult to audit for FIPS compliance.
As we move towards our FedRampHigh and eventual FIPS 140-3 support dates, it is preferred (sometimes required!) to change the hashing algorithms we are using.
Node.js's crypto library should natively provide the functionality required for most common cases and to reduce the number of 3rd party deps, I am proposing teams switch from their respective 3rd party libraries for compliance purposes.
Describe the feature:
Usage of 3rd party libraries for hashing and other cryptographic features make it difficult to audit for FIPS compliance.
As we move towards our FedRampHigh and eventual FIPS 140-3 support dates, it is preferred (sometimes required!) to change the hashing algorithms we are using.
Node.js's crypto library should natively provide the functionality required for most common cases and to reduce the number of 3rd party deps, I am proposing teams switch from their respective 3rd party libraries for compliance purposes.
Server side (Node) only for now.