<Past |
Future> |
7.5 |
Approved w/Constraints [1] |
Approved w/Constraints [1] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
7.5.1 |
Approved w/Constraints [1] |
Approved w/Constraints [1] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
8.0 |
Approved w/Constraints [1] |
Approved w/Constraints [1] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
8.0.1 |
Approved w/Constraints [1] |
Approved w/Constraints [1] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
8.5.5 |
Unapproved |
Unapproved |
Approved w/Constraints [2, 3] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
8.5.6 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
8.5.7 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.6.0 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [1] | Known security vulnerabilities must be properly remediated prior to product deployment. Product must remain properly patched in order to mitigate known and future security vulnerabilities. The runtime dependency for this technology is the WebSphere Application Server which was approved with Constraints. | | [2] | 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.
Veterans Affairs (VA) users must ensure VA sensitive data is protected properly in accordance with VA Handbook 6500 and the Federal Information Security Management Act (FISMA). Per VA Handbook 6500, FIPS 140-2 certified encryption must be used to protect and encrypt data in transit and at rest if Personally Identifiable Information/Protected Health Information/VA (PII/PHI/VA) sensitive information is involved. If FIPS 140-2 certified encryption in not used, additional mitigating controls must be documented in an approved System Security Plan (SSP). In addition, the technology must be implemented within the VA production network (not in a Demilitarized Zone (DMZ)) unless the specific uses and instances of the technology are approved by the Enterprise Security Change Control Board (ESCCB). In these cases, Memorandum of Understanding and Interconnection Security Agreements (MOU/ISA), which detail the security requirements for users and systems that share information and resources outside of the VA production network must be included. | | [3] | 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.
| | [4] | This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards and an ISO Risk Based Decision (RBD) must be approved by the local ISO/CIO before it can be used in the VA Production Environment. In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004, VA Directive 6517
and VA Directive 6513. The local ISO can advise on the ESCCB review process and ensure privacy of information compliance protections are in place. | | [5] | 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. | | [6] | 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. |
|
Note: |
Version 8.6.0 was never a released version of this technology and wad added in error. At the time of writing, the most recently released version for this technology was 8.5.7. Due to technical limitations, version 8.6.0 cannot be removed from the forecast map. |