|
<Past |
Future> |
| 1.0.x |
Approved w/Constraints
[1, 3, 6, 7, 8] |
Approved w/Constraints
[1, 3, 6, 7, 8] |
Approved w/Constraints
[1, 3, 6, 7, 8] |
Approved w/Constraints
[1, 3, 6, 8, 9] |
Approved w/Constraints
[1, 3, 8, 9, 10] |
Approved w/Constraints
[1, 3, 8, 9, 10] |
Divest
[3, 8, 9, 10, 11, 12] |
Divest
[3, 8, 9, 10, 11, 12] |
Divest
[3, 8, 9, 10, 11, 12] |
Divest
[3, 8, 9, 10, 11, 12] |
Divest
[3, 8, 9, 10, 11, 12] |
Unapproved |
| 1.1.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints
[3, 8, 9, 10, 11, 12] |
Approved w/Constraints
[3, 8, 9, 10, 11, 12] |
Approved w/Constraints
[3, 8, 9, 10, 11, 12] |
Approved w/Constraints
[3, 8, 9, 10, 11, 12] |
Approved w/Constraints
[3, 8, 9, 10, 11, 12] |
Approved w/Constraints
[3, 8, 9, 10, 11, 12] |
| | | | [1] | This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle.
Users must not utilize Secure Sockets Layer (SSL), Ubuntu Server, and VersionOne LifeCycle as these are unapproved in the TRM.
Users must ensure that Firefox, Google Chrome, and Microsoft Internet Explorer are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | | [2] | 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. | | | [3] | 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. | | | [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 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). | | | [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 VA OIT Product Engineering 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 ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500. | | | [8] | 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 ISSO (Information System Security Officer) can advise on the ESCCB review process. | | | [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 ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 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, visit the Product Marketplace.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [11] | This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle.
Users must not utilize Microsoft SharePoint Server, QAComplete (QAC), and VersionOne LifeCycle as these are unapproved in the TRM.
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
Users must utilize approved internet browsers, as Microsoft Internet Explorer (IE) has reached End of Life status. See Category Tab for details.
Users must ensure that Firefox and Google Chrome are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Initial Product Review, users must abide by the following constraints:
- Planview Viz will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information.
- The use of AI is increasing, and guidance is still developing. Users must check the most recent VA guidance before using AI technologies and solutions. Consideration should be given to the source of any initial data for the AI tool, if any VA data will be collected and ingested into the data set, where that data will be stored, and what rights the VA has to that data. No web-based, publicly available generative AI service has been approved for use with VA-sensitive data. Examples of these include OpenAI’s ChatGPT and GPT4, Google’s Bard, Anthropic’s Claude, and Microsoft’s new Bing. VA follows existing federal requirements and processes to ensure VA data is protected. When users enter information into an unapproved web-based tool, VA loses control of the data.
- Connecting applications and cloud services to one another increases the risks and attack vectors through means such as supply chain attacks. Prior to connection all applicable paperwork and security controls need to be addressed and approved. These documents include but are not limited to Service Level Agreements (SLAs), Authorization to Connect (ATC), and Authorization to Operate (ATO) for all applicable connecting services.
| | | [12] | 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. |
|
| Note: |
At the time of writing, version 1.1.1178 is the most current version, released 01/30/2024. |
