| 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> |
| 4.7 |
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) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
| 4.73 |
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) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
| 4.74 |
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) |
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
[12, 16, 17, 18, 19, 20] |
Authorized w/ Constraints
[12, 16, 17, 18, 19, 20] |
Authorized w/ Constraints
[12, 16, 17, 18, 19, 20] |
Authorized w/ Constraints
[12, 16, 17, 18, 19, 20] |
Authorized w/ Constraints
[12, 16, 17, 18, 19, 20] |
Authorized w/ Constraints
[12, 16, 17, 18, 19, 20] |
Authorized w/ Constraints
[12, 16, 17, 18, 19, 20] |
Authorized w/ Constraints
[12, 16, 17, 18, 19, 20] |
Authorized w/ Constraints
[12, 16, 17, 18, 19, 20] |
Authorized w/ Constraints
[12, 16, 17, 18, 19, 20] |
Authorized w/ Constraints
[12, 16, 17, 18, 19, 20] |
Authorized w/ Constraints
[12, 16, 17, 18, 19, 20] |
| | | | [1] | Veterans Affairs (VA) users must ensure VA sensitive data is protected properly in accordance with VA Handbook 6500 and the Federal Information Security Management Act (FISMA). Per VA Handbook 6500, FIPS 140-2 certified encryption must be used to protect and encrypt data in transit and at rest if Personally Identifiable Information/Protected Health Information/VA (PII/PHI/VA) sensitive information is involved. If FIPS 140-2 certified encryption in not used, additional mitigating controls must be documented in an authorized System Security Plan (SSP). In addition, the technology must be implemented within the VA production network (not in a Demilitarized Zone (DMZ)) unless the specific uses and instances of the technology are authorized by the Enterprise Security Change Control Board (ESCCB). All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Hand Book 6500. In cases where the technology is used for external connections, a full ESCCB review is required in accordance VA Directive 6004, VA Directive 6517 and VA Directive 6513. | | | [2] | As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an assessment by the VA Section 508 office. Section 508 of the Rehabilitation Act Amendments of 1998 is a federal law that sets the guidelines for technology accessibility. A VA Section 508 assessment of this technology has not been completed at the time of publication. Therefore, as of April 23, 2015 only users of this technology who have deployed the technology to the production environment, or have project design and implementation plans authorized, may continue to operate this technology. In the case of a project that has implemented, or been authorized for a specific site or number of users, and that project needs to expand operations to other sites or to an increased user base, it may do so as long as the project stays on the existing version of the technology that was authorized or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.
| | | [3] | This product is Class 2 or Class 3 VA-designed and built Local Software OR is a commercially-licensed software product purchased or leased that will run in a VA VISTA environment or integrate with Class 1 National VISTA Software. Presence of this software on the One-VA TRM does not equate to designation as a Class 1 National Software product and MUST NOT be assumed to comply with all VA programming standards, namespacing and interface control agreement standards, data management standards, documentation standards, information assurance standards, security standards and 508 compliance standards. As a Class 2 or Class 3 product, it MUST NOT be assumed to having been released into production through all OI&T product release and sustainment process controls for project management; requirements, development and testing management; and configuration, change, and release management necessary to satisfy OI&T process and product compliance. The OI&T Enterprise Program Management Office does not endorse nor support Class 2 and Class 3 products and does not support data usage or application programmer interfaces (APIs) between Class 1 National Software products and Class 2 or Class 3 products. Class 2 or Class 3 products must restrict their interfaces to Class 1 National Software to use of publicly-supported APIs ONLY. VA Directive 6402, Modifications to Standardized National Software, dictates the policy for Class 2 and Class 3 products and modifications to Class 1 National Software products. Local enhancements to, or modifications of, Class 1 Protected National Software (as listed in the Directive), in part or in whole, is PROHIBITED. Local enhancements to, or modifications of, Non-Protected Class 1 National Software is allowed ONLY with an authorized waiver by the Software Modification Waiver Committee (SMWC). Class 2 and Class 3 software that does not modify the Class 1 National Software in any way must still adhere to namespacing and interface control agreement standards as well as National Field Operations Processes. | | | [4] | 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. | | | [5] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | | [6] | 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. | | | [7] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | | [8] | Users must ensure that Microsoft Internet Explorer (IE) and Microsoft Structured Query Language (SQL) Server are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | | [9] | 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. | | | [10] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | | [11] | Users must ensure that Microsoft Internet Explorer (IE),Google Chrome and Microsoft Structured Query Language (SQL) Server are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must not use Microsoft Internet Explorer which is in divest at this time. Other browsers are available (see `Category` tab) | | | [12] | 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. | | | [13] | Users must ensure that Acrobat Adobe, Google Chrome and Microsoft Structured Query Language (SQL) Server are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must Divest the use of Internet Explorer with this technology. Other authorized internet browsers are available. See Category Tab for details. | | | [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 ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500. | | | [15] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | | [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. | | | [17] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 or its successor to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes. | | | [18] | This product is Class 2 or Class 3 VA-designed and built Local Software OR is a commercially-licensed software product purchased or leased that will run in a VA VISTA environment or integrate with Class 1 National VISTA Software. Presence of this software on the One-VA TRM does not equate to designation as a Class 1 National Software product and MUST NOT be assumed to comply with all VA programming standards, namespacing and interface control agreement standards, data management standards, documentation standards, information assurance standards, security standards and 508 compliance standards. As a Class 2 or Class 3 product, it MUST NOT be assumed to having been released into production through all OI&T product release and sustainment process controls for project management; requirements, development and testing management; and configuration, change, and release management necessary to satisfy OI&T process and product compliance. The OI&T Enterprise Program Management Office does not endorse nor support Class 2 and Class 3 products and does not support data usage or application programmer interfaces (APIs) between Class 1 National Software products and Class 2 or Class 3 products. Class 2 or Class 3 products must restrict their interfaces to Class 1 National Software to use of publicly-supported APIs ONLY. VA Directive 6402, Modifications to Standardized National Software, dictates the policy for Class 2 and Class 3 products and modifications to Class 1 National Software products. Local enhancements to, or modifications of, Class 1 Protected National Software (as listed in the Directive), in part or in whole, is PROHIBITED. Local enhancements to, or modifications of, Non-Protected Class 1 National Software is allowed ONLY with an authorized waiver by the Software Modification Waiver Committee (SMWC). Class 2 and Class 3 software that does not modify the Class 1 National Software in any way must still adhere to namespacing and interface control agreement standards as well as National Field Operations Processes. | | | [19] | Users must ensure that Microsoft Edge, Google Chrome, and Microsoft Structured Query Language (SQL) Server are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | | [20] | 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. |
|
| Note: |
At the time of writing, version 5.0.3.0 is the most current version, released 01/23/2024. |
