Warning: The magic method WPML_Absolute_Url_Persisted::__wakeup() must have public visibility in /usr/home/corsec/public_html/corsec.com/wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/resolver/wpml-absolute-url-persisted.php on line 30

Warning: Cannot modify header information - headers already sent by (output started at /usr/home/corsec/public_html/corsec.com/wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/resolver/wpml-absolute-url-persisted.php:30) in /usr/home/corsec/public_html/corsec.com/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /usr/home/corsec/public_html/corsec.com/wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/resolver/wpml-absolute-url-persisted.php:30) in /usr/home/corsec/public_html/corsec.com/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /usr/home/corsec/public_html/corsec.com/wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/resolver/wpml-absolute-url-persisted.php:30) in /usr/home/corsec/public_html/corsec.com/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /usr/home/corsec/public_html/corsec.com/wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/resolver/wpml-absolute-url-persisted.php:30) in /usr/home/corsec/public_html/corsec.com/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /usr/home/corsec/public_html/corsec.com/wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/resolver/wpml-absolute-url-persisted.php:30) in /usr/home/corsec/public_html/corsec.com/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /usr/home/corsec/public_html/corsec.com/wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/resolver/wpml-absolute-url-persisted.php:30) in /usr/home/corsec/public_html/corsec.com/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /usr/home/corsec/public_html/corsec.com/wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/resolver/wpml-absolute-url-persisted.php:30) in /usr/home/corsec/public_html/corsec.com/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /usr/home/corsec/public_html/corsec.com/wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/resolver/wpml-absolute-url-persisted.php:30) in /usr/home/corsec/public_html/corsec.com/wp-includes/rest-api/class-wp-rest-server.php on line 1893
{"id":12747,"date":"2018-01-23T14:15:14","date_gmt":"2018-01-23T19:15:14","guid":{"rendered":"https:\/\/www.corsec.com\/?p=12747"},"modified":"2022-02-07T14:55:27","modified_gmt":"2022-02-07T19:55:27","slug":"fips-archived","status":"publish","type":"post","link":"https:\/\/www.corsec.com\/fips-archived\/","title":{"rendered":"CMVP Archives Additional FIPS Validations"},"content":{"rendered":"

[vc_row][vc_column][vc_column_text]On January 1, 2018, the CMVP carried out the archiving of specific FIPS modules to their Historical validations list as seen below:<\/p>\n

“per the transition schedule published in SP 800-131Arev1, symmetric key-based key wrapping that is not compliant to SP 800-38F is no longer allowed. Accordingly, modules on the Active List were moved to the Historical List if they employed the previously non-compliant but allowed key wrapping. This is the same procedure that was followed for the non-SP-800-90A RNG transition.”<\/i><\/p>\n

What does it mean to be added to the Historical List?<\/b><\/p>\n

When your listing is moved, the CMVP states that the cryptographic module should not be included by Federal Agencies in new procurements. They go on to say that Agencies may make a risk determination on whether to continue using this module based on their own assessment of where and how it is used, but they cannot provide accurate and up-to-date guidance on how to securely use these modules. It is up to the vendor to update the Security Policy so that the users can continue to operate modules in a secure manner.<\/p>\n

What Does This Mean For My Listing?<\/strong><\/p>\n

First, check to see if your listing was one of the modules added to the Historical list here<\/a>.<\/p>\n