That means if I am testing using my FIPS enabled laptop under Windows 7 IIS my PE DNN app should work without the "This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms" error message. I am not sure why then it fails and points to "MD5CryptoServiceProvider".BTW what PE edition setting/s should I use to explicitly disable "file based caching" and how to modify it? web.config/host settings/portal settings? Appreciate your help very much.

Bandon,Thanks a lot for raising the work order. Though we have successfully completed all testing (QA/UAT etc) currently we are "on hold" with respect to production rollout due to FIPS compliance issues. The customer has assumed that our apps are compliant. We are using DNN 5.2.2 (PE). our custom modules are all built using C#/SQL2005. Our modules do not explicitely invoke any hashing algorithms. Once again thanks a lot for your help.

We have reviewd the articles 108 and 109 as suggested by Leith Tussing but we still not sure how to implementa a workaround in the mean time. Is there a specific knowledge base article that covers the work around? We are developing under DNN 5.2.2.75 (PE). We poked around the host settings and found the "Performance Settings" allowing selections under "Module Cache Provider and "Page Output Cache Provider".  Not sure if these are settings that we should be looking at. However to our dismay none of them has "WeBasedCachingProvider" as an option. The only options that I see are  "File/Database/Memory".  Not sure if "WebCachingProvider" is only available with later versions of DNN.  We are despartely looking for a work around while awaiting the future FIPS compliant DNN 6.