General Questions

Q: Do we need FIPS if we're not a government contractor?

A: FIPS becomes relevant depending on your industry and customer base. Financial services organizations increasingly require FIPS for trading systems due to SEC regulations. Healthcare providers benefit from FIPS compliance as HIPAA strongly recommends it for sensitive data protection. Any SaaS provider using cloud infrastructure like AWS GovCloud or Azure Government requires FIPS compliance for those services. Many enterprise customers increasingly demand FIPS in their service contracts, treating it as a baseline security requirement rather than a specialized need. In practice, many industries treat FIPS as standard practice for data security across their infrastructure.

Q: What's the difference between "FIPS mode" and FIPS compliance?

A: The term "FIPS mode" is vague and varies across products. Actual FIPS compliance requires several concrete elements working together. First, you must use a CMVP-validated cryptographic module such as OpenSSL #4949. Second, you can only use FIPS-approved algorithms including TLS 1.2 or higher, AES-256 for encryption, RSA-2048 or better for signatures, and SHA-256 for hashing. Third, proper configuration and key management must be implemented and audited. Finally, you need an audit trail such as FIPS-Traces provides for runtime verification. Simply enabling a "FIPS mode" setting in an application doesn't guarantee compliance without these elements working in concert.

Q: Does Kubernetes have FIPS support?

A: Kubernetes support for FIPS is nuanced. Kubernetes itself hasn't been formally FIPS-certified as a whole system. However, the kubelet component can be configured to use FIPS-validated OpenSSL for TLS connections between nodes and the API server. Applications running in pods must individually implement FIPS for their own cryptographic operations. CleanStart handles FIPS for container images themselves; you configure FIPS OpenSSL at the operating system level. The result is that you can achieve FIPS compliance in a Kubernetes environment, but it requires configuration at both the OS and application levels.

Q: Can we mix FIPS and non-FIPS code?

A: Yes, but it requires careful management. Non-FIPS code can run alongside FIPS code in the same system without breaking. However, all cryptographic operations themselves should use FIPS modules—non-FIPS cryptography undermines compliance. FIPS-Traces can automatically block non-FIPS cryptographic attempts, failing closed to enforce compliance. When non-FIPS code must exist, audit and document why it's necessary, as legacy code often can be updated to use FIPS libraries with minimal effort.

Implementation Questions

Q: How much does FIPS compliance cost?

A: FIPS compliance costs are minimal when using open-source solutions like CleanStart. OpenSSL FIPS is completely open-source with no licensing cost. CleanStart tools themselves are free to use. Infrastructure costs remain the same whether you implement FIPS or not. Staff training typically requires one to two days of learning. The total cost for a typical organization runs below $50,000, compared to $200,000 or more when using proprietary solutions that bundle compliance consulting and specialized tools.

Q: How much performance penalty does FIPS impose?

A: Performance overhead varies by operation. TLS handshakes see five to ten percent slowdown, though this occurs only once per connection and is rarely a bottleneck. Symmetric encryption operations like AES-256 typically slow by two to five percent since FIPS algorithms are highly optimized. Hashing operations see less than two percent overhead. RSA operations experience ten to twenty percent slowdown, but these are rare in most workloads. Modern hardware acceleration through AES-NI and similar CPU extensions mitigates most of the penalty, making FIPS practical for production environments.

Q: Can we use third-party cloud services with FIPS?

A: Cloud provider FIPS support varies significantly. AWS GovCloud provides FIPS 140-2 support and is upgrading to FIPS 140-3 modules. Azure Government offers FIPS 140-2 modules. Google Cloud provides FIPS-validated OpenSSL. Regular AWS, Azure, and GCP regions are not FIPS-certified by default. Always check your specific cloud provider's documentation for FIPS services available in your region and the specific certification level they've achieved.

Technical Questions

Q: What's the difference between FIPS 140-2 and 140-3?

