<Past |
Future> |
8 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.0.1 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
9 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
9.0.1 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
10 |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6, 7] |
Approved w/Constraints [5, 6, 7] |
Approved w/Constraints [5, 6, 7] |
Approved w/Constraints [5, 6, 7] |
Approved w/Constraints [5, 6, 7] |
Approved w/Constraints [6, 7, 8] |
Divest [6, 7, 9] |
Divest [6, 7, 9] |
Divest [6, 7, 9] |
Divest [6, 9, 10] |
10 Update 11 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
11 |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6, 7] |
Approved w/Constraints [5, 6, 7] |
Approved w/Constraints [5, 6, 7] |
Approved w/Constraints [5, 6, 7] |
Approved w/Constraints [5, 6, 7] |
Approved w/Constraints [6, 7, 8] |
Divest [6, 7, 9] |
Divest [6, 7, 9] |
Divest [6, 7, 9] |
Divest [6, 9, 10] |
2016.x |
Unapproved |
Unapproved |
Approved w/Constraints [5, 6, 7] |
Approved w/Constraints [5, 6, 7] |
Approved w/Constraints [5, 6, 7] |
Approved w/Constraints [5, 6, 7] |
Approved w/Constraints [5, 6, 7] |
Approved w/Constraints [6, 7, 8] |
Approved w/Constraints [6, 7, 9] |
Approved w/Constraints [6, 7, 9] |
Approved w/Constraints [6, 7, 9] |
Approved w/Constraints [6, 9, 10] |
2018.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [6, 9, 10] |
2021.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2023.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [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] | Users must utilize version 10 Update 11 or higher due to common vulnerability exposures (CVE-2013-3350 & CVE-2013-3349) associated with older versions and users must ensure that all patches and updates are applied in accordance with VA Handbook 6500 policy. Additionally, users should apply the suggested mitigation strategies listed in the VA-NSOC Bulletin B-13-122 Adobe ColdFusion. | | [3] | Users must utilize version 10 Update 11 or higher due to common vulnerability exposures (CVE-2013-3350 & CVE-2013-3349) associated with older versions and users must ensure that all patches and updates are applied in accordance with VA Handbook 6500 policy. Additionally, users should apply the suggested mitigation strategies listed in the VA-NSOC Bulletin B-13-122 Adobe ColdFusion. | | [4] | 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.
| | [5] | 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. | | [6] | 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. | | [7] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [8] | 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). | | [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). | | [10] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This product can be configured with a MySQL Database which currently has TRM constraints for intranet use only due to its many known security issues. If MySQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High Risk system. Please see the MySQL Database TRM entry for more details. |
|
Note: |
At the time of writing, version 2023 Update 5 is the most current version, released 10/05/2023. |