|
[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] | 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. |
|
[3] | No new acquisitions or installations of vSphere Hypervisor (free edition) are allowed in VA after 9/30/2015 because of the replication and visibility limitations with this free edition.
No new acquisitions or installations of vSphere Essentials Kits are allowed in VA after 9/30/2015 due to the limitations of the Hypervisor edition used by these kits.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. |
|
[4] | Due to potential information security risks, cloud based versions of this product are not permitted without a waiver signed by the Deputy CIO of ASD based upon a recommendation from the Architecture and Engineering Review Board (AERB). In addition, cloud based features of this software may not be used without an Enterprise Security Change Control Board (ESCCB) approval to ensure that confidential organization and/or PII/PHI data are not compromised (ref: VA Directive 6004, VA Directive 6517 and VA Directive 6513). Use of public cloud storage requires documented Federal Risk and Authorization Management Program (FedRAMP) compliance and a Memorandum of Understanding / Interconnection Security Agreement (MOU/ISA) between the vendor and VA prior to ESCCB review. |
|
[5] | 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. |
|
[6] | No new acquisitions or installations of vSphere Hypervisor (free edition) are allowed in VA after 9/30/2015 because of the replication and visibility limitations with this free edition.
No new acquisitions or installations of vSphere Essentials Kits are allowed in VA after 9/30/2015 due to the limitations of the Hypervisor edition used by these kits.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Configuration baseline and deployment standards for this technology that are maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering (ESE) must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information. |
|
[7] | No new acquisitions or installations of vSphere Hypervisor (free edition) are allowed in VA after 9/30/2015 because of the replication and visibility limitations with this free edition.
No new acquisitions or installations of vSphere Essentials Kits are allowed in VA after 9/30/2015 due to the limitations of the Hypervisor edition used by these kits.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Configuration baseline and deployment standards for this technology that are maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering (ESE) must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information |
|
[8] | Due to potential information security risks, cloud based technologies may not be used without an Enterprise Security Change Control Board (ESCCB) approval. 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). |
|
[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] | Due to potential information security risks, cloud based technologies may not be used without the approval of the VA Enterprise Cloud Services (ECS) Group. 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). |
|
[11] | 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. |
|
[12] | No new acquisitions or installations of vSphere Hypervisor (free edition) are allowed in VA after 9/30/2015 because of the replication and visibility limitations with this free edition.
No new acquisitions or installations of vSphere Essentials Kits are allowed in VA after 9/30/2015 due to the limitations of the Hypervisor edition used by these kits.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Configuration baseline and deployment standards for this technology that are maintained by the Infrastructure Engineering organization within VA ITOPS Solution Delivery (SD) must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information |
|
[13] | 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). |
|
[14] | No new acquisitions or installations of vSphere Hypervisor (free edition) are allowed in VA after 9/30/2015 because of the replication and visibility limitations with this free edition.
No new acquisitions or installations of vSphere Essentials Kits are allowed in VA after 9/30/2015 due to the limitations of the Hypervisor edition used by these kits.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Configuration baseline and deployment standards for this technology that are maintained by the Infrastructure Engineering organization within VA Information Technology Operations and Services (ITOPS) Solution Delivery (SD) must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information |
|
[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] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Version 7.0 of VMware vSphere is currently under evaluation and only Solution Delivery Platform Engineering may use or authorize the technology until the VA baseline for VMware vSphere is published. |
|
[17] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Configuration baseline and deployment standards for this technology that are maintained by the Infrastructure Engineering organization within VA Information Technology Operations and Services (ITOPS) Solution Delivery (SD) must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information.
Version 7.0 of VMware vSphere is currently under evaluation and only Solution Delivery Platform Engineering may use or authorize the technology until the VA baseline for VMware vSphere is published. |
|
[18] | 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. |
|
[19] | 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). |
|
[20] | 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). |
|
[21] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Configuration baseline and deployment standards for this technology that are maintained by the Infrastructure Engineering organization within VA Information Technology Operations and Services (ITOPS). Solution Delivery (SD) must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information. |
|
[22] | 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. |
|
[23] | 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). |
|
[24] | 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. |
|
[25] | 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. |
|
[26] | 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. |
|
[27] | 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. |
|
[28] | The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website. |
|
[29] | 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, visit the Product Marketplace.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). |