On Sep 16, 2014, at 7:35 AM, T, Satyanarayana (GE Healthcare) <[email protected]> wrote:
> Hi, > > This is regarding FIPS support for openssl. I was able to build FIPS capable > Openssl and link it to my application which uses Openssl(AES-256) for > Database encryption. I enabled FIPS mode using FIPS_mode_set(1) (which did > passed) and ran some unit tests and I see that all of the current tests are > passing. > > From the openssl user guide I see that once I enabled FIPS mode using > FIPS_mode_set(1) all non-fips algorithms will be disabled. Having said that > since all my current tests are passing, Does that mean I am in FIPS compliant > for database encryption. It means you’re running OpenSSL in “FIPS mode”. What that means for compliance is something for your lawyers to determine. What you can do is pass along to the lawyers that you followed all of the rules set forth in the OpenSSL FIPS Security Guide (assuming you did), and that you’ve enabled FIPS mode. Let the lawyers worry about if that’s good enough or not — most of the time, it is, but just stating FIPS 140 compliance might not be correct. > Please do help me understand if I have to do anything else for enabling FIPS > mode…… Nope, from a technical perspective, as long as you followed the Security Guide (and using the exact steps in the FIPS User’s Guide is the best way to ensure that), the technical stuff is all done. :) TOM > Regards, > Satya. > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > User Support Mailing List [email protected] > Automated List Manager [email protected] ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [email protected] Automated List Manager [email protected]
