| 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> |
| 5.x |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints
[1, 2, 3, 4, 5, 6] |
Approved w/Constraints
[1, 2, 3, 5, 6, 7] |
Approved w/Constraints
[1, 2, 3, 5, 6, 7] |
Approved w/Constraints
[1, 2, 3, 5, 6, 7] |
Approved w/Constraints
[1, 2, 3, 5, 6, 7] |
Authorized w/ Constraints
[1, 2, 3, 5, 6, 7] |
Approved w/Constraints
[1, 2, 3, 5, 6, 7] |
Approved w/Constraints
[1, 2, 3, 5, 6, 7] |
Approved w/Constraints
[1, 2, 3, 5, 6, 7] |
| 6.x |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints
[1, 2, 3, 4, 5, 6] |
Approved w/Constraints
[1, 2, 3, 5, 6, 7] |
Approved w/Constraints
[1, 2, 3, 5, 6, 7] |
Approved w/Constraints
[1, 2, 3, 5, 6, 7] |
Approved w/Constraints
[1, 2, 3, 5, 6, 7] |
Authorized w/ Constraints
[1, 2, 3, 5, 6, 7] |
Approved w/Constraints
[1, 2, 3, 5, 6, 7] |
Approved w/Constraints
[1, 2, 3, 5, 6, 7] |
Approved w/Constraints
[1, 2, 3, 5, 6, 7] |
| | | | [1] | Users must ensure that PostgreSQL is implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the [Initial Product Review/Security Assessment Review], users must abide by the following constraints:
- Neocortex will require a 3rd party FIPS 140-2 (or its successor) certified solution
for any data containing PHI/PII or VA sensitive information.
- Users should check with their supervisor, 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.
- Due to potential information security risks, Software as a Service
(SaaS)/Platform as a Service (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.
- AI products add a new set of security challenges to the VA. Evaluations should
include a review of the most recent VA guidance on AI products. Data poisoning
would be the biggest concern identified at this time. This sophisticated security
challenge involves the deliberate manipulation of training datasets. The
manipulation of the data input can lead to altered AI models with systemic flaws
or biases at their core. Data poisoning compromises the accuracy and
dependability of AI-driven decisions, particularly in critical applications.
Addressing this threat requires stringent data validation and robust security
measures to ensure the integrity of AI systems.
| | | [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] | 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). | | | [5] | This product can be configured with a PostgreSQL Database, which currently has TRM constraints limiting its use to Red Hat Enterprise Linux (RHEL) only due to its many known security issues on other platforms. If PostgreSQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See PostgreSQL Database TRM entry for more details. | | | [6] | 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. | | | [7] | 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. |
|
| Note: |
At the time of writing, version 6.0 is the most current version, released 10/01/2023. |
