| 7.0x |
Approved w/Constraints
[15, 17, 18, 19, 20, 21] |
Approved w/Constraints
[15, 17, 18, 19, 20, 21] |
Approved w/Constraints
[15, 17, 18, 19, 20, 21] |
Approved w/Constraints
[15, 17, 18, 19, 20, 21] |
Approved w/Constraints
[15, 17, 18, 19, 20, 21] |
Approved w/Constraints
[15, 17, 18, 19, 20, 21] |
Approved w/Constraints
[15, 17, 18, 19, 20, 21] |
Approved w/Constraints
[15, 17, 18, 19, 20, 21] |
Approved w/Constraints
[15, 17, 18, 19, 20, 21] |
Approved w/Constraints
[15, 17, 18, 19, 20, 21] |
Approved w/Constraints
[15, 17, 18, 19, 20, 21] |
Approved w/Constraints
[15, 17, 18, 19, 20, 21] |
| | | | [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. | | | [9] | 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. | | | [10] | 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. | | | [11] | 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. | | | [12] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology has a published path traversal zero-day vulnerability that was corrected in version 5.70. Versions prior to version 5.70 are prohibited from use across the enterprise. | | | [13] | 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. | | | [14] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology has a published path traversal zero-day vulnerability that was corrected in version 5.70. Versions prior to version 5.70 are prohibited from use across the enterprise. | | | [15] | This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product. | | | [16] | 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 ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500. | | | [17] | Users should check with their supervisor, Information System Security Officer (ISSO) 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. | | | [18] | 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 ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities. | | | [19] | 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 ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500. | | | [20] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology has a published path traversal zero-day vulnerability that was corrected in version 5.70. Versions prior to version 5.70 are prohibited from use across the enterprise.
Users must not utilize ZIP, as it is at the time of writing, unapproved in the TRM. | | | [21] | The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website. |
|
