2.03 |
Authorized w/ Constraints [1, 2, 3, 4] |
Authorized w/ Constraints [1, 2, 3, 4] |
Authorized w/ Constraints [1, 2, 3, 4] |
Authorized w/ Constraints [1, 2, 3, 4] |
Authorized w/ Constraints [1, 2, 3, 4] |
Authorized w/ Constraints [1, 2, 3, 4] |
Authorized w/ Constraints [1, 2, 3, 4] |
Authorized w/ Constraints [1, 2, 3, 4] |
Authorized w/ Constraints [1, 2, 3, 4] |
Authorized w/ Constraints [1, 2, 3, 4] |
Authorized w/ Constraints [1, 2, 3, 4] |
Authorized w/ Constraints [1, 2, 3, 4] |
| | [1] | 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.
Per the [Initial Product Review/Security Assessment Review], users must abide by the following constraints:
- System Administrators will need to work with the vendor to limit/identify the ports the software uses and verify with the vendor
if removing the firewall exception may impact the functionality of the application. Ensure that the latest stable version of Bonjour is
used to mitigate vulnerabilities.
- TrakPro Ultra will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing PHI/PII or VA sensitive information.
- 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
| | [2] | 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). | | [3] | 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. | | [4] | 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. |
|