| 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 |
Unauthorized, Conditions Required[a]
: 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 |
Unauthorized, Conditions Required[b]
: 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 |
Unauthorized, Conditions Required[c]
: 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 Unauthorized, Conditions Required
[a]
. |
|
<Past |
Future> |
| 7.x |
Approved w/Constraints
[1, 2] |
Approved w/Constraints
[1, 2] |
Approved w/Constraints
[2, 3, 4] |
Authorized w/ Constraints (DIVEST)
[2, 3, 4] |
Authorized w/ Constraints (DIVEST)
[2, 3, 4] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
| 24.x |
Unapproved |
Unapproved |
Approved w/Constraints
[2, 3, 4] |
Authorized w/ Constraints
[2, 3, 4] |
Authorized w/ Constraints
[2, 3, 4] |
Authorized w/ Constraints
[2, 3, 4] |
Authorized w/ Constraints
[2, 3, 4] |
Authorized w/ Constraints
[4, 5, 6] |
Authorized w/ Constraints
[4, 5, 6] |
Authorized w/ Constraints
[4, 5, 6] |
Authorized w/ Constraints
[4, 5, 6] |
Authorized w/ Constraints
[4, 5, 6] |
| 25.x |
Unapproved |
Unapproved |
Unapproved |
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) |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
| Note: |
At the time of writing, version 25.3.0 is the most current version, released 10/01/2025.
A standard configuration of this technology was developed by the DDE team. At the time of writing, the standard version is 24.1.000.9, and version 24.3.003.19 is under testing and development for six weeks from 09/29/2025. |
| | | | [1] | Users must ensure that VMware vSphere and Cerner iAccess are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Initial Product Review, users must abide by the following constraints:
- Ensure that Imprivata OneSign Single Sign-on versions 7.5 and above are used, as prior versions use a FIPS 140-2 cryptographic module that is in historical status. NIST states that historical cryptographic modules should not be included by Federal Agencies in new procurements. Agencies may make a risk determination on whether to continue using this module based on their own assessment of where and how it is used.
- Imprivata OneSign should only be used as part of the AO authorized Cerner FISMA ATO boundaries to include: OEHRM iAccess Component Kiosk and OEHRM Tracking Board Kiosk.
- NIAP is responsible for overseeing and monitoring the security of commercial IT products used in National Security Systems. The Defense Health Agency requires NIAP approval of all Information Assurance products such as Imprivata OneSign. Per DHA point of contact, Imprivata is expected to submit the final package in February 2022 for NIAP certification. Once submitted, it is estimated that NAIP review and final certification takes approximately 6 months.
- Automatic re-authentication must not be used. VA Handbook 6500 states that applications must not be enabled to retain passwords for subsequent reuse, or be configured to bypass authentication mechanisms.
- Use strong passwords for all accounts, especially the accounts that are members of the SSO Administrators group, because these users have control over the entire SSO system. Use different service accounts for the SSO services running on different computers. Role-based access controls (RBAC) should be configured to ensure that least privilege and separation of duties are enforced.
- Use Transport Layer Security (TLS) and/or Internet Protocol security (IPsec) to protect the confidentiality and integrity of credentials in transit.
| | | [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] | Users must ensure that VMware vSphere is implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Initial Product Review, users must abide by the following constraints:
- NIST states that historical cryptographic modules should not be included by Federal Agencies in new procurements. Agencies may make a risk determination on whether to continue using this module based on their own assessment of where and how it is used.
- Imprivata Enterprise Access Management with SSO should only be used as part of the AO authorized Cerner FISMA ATO boundaries to include: OEHRM iAccess Component Kiosk and OEHRM Tracking Board Kiosk.
- Automatic re-authentication must not be used. VA Handbook 6500 states that applications must not be enabled to retain passwords for subsequent reuse or be configured to bypass authentication mechanisms.
- Use strong passwords for all accounts, especially the accounts that are members of the SSO Administrators group, because these users have control over the entire SSO system. Use different service accounts for the SSO services running on different computers. Role-based access controls (RBAC) should be configured to ensure that least privilege and separation of duties are enforced.
- Use Transport Layer Security (TLS) and/or Internet Protocol security (IPsec) to protect the confidentiality and integrity of credentials in transit.
| | | [4] | 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. | | | [5] | Users must ensure that VMware vSphere and Citrix Virtual Apps and Desktops (CVAD) are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Initial Product Review, users must abide by the following constraints:
- NIST states that historical cryptographic modules should not be included by Federal Agencies in new procurements. Agencies may make a risk determination on whether to continue using this module based on their own assessment of where and how it is used.
- Imprivata Enterprise Access Management with SSO should only be used as part of the AO authorized Cerner FISMA ATO boundaries to include: OEHRM iAccess Component Kiosk and OEHRM Tracking Board Kiosk.
- Automatic re-authentication must not be used. VA Handbook 6500 states that applications must not be enabled to retain passwords for subsequent reuse or be configured to bypass authentication mechanisms.
- Use strong passwords for all accounts, especially the accounts that are members of the SSO Administrators group, because these users have control over the entire SSO system. Use different service accounts for the SSO services running on different computers. Role-based access controls (RBAC) should be configured to ensure that least privilege and separation of duties are enforced.
- Use Transport Layer Security (TLS) and/or Internet Protocol security (IPsec) to protect the confidentiality and integrity of credentials in transit.
| | | [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 ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities. |
|
