5.x |
Authorized w/ Constraints (DIVEST) [2, 3, 4, 5, 6] |
DIVEST [2, 3, 4, 5, 6] |
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) |
6.x |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
Approved w/Constraints [2, 3, 4, 5, 6] |
Approved w/Constraints [2, 3, 4, 5, 6] |
Approved w/Constraints [2, 3, 4, 5, 6] |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
| | [1] | Users must ensure that Microsoft Internet Information Services (IIS), Google Chrome, Microsoft Edge, and Apache Hypertext Transfer Protocol (HTTP) Server are implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must utilize authorized internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details.
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
Users must not utilize Opera (Opera Desktop), as it is at the time of writing, unapproved in the TRM.
This technology should not be used with Open Java Development Kit (OpenJDK) as it is unapproved for use at this time. There are other authorized java environments available. See Category tab for details.
This technology must use the latest TRM-authorized version of Java Development Kit (JDK) - Oracle.
This technology must use the latest TRM-authorized version of Java Runtime Environment (JRE) - Oracle.
Users must not utilize Docker Desktop (Community), as it is at the time of writing, unapproved in the TRM.
Per the Initial Product Review, users must abide by the following constraints:
- CommandBox will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information where applicable. 2. System Owners/Administrators should download
- Department of Veterans Affairs GPO settings may block the ability to install the product and special installation instructions may be required. System Administrators/Owners will need to “unblock” the installation in the properties of the installer prior to installation on VA resources.
| | [2] | 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. | | [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] | Users must ensure that Microsoft Internet Information Services (IIS), Google Chrome, Microsoft Edge, Firefox, and Apache Hypertext Transfer Protocol (HTTP) Server are implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
Users must not utilize Opera (Opera Desktop), as it is at the time of writing, unapproved in the TRM.
This technology should not be used with Open Java Development Kit (OpenJDK) as it is unapproved for use at this time. There are other authorized java environments available. See Category tab for details.
This technology must use the latest TRM-authorized version of Java Development Kit (JDK) - Oracle.
This technology must use the latest TRM-authorized version of Java Runtime Environment (JRE) - Oracle.
Users must not utilize Docker Desktop (Community), as it is at the time of writing, unapproved in the TRM.
Users must not utilize Heroku Command Line Interface (CLI), as it is at the time of writing, unapproved in the TRM.
Per the Initial Product Review, users must abide by the following constraints:
- CommandBox will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information where applicable.
- System Owners/Administrators should download CommandBox without the Java Runtime Environment bundled into the package. Java versions should be monitored for compliance with the One-VA TRM.
- Department of Veterans Affairs GPO settings may block the ability to install the product and special installation instructions may be required. System Administrators/Owners will need to “unblock” the installation in the properties of the installer prior to installation on VA resources.
| | [5] | 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. | | [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. |
|