2020.x |
Unapproved |
Approved w/Constraints [3, 4, 6, 7, 8] |
Approved w/Constraints [3, 4, 6, 7, 8] |
Approved w/Constraints [3, 4, 6, 7, 8] |
Approved w/Constraints [3, 4, 8, 9, 10] |
Approved w/Constraints [3, 4, 8, 9, 10] |
Approved w/Constraints [3, 4, 8, 9, 10] |
Approved w/Constraints [3, 4, 8, 9, 10] |
Approved w/Constraints [3, 4, 8, 9, 10] |
Approved w/Constraints [3, 4, 8, 9, 10] |
Approved w/Constraints [3, 4, 8, 9, 10] |
Divest [3, 4, 9, 10] |
| | [1] | Federal Information Processing Standard (FIPS) 140-2, certified encryption must be used to encrypt data in transit if Personal Identifiable Information (PII), Personal Health Information (PHI), or Veteran Affairs (VA) sensitive information is involved, or additional mitigating controls must be documented in an approved System Security Plan (SSP). Additionally, the technology must be implemented within the VA production network (not in a Demilitarized Zone (DMZ)) if PII/PHI/VA sensitive information is involved. | | [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] | 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. | | [7] | 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. | | [8] | Users must ensure that Microsoft Internet Explorer (IE) is implemented with VA-approved baselines. | | [9] | 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. | | [10] | 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. |
|