| 2.x |
Approved w/Constraints
[11, 14, 15, 16, 17, 18] |
Approved w/Constraints
[11, 14, 15, 16, 17, 18] |
Approved w/Constraints
[11, 14, 15, 16, 17, 18] |
Approved w/Constraints
[11, 14, 15, 17, 18, 19] |
Approved w/Constraints
[11, 14, 17, 18, 19, 20] |
Approved w/Constraints
[11, 14, 17, 18, 19, 20] |
Approved w/Constraints
[11, 17, 18, 19, 20, 21, 22] |
Approved w/Constraints
[11, 17, 18, 19, 20, 21, 22] |
Approved w/Constraints
[11, 17, 18, 19, 20, 21, 22] |
Approved w/Constraints
[11, 17, 18, 19, 20, 21, 22] |
Approved w/Constraints
[11, 17, 18, 19, 20, 21, 22] |
Approved w/Constraints
[11, 17, 18, 19, 20, 21, 22] |
| | | | [1] | 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 approved, may continue to operate this technology. In the case of a project that has implemented, or been approved 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 approved or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.
| | | [2] | 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. | | | [3] | 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. | | | [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] | Per the Initial Product Review, users must abide by the following constraints:
- The application does not comply with the minimum standards for security required by the VA for access control or clear delineation of duties of IT staff supporting and utilizing the system. All applications used must store and transmit data using a FIPS 140-2 (or its successor) validated application (or the application data resides in a container-based encryption solution) and must be listed in the VA’s Technical Reference Model (TRM).
- Due to the frequency of this technology`s updates and version changes, the VA may be unable to keep up with the rapid release schedule of this technology.
- Due to potential information security risks, Software as a Service/ Platform as a Service (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. The VA requires support for all software used on the VA network. Enterprise level support for Jenkins is not guaranteed.
- Jenkins Continuous Integration Server should only be considered when a VA approved solution does not meet the necessary requirements, and the use for more specialized tools are warranted.
This technology must use the latest version of Java Development Kit (JDK) - Oracle.
Based on the above findings and concerns raised by Security Engineering and OIS, this technology is considered unapproved for new production deployments after 2/29/2020 while the VA configuration standard is developed. Existing production deployments before 2/29/2020 are considered to be grandfathered in a divest status. This constraint will be revisited after VA determines a national standard and creates a configuration standard. After 02/29/2020, any new project or deployment of Jenkins Continuous Integration Server must have a STAT waiver to deploy. See the Baseline Configuration Management website for more information: https://vaww.vashare.oit.va.gov/sites/itops/svcs/sma/BCM/Pages/BCM.aspx | | | [6] | 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). | | | [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 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). | | | [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 Initial Product Review, users must abide by the following constraints:
- The product must be used with the VA approved implementation standard with specific hardening guidance regarding the secure implementation of the product. Please reference the implementation guide for Jenkins Continuous Integration Server:
https://vaww.vashare.oit.va.gov/sites/itops/svcs/sma/BCM/Supporting_Documents/Jenkins%20Continuous%20Integration%20Server%20Enterprise%20Implementation%20Standard.pdf
- Ensure a FIPS 140-2 solution is in place if applicable.
- Due to the frequency of this technology`s updates and version changes, the VA may be unable to keep up with the rapid release schedule of this technology. The product must be included on the list of applications for continuous monitoring for published updates, and patches.
- Due to potential information security risks, Software as a Service/ Platform as a Service (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. Enterprise level support for Jenkins is not guaranteed.
This technology must use the latest version of Java Development Kit (JDK) - Oracle.
Based on the above findings and concerns raised by Security Engineering and OIS, this technology is considered unapproved for new production deployments after 2/29/2020 while the VA configuration standard is developed. Existing production deployments before 2/29/2020 are considered to be grandfathered in a divest status. This constraint will be revisited after VA determines a national standard and creates a configuration standard. After 02/29/2020, any new project or deployment of Jenkins Continuous Integration Server must have a STAT waiver to deploy. See the Baseline Configuration Management website for more information: https://vaww.vashare.oit.va.gov/sites/itops/svcs/sma/BCM/Pages/BCM.aspx | | | [11] | 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. | | | [12] | Per the Initial Product Review, users must abide by the following constraints:
- The product must be used with the VA approved implementation standard with specific hardening guidance regarding the secure implementation of the product. Please reference the implementation guide for Jenkins Continuous Integration Server:
https://vaww.vashare.oit.va.gov/sites/itops/svcs/sma/BCM/Supporting_Documents/Jenkins%20Continuous%20Integration%20Server%20Enterprise%20Implementation%20Standard.pdf
- Ensure a FIPS 140-2 solution is in place if applicable.
- Due to the frequency of this technology`s updates and version changes, the VA may be unable to keep up with the rapid release schedule of this technology. The product must be included on the list of applications for continuous monitoring for published updates, and patches.
- Due to potential information security risks, Software as a Service/ Platform as a Service (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. Enterprise level support for Jenkins is not guaranteed.
This technology must use the latest version of Java Development Kit (JDK) - Oracle.
Based on the above findings and concerns raised by Security Engineering and OIS, this technology is considered unapproved for new production deployments after 2/29/2020 while the VA configuration standard is developed. Existing production deployments before 2/29/2020 are considered to be grandfathered in a divest status. This constraint will be revisited after VA determines a national standard and creates a configuration standard. After 02/29/2020, any new project or deployment of Jenkins Continuous Integration Server must have a STAT waiver to deploy. See the Baseline Configuration Management website for more information: https://vaww.vashare.oit.va.gov/sites/itops/svcs/sma/BCM/Pages/BCM.aspx
Users must ensure that Apache Hypertext Transfer Protocol (HTTP) Server and Microsoft Internet Information Services (IIS) Technology are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | | [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 (PSF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [14] | Per the Initial Product Review, users must abide by the following constraints:
- The product must be used with the VA approved implementation standard with specific hardening guidance regarding the secure implementation of the product. Please reference the implementation guide for Jenkins Continuous Integration Server:
https://vaww.vashare.oit.va.gov/sites/itops/svcs/sma/BCM/Supporting_Documents/Jenkins%20Continuous%20Integration%20Server%20Enterprise%20Implementation%20Standard.pdf
- Ensure a FIPS 140-2 solution is in place if applicable.
- Due to the frequency of this technology`s updates and version changes, the VA may be unable to keep up with the rapid release schedule of this technology. The product must be included on the list of applications for continuous monitoring for published updates, and patches.
- Due to potential information security risks, Software as a Service/ Platform as a Service (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. Enterprise level support for Jenkins is not guaranteed.
This technology must use the latest version of Java Development Kit (JDK) - Oracle.
Users must ensure that Apache Hypertext Transfer Protocol (HTTP) Server and Microsoft Internet Information Services (IIS) Technology are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Jenkins Continuous Integration Server should not be used with technologies such as Docker and Kubernetes, as these technologies are unapproved for use on the TRM. | | | [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 VA OIT Product Engineering team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [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 VA Handbook 6500. | | | [17] | 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. | | | [18] | 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. | | | [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] | 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). | | | [21] | Users must ensure that Kubernetes, Apache Hypertext Transfer Protocol (HTTP) Server and Microsoft Internet Information Services (IIS) Technology are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
This technology should not be used with Open Java Development Kit (OpenJDK) as it is unapproved for use at this time. There are other approved java environments available. See Category tab for details.
This technology can be deployed with Kubernetes. At the time of writing, the baseline for Kubernetes dictates that it can only be used in on-premises in Amazon Web Services (AWS) VA Enterprise Cloud (VAEC) implementations.
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle.
Per the Initial Product Review, users must abide by the following constraints:
- The product must be used with the VA approved implementation standard with specific hardening guidance regarding the secure implementation of Jenkins Continuous Integration Server. Please reference the implementation guide here: https://dvagov.sharepoint.com/sites/OITBCM/supporting_documents/jenkins%20continuous%20integration%20server%20enterprise%20implementation%20standard.pdf
- Jenkins Continuous Integration Server will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing PHI/PII or VA sensitive information.
- Due to the frequency of this technology`s updates and version changes, the VA may be unable to keep up with the rapid release schedule of this technology. The product must be included on the list of applications for continuous monitoring for published updates, and patches.
- Due to potential information security risks, SaaS/PaaS solutions must complete the Business Integration and Outcomes Service (BIOS) 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. Enterprise level support for Jenkins is not guaranteed. The use of open-source products, lacking any vendor support, hosting potentially critical VA production systems may pose severe security risks to the VA. Users should check with their supervisor, ISSO or local OIT representative for permission to download and use this software.
| | | [22] | 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. |
|
