| 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.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
| 5.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
| 6.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
| 7.x |
DIVEST
[18, 20, 21, 22] |
DIVEST
[18, 20, 21, 22] |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
| 8.x |
Approved w/Constraints
[18, 20, 21, 22] |
Approved w/Constraints
[18, 20, 21, 22] |
Approved w/Constraints
[18, 20, 21, 22] |
Approved w/Constraints
[18, 20, 21, 22] |
Approved w/Constraints
[18, 20, 22, 23] |
Authorized w/ Constraints
[18, 20, 22, 23] |
Approved w/Constraints
[18, 20, 22, 23] |
Approved w/Constraints
[18, 20, 22, 23] |
Authorized w/ Constraints
[18, 20, 22, 23] |
Authorized w/ Constraints
[18, 20, 22, 23] |
Authorized w/ Constraints
[18, 20, 22, 23] |
Authorized w/ Constraints
[18, 20, 22, 23] |
| 9.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints
[18, 20, 22, 23] |
Authorized w/ Constraints
[18, 20, 22, 23] |
Approved w/Constraints
[18, 20, 22, 23] |
Approved w/Constraints
[18, 20, 22, 23] |
Authorized w/ Constraints
[18, 20, 22, 23] |
Authorized w/ Constraints
[18, 20, 22, 23] |
Authorized w/ Constraints
[18, 20, 22, 23] |
Authorized w/ Constraints
[18, 20, 22, 23] |
| | | | [1] | 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. | | | [2] | Due to multiple NIST security vulnerabilities and NSOC bulletins, extra vigilance should be applied to ensure supported versions of the product remain properly patched to mitigate known and future vulnerabilities. | | | [3] | Use of this operating system in the production environment must conform to the published baseline (see reference tab) for installation, configuration and security. Due to multiple NIST security vulnerabilities and NSOC bulletins, extra vigilance should be applied to ensure supported versions of the product remain properly patched to mitigate known and future vulnerabilities. | | | [4] | 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.
| | | [5] | Use of this operating system in the production environment must conform to the published baseline (see reference tab) for installation, configuration and security. Due to multiple NIST security vulnerabilities and NSOC bulletins, extra vigilance should be applied to ensure supported versions of the product remain properly patched to mitigate known and future vulnerabilities.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | | [6] | 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. | | | [7] | 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. | | | [8] | Due to multiple NIST security vulnerabilities and NSOC bulletins, extra vigilance should be applied to ensure supported versions of the product remain properly patched to mitigate known and future vulnerabilities.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | | [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] | Due to multiple NIST security vulnerabilities and NSOC bulletins, extra vigilance should be applied to ensure supported versions of the product remain properly patched to mitigate known and future vulnerabilities.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | | [11] | Configuration Baselines standards for Red Hat Linux are published and maintained by VA on the BCM website and must be implemented and followed for each instance of Red Hat Linux. See the reference section of this entry for more information. As of this writing, Red Hat Enterprise Linux 7, is the current published VA baseline.
Due to multiple NIST security vulnerabilities and NSOC bulletins, extra vigilance should be applied to ensure supported versions of the product remain properly patched to mitigate known and future vulnerabilities.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | | [12] | Configuration Baselines standards for Red Hat Linux are published and maintained by VA on the BCM website and must be implemented and followed for each instance of Red Hat Linux. See the reference section of this entry for more information. As of this writing, Red Hat Enterprise Linux 7, is the current published VA baseline.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | | [13] | 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 ISO can provide assistance in reviewing the NIST vulnerabilities. | | | [14] | Configuration Baselines standards for Red Hat Linux are published and maintained by VA on the BCM website and must be implemented and followed for each instance of Red Hat Linux. See the reference section of this entry for more information. As of this writing, Red Hat Enterprise Linux 7, is the current published VA baseline. | | | [15] | Configuration Baselines standards for Red Hat Linux are published and maintained by VA on the BCM website and must be implemented and followed for each instance of Red Hat Enterprise Linux. There are baselines for On-Premise, Azure, and AWS implementations. See the reference section of this entry for more information on baselines. As of this writing, Red Hat Enterprise Linux 7, is the current published VA baseline standard for all platforms. | | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | | [17] | Configuration Baselines standards for Red Hat Linux are published and maintained by VA on the BCM website and must be implemented and followed for each instance of Red Hat Enterprise Linux. There are baselines for On-Premise, Azure, and AWS implementations. See the reference section of this entry for more information on baselines. As of this writing, Red Hat Enterprise Linux 8, is the current published VA baseline standard for all platforms. | | | [18] | This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product. | | | [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] | 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. | | | [21] | Configuration Baselines standards for Red Hat Linux are published and maintained by VA on the BCM website and must be implemented and followed for each instance of Red Hat Enterprise Linux. There are baselines for On-Premise, Azure, and AWS implementations. See the reference section of this entry for more information on baselines. As of this writing, Red Hat Enterprise Linux 8, is the current published VA baseline standard for all platforms.
Users must not utilize Red Hat Enterprise Virtualization (Servers), as it is at the time of writing, unapproved in the TRM. | | | [22] | 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. | | | [23] | Configuration Baselines standards for Red Hat Linux are published and maintained by VA on the Baseline Configuration Management (BCM) website and must be implemented and followed for each instance of Red Hat Enterprise Linux. There are baselines for On-Premise, Azure, and Amazon Web Services (AWS) implementations. See the reference section of this entry for more information on baselines. As of this writing, Red Hat Enterprise Linux 9, is the current published VA baseline standard for all platforms.
Users must not utilize Red Hat Enterprise Virtualization (Servers), as it is at the time of writing, unapproved in the TRM. |
|
| Note: |
At the time of writing, version 9.5 is the most current version, released 11/13/2024.
A baseline configuration of this technology was developed by the BCM team. At the time of writing, the baseline version is 9.x. |
