4 ms·
It’s replacing enterprise products that cost way more to meet compliance requirements. It would have saved me about $50k on a project awhile back. No open sour
by Spooky23 8y ago
It’s replacing enterprise products that cost way more to meet compliance requirements. It would have saved me about $50k on a project awhile back.
No open source product will meet the requirement, because you often need FIPS validated crypto.
- viraptor 8y ago> No open source product will meet the requirement, because you often need FIPS validated crypto. What do you mean? Redhat has FIPS mode. Openssl has FIPS object module. You can create a secrets storage product out of those blocks. Do you mean some specific requirements for the project you were working on?
- Spooky23 8y agoRolling your own is expensive if you’re getting audited for compliance that includes FIPS or other things. You need to have a Dev who understands and documents everything, your ops guys need to be careful to not fix a security bug in OpenSSL that leaves you with a non-validated version, etc. Or you can give AWS $5/secret/year. It’s the path of least resistance.
- viraptor 8y agoI agree it's simple to use aws in this case. I meant specifically the claim that "No open source product will meet the requirement". It may not be the financially optimal solution, but that's not "open source" specific.
- Spooky23 8y agoI see your POV, but I think the distinction is that RHEL or OpenSSL aren’t vaults. They are components or tools. If RHEL includes a vault product, that would be different. If I need to sit, I need a chair can support my weight. A box containing 2x4s, a hammer and box of nails doesn’t meet the need. I’m not disparaging OSS — it just isn’t a good fit for use cases like this when you need to deal with bullshit like FIPS 140-2.
- eropple 8y agoCredstash uses KMS (in much the same way as AWS Secret Provider does) and AES-256 (which is a FIPS 140-2 validated algorithm) internally. If AWS's crypto validates, Credstash's will.