A crypto module in FIPS goes through several stages (and substages) when it is present in various lists (IUT, MIP lists) and then finally a cert is issued and it is present in the final certificate list. We could track (or rather link together) how a particular module moves through these lists. The lists should have a shared key of module_name + vendor_name though it may not be a perfect mapping so maybe some fuzziness/special-casing might be required. We could then also give stats on the IUT/MIP parts of a certificate lifetime on the certificate page (e.g., this certificate spent 30 days in the "In-review" stage of the MIP list). This would also allow us to get correlations between the final certificate properties (e.g. vendor, crypto used, ...) and how long it spent in the various IUT/MIP stages.
A crypto module in FIPS goes through several stages (and substages) when it is present in various lists (IUT, MIP lists) and then finally a cert is issued and it is present in the final certificate list. We could track (or rather link together) how a particular module moves through these lists. The lists should have a shared key of
module_name + vendor_namethough it may not be a perfect mapping so maybe some fuzziness/special-casing might be required. We could then also give stats on the IUT/MIP parts of a certificate lifetime on the certificate page (e.g., this certificate spent 30 days in the "In-review" stage of the MIP list). This would also allow us to get correlations between the final certificate properties (e.g. vendor, crypto used, ...) and how long it spent in the various IUT/MIP stages.