What is the problem this feature will solve?
Reduce the amount of time and money required to become FIPS validated/certified.
What is the feature you are proposing to solve the problem?
With the integration of OpenSSL 3.x in the Node.JS core (https://nodejs.org/en/blog/release/v17.0.0), the cryptographic system that powers Node.JS is now certified out of the box for FIPS (https://www.openssl.org/blog/blog/2021/09/07/OpenSSL3.Final/ and https://www.openssl.org/blog/blog/2022/08/24/FIPS-validation-certificate-issued/), which reduces the amount of investment necessary to demon straight that the framework is FIPS.
I propose that the build process for Node.JS be modified so that it includes the FIPS module by default. As it is now, when the module is included in the build, the end user is still responsible for enabling FIPS mode by using the crypto.setFips object.
This allows for devs to not have to use FIPS mode if they don't want to and if they do want to, it will save them tremendous investment and months of validation/certification testing their code every release they make.
I have personally heard some quotes of north of $100,000 per certification when building from source.
This would reduce that number dramatically. I have heard some orgs offering to do the paperwork for solutions that have been pre-certified for $10k or less.
This represents 90% cost savings to devs/orgs (not including the time and build infra costs needed to build from source) that are able to take advantage of the build that comes with the module built in.
What alternatives have you considered?
Doing it the hard way, building from source :-(
What is the problem this feature will solve?
Reduce the amount of time and money required to become FIPS validated/certified.
What is the feature you are proposing to solve the problem?
With the integration of OpenSSL 3.x in the Node.JS core (https://nodejs.org/en/blog/release/v17.0.0), the cryptographic system that powers Node.JS is now certified out of the box for FIPS (https://www.openssl.org/blog/blog/2021/09/07/OpenSSL3.Final/ and https://www.openssl.org/blog/blog/2022/08/24/FIPS-validation-certificate-issued/), which reduces the amount of investment necessary to demon straight that the framework is FIPS.
I propose that the build process for Node.JS be modified so that it includes the FIPS module by default. As it is now, when the module is included in the build, the end user is still responsible for enabling FIPS mode by using the
crypto.setFipsobject.This allows for devs to not have to use FIPS mode if they don't want to and if they do want to, it will save them tremendous investment and months of validation/certification testing their code every release they make.
I have personally heard some quotes of north of $100,000 per certification when building from source.
This would reduce that number dramatically. I have heard some orgs offering to do the paperwork for solutions that have been pre-certified for $10k or less.
This represents 90% cost savings to devs/orgs (not including the time and build infra costs needed to build from source) that are able to take advantage of the build that comes with the module built in.
What alternatives have you considered?
Doing it the hard way, building from source :-(