A: FIPS 140-3 represents the current standard released in 2019 and incorporates several improvements over 140-2. FIPS 140-3 requires stronger controls for tamper detection, preventing physical attacks on cryptographic hardware. Key management controls are more sophisticated. More algorithms are tested—SHA-3 is now included alongside SHA-2. The standard is also easier to update and evolve without locking implementations to specific algorithm versions. All new cryptographic module validations use FIPS 140-3. FIPS 140-2 remains widely used for older modules but represents an older standard that no longer receives new validations.

Q: Can we use RSA-2048 indefinitely?

A: RSA-2048 is acceptable for FIPS compliance only until 2030. After that date, you must migrate to RSA-3072 or higher for continued compliance. An alternative is switching to ECDSA with P-384 parameters, which provides equivalent strength to much larger RSA keys. Plan key rotation well in advance to avoid emergency migrations before 2030.

Q: Is TLS 1.3 faster than TLS 1.2 with FIPS?

A: Yes, TLS 1.3 is faster despite FIPS overhead. TLS 1.3 requires only one round-trip for connection establishment, while TLS 1.2 requires two. Both are approved under FIPS. TLS 1.3 is recommended because it's faster and offers additional security improvements beyond FIPS requirements.

Q: Can we use ECDSA instead of RSA?

A: Yes, ECDSA is a viable alternative if your clients support it. ECDSA with P-256 parameters provides equivalent strength to RSA-3072. ECDSA with P-384 provides strength equivalent to RSA-7680. Both are FIPS-approved algorithms. ECDSA offers performance advantages—it's significantly faster than RSA for equivalent security strength. Example cipher suite: TLS_ECDHE_ECDSA_WITH_AES256_GCM_SHA384.

Compliance Questions

Q: What does "FedRAMP SC-13" require?

A: Security Control SC-13 mandates cryptographic protection with specific requirements. First, systems must use FIPS-validated cryptographic modules. Second, only NIST-approved algorithms can be used. Third, cryptographic keys must be managed securely throughout their lifecycle. Fourth, both data in transit and data at rest must be encrypted.

CleanStart satisfies SC-13 through several mechanisms. It uses CMVP-validated modules like OpenSSL #4949. It exclusively uses FIPS-approved algorithms including AES-256, SHA-256, and others. FIPS-Traces provides comprehensive key management audit trails. Documentation includes encryption examples for both transit and at-rest scenarios.

Q: How do we audit FIPS compliance?

A: Comprehensive FIPS compliance auditing requires multiple tools and approaches. FIPS-Verifier performs static configuration analysis to verify all enabled algorithms are approved. FIPS-Traces logs all runtime cryptographic operations for audit review. Certificate verification commands like openssl allow direct inspection of cryptographic configuration. Log analysis by grepping FIPS-Traces logs reveals any violations. Third-party auditors provide optional independent assessment. All three layers together provide complete evidence of FIPS compliance.

Q: What's the difference between FIPS and NSA Suite B?

A: Suite B was NSA guidance that is now deprecated. Suite B mandated use of only FIPS-approved algorithms, recommended specific cipher combinations, and required certain key sizes that are now considered too conservative. NSA Suite B has been replaced by FIPS 140-3 as the current standard. FIPS 140-3 alone is flexible enough for modern requirements. Organizations define their own specific policies identifying which FIPS-approved algorithms they'll use, rather than following a one-size-fits-all NSA recommendation.

Q: Can we get FIPS certified ourselves?

A: Individual organizations cannot obtain FIPS certification. Only NIST and the CMVP certify cryptographic modules. However, organizations can use CMVP-certified modules like OpenSSL and BoringSSL. Document your use of certified modules in your system architecture. Audit your implementation with FIPS-Verifier to ensure it complies with the standard. Include FIPS compliance in third-party assessments like FedRAMP or SOC 2 audits. The result is a thorough, auditable compliance posture even though your organization doesn't hold the certification itself.

Q: How often does FIPS certification expire?

