<Past |
Future> |
10.3 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
11.x |
Approved w/Constraints [4, 6, 7, 8] |
Approved w/Constraints [4, 6, 7, 8] |
Approved w/Constraints [4, 6, 7, 8] |
Approved w/Constraints [4, 6, 7, 9] |
Divest [4, 6, 7, 9, 10, 11] |
Divest [4, 6, 7, 9, 10, 11] |
Divest [4, 6, 7, 9, 10, 11] |
Divest [4, 6, 7, 9, 10, 11] |
Divest [4, 6, 7, 9, 10, 11] |
Divest [4, 6, 7, 9, 10, 11] |
Unapproved |
Unapproved |
12.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [4, 6, 7, 9, 10, 11] |
Approved w/Constraints [4, 6, 7, 9, 10, 11] |
Approved w/Constraints [4, 6, 7, 9, 10, 11] |
Approved w/Constraints [4, 6, 7, 9, 10, 11] |
Approved w/Constraints [4, 6, 7, 9, 10, 11] |
Approved w/Constraints [4, 6, 7, 9, 10, 11] |
Approved w/Constraints [4, 6, 7, 9, 10, 11] |
Approved w/Constraints [4, 6, 7, 9, 10, 11] |
| | [1] | This technology must use the latest version of Java Runtime Environment (JRE) - Oracle.
Users must ensure that Microsoft Internet Information Service (IIS) is implemented with VA-approved baselines. | | [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] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (contact VA e-mail: [OIT ITOPS SD Engagement Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | [4] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (yourIT Service Portal:[SNOW Service Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | [5] | 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. | | [6] | This technology must use the latest version of Java Runtime Environment (JRE) - Oracle.
Users must ensure that Apache Hypertext Transfer Protocol (HTTP) Server and Microsoft Internet Information Service (IIS) are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [7] | 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. | | [8] | 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. | | [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 ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500. | | [10] | 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). | | [11] | 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. |
|
Note: |
At the time of writing, version 12.2 is the most current version released. |