10.x |
Approved w/Constraints [8, 10, 11, 12] |
Approved w/Constraints [8, 10, 11, 12] |
Approved w/Constraints [8, 10, 11, 12] |
Approved w/Constraints [8, 10, 11, 12] |
Approved w/Constraints [8, 10, 11, 12] |
Approved w/Constraints [8, 10, 11, 12] |
Approved w/Constraints [8, 10, 11, 12] |
Approved w/Constraints [8, 10, 11, 12] |
Approved w/Constraints [8, 10, 11, 12] |
Approved w/Constraints [8, 10, 11, 12] |
Approved w/Constraints [8, 10, 11, 12] |
Approved w/Constraints [8, 10, 11, 12] |
| | [1] | Only instances of this technology that have been deployed may continue to use this technology. No further expansion or use of this technology is permitted without a waiver from the Architecture and Engineering Review Board (AERB) and expressed authorization from the Assistant Secretary/Chief Information Officer or the Principal Deputy Assistant Secretary for the Office of Information and Technology. | | [2] | 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. | | [3] | Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities. | | [4] | 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. | | [5] | 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. | | [6] | Using the below link, please reference the VA Cyber Security Operations Center (CSOC) Bulletin addressing “VA CSOC Bulletin B-20-230 OpenManage Server Path Traversal Vulnerability” which was published August 10, 2020.
https://vaww.vashare.oit.va.gov/sites/ois/KnowledgeService/TAAP/Pages/Bulletins.aspx | | [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] | This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product. | | [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 ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500. | | [10] | 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 approved and the user should take the proper steps to decline those installations. | | [11] | Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities. | | [12] | 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. |
|