| 2.x |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints
[1, 2, 3, 4, 5] |
Authorized w/ Constraints
[1, 2, 3, 4, 5] |
Approved w/Constraints
[1, 2, 3, 4, 5] |
Approved w/Constraints
[1, 2, 3, 4, 5] |
Approved w/Constraints
[1, 2, 3, 4, 5] |
Authorized w/ Constraints
[1, 2, 3, 4, 5] |
Authorized w/ Constraints
[1, 2, 3, 4, 5] |
Authorized w/ Constraints
[1, 2, 3, 4, 5] |
Authorized w/ Constraints
[1, 2, 3, 4, 5] |
| | | | [1] | Users should not utilize Bitmap Image File, as it is at the time of writing, Authorized w/Constraints (DIVEST) for use on the TRM.
Users must ensure that Firefox, Google Chrome, and Microsoft Edge are implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
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 Roland CutStudio, as it, at the time of writing, requires a POA&M.
Per the Security Assessment Review, users must abide by the following constraints:
- System Owners/Administrators shall verify the software is downloaded from a trusted source such as the vendor website or a
VA approved repository.
- To mitigate, administrators must ensure that installed versions of Microsoft Webview2 Runtime Libraries are updated to a TRM
authorized version of the software. The vendor must maintain all third-party components during the entire product lifecycle, including responding to vulnerabilities discovered in third-party components used in the product.
- To mitigate, administrators must ensure that installed versions of SQLite Libraries are updated to a TRM authorized version of the
software. The vendor must maintain all third-party components during the entire product lifecycle, including responding to vulnerabilities
discovered in third-party components used in the product.
- To mitigate, administrators must ensure that installed versions of Visual Studio Libraries are updated to a TRM authorized version of
the software. The vendor must maintain all third-party components during the entire product lifecycle, including responding to vulnerabilities
discovered in third-party components used in the product.
| | | [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 both VA Handbook 6500 and VA Directive 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] | 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. | | | [5] | 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. |
|