A: FIPS certification validity depends on the specific module. OpenSSL 3.0 FIPS has certificate #4949 with validity continuing until re-validation becomes necessary. Re-validation is triggered when algorithm changes occur or vulnerabilities are found. Monitor status at https://csrc.nist.gov/projects/cryptographic-module-validation-program/ quarterly to catch updates affecting your modules.

Troubleshooting Questions

Q: We want to use library X, but it's not FIPS-compatible. What do we do?

A: Several options exist for handling non-FIPS libraries. The first and usually best option is switching libraries to a FIPS-compatible alternative—OpenSSL can replace many crypto libraries, and BoringSSL is CMVP-validated. For hashing, SHA-256 is almost always a viable replacement for MD5. Second, you can fork and modify the library to use FIPS algorithms, though this is expensive and requires ongoing maintenance. Third, you can accept the risk, document the non-FIPS component, and complete a risk assessment and approval process. Fourth, contact the vendor—some will add FIPS support if requested by customers. In practice, option one is almost always viable.

Q: Our legacy app uses MD5. Must we upgrade it?

A: For FIPS compliance, upgrading is necessary. MD5 is explicitly not FIPS-approved. FIPS-Traces will block MD5 operations in a compliant system. Your options are upgrading to SHA-256, which is usually a simple code change, isolating the non-FIPS code if it's truly unavoidable, or documenting and formally accepting the risk. In practice, most applications can upgrade to SHA-256 within days, making this a worthwhile investment.

Q: TLS handshake is failing. How do we debug?

A: Use the openssl command-line tool to diagnose TLS issues:

openssl s_client -connect server:443 -tls1_2 -cert client.crt -key client.key -CAfile ca.crt -debug

Common issues fall into a few categories. Certificate expiration requires renewal using FIPS-compliant hash algorithms. Wrong cipher suite requires adding FIPS-approved ciphers to your configuration. TLS version mismatch means ensuring both client and server support TLS 1.2 or higher.

Q: FIPS-Traces is blocking legitimate operations. How do we allow them?

A: When FIPS-Traces blocks operations, consider your options carefully. First, use a FIPS-approved alternative—MD5 can become SHA-256, and most crypto libraries have FIPS alternatives. This is the recommended approach. Second, you can disable tracing by setting export FIPS_TRACES_LEVEL=warn, which alerts without blocking, though this weakens compliance. Third, create a formal exception—document why non-FIPS is needed, complete a risk assessment, get approval, and document the exception in your FIPS policy. Fourth, schedule the non-FIPS task to run during maintenance windows outside production hours. Option one is almost always possible and maintains full compliance.

Getting Help

Q: Where can we learn more?

A: Multiple resources support FIPS learning. NIST SP 800-175B provides the official implementation guide. OpenSSL maintains comprehensive documentation at https://www.openssl.org/docs/. CleanStart's documentation set includes detailed FIPS guidance. The CMVP Database at https://csrc.nist.gov/projects/cryptographic-module-validation-program/ lists all validated modules. Professional consultants offer FIPS training courses.

Q: Do we need professional auditors?

A: The need for auditors depends on your compliance requirements. FedRAMP absolutely requires FedRAMP-authorized assessors. SOC 2 audits benefit from independent review of FIPS controls. Internal compliance programs can often manage with FIPS-Verifier and FIPS-Traces without external auditors. For any organization using FIPS critically, annual third-party reviews provide valuable external perspective and assurance.

Q: How do we keep FIPS compliance up-to-date?

A: Sustained FIPS compliance requires ongoing attention. Subscribe to CMVP update notifications and check quarterly for changes. Re-scan your systems with FIPS-Verifier when any cryptographic modules update. Monitor FIPS-Traces logs regularly for any violations. Complete annual compliance audits to verify continued compliance. Update documentation when algorithms are deprecated or new standards are released. This routine maintenance prevents compliance decay as your systems evolve.

See Also

FIPS Overview: fips-140-overview.md — Core concepts. Regulatory: ../regulatory/fedramp-high.md — FedRAMP compliance. Tools: fips-verifier.md, fips-traces.md — Verification tools.