| 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 |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
| 5.x |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
| 6.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| 7.x |
Approved w/Constraints (PLANNING/EVALUATION)
[1, 4, 5, 12, 14] |
Approved w/Constraints (PLANNING/EVALUATION)
[1, 4, 5, 12, 14] |
Approved w/Constraints (PLANNING/EVALUATION)
[1, 4, 5, 12, 15] |
Approved w/Constraints (PLANNING/EVALUATION)
[1, 4, 5, 15, 16] |
Approved w/Constraints (PLANNING/EVALUATION)
[1, 4, 5, 15, 16] |
Approved w/Constraints (PLANNING/EVALUATION)
[1, 4, 5, 16, 17] |
Approved w/Constraints (PLANNING/EVALUATION)
[1, 4, 5, 16, 17] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| 8.x |
Approved w/Constraints (PLANNING/EVALUATION)
[1, 4, 5, 12, 14] |
Approved w/Constraints (PLANNING/EVALUATION)
[1, 4, 5, 12, 14] |
Approved w/Constraints (PLANNING/EVALUATION)
[1, 4, 5, 12, 15] |
Approved w/Constraints (PLANNING/EVALUATION)
[1, 4, 5, 15, 16] |
Approved w/Constraints (PLANNING/EVALUATION)
[1, 4, 5, 15, 16] |
Approved w/Constraints (PLANNING/EVALUATION)
[1, 4, 5, 16, 17] |
Approved w/Constraints (PLANNING/EVALUATION)
[1, 4, 5, 16, 17] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | | | [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] | Product use is restricted to laboratory and development test systems only. Product may not be used for VistA site mirror test systems or other pre-production verification systems. Applications and strategies developed on systems running this product must be tested properly on enterprise level Red Hat platforms prior to production release. Product must remain properly patched in order to mitigate known and future security vulnerabilities. Organization security baseline configuration standards for Linux systems must be employed and properly maintained. Only versions 5.x and higher are permitted. | | | [3] | Product use is restricted to laboratory and development test systems only. Product may not be used for VistA site mirror test systems or other pre-production verification systems. Applications and strategies developed on systems running this product must be tested properly on enterprise level Red Hat platforms prior to production release. Product must remain properly patched in order to mitigate known and future security vulnerabilities. Organization security baseline configuration standards for Linux systems must be employed and properly maintained. | | | [4] | 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. | | | [5] | 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. | | | [6] | Users must abide by the constraints and limitations of the Red Hat Enterprise Linux TRM entry.
Use of this product is restricted to laboratory and development test systems only. This product may not be used for Veterans Information Systems and Technology Architecture (VistA) site mirror test systems or other pre-production verification systems. Applications and strategies developed on systems running this product must be tested properly on enterprise level Red Hat platforms prior to production release. This product must remain properly patched in order to mitigate known and future security vulnerabilities. Organization security baseline configuration standards for Linux systems must be employed and properly maintained. | | | [7] | 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). | | | [8] | 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). | | | [9] | 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). | | | [10] | Users must abide by the constraints and limitations of the Red Hat Enterprise Linux TRM entry.
Use of this product is restricted to laboratory and development test systems only. This product may not be used for Veterans Information Systems and Technology Architecture (VistA) site mirror test systems or other pre-production verification systems. Applications and strategies developed on systems running this product must be tested properly on enterprise level Red Hat platforms prior to production release. This product must remain properly patched in order to mitigate known and future security vulnerabilities. Organization security baseline configuration standards for Linux systems must be employed and properly maintained. | | | [11] | Users must abide by the constraints and limitations of the Red Hat Enterprise Linux TRM entry.
Use of this product is restricted to laboratory and development test systems only. This product may not be used for Veterans Information Systems and Technology Architecture (VistA) site mirror test systems or other pre-production verification systems. Applications and strategies developed on systems running this product must be tested properly on enterprise level Red Hat platforms prior to production release. Organization security baseline configuration standards for Linux systems must be employed and properly maintained.
The CentOS Secure Configuration Baseline must be followed, and care must be taken to ensure that vulnerabilities are monitored and known vulnerabilities mitigated expeditiously.
The administrator or installer must ensure that CentOS is obtained from the CentOS website with a verifiable web certificate. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Users should check with their supervisor, Information Security Officer (ISO) or local Office of Information and Technology (OI&T) representative for permission to download and use this software. | | | [12] | A Secure Configuration Baseline must be developed and authorized for CentOS to be adopted for usage within VA.
Once authorized, the CentOS Secure Configuration Baseline must be followed and care must be taken to ensure that vulnerabilities are monitored and known vulnerabilities mitigated expeditiously.
The administrator or installer should ensure that CentOS is obtained from the CentOS website with a verifiable web certificate. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Users should check with their supervisor, Information Security Officer (ISO) or local OI&T representative for permission to download and use this software.
CentOS is based on the stable release of Red Hat Enterprise Linux (RHEL). Support can be obtained via the community supporting CentOS and ultimately Red Hat.
Users must abide by the constraints and limitations of the Red Hat Enterprise Linux TRM entry.
Use of this product is restricted to laboratory and development test systems only. This product may not be used for Veterans Information Systems and Technology Architecture (VistA) site mirror test systems or other pre-production verification systems. Applications and strategies developed on systems running this product must be tested properly on enterprise level Red Hat platforms prior to production release. Organization security baseline configuration standards for Linux systems must be employed and properly maintained. | | | [13] | 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). | | | [14] | 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). | | | [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 (PSF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [16] | Per the Initial Product Review, users must abide by the following constraints:
- Establishing and enforcing a secure configuration baseline for CentOS is an
extremely heavy lift without a DISA STIG or compliance monitoring. The use of CentOS to host potentially critical VA production systems, that process sensitive information, may pose severe security risks to the VA
- CentOS is maintained by the community, and there are no assurances for
malicious free source code or a release schedule for maintenance updates
that would allow VA to plan out the product security roadmap. The use of open
source products, lacking any vendor support, hosting potentially critical VA
production systems may pose severe security risks to the VA.
| | | [17] | 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). |
|
| Note: |
At the time of writing, version 8 (2105) is end-of-life as of 12/31/2021. At the time of writing, 2009 is the most current update for version 7 and released 11/11/2020. |
