1.x |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
2.x |
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] |
Authorized w/ Constraints [11, 17, 18, 19, 20, 21, 22] |
Authorized w/ Constraints [11, 17, 18, 19, 20, 21, 22] |
Authorized w/ Constraints [11, 17, 18, 19, 20, 21, 22] |
Authorized w/ Constraints [11, 17, 18, 19, 20, 21, 22] |
Authorized w/ Constraints [11, 17, 18, 19, 20, 21, 22] |
Authorized w/ Constraints [11, 17, 18, 19, 20, 21, 22] |
Authorized w/ Constraints [11, 17, 18, 19, 20, 21, 22] |
Authorized w/ Constraints [11, 17, 18, 19, 20, 21, 22] |
Authorized w/ Constraints [11, 17, 18, 19, 20, 21, 22] |
| | [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. | | [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 authorized 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 authorized 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 authorized container platform that has a developed and authorized baseline configuration with specific hardening guidance regarding the secure implementation of Prometheus. Please reference the TRM for the authorized 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. |
|