<Past |
Future> |
1.3.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.0.x |
Divest [3, 4, 5] |
Divest [3, 4, 5] |
Divest [3, 4, 5, 6] |
Divest [3, 4, 5, 6] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.1.x |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 4, 5] |
Divest [3, 4, 5, 6] |
Divest [3, 4, 5, 6] |
Divest [3, 4, 5, 6] |
Divest [3, 4, 5, 6] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.3.x |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 4, 5, 6] |
Approved w/Constraints [3, 4, 5, 6] |
Divest [3, 4, 5, 6] |
Divest [3, 4, 5, 6] |
Divest [3, 4, 5, 6] |
Divest [3, 5, 6, 7] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.4.x |
Unapproved |
Unapproved |
Approved w/Constraints [3, 4, 5, 6] |
Approved w/Constraints [3, 4, 5, 6] |
Approved w/Constraints [3, 4, 5, 6] |
Approved w/Constraints [3, 4, 5, 6] |
Approved w/Constraints [3, 4, 5, 6] |
Approved w/Constraints [3, 5, 6, 7] |
Divest [5, 7, 8, 9] |
Divest [5, 7, 8, 9] |
Divest [5, 7, 9] |
Divest [5, 7, 9] |
2.6.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [5, 7, 8, 9] |
Approved w/Constraints [5, 7, 8, 9] |
Approved w/Constraints [5, 7, 9] |
Approved w/Constraints [5, 7, 9] |
3.0.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [5, 7, 9] |
Approved w/Constraints [5, 7, 9] |
3.1.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [1] | At time of writing, product does not provide native data at rest encryption. This technology should not be used to store PII/PHI sensitive data, unless used with third-party FIPS 140-2 validated encryption products. | | [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] | At the time of writing, the technology does not provide native data at rest encryption. This technology should not be used to store Personally Identifiable Information (PII) / Protected Health Information (PHI) sensitive data unless used with third-party FIPS 140-2 validated encryption products. | | [4] | 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. | | [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] | 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. | | [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] | At the time of writing, the technology does not provide native data at rest encryption. This technology must not be used to store Personally Identifiable Information (PII) / Protected Health Information (PHI) sensitive data unless used with third-party FIPS 140-2 validated encryption products. | | [9] | 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). |
|
Note: |
At the time of writing, version 3.1.5.6189-1 is the latest version of this technology. |