|
[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] | 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] | 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] | 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] | 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.
|
|
[6] | Mac Office 15.x/2016 and Windows Office 15.x/2013, including Skype for Business, are under evaluation and are 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 Desktop Technologies team for Windows (email: VA IT Engineering CS Desktop Technologies Team) or ESE MAC Support Team for MAC (email: VA IP Mac Team) or an AERB waiver while under evaluation. As of this writing, no deployment date for Mac Office 2016 or Windows Office 2013 has been determined. Mac Office 2011 becomes unapproved on 1/12/2016 when product support ends. |
|
[7] | Mac Office 15.x/2016 and Windows Office 15.x/2013, including Skype for Business, are under evaluation and are 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 Desktop Technologies team for Windows (email: VA IT Engineering CS Desktop Technologies Team) or ESE MAC Support Team for MAC (email: VA IP Mac Team) or an Architecture and Engineering Review Board (AERB) waiver while under evaluation. As of this writing, no deployment date for Mac Office 2016 or Windows Office 2013 has been determined. |
|
[8] | Mac Office 15.x/2016 Skype for Business is under evaluation and is currently not approved for production except as part of an official Solution Delivery (SD) production pilot or production test of this version as approved by SD Desktop Technologies team for Windows (email: OIT ITOPS SD EE Desktop and Device Engineering) or SD MAC Support Team for MAC (email: VA IP Mac Team) or an Architecture and Engineering Review Board (AERB) waiver while under evaluation. As of this writing, no deployment date for Mac Office 2016 has been determined. |
|
[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] | Mac Office 15.x/2016 Skype for Business is under evaluation and is currently not approved for production except as part of an official Solution Delivery (SD) production pilot or production test of this version as approved by SD Desktop Technologies team for Windows (email: OIT ITOPS SD EE Desktop and Device Engineering) or SD MAC Support Team for MAC (email: VA IP Mac Team) or an Strategic Technology Alignment Team (STAT) waiver while under evaluation. As of this writing, no deployment date for Mac Office 2016 has been determined. |
|
[11] | 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). |
|
[12] | 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). |
|
[13] | Mac Office 15.x/2016 Skype for Business is under evaluation and is currently not approved for production except as part of an official Solution Delivery (SD) production pilot or production test of this version as approved by SD Desktop Technologies team for Windows (email: OIT ITOPS SD EE Desktop and Device Engineering) or SD MAC Support Team for MAC (email: VA IP Mac Team) or a waiver while under evaluation. As of this writing, no deployment date for Mac Office 2016 has been determined. |
|
[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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. |
|
[15] | 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). |
|
[16] | 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). |
|
[17] | 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). |