| Office 14.0/2010 |
Approved w/Constraints
[7, 8, 9, 10] |
Approved w/Constraints
[7, 8, 10, 11, 12] |
Approved w/Constraints
[7, 8, 10, 11, 12] |
Divest
[7, 8, 10, 11, 12] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| Office 16.0/2016 |
Approved w/Constraints
[7, 8, 9, 10] |
Approved w/Constraints
[7, 8, 10, 11, 12] |
Approved w/Constraints
[7, 8, 10, 11, 12] |
Approved w/Constraints
[7, 8, 10, 11, 12] |
Approved w/Constraints
[7, 8, 10, 11, 12] |
Approved w/Constraints
[7, 8, 10, 11, 12] |
Approved w/Constraints
[7, 8, 10, 11, 12] |
Approved w/Constraints
[7, 8, 10, 11, 12] |
Approved w/Constraints
[7, 8, 10, 11, 13] |
Approved w/Constraints
[7, 8, 10, 11, 13] |
Approved w/Constraints
[7, 8, 10, 11, 13] |
Approved w/Constraints
[7, 8, 10, 13, 14] |
| | | | [1] | This Technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. | | | [2] | Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. Configuration and deployment standards for Microsoft Office images, which are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering must be followed and adhered to unless an appropriate waiver is granted.
Office 15.0/2013 is under evaluation and is currently not approved for production except as part of an official Enterprise System Engineering (ESE) production pilot or production test of this version as approved by ESE Client Services or an AERB waiver while under evaluation. | | | [3] | Configuration and deployment standards for Microsoft Office images which are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering must be followed and adhered to unless an appropriate waiver is granted.
Office 15.0/2013 is under evaluation and is currently not approved for production except as part of an official Enterprise System Engineering (ESE) production pilot or production test of this version as approved by ESE Client Services or an AERB waiver while under evaluation. | | | [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] | 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] | Configuration and deployment standards for Microsoft Office images which are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering must be followed and adhered to unless an appropriate waiver is granted.
Windows Office 15.x/2013 is unapproved as the VA will not being deploying or approving the use of Office 2013 or its components (InfoPath, Excel, OneNote, Outlook, PowerPoint, Publisher and Word). Enterprise System Engineering (ESE) is testing and working on a deployment plan for Office 365 ProPlus (Office 2016). As such, Windows Office 15.x/2013 is unapproved and 16.x/2016 is under evaluation and is currently not approved for production.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | | [7] | 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. | | | [8] | 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. | | | [9] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Configuration and deployment standards for Microsoft Office images which are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering must be followed and adhered to unless an appropriate waiver is granted. | | | [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] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | | [12] | Due to potential information security risks, cloud based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [13] | 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). | | | [14] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Microsoft .NET Framework is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) |
|
