<Past |
Future> |
10.0 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
11.0 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
12.0 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
15.0 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
16.0 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
17.0 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
18.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2018.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2019.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2020.x |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
2021.x |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
2022.x |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
2023.x |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
2024.x |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
Approved w/Constraints [2, 12, 14, 15, 16] |
| | [1] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [2] | 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. | | [3] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Standard secure measures must be taken when using screen readers to process sensitive data in order to prevent unauthorized users from obtaining information that contains Protected Health Information (PHI)/Personally Identifiable Information (PII).
Job Access with Speech should only be used to store, process, or transmit VA sensitive information when the underlying infrastructure can provide Federal Information Processing Standards (FIPS) 140-2 encryption.
If it is necessary to disable protective technology in order to facilitate 508 compliance, it is recommended that this is limited to those applications and users that require the access. Access Control Lists, White Lists and Group Policy are all acceptable solutions to limit the impact across the Enterprise. | | [4] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology 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.
Per the Initial Product Review, users must abide by the following constraints:
- Standard secure measures must be taken when using screen readers to process sensitive data in order to prevent unauthorized users from obtaining information that contains Protected Health Information (PHI)/Personally Identifiable Information (PII).
- Job Access with Speech should only be used to store, process, or transmit VA sensitive information when the underlying infrastructure can provide Federal Information Processing Standards (FIPS) 140-2 encryption.
- If it is necessary to disable protective technology in order to facilitate 508 compliance, it is recommended that this is limited to those applications and users that require the access. Access Control Lists, White Lists and Group Policy are all acceptable solutions to limit the impact across the Enterprise.
| | [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] | 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. | | [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] | 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] | This product includes a Bluetooth capability. If that capability is leveraged, the implementer must conform to the Bluetooth Standard. 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] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology 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.
It is advised that if this product is used within the Department of Veterans Affairs (VA) that the following constraints be applied:
- Standard secure measures should be taken when using screen readers to process sensitive data in order to prevent unauthorized users from obtaining information that contains PII/PHI.
- Job Access with Speech should only be used to store, process, or transmit VA sensitive information when the underlying infrastructure can provide FIPS 140-2 certified encryption.
- If it is necessary to disable protective technology in order to facilitate 508 compliance, it is recommended that this is limited to those applications and users that require the access. Access Control Lists, White Lists and Group sPolicy are all acceptable solutions to limit the impact across the Enterprise.
| | [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] | 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. | | [14] | This product includes a Bluetooth capability. If that capability is leveraged, the implementer must conform to the Bluetooth Standard. 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. | | [15] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology 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.
Per the Initial Product Review, users must abide by the following constraints:
- Standard secure measures should be taken when using screen readers to process sensitive data in order to prevent unauthorized users from obtaining information that contains PII/PHI.
- Job Access with Speech should only be used to store, process, or transmit VA sensitive information when the underlying infrastructure can provide FIPS 140-2 certified encryption.
- If it is necessary to disable protective technology in order to facilitate 508 compliance, it is recommended that this is limited to those applications and users that require the access. Access Control Lists, White Lists and Groups Policy are all acceptable solutions to limit the impact across the Enterprise.
| | [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 both VA Handbook 6500 and VA Directive 6500. |
|
Note: |
At the time of writing, version 2024.2310.70 is the most current version, released 10/26/2023. |