| 2024.x |
Approved w/Constraints
[17, 18, 20, 21, 22, 23] |
Approved w/Constraints
[17, 18, 20, 21, 22, 23] |
Approved w/Constraints
[17, 18, 20, 21, 22, 23] |
Approved w/Constraints
[17, 18, 20, 21, 22, 23] |
Approved w/Constraints
[17, 18, 20, 21, 22, 23] |
Approved w/Constraints
[17, 18, 20, 21, 22, 23] |
Approved w/Constraints
[17, 18, 20, 21, 22, 23] |
Approved w/Constraints
[17, 18, 20, 21, 22, 23] |
Approved w/Constraints
[17, 18, 20, 21, 22, 23] |
Approved w/Constraints
[17, 18, 20, 21, 22, 23] |
Approved w/Constraints
[17, 18, 20, 21, 22, 23] |
Approved w/Constraints
[17, 18, 20, 21, 22, 23] |
| | | | [1] | Known security vulnerabilities must be properly remediated prior to product deployment. Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines.
Note: Versions 10 and 11 before 11.1 are prohibited due to a NIST high severity security vulnerability. | | | [2] | Known security vulnerabilities must be properly remediated prior to product deployment. Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. | | | [3] | Users are restricted from using File Transfer Protocol (FTP) as a means to share captured images and videos as it is an unsupported standard. Additionally, if free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | | [4] | 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. | | | [5] | 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. | | | [6] | 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. | | | [7] | This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards and an ISO Risk Based Decision (RBD) must be approved by the local ISO/CIO before it can be used in the VA Production Environment. In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004, VA Directive 6517
and VA Directive 6513. The local ISO can advise on the ESCCB review process and ensure privacy of information compliance protections are in place. | | | [8] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process. | | | [9] | 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. | | | [10] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process. | | | [11] | This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004, VA Directive 6517
and VA Directive 6513. The local ISO can advise on the ESCCB review process and ensure privacy of information compliance protections are in place. | | | [12] | Microsoft .Net Framework on Windows Client version combinations, baseline configuration and deployment standards which are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering (ESE) must be followed and adhered to. The current build for this baseline is version 4.7.03062.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | | [13] | Users must ensure that Microsoft.NET Framework is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | | [14] | Users must ensure that Microsoft .NET Framework is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | | [15] | 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. | | | [16] | Users must ensure that Microsoft .NET Framework is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
The File Transfer Protocol (FTP) features of this software must not be used as the FTP protocol is prohibited for use on the VA network. (For further information see: VA Policy Memo VAIQ 7615193 on Prohibited Use of File Transfer Protocol (FTP) and Telnet Services) | | | [17] | 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. | | | [18] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
The File Transfer Protocol (FTP) features of this software must not be used as the FTP protocol is prohibited for use on the VA network. (For further information see: VA Policy Memo VAIQ 7615193 on Prohibited Use of File Transfer Protocol (FTP) and Telnet Services) | | | [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 VA Handbook 6500. | | | [20] | 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. | | | [21] | 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. | | | [22] | 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. | | | [23] | 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. |
|
