<Past |
Future> |
1.5.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.6.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.7.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.8.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.9.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.0.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.1.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.2.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.3.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.4.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.5.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.6.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.7.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.8.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.9.x |
Approved w/Constraints [2, 4, 8, 9, 11] |
Approved w/Constraints [2, 4, 8, 9, 12] |
Divest [2, 4, 9, 12, 13, 14] |
Divest [2, 4, 9, 12, 13, 14] |
Divest [12, 13, 14, 15, 16, 17] |
Divest [12, 13, 14, 15, 16, 17] |
Divest [12, 13, 14, 15, 16, 17] |
Divest [12, 14, 15, 16, 18, 19, 20] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.10.x |
Unapproved |
Unapproved |
Divest [2, 4, 9, 12, 13, 14] |
Divest [2, 4, 9, 12, 13, 14] |
Divest [12, 13, 14, 15, 16, 17] |
Divest [12, 13, 14, 15, 16, 17] |
Divest [12, 13, 14, 15, 16, 17] |
Divest [12, 14, 15, 16, 18, 19, 20] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.11.x |
Unapproved |
Unapproved |
Divest [2, 4, 9, 12, 13, 14] |
Divest [2, 4, 9, 12, 13, 14] |
Divest [12, 13, 14, 15, 16, 17] |
Divest [12, 13, 14, 15, 16, 17] |
Divest [12, 13, 14, 15, 16, 17] |
Divest [12, 14, 15, 16, 18, 19, 20] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.12.x |
Unapproved |
Unapproved |
Divest [2, 4, 9, 12, 13, 14] |
Divest [2, 4, 9, 12, 13, 14] |
Divest [12, 13, 14, 15, 16, 17] |
Divest [12, 13, 14, 15, 16, 17] |
Divest [12, 13, 14, 15, 16, 17] |
Divest [12, 14, 15, 16, 18, 19, 20] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.13.x |
Unapproved |
Unapproved |
Approved w/Constraints [2, 4, 9, 12, 13, 14] |
Approved w/Constraints [2, 4, 9, 12, 13, 14] |
Approved w/Constraints [12, 13, 14, 15, 16, 17] |
Approved w/Constraints [12, 13, 14, 15, 16, 17] |
Approved w/Constraints [12, 13, 14, 15, 16, 17] |
Divest [12, 14, 15, 16, 18, 19, 20] |
Divest [14, 15, 16, 18, 19, 20, 21] |
Divest [14, 15, 16, 19, 20, 21, 22] |
Divest [14, 15, 16, 19, 20, 21, 22] |
Divest [14, 15, 16, 19, 20, 21, 22] |
2.14.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [12, 14, 15, 16, 18, 19, 20] |
Divest [14, 15, 16, 18, 19, 20, 21] |
Divest [14, 15, 16, 19, 20, 21, 22] |
Divest [14, 15, 16, 19, 20, 21, 22] |
Divest [14, 15, 16, 19, 20, 21, 22] |
2.15.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [12, 14, 15, 16, 18, 19, 20] |
Approved w/Constraints [14, 15, 16, 18, 19, 20, 21] |
Divest [14, 15, 16, 19, 20, 21, 22] |
Divest [14, 15, 16, 19, 20, 21, 22] |
Divest [14, 15, 16, 19, 20, 21, 22] |
2.16.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [14, 15, 16, 19, 20, 21, 22] |
Approved w/Constraints [14, 15, 16, 19, 20, 21, 22] |
Approved w/Constraints [14, 15, 16, 19, 20, 21, 22] |
| | [1] | One component of this technology, Ansible-vault, is not permitted for use. This feature enables the storage of passwords using reversible encryption implemented through a python library which is not FIPS-140-2 compliant.
System configuration changes made using this technology must first be vetted and approved through appropriate Change Control Board processes and comply with established baselines as appropriate. | | [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 approved and the user should take the proper steps to decline those installations. | | [3] | 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. | | [4] | 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. | | [5] | 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. | | [6] | Based on the IPR findings from Security Engineering and pending required VA security policy guidance from OIS DevSecOps on container and orchestrator technology, this technology is only approved for Development and Test systems usage. Production system use of this technology is considered TRM unapproved must have an approved TRM waiver to accept the risks of using this technology in production without required policy and configuration standards. This constraint will be revisited after VA determines relevant policy and creates configuration standard(s). See the reference section and the Baseline Configuration Management website for more information: https://vaww.vashare.oit.va.gov/sites/itops/svcs/sma/BCM/Pages/BCM.aspx
It is advised that if this product is used within the Department of Veterans Affairs (VA) that the following constraints be applied:
-
System administrators must ensure that underlying infrastructure (Operating
System (OS), Web Server, etc.) or a third party FIPS 140-2 cryptographic
module can protect the security of FIPS-supported versions of Red Hat
Ansible/Ansible Tower before it stores and processes VA sensitive information.
-
Red Hat Ansible and Ansible Tower should not be used in a production
environment until the VA develops a container strategy and establishes an
enterprise orchestration solution. Should a user request to use Red Hat Ansible
and Ansible Tower, the product must be used in a development or testing
environment.
-
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).
-
Open source software may be obtained at no cost. VA requires support for all
software used on the VA network. Vendor or third-party support at an enterprise
level is not free and must be acquired for any open source product to be
deployed on the VA network.
| | [7] | 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). | | [8] | Per the Initial Product Review, users must abide by the following constraints:
- System administrators must ensure that underlying infrastructure (Operating System (OS), Web Server, etc.) or a third party FIPS 140-2 cryptographic module can protect the security of FIPS-supported versions of Red Hat Ansible/Ansible Tower before it stores and processes VA sensitive information.
- 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).
- Open source software may be obtained at no cost. VA requires support for all software used on the VA network. Vendor or third-party support at an enterprise level is not free and must be acquired for any open source product to be deployed on the VA network.
| | [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 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). | | [11] | 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). | | [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 VA OIT Product Engineering team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [13] | Per the Initial Product Review, users must abide by the following constraints:
- System administrators must ensure that underlying infrastructure (Operating System (OS), Web Server, etc.) or a third party FIPS 140-2 certified cryptographic module can protect the security of FIPS-supported versions of Red Hat Ansible/Ansible Tower before it stores and processes 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), 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.
- Open-source software may be obtained at no cost. VA requires support for all software used on the VA network. Vendor or third-party support at an enterprise level is not free and must be acquired for any open-source product to be deployed on the VA network.
| | [14] | 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. | | [15] | 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 approved and the user should take the proper steps to decline those installations. | | [16] | 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. | | [17] | 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. | | [18] | Per the Initial Product Review, users must abide by the following constraints:
- System administrators must ensure that underlying infrastructure (Operating System (OS), Web Server, etc.) or a third party FIPS 140-2 certified cryptographic module can protect the security of FIPS-supported versions of Red Hat Ansible/Ansible Tower before it stores and processes 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), 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.
- Open-source software may be obtained at no cost. VA requires support for all software used on the VA network. Vendor or third-party support at an enterprise level is not free and must be acquired for any open-source product to be deployed on the VA network.
- System owners should review the One-VA TRM entries for the approved versions of PostgreSQL
- Ensure that the latest stable version of Ansible Automation Platform and Ansible Tower is used. Additionally, the products must be added to the list of applications for continuous monitoring for published vulnerabilities, updates, and patches. ISSO’s and administrators must monitor the National Vulnerability website for any new security vulnerabilities
| | [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 both VA Handbook 6500 and VA Directive 6500. | | [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. | | [21] | 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). | | [22] | Per the Initial Product Review, users must abide by the following constraints:
- System administrators must ensure that underlying infrastructure (Operating System (OS), Web Server, etc.) or a third party FIPS 140-2 certified cryptographic module can protect the security of FIPS-supported versions of Red Hat Ansible/Ansible Tower before it stores and processes 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.
- Open-source software may be obtained at no cost. VA requires support for all software used on the VA network. Vendor or third-party support at an enterprise level is not free and must be acquired for any open-source product to be deployed on the VA network.
- System owners should review the One-VA TRM entries for the approved versions of PostgreSQL.
- Ensure that the latest stable version of Ansible Automation Platform and Ansible Tower is used. Additionally, the products must be added to the list of applications for continuous monitoring for published vulnerabilities, updates, and patches. ISSO’s and administrators must monitor the National Vulnerability website for any new security vulnerabilities.
|
|
Note: |
At the time of writing, version 2.16.6 is the most current version, released 04/15/2024. |