| Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to,
VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information
Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users
should check with their supervisor, Information System Security Officer (ISSO), Facility Chief Information Officer (CIO), or local Office of Information and Technology
(OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation. |
| The VA Decision Matrix displays the current and future VAIT
position regarding different releases of a TRM entry. These decisions are
based upon the best information available as of the most current date. The consumer of this information has the
responsibility to consult the organizations responsible for the desktop, testing, and/or production environments
to ensure that the target version of the technology will be supported.
|
|
|
| Legend: |
| White |
Authorized: The technology/standard has been authorized for use.
|
| Yellow |
Authorized w/ Constraints: The technology/standard can be used within the specified constraints located
below the decision matrix in the footnote[1] and on the General tab.
|
| Gray |
Authorized w/ Constraints (POA&M): This technology or standard can be used only if a POA&M review is conducted and signed by
the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee
and based upon a recommendation from the POA&M Compliance Enforcement,
has been granted to the project team or organization that wishes to use the technology.
|
| Orange |
Authorized w/ Constraints (DIVEST): VA has decided to divest itself on the use of the technology/standard.
As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of
the technology/standard. Additional information on when the entry is projected to become unauthorized may be
found on the Decision tab for the specific entry.
|
| Black |
Unauthorized: The technology/standard is not (currently) permitted to be used under any circumstances.
|
| Blue |
Authorized w/ Constraints (PLANNING/EVALUATION): The period of time this technology is currently being evaluated, reviewed,
and tested in controlled environments. Use of this technology is strictly controlled and not available
for use within the general population. If a customer would like to use this technology, please work with
your local or Regional OI&T office and contact the appropriate evaluation office
displayed in the notes below the decision matrix. The Local or Regional OI&T
office should submit an
inquiry to the TRM
if they require further assistance or if the evaluating office is not listed in the notes below.
|
|
| Release/Version Information: |
|
VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.
|
|
For example, a technology authorized with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision
would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.
|
|
VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than
what is specified but is not to exceed or affect previous decimal places.
|
|
For example, a technology authorized with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401
is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.
|
| Any major.minor version that is not listed in the VA Decision Matrix is considered Authorized w/ Constraints (POA&M). |
|
<Past |
Future> |
| 2024.0.x |
Unapproved |
DIVEST
[1, 2, 3, 4, 5] |
DIVEST
[1, 2, 3, 4, 5] |
Authorized w/ Constraints (DIVEST)
[1, 2, 3, 4, 5] |
Authorized w/ Constraints (DIVEST)
[1, 2, 3, 4, 5] |
Authorized w/ Constraints (DIVEST)
[2, 3, 4, 5, 6] |
Authorized w/ Constraints (DIVEST)
[2, 3, 4, 5, 6] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
| 2024.1.x |
Unapproved |
Approved w/Constraints
[1, 2, 3, 4, 5] |
Approved w/Constraints
[1, 2, 3, 4, 5] |
Authorized w/ Constraints
[1, 2, 3, 4, 5] |
Authorized w/ Constraints
[1, 2, 3, 4, 5] |
Authorized w/ Constraints (DIVEST)
[2, 3, 4, 5, 6] |
Authorized w/ Constraints (DIVEST)
[2, 3, 4, 5, 6] |
Authorized w/ Constraints (DIVEST)
[2, 3, 4, 5, 6] |
Authorized w/ Constraints (DIVEST)
[2, 3, 4, 5, 6] |
Authorized w/ Constraints (DIVEST)
[2, 3, 4, 5, 6] |
Authorized w/ Constraints (DIVEST)
[2, 3, 4, 5, 6] |
Authorized w/ Constraints (POA&M) |
| 2025.x |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints
[2, 3, 4, 5, 6] |
Authorized w/ Constraints
[2, 3, 4, 5, 6] |
Authorized w/ Constraints
[2, 3, 4, 5, 6] |
Authorized w/ Constraints
[2, 3, 4, 5, 6] |
Authorized w/ Constraints
[2, 3, 4, 5, 6] |
Authorized w/ Constraints
[2, 3, 4, 5, 6] |
Authorized w/ Constraints
[2, 3, 4, 5, 6] |
| Note: |
At the time of writing, version 2025.3.0 is the most current version, released 06/16/2025. |
| | | | [1] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Firefox, Google Chrome, and Microsoft Edge are implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Security Assessment Review, users must abide by the following constraints: - A vulnerability exists because Audiate checks for updates when the application is launched. Engineers could not find a way in the Graphical User Interface (GUI) to disable automatic updates. System Owners/Administrators should find alternative methods to manage updates. To mitigate, it is recommended that a baseline of communications be established, then all traffic relating to the application be monitored for any deviations from the baseline. This will assist with identifying possible malicious activity.
- A vulnerability exists because Audiate utilizes commercial cloud computing services. To mitigate, the ISSO shall educate and prohibit users from using the integrated cloud service capability until the VA Cloud Security Requirements have been met and the affected A&A package has been appropriately updated
- Audiate is not FIPS 140-2 or its successor certified. Audiate will require a 3rd party FIPS 140-2 or its successor certified solution for any data containing PHI/PII or VA sensitive information
- A vulnerability exists because Audiate includes a software improvement program. System Owners/Administrators must disable the Software Improvement Program from the GUI of the application.
- A vulnerability exists because Audiate installs privilege escalation software. To mitigate, System Owners/Administrators should be aware of that privilege escalation using elevate.exe is not permitted with the VA. Only authorized VA privileged escalation techniques should be used.
- A vulnerability exists because Audiate installs .dll packages that are open source. System Owners/Administrators should be aware of .dll versioning within the Audiate of open-source components and collaborate with the vendor to mitigate any vulnerabilities that may arise.
- A vulnerability exists because Audiate installs.exe files that are not digitally signed. This prevents verification of the publisher and file integrity. System Owners/Administrators should monitor the .exe files used by the application with a file integrity checker to ensure no unauthorized changes occur.
| | | [2] | 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. | | | [3] | 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. | | | [4] | 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 authorized and the user should take the proper steps to decline those installations. | | | [5] | 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. | | | [6] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Firefox, Google Chrome, and Microsoft Edge are implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Security Assessment Review, users must abide by the following constraints:
- A vulnerability exists because Audiate checks for updates when the application is launched. Engineers could not find a way in the Graphical User Interface (GUI) to disable automatic updates. System Owners/Administrators should find alternative methods to manage updates. To mitigate, it is recommended that a baseline of communications be established, then all traffic relating to the application be monitored for any deviations from the baseline. This will assist with identifying possible malicious activity.
- A vulnerability exists because Audiate utilizes commercial cloud computing services. To mitigate, the ISSO shall educate and prohibit users from using the integrated cloud service capability until the VA Cloud Security Requirements have been met and the affected A&A package has been appropriately updated
- Audiate is not FIPS 140-2 or its successor certified. Audiate will require a 3rd party FIPS 140-2 or its successor certified solution for any data containing PHI/PII or VA sensitive information
- A vulnerability exists because Audiate includes a software improvement program. System Owners/Administrators must disable the Software Improvement Program from the GUI of the application.
- A vulnerability exists because Audiate installs privilege escalation software. To mitigate, System Owners/Administrators should be aware of that privilege escalation using elevate.exe is not permitted with the VA. Only authorized VA privileged escalation techniques should be used.
- A vulnerability exists because Audiate installs .dll packages that are open source. System Owners/Administrators should be aware of .dll versioning within the Audiate of open-source components and collaborate with the vendor to mitigate any vulnerabilities that may arise.
- A vulnerability exists because Audiate installs.exe files that are not digitally signed. This prevents verification of the publisher and file integrity. System Owners/Administrators should monitor the .exe files used by the application with a file integrity checker to ensure no unauthorized changes occur.
|
|
