Secur32.dll using FIPS 140 certified crypto



Hello,

Does anyone know if Secur32.dll calls are actually calling a FIPS 140
certified crypto provider(ie rsaenh.dll, bcrypt.dll module listed on NIST's
site) ? We are calling secur32.dll using InitSecurityInterfaceA to get
function pointers for the following methods:

AcquireCredentialsHandleA
InitializeSecurityContextA
EncryptMessage
DecryptMessage
etc.

So, the question is whether these methods actually use the FIPS certified
crypto providers. Also, is there a url that documents this for reference
purposes in a FIPS security policy ?

thank you,
Mike
.