| 3.31.x |
Approved w/Constraints
[12, 13, 14, 15, 16] |
Approved w/Constraints
[12, 13, 14, 15, 16] |
Approved w/Constraints
[12, 13, 14, 15, 16] |
Approved w/Constraints
[12, 13, 15, 16, 17] |
Approved w/Constraints
[12, 13, 15, 17, 18] |
Approved w/Constraints
[12, 13, 15, 17, 18] |
Approved w/Constraints
[12, 13, 15, 17, 18] |
Approved w/Constraints
[12, 13, 15, 17, 18] |
Approved w/Constraints
[12, 13, 15, 17, 18] |
Approved w/Constraints
[12, 13, 15, 17, 18] |
Approved w/Constraints
[12, 13, 15, 17, 18] |
Approved w/Constraints
[12, 13, 15, 17, 18] |
| | | | [1] | 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). | | | [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] | 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. | | | [4] | 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. | | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | | [6] | 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). | | | [7] | This technology may only be used to join web-based conferences scheduled by non-organization users (e.g. vendor partners). Once the Avaya AURA Meeting Exchange meeting has concluded, users should uninstall the Avaya AURA Meeting Exchange technology installed on the client system to ensure that only the latest version of the downloaded software is used for each external Blackboard Collaborate Launcher. Veterans Affairs (VA) users MAY NOT schedule Avaya AURA Meeting Exchange conferences, but instead should leverage the organization`s teleconferencing solution of choice, Skype for Business for VA hosted conferences. Teleconferencing should not be used to share desktop(s), transfer user control, or view/modify data with users outside the firewall whom have not obtained proper Department user credentials in compliance with Federal and Department security and privacy requirements. | | | [8] | Users must ensure they are using a TRM-approved version of the Oracle Java Development Kit.
Use of this technology is limited to JOINING external web-based training sessions scheduled by non-organization users (e.g. vendor partners). VA users must leverage the organization`s preferred teleconferencing solution, Skype for Business (Formerly Microsoft Lync), for internal hosted conferences. VA has selected Skype for Business as its preferred teleconferencing solution. No waiver or review is required for JOINING Avaya AURA Meeting Exchange meetings.
Any use of this technology to host a VA event must be authorized by a Strategic Technology Alignment Team (STAT) waiver. There are no exceptions to the required waiver process for any reason. The STAT Board must seek guidance and/or approval from the Enterprise Security Change Control Board (ESCCB) as needed when a waiver is granted to host conferences. | | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | | [10] | 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). | | | [11] | Users must ensure they are using a TRM-approved version of the Oracle Java Development Kit.
Users must ensure that Apache Tomcat, PostgreSQL, Microsoft Excel, Microsoft Internet Explorer (IE), Microsoft Structured Query Language (SQL) Server, Firefox, and Google Chrome are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must Divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details.
Use of this technology is limited to JOINING external web-based training sessions scheduled by non-organization users (e.g. vendor partners). VA users must leverage the organization`s preferred teleconferencing solution, Skype for Business (Formerly Microsoft Lync), for internal hosted conferences. VA has selected Skype for Business as its preferred teleconferencing solution. No waiver or review is required for JOINING Avaya AURA Meeting Exchange meetings.
Any use of this technology to host a VA event must be authorized by a Strategic Technology Alignment Team (STAT) waiver. There are no exceptions to the required waiver process for any reason. The STAT Board must seek guidance and/or approval from the Enterprise Security Change Control Board (ESCCB) as needed when a waiver is granted to host conferences. | | | [12] | 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. | | | [13] | This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle.
Users must ensure that Apache Tomcat, PostgreSQL, Microsoft Excel, and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Use of this technology is limited to JOINING external web-based training sessions scheduled by non-organization users (e.g. vendor partners). VA users must leverage the organization`s preferred teleconferencing solution, Skype for Business (Formerly Microsoft Lync), for internal hosted conferences. VA has selected Skype for Business as its preferred teleconferencing solution. No waiver or review is required for JOINING Avaya AURA Meeting Exchange meetings.
Any use of this technology to host a VA event must be authorized by a Strategic Technology Alignment Team (STAT) waiver. There are no exceptions to the required waiver process for any reason. The STAT Board must seek guidance and/or approval from the Enterprise Security Change Control Board (ESCCB) as needed when a waiver is granted to host conferences. | | | [14] | 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. | | | [15] | 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. | | | [16] | 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). | | | [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. |
|
