On Wednesday, March 11, 2020 11:36:38 AM EDT Matěj Týč wrote:
One of RHEL7 bugzillas [1] shows an interesting discrepancy between
our
content and STIG:
* We feature [2] a rule "Use Only FIPS 140-2 Validated Ciphers"
* STIG has its own [3] "A FIPS 140-2 approved cryptographic algorithm
must be used for SSH communications."
There is a discrepancy between the two - while we claim that the
following ciphers are FIPS 140-2 certified on Red Hat Enterprise Linux
7, only three of them are recognized as such by the STIG:
* aes128-ctr(STIG)
* aes192-ctr(STIG)
* aes256-ctr(STIG)
* aes128-cb
* aes192-cbc
* aes256-cbc
* 3des-cbc
* rijndael-cbc(a)lysator.liu.se
I have confirmed correctness of our description with our FIPS SME Tomas
Mraz (in CC), so this issue looks as a bug in STIG - either the
requirement is too strict, so it is incorrect, or it is supposed to be
strict, and it should therefore be reworded, and we need to create a new
rule in our content.
What is the procedure in cases like this?
Common Criteria allows the cbc mode (but not the 192 variants). So, that is
another data point to consider that the STIG may be off on that one. However,
3des is consider deprecated in the 800-131a. It is not disallowed and can
still be used. But maybe its deprecation is the rationale for that one.
-Steve