|
<Past |
Future> |
| 2.3.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) |
| 3.0.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) |
| 3.2.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) |
| 3.3.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) |
| 3.5.x |
DIVEST
[16, 17, 20, 21, 22, 23, 24] |
DIVEST
[16, 17, 20, 21, 22, 23, 24] |
DIVEST
[16, 17, 20, 21, 22, 23, 24] |
Authorized w/ Constraints (DIVEST)
[16, 17, 20, 21, 22, 23, 24] |
Authorized w/ Constraints (DIVEST)
[16, 17, 20, 21, 22, 23, 24] |
Authorized w/ Constraints (DIVEST)
[16, 17, 20, 21, 22, 23, 24] |
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) |
| 3.6.x |
DIVEST
[16, 17, 20, 21, 22, 23, 24] |
DIVEST
[16, 17, 20, 21, 22, 23, 24] |
DIVEST
[16, 17, 20, 21, 22, 23, 24] |
Authorized w/ Constraints (DIVEST)
[16, 17, 20, 21, 22, 23, 24] |
Authorized w/ Constraints (DIVEST)
[16, 17, 20, 21, 22, 23, 24] |
Authorized w/ Constraints (DIVEST)
[16, 17, 20, 21, 22, 23, 24] |
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) |
| 3.7.x |
DIVEST
[16, 17, 20, 21, 22, 23, 24] |
DIVEST
[16, 17, 20, 21, 22, 23, 24] |
DIVEST
[16, 17, 20, 21, 22, 23, 24] |
Authorized w/ Constraints (DIVEST)
[16, 17, 20, 21, 22, 23, 24] |
Authorized w/ Constraints (DIVEST)
[16, 17, 20, 21, 22, 23, 24] |
Authorized w/ Constraints (DIVEST)
[16, 17, 20, 21, 22, 23, 24] |
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) |
| 3.8.x |
Approved w/Constraints
[16, 17, 20, 21, 22, 23, 24] |
Approved w/Constraints
[16, 17, 20, 21, 22, 23, 24] |
Approved w/Constraints
[16, 17, 20, 21, 22, 23, 24] |
Authorized w/ Constraints
[16, 17, 20, 21, 22, 23, 24] |
Authorized w/ Constraints
[16, 17, 20, 21, 22, 23, 24] |
Authorized w/ Constraints
[16, 17, 20, 21, 22, 23, 24] |
Authorized w/ Constraints
[16, 17, 20, 21, 22, 23, 24] |
Authorized w/ Constraints
[16, 17, 20, 21, 22, 23, 24] |
Authorized w/ Constraints
[16, 17, 20, 21, 22, 23, 24] |
Authorized w/ Constraints
[16, 17, 20, 21, 22, 23, 24] |
Authorized w/ Constraints
[16, 17, 20, 21, 22, 23, 24] |
Authorized w/ Constraints
[16, 17, 20, 21, 22, 23, 24] |
| | | | [1] | 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. | | | [2] | Per the Initial Product Review:
Apache James may not be used for any data containing Protected Health Information/Personally Identifiable Information (PHI/PII), or sensitive information;
When using Simple Mail Transfer Protocol (SMTP) , Post Office Protocol (POP3), Internet Message Access Protocol (IMAP), Hypertext Transfer Protocol (HTTP) or other clear-text protocols, James should be configured to apply Secure Sockets Layer/Transport Layer Security encryption;
System owners should disable insecure protocols and ports such as TELNET, and File Transfer Protocol;
VA authorized enterprise mail solution is currently in place and should be leveraged. System owners should reach out to Architecture, Strategy, and Design (ASD) for guidance on mail system implementation to ensure proposed solution aligns with the VA enterprise architecture. | | | [3] | 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. | | | [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] | 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. | | | [6] | Per the Initial Product Review:
Apache James must not be used for any data containing Protected Health Information/Personally Identifiable Information (PHI/PII), or sensitive information;
When using Simple Mail Transfer Protocol (SMTP) , Post Office Protocol (POP3), Internet Message Access Protocol (IMAP), Hypertext Transfer Protocol (HTTP) or other clear-text protocols, James must be configured to apply Secure Sockets Layer/Transport Layer Security encryption;
System owners must disable insecure protocols and ports such as TELNET, and File Transfer Protocol;
VA authorized enterprise mail solution is currently in place and must be leveraged. System owners must reach out to Architecture, Strategy, and Design (ASD) for guidance on mail system implementation to ensure proposed solution aligns with the VA enterprise architecture. | | | [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] | 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). | | | [10] | Per the Initial Product Review:
Apache James must not be used for any data containing Protected Health Information/Personally Identifiable Information (PHI/PII), or sensitive information;
When using Simple Mail Transfer Protocol (SMTP), Post Office Protocol (POP3), Internet Message Access Protocol (IMAP), Hypertext Transfer Protocol (HTTP) or other clear-text protocols, James must be configured to apply Secure Sockets Layer/Transport Layer Security encryption;
System owners must disable insecure protocols and ports such as TELNET, and File Transfer Protocol;
VA authorized enterprise mail solution is currently in place and must be leveraged. System owners must reach out to Architecture, Strategy, and Design (ASD) for guidance on mail system implementation to ensure proposed solution aligns with the VA enterprise architecture. | | | [11] | This technology must not be used for any data containing Personal Health Information/Personal Identification Information (PHI/PII), or sensitive information.
When using Simple Mail Transfer Protocol (SMTP), Post Office Protocol 3 (POP3), Internet Message Access Protocol (IMAP), Hypertext Transfer Protocol (HTTP) or other clear-text protocols, this technology must be configured to apply Secure Sockets Layer (SSL)/ Transport Layer Security (TLS) encryption.
System owners must disable insecure protocols and ports such as TELNET,and File Transfer Protocol (FTP).
VA authorized enterprise mail solution is currently in place and must be leveraged. System owners must reach out to Architecture, Strategy, and Design (ASD) for guidance on mail system implementation to ensure proposed solution aligns with the VA enterprise architecture. | | | [12] | This technology must not be used for any data containing Protected Health Information/Personally Identifiable Information (PHI/PII), or sensitive data.
When using Simple Mail Transfer Protocol (SMTP), Post Office Protocol 3 (POP3), Internet Message Access Protocol (IMAP), Hypertext Transfer Protocol (HTTP), or other clear-text protocols, this technology must be configured to apply Transport Layer Security (TLS) encryption.
System owners must disable insecure protocols and ports such as TELNET and File Transfer Protocol (FTP).
A VA authorized enterprise mail solution is currently in place and must be leveraged. System owners must reach out to Architecture, Strategy, and Design (ASD) for guidance on mail system implementation to ensure a proposed solution aligns with VA enterprise architecture. | | | [13] | This technology must use the latest TRM-authorized version of Java Runtime Environment (JRE) - Oracle.
Per the Initial Product Review, users must abide by the following constraints:
- Apache JAMES should not be used for any data containing Personal Health Information/Personal Identification Information (PHI/PII), or sensitive information.
- When using SMTP, POP3, IMAP, HTTP or other clear-text protocols, JAMES should be configured to apply SSL/TLS encryption.
- System owners should disable insecure protocols and ports such as TELNET, and FTP.
- VA authorized enterprise mail solution is currently in place and should be leveraged. System owners should reach out to Architecture, Strategy, and Design (ASD) for guidance on mail system implementation to ensure the proposed solution aligns with the VA enterprise architecture.
| | | [14] | 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). | | | [15] | 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. | | | [16] | 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. | | | [17] | 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. | | | [18] | 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 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). | | | [19] | 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. | | | [20] | 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. | | | [21] | This technology must use the latest TRM-authorized version of Java Runtime Environment (JRE) - Oracle.
This technology must use the latest TRM-authorized version of Java Development Kit (JDK) - Oracle.
Users must ensure that PostgreSQL, Microsoft Structured Query Language (SQL) Server, and Apache Hypertext Transfer Protocol (HTTP) Server are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
The File Transfer Protocol (FTP) and TELNET features of this software must not be used as the FTP and TELNET protocol is unapproved for use on the VA network. (For further information see: VA Policy Memo VAIQ 7615193 on Prohibited Use of File Transfer Protocol (FTP) and Telnet Services)
Per the Initial Product Review, users must abide by the following constraints:
- Apache JAMES will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing Protected Health Information (PHI)/Personally Identifiable Information (PII) or VA sensitive information. It is important to note that most, if not all, Cloud Service Providers (CSPs) will have data at rest encryption built into the standard product.
- 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 authorized and the user should take the proper steps to decline those installations.
- System administrators must ensure they are using the most recent, TRM authorized, version of Apache JAMES.
| | | [22] | 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. | | | [23] | 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. | | | [24] | 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 3.8.1 is the most current version, released 02/11/2024. |
