3.x |
DIVEST [2, 4, 5, 6] |
Authorized w/ Constraints (DIVEST) [2, 4, 5, 6] |
DIVEST [2, 4, 5, 6] |
DIVEST [2, 4, 5, 6] |
Authorized w/ Constraints (DIVEST) [2, 4, 5, 6] |
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) |
2024.x |
Approved w/Constraints [2, 4, 5, 6] |
Authorized w/ Constraints [2, 4, 5, 6] |
Approved w/Constraints [2, 4, 5, 6] |
Approved w/Constraints [2, 4, 5, 6] |
Authorized w/ Constraints [2, 4, 5, 6] |
Authorized w/ Constraints [2, 4, 5, 6] |
Authorized w/ Constraints [2, 4, 5, 6] |
Authorized w/ Constraints [2, 4, 5, 6] |
Authorized w/ Constraints [2, 4, 5, 6] |
Authorized w/ Constraints [2, 4, 5, 6] |
Authorized w/ Constraints [2, 4, 5, 6] |
Authorized w/ Constraints [2, 4, 5, 6] |
| | [1] | Users must not utilize Auth0, as it is at the time of writing, unapproved in the TRM. | | [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] | 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). | | [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, visit the Product Marketplace.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [5] | This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data.
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it requires a POA&M.
Users must not utilize Auth0, as it is at the time of writing, requires a POA&M.
Users must ensure that Visual C++ Redistributable Package, Firefox, Microsoft Edge, and Google Chrome are implemented with VA-approved baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [6] | 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. |
|