7.5.x |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
7.6.x |
Approved w/Constraints [11, 20, 21, 23, 24, 25] |
Approved w/Constraints [11, 20, 21, 23, 24, 25] |
Approved w/Constraints [11, 20, 21, 23, 24, 25] |
Authorized w/ Constraints [11, 20, 21, 23, 24, 25] |
Authorized w/ Constraints [11, 20, 21, 23, 24, 25] |
Authorized w/ Constraints [11, 20, 21, 23, 24, 25] |
Authorized w/ Constraints [11, 20, 21, 23, 24, 25] |
Authorized w/ Constraints [11, 20, 21, 23, 24, 25] |
Authorized w/ Constraints [11, 20, 21, 23, 24, 25] |
Authorized w/ Constraints [11, 20, 21, 23, 24, 25] |
Authorized w/ Constraints [11, 20, 21, 23, 24, 25] |
Authorized w/ Constraints [11, 20, 21, 23, 24, 25] |
| | [11] | Per the Initial Product Review, users must abide by the following constraints:
- Ensure the middleware that provides FIPS encryption is properly configured so that sensitive data collected and processed with IBM Maximo is encrypted IPR – IBM Maximo
June 20, 2019 For Internal VA Use Only Page 4 of 8 with a FIPS 140-2 validated cryptographic module. VA Handbook 6500, SC-28: Protection of Information at Rest requires that database management systems used in VA are encrypted using FIPS 140-2 validated encryption. Failure to employ the required cryptographic mechanism for VA database management systems will affect the security posture of the VA and potentially could be exploited by malicious users that could lead to unintended access.
- Ensure the use of a VA authorized database to ensure the server adheres to security hardening standards located on the VA Baseline Configuration Management website.
- Use the latest supported version of the Java platform.
- Due to known vulnerabilities in older versions including v7.6.1, users are advised to be on the lookout for later versions and are advised to regularly check vendor and CVE sites for security updates on reported vulnerabilities and associated fixes.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Oracle Database and Microsoft Structured Query Language (SQL) Server are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [20] | 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 authorized and the user should take the proper steps to decline those installations. | | [21] | 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. | | [23] | 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. | | [24] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 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 or its successor 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 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device 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 System Security Officer (ISSO) 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). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes. | | [25] | 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). |
|