| 1.8.x |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6, 7, 8, 9] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6, 7, 8, 9] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6, 7, 8, 9] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6, 7, 8, 9] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6, 7, 8, 9] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6, 7, 8, 9] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6, 7, 8, 9] |
| | | | [1] | Users must not utilize Apache Spark, as it, at the time of writing, requires a POA&M.
Users must not utilize Amazon Web Services (AWS) Software Development Kit (SDK) for Java, as it, at the time of writing, requires a POA&M.
This technology must use the latest TRM-authorized version of Java Runtime Environment (JRE) - Oracle.
Users must ensure that My Structured Query Language (MySQL) Database - Commercial Editions and PostgreSQL are implemented with VA-approved baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Initial Product Review, users must abide by the following constraints:
- Apache Iceberg will require a 3rd party FIPS 140-2 (or its successor) certified
solution for any data containing PHI/PII or VA sensitive information.
- Users should check with their supervisor, 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. Support for open-source software can vary so, it is important to
note that support services need to be maintained for this product. System
owners should review the One-VA Technical Reference Model (TRM) entries
for the approved versions for use of JRE.
- Apache Iceberg is designed to run in “trusted environments”, and the
database does not enable authentication or “Secure Mode” by default.
- VA must develop a policy that users must not use, disclose, transmit or
otherwise process any PII/PHI as defined in Health Insurance Portability and
Accountability Act (HIPAA) through Apache Iceberg.
| | | [2] | 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). | | | [3] | If this product uses a MySQL database, the product must be configured with a commercial edition of the MySQL Database, which currently has TRM constraints limiting its use for intranet and non-sensitive data only due to its many known security issues. If a commercial edition of 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. See MySQL Database – Commercial Edition TRM entry for more details. | | | [4] | This product can be configured with a PostgreSQL Database, which currently has TRM constraints limiting its use to Red Hat Enterprise Linux (RHEL) only due to its many known security issues on other platforms. If PostgreSQL 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. See PostgreSQL Database TRM entry for more details. | | | [5] | 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. | | | [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 ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500. | | | [7] | 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. | | | [8] | 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. | | | [9] | 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. |
|
