The FCS_COP.1/STIP EAs were originally written to paraphrase NIST CAVP testing since CAVP validation is the intended mechanism by which this SFR is validated. It is unclear whether NIST's change to ACVP validation updated the test functions in a way that would require the EA to be updated or if ACVP only changed the testing process such that the EA can be kept the same.
Note that while this question is being raised in the context of the STIP Module, it is generally applicable to other PPs/Modules/functional packages that expect cryptographic primitives to be tested through NIST validation.
The FCS_COP.1/STIP EAs were originally written to paraphrase NIST CAVP testing since CAVP validation is the intended mechanism by which this SFR is validated. It is unclear whether NIST's change to ACVP validation updated the test functions in a way that would require the EA to be updated or if ACVP only changed the testing process such that the EA can be kept the same.
Note that while this question is being raised in the context of the STIP Module, it is generally applicable to other PPs/Modules/functional packages that expect cryptographic primitives to be tested through NIST validation.