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 Security Officer (ISO), 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> |
3.x |
Authorized w/ Constraints (POA&M) |
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) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
4.x |
Authorized w/ Constraints (POA&M) |
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) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
5.x |
Authorized w/ Constraints [13, 20, 21, 22, 23, 24, 25] |
Approved w/Constraints [13, 20, 21, 22, 23, 24, 25] |
Approved w/Constraints [13, 20, 21, 22, 23, 24, 25] |
Approved w/Constraints [13, 20, 21, 22, 23, 24, 25] |
Authorized w/ Constraints [13, 20, 21, 22, 23, 24, 25] |
Authorized w/ Constraints [13, 20, 21, 22, 23, 24, 25] |
Authorized w/ Constraints [13, 20, 21, 22, 23, 24, 25] |
Authorized w/ Constraints [13, 20, 21, 22, 23, 24, 25] |
Authorized w/ Constraints [13, 20, 21, 22, 23, 24, 25] |
Authorized w/ Constraints [13, 20, 21, 22, 23, 24, 25] |
Authorized w/ Constraints [13, 20, 21, 22, 23, 24, 25] |
Authorized w/ Constraints [13, 20, 21, 22, 23, 24, 25] |
| | [1] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [2] | 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 authorized and the user should take the proper steps to decline those installations. | | [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] | Due to potential information security risks, cloud based technologies may not be used without an Enterprise Security Change Control Board (ESCCB) approval. This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [5] | Due to potential information security risks, cloud based technologies may not be used without the approval of the VA Enterprise Cloud Services (ECS) Group. This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [6] | Due to potential information security risks, cloud based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [7] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (contact VA e-mail: OIT ITOPS SD Engagement Requests) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | [8] | 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. | | [9] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Per the Initial Product Review, users must abide by the following constraints:
Users must ensure the use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications and devices.
Due to potential information security risks, software as a service (SaaS) must complete the veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO) and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production and sustainment provided by PSF.
If Hazelcast is considered for use within the VA, it is strongly advised that the VA invest in one of the Hazelcast Enterprise Editions to ensure assistance directly from a Hazelcast solutions architect, ensuring swift resolution of issues with minimal delay and that all available security features are provided in a timely manner.
The database administrator must refer to a VA Secure Configuration Baseline for guidance when implementing Hazelcast within the VA environment; only VA authorized databases are allowed. Further, users must abide by the following security measures which will help ensure that the data is secured and protected:
Leverage two-factor authentication (2FA) provided by the product or VA-authorized 2FA solution. Ensure connections between the web browser and web server are encrypted using SSL or TLS. Deploy a VA-authorized web application firewall (WAF) and database firewall to add layers of security to the database. Perform end-to-end security testing of Hazelcast and all its components to ensure security holes are addressed prior to implementation. Continuous vulnerability scanning, monitoring, and auditing of the database system and associated components. | | [10] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (contact VA e-mail: [OIT ITOPS SD Engagement Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | [11] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Per the Initial Product Review, users must abide by the following constraints:
Users must ensure the use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications and devices.
Due to potential information security risks, software as a service (SaaS) must complete the veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO) and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production and sustainment provided by PSF.
If Hazelcast is considered for use within the VA, it is strongly advised that the VA invest in one of the Hazelcast Enterprise Editions to ensure assistance directly from a Hazelcast solutions architect, ensuring swift resolution of issues with minimal delay and that all available security features are provided in a timely manner.
The database administrator must refer to a VA Secure Configuration Baseline for guidance when implementing Hazelcast within the VA environment; only VA authorized databases are allowed. Further, users must abide by the following security measures which will help ensure that the data is secured and protected:
Leverage two-factor authentication (2FA) provided by the product or VA-authorized 2FA solution. Ensure connections between the web browser and web server are encrypted using SSL or TLS. Deploy a VA-authorized web application firewall (WAF) and database firewall to add layers of security to the database. Perform end-to-end security testing of Hazelcast and all its components to ensure security holes are addressed prior to implementation. Continuous vulnerability scanning, monitoring, and auditing of the database system and associated components.
This technology must use the latest version of Java Development Kit (JDK) - Oracle. | | [12] | 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 (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [13] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (yourIT Service Portal:[SNOW Service Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | [14] | 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. | | [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 with the Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [16] | 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). | | [17] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology must use the latest version of Java Development Kit (JDK) - Oracle.
Users must ensure that Apache Tomcat is implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
Per the Initial Product Review, users must abide by the following constraints:
- Ensure the use of a FIPS 140-2 validated cryptographic module to secure VA
sensitive data in applications and devices.
- Due to potential information security risks, software as a service (SaaS) must
complete the Veterans-Focused Integration Process Request (VIPR) process
where a collaborative effort between Demand Management (DM), Enterprise
Program Management Office Information Assurance (EPMO IA), Project
Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief
Technology Officer (CTO) and stakeholders determines the SaaS/PaaS
category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC)
PaaS assets are routed to EPMO IA for Analysis and Approval to Operate
(ATO) with technical oversight, acquisition, production and sustainment
provided by PSF.
- If Hazelcast is considered for use within the VA, it is advised that the VA invest
in one of the Hazelcast Enterprise Editions to ensure assistance directly from
a Hazelcast solutions architect, ensuring swift resolution of issues with minimal
delay and that all available security features are provided in a timely manner.
- The database administrator must refer to a VA Secure Configuration Baseline
for guidance when implementing Hazelcast within the VA environment; only
VA authorized databases are allowed. Further, it is emphasized that the
IPR – Hazelcast In-Memory Data Grid (IMDG)
July 9, 2020 For Internal VA Use Only Page 5 of 9
following security measures will help ensure that the data is secured and
protected:
o Leverage two-factor authentication (2FA) provided by the product or VAapproved 2FA solution.
o Ensure connections between the web browser and web server are
encrypted using SSL or TLS.
o Deploy a VA-authorized web application firewall (WAF) and database
firewall to add layers of security to the database.
o Perform end-to-end security testing of Hazelcast and all its components
to ensure security holes are addressed prior to implementation.
o Continuous vulnerability scanning, monitoring, and auditing of the
database system and associated components. | | [18] | 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). | | [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 authorized and the user should take the proper steps to decline those installations. | | [21] | 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. | | [22] | 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). | | [23] | This technology must use the latest TRM-authorized version of Java Development Kit (JDK) - Oracle.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
Per the Initial Product Review (IPR), users must abide by the following constraints:
- Hazelcast IMDG will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information.
- Due to potential information security risks, SaaS/PaaS solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Digital Transformation Center (DTC), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS or Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by DTC.
- If Hazelcast is considered for use within the VA, it is advised that the VA invest in one of the Hazelcast Enterprise Editions to ensure assistance directly from a Hazelcast solutions architect, ensuring swift resolution of issues with minimal delay and that all available security features are provided in a timely manner.
- System owners must ensure they are using the most recent version of Hazelcast IMDG.
- The database administrator must refer to a VA Secure Configuration Baseline for guidance when implementing Hazelcast within the VA environment; only VA authorized databases are allowed. Further, it is emphasized that the following security measures will help ensure that the data is secured and protected:
- Leverage two-factor authentication (2FA) provided by the product or VA authorized 2FA solution.
- Ensure connections between the web browser and web server are encrypted using SSL or TLS.
- Deploy a VA-authorized web application firewall (WAF) and database firewall to add layers of security to the database.
- Perform end-to-end security testing of Hazelcast and all its components to ensure security holes are addressed prior to implementation.
- Continuous vulnerability scanning, monitoring, and auditing of the database system and associated components.
| | [24] | 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. | | [25] | 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. |
|
Note: |
At the time of writing, version 5.4 was the latest version, released 04/17/2024. |