67030.x |
Divest [1, 3, 4, 7, 8, 9] |
Divest [1, 3, 4, 7, 8, 9] |
Divest [1, 3, 4, 7, 8, 10] |
Divest [1, 3, 4, 7, 8, 10] |
Divest [1, 3, 4, 7, 8, 10] |
Divest [1, 3, 4, 7, 8, 11] |
Divest [1, 3, 4, 7, 8, 11] |
Divest [1, 3, 4, 7, 8, 11] |
Divest [1, 3, 4, 7, 8, 11] |
Divest [1, 3, 4, 7, 8, 11] |
Divest [1, 3, 4, 7, 8, 11] |
Divest [1, 3, 4, 7, 8, 11] |
| | [1] | Users should avoid interactions with Discord bots, as each bot utilizes different systems and some are known to have security vulnerabilities. This TRM assessment is unable to cover all user-created automated assistants.
Users should ensure that Google Chrome and Firefox are implemented within VA-approved baselines.
Use of this technology is limited to JOINING external web-based training sessions scheduled by non-organization users (e.g. vendor partners). VA users must leverage the organization`s preferred teleconferencing solutions, Microsoft Teams or WebEx, for internal hosted conferences. VA has selected Microsoft Teams and WebEx as its preferred teleconferencing solutions. No waiver or review is required for JOINING 3rd Party Adobe Connect meetings.
Per the Initial Product Review, users must abide by the following constraints:
- Discord should not be used for any data containing PHI/PII or sensitive information.
- The content on Discord is not heavily moderated and there are no administrative controls dashboard or similar application to filter out inappropriate/malicious links or chats. Users should practice due diligence by not clicking on links in the application and only chat with trusted known contacts.
- The most common type of malware in Discord is the Remote Access Trojan (RAT). Other malware includes AnarchyGrabber. AnarchyGrabber works by modifying JavaScript code that the Discord client loads when it starts up. Once that code is modified, the malware itself more or less vanishes and antimalware software cannot detect it. System Owners should make sure the latest version of Discord is used.
- Discord must only be used to join external web-based training sessions scheduled by non-organization users (e.g. vendor partners). VA users must leverage the organization`s preferred teleconferencing solutions, Microsoft
Teams or WebEx, for internal hosted conferences. VA has selected Microsoft Teams and WebEx as its preferred teleconferencing solutions.
| | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [3] | Users should check with their supervisor, Information Security Office (ISO) 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 approved 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 ISO 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 with the Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [7] | 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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [8] | 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 ISO can advise on the ESCCB review process. | | [9] | 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 Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [10] | 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 Project Special Forces (PSF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [11] | 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). |
|