| 8.x |
Approved w/Constraints
[12, 13, 14, 15, 16] |
Approved w/Constraints
[12, 13, 14, 15, 16] |
Approved w/Constraints
[12, 13, 14, 15, 16] |
Approved w/Constraints
[12, 13, 15, 16, 17] |
Approved w/Constraints
[12, 13, 15, 16, 17] |
Approved w/Constraints
[12, 15, 17, 18, 19] |
Approved w/Constraints
[12, 15, 17, 18, 19] |
Approved w/Constraints
[12, 15, 17, 18, 19] |
Approved w/Constraints
[12, 15, 17, 18, 19] |
Approved w/Constraints
[12, 15, 17, 18, 19] |
Approved w/Constraints
[12, 15, 17, 18, 19] |
Approved w/Constraints
[12, 15, 17, 18, 19] |
| | | | [1] | JRE - IBM should be leveraged only on IBM platforms where the Sun JRE is not supported. Users must ensure that all patches and updates are applied in accordance with VA Handbook 6500 policy to mitigate known and future security vulnerabilities involved, or additional mitigating controls must be documented in an approved System Security Plan (SSP). | | | [2] | A waiver from the Architecture and Engineering Review Board (AERB) is required for the use of version 6SR15FP1 or earlier. This technology should be leveraged only on IBM platforms where Oracle Java SE 7 JRE is not supported. | | | [3] | 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. | | | [4] | A waiver from the Architecture and Engineering Review Board (AERB) is required for the use of versions 7R1SR2FP10 and earlier.
This technology must be leveraged only on IBM platforms where the JRE-Oracle is not compatible or when this product is built into TRM-approved IBM technologies. | | | [5] | A waiver from the Architecture and Engineering Review Board (AERB) is required for the use of versions 7R1SR2FP10 and earlier.
This technology must be leveraged only on International Business Machines (IBM) platforms where the Java Runtime Environment (JRE)-Oracle is not compatible or when this product is built into TRM-approved IBM technologies. | | | [6] | 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. | | | [7] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | | [9] | A waiver from the Architecture and Engineering Review Board (AERB) is required for the use of versions 7R1SR2FP10 and earlier.
This technology must be leveraged only on International Business Machines (IBM) platforms where the Java Runtime Environment (JRE)-Oracle is not compatible or when this product is built into TRM-approved IBM technologies. | | | [10] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | | [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] | This technology must be leveraged only on International Business Machines (IBM) platforms where the Java Runtime Environment (JRE)-Oracle is not compatible or when this product is built into TRM-approved IBM technologies. | | | [13] | 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. | | | [14] | 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. | | | [15] | 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. | | | [16] | 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. | | | [17] | 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. | | | [18] | 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. | | | [19] | 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. |
|
