| 7.6.x |
Approved w/Constraints
[9, 13, 15, 16, 17] |
Approved w/Constraints
[9, 13, 15, 16, 17] |
Approved w/Constraints
[9, 13, 15, 16, 17] |
Approved w/Constraints
[9, 13, 15, 16, 17] |
Approved w/Constraints
[9, 13, 15, 16, 17] |
Approved w/Constraints
[9, 13, 15, 16, 17] |
Approved w/Constraints
[9, 13, 15, 16, 17] |
Approved w/Constraints
[9, 13, 15, 16, 17] |
Approved w/Constraints
[9, 13, 15, 16, 17] |
Approved w/Constraints
[9, 13, 15, 16, 17] |
Approved w/Constraints
[9, 13, 15, 16, 17] |
Approved w/Constraints
[9, 13, 15, 16, 17] |
| | | | [1] | This product may only be used as a third party component required by other TRM approved software and may not be installed and used separately as a substitute for enterprise approved Microsoft Office products. Due to several NIST security vulnerabilities, extra vigilance should be applied to ensure the product remains properly patched to mitigate known and future vulnerabilities. | | | [2] | As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an assessment by the VA Section 508 office. Section 508 of the Rehabilitation Act Amendments of 1998 is a federal law that sets the guidelines for technology accessibility. A VA Section 508 assessment of this technology has not been completed at the time of publication. Therefore, as of April 23, 2015 only users of this technology who have deployed the technology to the production environment, or have project design and implementation plans approved, may continue to operate this technology. In the case of a project that has implemented, or been approved for a specific site or number of users, and that project needs to expand operations to other sites or to an increased user base, it may do so as long as the project stays on the existing version of the technology that was approved or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.
| | | [3] | This product may only be used as a third party component required by other TRM approved software and may not be installed and used separately as a substitute for enterprise approved Microsoft Office products. | | | [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] | 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. | | | [6] | This product may only be used as a third party component required by other TRM approved software and may not be installed and used separately as a substitute for enterprise approved Microsoft Office products. | | | [7] | This product must only be used as a third party component required by other TRM approved software and may not be installed and used separately as a substitute for enterprise approved Microsoft Office products. | | | [8] | This product must only be used as a third-party component required by other TRM-approved software and may not be installed and used separately as a substitute for enterprise approved Microsoft Office products. | | | [9] | This technology must only be downloaded from the vendor`s website and not from any App Store. | | | [10] | 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. | | | [11] | 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. | | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | | [13] | 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. | | | [14] | 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. | | | [15] | 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. | | | [16] | 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. | | | [17] | 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. |
|
