3 ms·
>FIPS compliance is not a great idea, the benefits are questionable and possibly nonexistent. I counter about the benefits of FIPS. If you don't do it, you don
by pixl97 10mo ago
>FIPS compliance is not a great idea, the benefits are questionable and possibly nonexistent.
I counter about the benefits of FIPS. If you don't do it, you don't get paid by the government for whatever contract you have. Many people find getting paid to be beneficial.
Now, it's not the vast majority of applications, but I'm sure there are a significant number of developers on HN that are working on applications that need to meet FedRamp requirements and posts like this point out potential pitfalls on what needs enabled.
Not much different when dealing with stuff like STIGs. A large number of them are highly questionable and may only apply to very specific applications, yet you see barely trained button pushers saying you need to follow them. If you're aware of them when writing your application it will save a bunch of implementation headaches when it ends up in the field.
- firesteelrain 10mo agoYou can always waiver STIGs based on business or mission critical needs. You add it to your POA&M and/or SSP. Not the entire RHEL STIG mind you but parts of it
- pixl97 10mo agoOh yeah, I know, but God getting exceptions is a pain in the ass.
- JasonADrury 10mo ago>I counter about the benefits of FIPS. If you don't do it, you don't get paid by the government for whatever contract you have. Many people find getting paid to be beneficial. I absolutely agree, but the OP does speak about making "the entire software supply chain safer" which is far from true.