<Past |
Future> |
4.3x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 4, 5] |
Divest [3, 4, 5] |
Divest [3, 4, 5] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.0x |
Approved w/Constraints [1] |
Approved w/Constraints [2] |
Approved w/Constraints [2] |
Approved w/Constraints [2] |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 4, 5] |
Divest [3, 4, 5] |
Divest [5, 6, 7, 8] |
Divest [5, 6, 7, 8] |
Divest [5, 6, 7, 8] |
Unapproved |
5.1x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [5, 6, 7, 8] |
Approved w/Constraints [5, 6, 7, 8] |
Approved w/Constraints [5, 6, 7, 8] |
Divest [5, 6, 7, 8] |
5.2x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [5, 6, 7, 8] |
Approved w/Constraints [5, 6, 7, 8] |
Approved w/Constraints [5, 6, 7, 8] |
Approved w/Constraints [5, 6, 7, 8] |
5.3x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [5, 6, 7, 8] |
Approved w/Constraints [5, 6, 7, 8] |
Approved w/Constraints [5, 6, 7, 8] |
Approved w/Constraints [5, 6, 7, 8] |
5.4x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.5x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.6x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.7x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.9x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
6.0x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
6.1x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
6.2x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
7.0x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [1] | The encryption technology that is contained in this product is not FIPS 140-2 certified and therefore cannot be used to secure PII/PHI/VA Sensitive data at rest or in transit. Per VA Handbook 6500, FIPS 140-2 certified encryption must be used to encrypt data at rest or in transit if PII/PHI/VA sensitive information is involved or additional mitigating controls must be documented in an approved System Security Plan (SSP). | | [2] | The encryption technology that is contained in this product is NOT Federal Information Processing Standards (FIPS) 140-2 certified and therefore cannot be used to secure Personally Identifiable Information (PII), Protected Health Information (PHI) or VA sensitive information at rest or in transit.
Per VA Handbook 6500, Federal Information Processing Standards (FIPS) 140-2 certified encryption must be used to encrypt data in transit and at rest if Personally Identifiable Information (PII), Protected Health Information (PHI) or VA sensitive information is involved or additional mitigating controls must be documented in an approved System Security Plan (SSP). Additionally the technology must be implemented within the VA production network (not in a Demilitarized Zone (DMZ)).
Known security vulnerabilities must be properly remediated prior to product deployment. Product must remain properly patched per Federal and Department standards in order to mitigate known and future security vulnerabilities. | | [3] | The encryption technology that is contained in this product is NOT Federal Information Processing Standards (FIPS) 140-2 certified and therefore, cannot be used to secure Personally Identifiable Information (PII), Protected Health Information (PHI) or VA sensitive information at rest or in transit.
Per VA Handbook 6500, Federal Information Processing Standards (FIPS) 140-2 certified encryption must be used to encrypt data in transit and at rest if Personally Identifiable Information (PII), Protected Health Information (PHI) or VA sensitive information is involved or additional mitigating controls must be documented in an approved System Security Plan (SSP). Additionally the technology must be implemented within the VA production network (not in a Demilitarized Zone (DMZ)).
Known security vulnerabilities must be properly remediated prior to product deployment. Product must remain properly patched per Federal and Department standards in order to mitigate known and future security vulnerabilities. | | [4] | Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities. | | [5] | Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [6] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
The encryption technology that is contained in this product is NOT Federal Information Processing Standards (FIPS) 140-2 certified and therefore cannot be used to secure Personally Identifiable Information (PII), Protected Health Information (PHI) or VA sensitive information at rest or in transit. | | [7] | Users should check with their supervisor, Information Security Office (ISO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations. | | [8] | Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities. |
|
Note: |
At the time of writing, version 7.01 is the most current version, released 05/15/2024. |