2.x |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 5, 6, 7] |
Approved w/Constraints [1, 5, 6, 7] |
Approved w/Constraints [1, 5, 6, 7] |
Approved w/Constraints [6, 7, 8, 9, 10] |
Approved w/Constraints [6, 7, 8, 9, 10] |
Approved w/Constraints [6, 7, 8, 9, 10] |
Approved w/Constraints [6, 7, 8, 9, 10] |
Authorized w/ Constraints [6, 7, 8, 9, 10] |
| | [1] | Per the Initial Product Review, users must abide by the following constraints:
- Ensure the use of FIPS 140-2 validated encryption to protect sensitive data stored on Apache Atlas and when VA sensitive data is transmitted over the network.
- The VA utilizes the risk-based decision process defined in the VA POA&M Management Guide and Accreditation Requirement Guide in accordance with VA Handbook 6500 - Risk Management Framework for VA Information Systems - Tier 3: VA Information Security Program. Please reach out to your ISSO and SS for pre-existing systems to enter a POA&M for the “TRM Unapproved technology”.
- Apache Atlas is an open source product. Patches and critical fixes may not be released in a timely fashion. System owners and administrators should verify Apache Atlas is updated accordingly to help prevent potential critical security issues and unintended loss of data.
Users must not utilized unapproved versions of Python and Maven while running this technology. | | [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] | 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 authorized and the user should take the proper steps to decline those installations. | | [4] | 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. | | [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 ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500. | | [6] | 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. | | [7] | 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. | | [8] | Per the Initial Product Review, users must abide by the following constraints:
- Apache Atlas will require a 3rd party FIPS 140-2 or its successor certified solution for any data containing PHI/PII or VA sensitive information.
- The VA utilizes the risk-based decision process defined in the VA POA&M Management Guide and Accreditation Requirement Guide in accordance with VA Handbook 6500 - Risk Management Framework for VA Information Systems - Tier 3: VA Information Security Program. Please reach out to your ISSO and SS for pre-existing systems to enter a POA&M for the “TRM Unapproved technology”.
- Apache Atlas is an open-source product. Patches and critical fixes may not be released in a timely fashion. System owners and administrators should verify Apache Atlas is updated accordingly to help prevent potential critical security issues and unintended loss of data.
- System owners must ensure they are using the most recent version of Apache Atlas.
Users must not utilized unapproved versions of Python and Maven while running this technology.
Users must not utilize Apache Storm, as it is at the time of writing, unapproved in the TRM. | | [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] | 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. |
|