Important News:SafeLogic's CryptoComply Achieves FIPS 140-3 Validation for 28 OEs and Receives Certificate #4781! Read the blog post!
-
Companies selling technology that performs encryption to the federal government must obtain NIST certification per its FIPS 140-2 & 140-3 regulations that confirm their cryptography has been tested and approved for use by government agencies
-
FIPS 140 validation has been so successful, it has been adopted as mandatory by several additional security regulations, including FedRAMP, StateRAMP, CMMC v2, Common Criteria, DoDIN APL and CNSA 2.0
-
While traditional FIPS 140-2 certification took as long as two years, the queue appears to be even longer as the industry transitions to FIPS 140-3
-
Without an active FIPS 140-2 or 140-3 certificate in your company's name, federal procurement agents may block the acquisition of your products, freezing you out of markets requiring FIPS validated solutions
Many people assume these are synonyms. With FIPS, they are not. In fact, there is a huge difference between them.
Validation means your company's cryptography module has passed a formal testing process with a NIST-approved lab. Certified means your company has received a certificate in its name from NIST that verifies your module has been validated.
Some claim that using another company’s certified module constitutes 'FIPS compliant’(which is called by some 'FIPS inside'). But compliance is not always good enough. Compliant today may also not be compliant tomorrow if someone else’s module goes out of compliance (e.g., goes historical). Historical certificates cannot be used for new government acquisitions.
Also, government procurement agents may block acquisition of products that do not have FIPS certification in their own name listed in NIST's validated modules database.
Why take the chance?
CryptoComplyTM
CryptoComply is SafeLogic’s flagship software, a family of FIPS 140-3 validated cryptographic software modules that support multiple operating systems, platforms, and languages. They deliver “Drop-in Compatibility” as direct replacements for popular open-source crypto providers. SafeLogic ensures that as FIPS 140-3 standards evolve or other relevant changes occur, it keeps CryptoComply FIPS 140-3 validated modules up-to-date.
RapidCertTM
SafeLogic revolutionized the FIPS industry twelve years ago with RapidCert, the industry's first expedited FIPS 140 validation program. Get FIPS certification of your CryptoComply solution, in your name, in only two months with RapidCert. Our FIPS validation boundary excludes your proprietary product code so you can update and iterate releases independently from FIPS 140-3 requirements.
MaintainCertTM
MaintainCert is a fixed-cost, white-glove service that takes over upon the delivery of RapidCert, proactively ensuring your NIST certification does not go ‘historical’ due to discovered vulnerabilities or other factors. While MaintainCert does include enterprise-level support for CryptoComply, don’t confuse it with a software maintenance agreement, as MaintainCert covers both your software and your certificate.
- Less Expertise and Effort Required. Sure you could hire and train your own team to work with a FIPS lab to achieve and maintain FIPS certification, but couldn’t your engineers deliver more value to your customers on other projects?
- Faster Time to Market. If you are new to federal markets, did you want to start generating revenue in two months or two years?
- Predictable Fixed Costs Over Time. How much will it cost you to develop your encryption software, get it certified by NIST, then get it recertified multiple times over it’s lifetime to avoid going Historical?
