5.0 |
Approved w/Constraints [6, 10, 11, 12] |
Approved w/Constraints [6, 10, 11, 12] |
Approved w/Constraints [6, 10, 11, 12] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [12, 13, 14, 15, 16] |
Approved w/Constraints [12, 13, 14, 15, 16] |
Approved w/Constraints [12, 13, 14, 15, 16] |
Approved w/Constraints [12, 13, 14, 15, 16] |
Approved w/Constraints [12, 13, 14, 15, 16] |
Approved w/Constraints [12, 13, 14, 15, 16] |
Approved w/Constraints [12, 13, 14, 15, 16] |
Approved w/Constraints [12, 13, 14, 15, 16] |
| | [1] | This product attaches itself to the Windows operating system keyboard driver. This technology may disrupt other technologies. If a conflict occurs this technology should be uninstalled. | | [2] | This product attaches itself to the Windows operating system keyboard driver. This technology may disrupt other technologies. If a conflict occurs this technology should be uninstalled.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [3] | This product attaches itself to the Windows operating system keyboard driver. This technology may disrupt other technologies. If a conflict occurs this technology must be uninstalled.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [4] | This product attaches itself to the Windows operating system keyboard driver. This technology may disrupt other technologies. If a conflict occurs this technology must be uninstalled.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [5] | This product attaches itself to the Windows operating system keyboard driver. This technology may disrupt other technologies. If a conflict occurs this technology must be uninstalled.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [6] | This product attaches itself to the Windows operating system keyboard driver. This technology may disrupt other technologies. If a conflict occurs this technology must be uninstalled.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology can integrate with third party cloud storage services such as Dropbox, Google Drive, etc. The use of these services are prohibited by the VA, and must not be used.
Users must Divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details.
Users must ensure that Google Chrome and Microsoft Internet Explorer (IE) are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [7] | 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. | | [8] | 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. | | [9] | Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (PSF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [10] | Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the VA OIT Product Engineering team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [11] | 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. | | [12] | 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. | | [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 ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500. | | [14] | This product attaches itself to the Windows operating system keyboard driver. This technology may disrupt other technologies. If a conflict occurs this technology must be uninstalled.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology can integrate with third party cloud storage services such as Dropbox, Google Drive, etc. The use of these services are prohibited by the VA, and must not be used.
Microsoft Internet Explorer, a dependency of this technology, is in End of Life status and must no longer be used.
Users must ensure that Google Chrome is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
This technology potentially requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data. | | [15] | Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request, visit the Product Marketplace.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [16] | 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. |
|