1.1.x |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6, 7, 8] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6, 7, 8] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6, 7, 8] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6, 7, 8] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6, 7, 8] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6, 7, 8] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6, 7, 8] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6, 7, 8] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6, 7, 8] |
| | [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.
Users must not utilize DropBox, as it, at the time of writing, requires a POA&M.
This technology can utilize commercial cloud storage options (Google Drive, Dropbox, etc.). These services require a POA&M for use on the VA network. | | [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] | 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. | | [4] | 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. | | [5] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISSO (Information System Security Officer) can advise on the ESCCB review process. | | [6] | 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). | | [7] | This product includes a Bluetooth capability. If that capability is leveraged, the implementer must conform to the Bluetooth Standard. 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. | | [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. |
|