<Past |
Future> |
2022.10.x |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Divest [2, 3, 4, 5, 6] |
Divest [3, 4, 6, 7, 8, 9] |
Divest [6, 7, 8, 9, 10, 11] |
Divest [6, 7, 8, 9, 10, 11] |
Divest [6, 7, 8, 9, 10, 11] |
Divest [6, 7, 8, 9, 10, 11] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2023.4.x |
Unapproved |
Unapproved |
Approved w/Constraints [2, 3, 4, 5, 6] |
Divest [3, 4, 6, 7, 8, 9] |
Divest [6, 7, 8, 9, 10, 11] |
Divest [6, 7, 8, 9, 10, 11] |
Divest [6, 7, 8, 9, 10, 11] |
Divest [6, 7, 8, 9, 10, 11] |
Divest [6, 7, 8, 9, 10, 11] |
Unapproved |
Unapproved |
Unapproved |
2023.10.x |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [3, 4, 6, 7, 8, 9] |
Approved w/Constraints [6, 7, 8, 9, 10, 11] |
Approved w/Constraints [6, 7, 8, 9, 10, 11] |
Approved w/Constraints [6, 7, 8, 9, 10, 11] |
Approved w/Constraints [6, 7, 8, 9, 10, 11] |
Approved w/Constraints [6, 7, 8, 9, 10, 11] |
Approved w/Constraints [6, 7, 8, 9, 10, 11] |
Approved w/Constraints [6, 7, 8, 9, 10, 11] |
Approved w/Constraints [6, 7, 8, 9, 10, 11] |
| | [1] | Users must ensure that Microsoft Structured Query Language (SQL) Server and Kubernetes are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Microsoft Internet Explorer, a dependency of this technology, is in End-of-Life status and must no longer be used.
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
Users must not utilize Redis and Ceph, as it is at the time of writing, unapproved in the TRM.
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. | | [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 ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500. | | [3] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | [4] | 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). | | [5] | Users must ensure that Microsoft Structured Query Language (SQL) Server and Kubernetes are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Microsoft Internet Explorer, a dependency of this technology, is in End-of-Life status and must no longer be used.
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
Users must not utilize Redis and Ceph, as it is at the time of writing, unapproved in the TRM.
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.
Per the Security Assessment Review (SAR), users must abide by the following constraints:
- To mitigate, the administrator shall update the unsupported version of OpenSSL to a TRM approved version.
- o mitigate, the ISSO shall educate and prohibit users from using the integrated cloud service capability until the VA Cloud Security Requirements have been met and the affected A&A package has been appropriately updated.
- To mitigate, the optional mobile code shall not be installed unless it is TRM approved.
- Maintenance and support will be provided for the Open Source Software used within UiPath Studio v23.x as per the application’s lifecycle.
- To mitigate, System Administrators shall set Telemetry to disabled under Settings > General > Telemetry within the UiPath Studio interface or manually within the .config file.
- To mitigate, the administrator shall disable automatic update checking.
| | [6] | 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. | | [7] | Users must ensure that Microsoft Structured Query Language (SQL) Server, Firefox, Google Chrome, and Kubernetes are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Microsoft Internet Explorer, a dependency of this technology, is in End-of-Life status and must no longer be used.
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
Users must not utilize Redis and Ceph, as it is at the time of writing, unapproved in the TRM.
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.
Per the Security Assessment Review (SAR), users must abide by the following constraints:
- To mitigate, the administrator shall update the unsupported version of OpenSSL to a TRM approved version.
- To mitigate, the ISSO shall educate and prohibit users from using the integrated cloud service capability until the VA Cloud Security Requirements have been met and the affected A&A package has been appropriately updated.
- To mitigate, the optional mobile code shall not be installed unless it is TRM approved.
- Maintenance and support will be provided for the Open Source Software used within UiPath Studio v23.x as per the application’s lifecycle.
- To mitigate, System Administrators shall set Telemetry to disabled under Settings > General > Telemetry within the UiPath Studio interface or manually within the .config file.
- To mitigate, the administrator shall disable automatic update checking.
| | [8] | 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. | | [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] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 or its successor to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes. | | [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, visit the Product Marketplace.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). |
|
Note: |
At the time of writing, version 2023.10 is the most current version, released 11/03/2023. |