|
<Past |
Future> |
| 13.1 (Windows) |
Divest
[11, 12, 13, 14, 15, 16] |
Divest
[11, 12, 13, 14, 15, 16] |
Divest
[11, 12, 13, 14, 15, 16] |
Divest
[11, 12, 14, 15, 16, 17] |
Divest
[11, 12, 14, 16, 17, 18] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| 14.1 (Windows) |
Approved w/Constraints
[11, 12, 13, 14, 15, 16] |
Approved w/Constraints
[11, 12, 13, 14, 15, 16] |
Approved w/Constraints
[11, 12, 13, 14, 15, 16] |
Approved w/Constraints
[11, 12, 14, 15, 16, 17] |
Approved w/Constraints
[11, 12, 14, 16, 17, 18] |
Approved w/Constraints
[11, 12, 14, 16, 17, 18] |
Approved w/Constraints
[11, 12, 14, 16, 17, 18] |
Approved w/Constraints
[11, 12, 14, 16, 17, 18] |
Approved w/Constraints
[11, 12, 14, 16, 17, 18] |
Approved w/Constraints
[11, 12, 14, 16, 17, 18] |
Approved w/Constraints
[11, 12, 14, 16, 17, 18] |
Approved w/Constraints
[11, 12, 14, 16, 17, 18] |
| 13R1 (Linux) |
Divest
[11, 12, 13, 14, 15, 16] |
Divest
[11, 12, 13, 14, 15, 16] |
Divest
[11, 12, 13, 14, 15, 16] |
Divest
[11, 12, 14, 15, 16, 17] |
Divest
[11, 12, 14, 16, 17, 18] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| 14R1 (Linux) |
Approved w/Constraints
[11, 12, 13, 14, 15, 16] |
Approved w/Constraints
[11, 12, 13, 14, 15, 16] |
Approved w/Constraints
[11, 12, 13, 14, 15, 16] |
Approved w/Constraints
[11, 12, 14, 15, 16, 17] |
Approved w/Constraints
[11, 12, 14, 16, 17, 18] |
Approved w/Constraints
[11, 12, 14, 16, 17, 18] |
Approved w/Constraints
[11, 12, 14, 16, 17, 18] |
Approved w/Constraints
[11, 12, 14, 16, 17, 18] |
Approved w/Constraints
[11, 12, 14, 16, 17, 18] |
Approved w/Constraints
[11, 12, 14, 16, 17, 18] |
Approved w/Constraints
[11, 12, 14, 16, 17, 18] |
Approved w/Constraints
[11, 12, 14, 16, 17, 18] |
| | | | [1] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users are not authorized to connect to databases that utilize MySQL databases, as the driver that allows connection with this technology (MySQL Open Database Connectivity (ODBC) Driver) is unapproved for use by the TRM.
Users must ensure that Firefox, Microsoft .NET Framework, Microsoft Internet Explorer (IE), Microsoft Structured Query Language (SQL) Server, My Structured Query Language (MySQL) Database - Commercial Editions, and Oracle Database are implemented within VA-approved baselines.
This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle.
Per the Initial Product Review, users must abide by the following constraints:
- Business Information Server must be run on VA standard desktops and servers as it relies on the underlying operating system for encryption.
- Users should consult the VA Technical Reference Model (TRM) to ensure that
the JRE version that they plan to use with this technology is approved. JRE
1.6x is Unapproved or Prohibited based on the exact version number, and
multiple versions of 1.7x are listed as either Divest, Unapproved or Prohibited.
Divest: VA has decided to divest itself on the use of the technology/standard.
As a result, all projects currently utilizing the technology/standard must plan to
eliminate their use of the technology/standard. Additional information on when
the entry is projected to become unapproved may be found on the Decision tab
for the specific entry. Unapproved: 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, ISO and SS for pre-existing systems to enter a high or
higher POA&M for the “TRM Unapproved technology”. Prohibited: The technology/standard is not (currently) permitted to be used under any
circumstances.
- Firefox version 68.x should be the only browser used as all other supported
browsers are listed Divest or Unapproved in the VA Technical Reference Model
(TRM) v20.7. Divest: VA has decided to divest itself on the use of the
technology/standard. As a result, all projects currently utilizing the
technology/standard must plan to eliminate their use of the
technology/standard. Additional information on when the entry is projected to
become unapproved may be found on the Decision tab for the specific entry.
Unapproved: 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, ISO and SS for pre-existing systems to enter a high or higher
POA&M for the “TRM Unapproved 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 approved and the user should take the proper steps to decline those installations. | | | [4] | 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). | | | [5] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process. | | | [6] | This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004, VA Directive 6517
and VA Directive 6513. The local ISO can advise on the ESCCB review process and ensure privacy of information compliance protections are in place. | | | [7] | 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. | | | [8] | 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). | | | [9] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process. | | | [10] | This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004, VA Directive 6517
and VA Directive 6513. The local ISO can advise on the ESCCB review process and ensure privacy of information compliance protections are in place. | | | [11] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Microsoft Structured Query Language (SQL) Server, Microsoft Internet Information Services (IIS), and Oracle Database are implemented within VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle.
This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle.
Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details.
Per the Initial Product Review, users must abide by the following constraints:
- Business Information Server will require a 3rd party FIPS 140-2 certified encryption solution on VA standard desktops and servers where applicable.
- Users should consult the VA Technical Reference Model (TRM) to ensure that the JRE version that they plan to use with this technology is approved. Certain versions are listed as Divest, Unapproved, or Prohibited in the VA Technical Reference Model depending on the specific version number. Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry. Unapproved: 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, ISO and SS for pre-existing systems to enter a high or higher POA&M for the “TRM Unapproved technology”. Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
- Business Information Server must only utilize the TRM approved Commercial Edition of MySQL. System administrators to continuously monitor vendor documentation to determine the latest upgrades for MySQL that are compatible with Business Information Server..
| | | [12] | 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. | | | [13] | 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. | | | [14] | 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. | | | [15] | 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). | | | [16] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISSO (Information System Security Officer) can advise on the ESCCB review process. | | | [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] | 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. |
|
| Note: |
At the time of writing, version 14.1 (Windows) and 14R1 (Linux) is the most current version, released 06/01/2020. |
