| 2.x |
Approved w/Constraints
[11, 15, 16, 17, 18] |
Approved w/Constraints
[11, 15, 16, 17, 18] |
Approved w/Constraints
[11, 15, 16, 17, 18] |
Approved w/Constraints
[11, 15, 16, 17, 18] |
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] |
Approved w/Constraints
[11, 17, 18, 19, 20, 21, 22] |
Approved w/Constraints
[11, 17, 18, 19, 20, 21, 22] |
| | | | [1] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (contact VA e-mail: OIT ITOPS SD Engagement Requests) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | | [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] | 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). | | | [4] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process. | | | [5] | 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). | | | [6] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process. | | | [7] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (contact VA e-mail: [OIT ITOPS SD Engagement Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | | [8] |
Per the Initial Product Review, users must abide by the following constraints:
- Prometheus should not be used to handle sensitive VA data at rest and in transit.
- Should users request to use Prometheus, administrators should obtain Prometheus from the official Prometheus site or the authentic GitHub page for Prometheus, and commercial third-party support for Prometheus must be purchased to ensure enterprise level support.
- Should users request to use Prometheus, administrators must ensure that they are using the latest version of Prometheus. Prometheus’ GitHub page and systems running Prometheus should be continually monitored for vulnerabilities, patches, and updates.
- Prometheus would only be considered when a VA approved solution does not meet the necessary requirements, and the use for more specialized tools are warranted. Unauthorized applications should not be installed or used on the VA network unless a waiver from the Strategic Technology Alignment Team (STAT) has been granted to the project team or organization that wishes to use the technology.
- This technology is currently unapproved due to VA standardization and the lack of a required VA baseline. In order to reduce costs, risk and overhead in manyareas including: training, patching, configuration standards, and documentation, VA has standardized the types and configurations of the platforms/technologies it uses and maintains baselines for in its internal operating environment.
| | | [9] | 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. | | | [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] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (yourIT Service Portal:[SNOW Service Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | | [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 Project Special Forces (SPF) 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:
Prometheus should not be used to handle sensitive VA data at rest and in transit.
Should users request to use Prometheus, administrators should obtain Prometheus from the official Prometheus site or the authentic GitHub page for Prometheus, and commercial third-party support for Prometheus must be purchased to ensure enterprise level support.
Should users request to use Prometheus, administrators must ensure that they are using the latest version of Prometheus, currently 2.24.1. Prometheus’ GitHub page and systems running Prometheus should be continually monitored for vulnerabilities, patches, and updates.
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.
Any database being monitored using Prometheus should be properly baselined to protect VA information.
| | | [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 (PSF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [15] | Per the Initial Product Review, users must abide by the following constraints:
- Prometheus should not be used to handle sensitive VA data at rest and in transit.
- Should users request to use Prometheus, administrators should obtain Prometheus from the official Prometheus site or the authentic GitHub page for Prometheus, and commercial third-party support for Prometheus must be purchased to ensure enterprise level support.
- Should users request to use Prometheus, administrators must ensure that they are using the latest version of Prometheus, currently 2.24.1. Prometheus’ GitHub page and systems running Prometheus should be continually monitored for vulnerabilities, patches, and updates.
- 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.
- This product must be used with a VA approved container platform that has a
developed and approved baseline configuration with specific hardening
guidance regarding the secure implementation of Prometheus. Currently
Kubernetes, Docker, and OpenShift are container products VA is evaluating.
Please reference the TRM for the approved solution and the Baseline
Configuration Management website for more information.
Any database being monitored using Prometheus should be properly baselined to protect VA information.
This technology is compatible with a wide variety of operating systems, including some that are not evaluated by the TRM. Users must ensure that this technology is implemented within approved operating systems. | | | [16] | 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). | | | [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] | Per the Initial Product Review, users must abide by the following constraints:
- Prometheus will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing Protected Health Information (PHI)/Personally Identifiable Information (PII) or VA sensitive information. It is important to note that most, if not all, Cloud Service Providers (CSPs) will have data at rest encryption built into the standard product.
- 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 approved and the user should take the proper steps to decline those installations. Support for open-source software can vary so, it is important to note that support services need to be maintained for this product.
- The product must remain patched, updated, and operated in accordance with Federal and Department security and privacy policies and guidelines.
- 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.
- This product should be used with a VA approved container platform that has a developed and approved baseline configuration with specific hardening guidance regarding the secure implementation of Prometheus. Please reference the TRM for the approved solution and the Baseline Configuration Management website for more information.
| | | [20] | 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. | | | [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] | 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. |
|
