1.4.x |
Approved w/Constraints [4, 5, 10, 11, 12] |
Approved w/Constraints [4, 5, 10, 11, 12] |
Approved w/Constraints [4, 5, 10, 11, 12] |
Approved w/Constraints [4, 5, 10, 12, 13] |
Approved w/Constraints [4, 5, 10, 13, 14] |
Approved w/Constraints [4, 5, 10, 13, 14] |
Approved w/Constraints [4, 5, 13, 14, 15, 16] |
Approved w/Constraints [4, 5, 13, 14, 15, 16] |
Approved w/Constraints [4, 5, 13, 14, 15, 16] |
Approved w/Constraints [4, 5, 13, 14, 15, 16] |
Approved w/Constraints [4, 5, 13, 14, 15, 16] |
Approved w/Constraints [4, 5, 13, 14, 15, 16] |
| | [1] | Users should ensure that Firefox, Google Chrome, and Microsoft Internet Explorer (IE) are implemented within VA-approved baselines.
This product can be configured with a MySQL Database which currently has TRM constraints for intranet use only due to its many known security issues. If MySQL is selected for use with this product, these factors should be considered especially when an instance of this product will be considered a Moderate or High Risk system. See the MySQL Database TRM entry for more details. | | [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] | 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). | | [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] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (yourIT Service Portal:[SNOW Service Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [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] | Users should ensure that Firefox, Google Chrome, and Microsoft Internet Explorer (IE) are implemented within VA-approved baselines.
This product should not be configured with a MySQL Database Community Edition which currently is TRM unapproved due to its many known security issues. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Maria Database is being used, in this Application, and managed as a component (IPR reference provided). | | [9] | Users should ensure that Firefox, Google Chrome, and Microsoft Internet Explorer (IE) are implemented within VA-approved baselines.
Users must Divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details.
This product should not be configured with a MySQL Database Community Edition which currently is TRM unapproved due to its many known security issues.
Maria Database is being used, in this Application, and managed as a component (IPR reference provided).
Per the Initial Product Review, users must abide by the following constraints:
- The Vocera Communications Platform must be configured for FIPS mode only.
- Only FIPS certified client devices (badges and smartphones) must be used.
The Vocera V5000 Smartbadge has achieved FIPS certification # 3865. The B3000n FIPS module expired on 4/17/2021 but the replacement is in “review pending” status. The replacement module is listed at https://csrc.nist.gov/Projects/cryptographic-module-validation-program/modules-in-process/Modules-In-Process-List. Sites using the B3000n must complete a local POA&M to continue to use these devices and only procure the devices utilizing the Vocera Cryptographic Module 3.1 once the FIPS certification is finalized and certificate number is issued.
- Vocera recommends the use of Advanced Encryption Standards (AES) based WIFI-Protected Access 2- Pre-Shared Key (WPA2-PSK) with FIPS 140-2 deployed in an enclave on its own Virtual Local Area Network (VLAN) and protected by firewalls, Access Control Lists (ACLs) and other network boundary traffic controls. With this network isolation implemented and the use of industry standard components, the risk of not having a finalized threat model is minimized. Standard network application monitoring tools can be used to monitor the system (Windows) and the specific resource usage of the application. Vocera does provide an e-mail alert system for system events and this can be configured to send e-mails for significant system events and
should be utilized
- Upgrade to Apache Tomcat version 8.5 / 9.x or later. Vocera will provide an Apache Tomcat update in the next maintenance release. Additional mitigation is to deploy the Vocera solution behind site firewall and VLAN. This will limit access to Vocera Server resources to only individual allowed to be on the site network. Further mitigation is to limit (via official assignment) access to the Vocera servers and web consoles to Vocera administrators only.
- This issue is resolved in Vocera Platform 6. System owners must up upgrade to the latest version of Vocera to ensure the use of secure ciphers.
- System owners should use the most up to date version of Apache Spark on the Vocera Analytic Server as the older versions (2.3.3 and earlier) can allow data to be written to disk unencrypted when encryption is enabled.
- The Vocera Communications Platform will need to be isolated on a SDIA if
any of the following apply:
Requirements for isolation:
- Vocera servers cannot follow VA approved baselines.
- The servers cannot be managed in a SCCM environment.
- Status of McAfee availability for systems.
- TRM approved status.
- The solution uses or requires external connections.
- The vendor offers a remote support option.
| | [10] | Users should ensure that Apache Tomcat, Firefox and Google Chrome are implemented within VA-approved baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details.
This product should not be configured with a MySQL Database Community Edition which currently is TRM unapproved due to its many known security issues.
Maria Database is being used, in this Application, and managed as a component (IPR reference provided).
Per the Initial Product Review, users must abide by the following constraints:
- The Vocera Communications Platform must be configured for FIPS mode only.
- Vocera recommends the use of Advanced Encryption Standards (AES) based WIFI-Protected Access 2- Pre-Shared Key (WPA2-PSK) with FIPS 140-2 deployed in an enclave on its own Virtual Local Area Network (VLAN) and protected by firewalls, Access Control Lists (ACLs) and other network boundary traffic controls. With this network isolation implemented and the use of industry standard components, the risk of not having a finalized threat model is minimized. Standard network application monitoring tools can be used to monitor the system (Windows) and the specific resource usage of the application. Vocera does provide an e-mail alert system for system events and this can be configured to send e-mails for significant system events and should be utilized.
- Upgrade to Apache Tomcat version 8.5 / 9.x or later. Vocera will provide an Apache Tomcat update in the next maintenance release. Additional mitigation is to deploy the Vocera solution behind site firewall and VLAN. This will limit access to Vocera Server resources to only individual allowed to be on the site network. Further mitigation is to limit (via official assignment) access to the Vocera servers and web consoles to Vocera administrators only.
- This issue is resolved in Vocera Platform 6. System owners must upgrade to the latest version of Vocera to ensure the use of secure ciphers.
- System owners should use the most up to date version of Apache Spark on the Vocera Analytic Server as the older versions (2.3.3 and earlier) can allow data to be written to disk unencrypted when encryption is enabled.
- The Vocera Communications Platform will need to be isolated if any of the following apply:
Requirements for isolation:
•Vocera servers cannot follow VA approved baselines.
•The servers cannot be managed in a SCCM environment.
•Status of McAfee availability for systems.
•TRM approved status.
•The solution uses or requires external connections.
•The vendor offers a remote support option.
A SNOW ticket must be submitted to the Specialized Device Security Division and ACL COMM Profile assigned to the system. | | [11] | 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. | | [12] | 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). | | [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 both VA Handbook 6500 and VA Directive 6500. | | [14] | 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. | | [15] | Users should ensure that Firefox and Google Chrome are implemented within VA-approved baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Maria Database is being used, in this Application, and managed as a component (IPR reference provided).
Users must not utilize Vocera Engage Platform, as it is at the time of writing, unapproved in the TRM.
Per the Initial Product Review, users must abide by the following constraints:
- The Vocera Communications Platform must be configured for FIPS mode only.
- Vocera recommends the use of Advanced Encryption Standards (AES) based WIFI-Protected Access 2- Pre-Shared Key (WPA2-PSK) with FIPS 140-2 deployed in an enclave on its own Virtual Local Area Network (VLAN) and protected by firewalls, Access Control Lists (ACLs) and other network boundary traffic controls. With this network isolation implemented and the use of industry standard components, the risk of not having a finalized threat model is minimized. Standard network application monitoring tools can be used to monitor the system (Windows) and the specific resource usage of the application. Vocera does provide an e-mail alert system for system events and this can be configured to send e-mails for significant system events and should be utilized.
- Upgrade to Apache Tomcat version 8.5 / 9.x or later. Vocera will provide an Apache Tomcat update in the next maintenance release. Additional mitigation is to deploy the Vocera solution behind site firewall and VLAN. This will limit access to Vocera Server resources to only individual allowed to be on the site network. Further mitigation is to limit (via official assignment) access to the Vocera servers and web consoles to Vocera administrators only.
- This issue is resolved in Vocera Platform 6. System owners must upgrade to the latest version of Vocera to ensure the use of secure ciphers.
- System owners should use the most up to date version of Apache Spark on the Vocera Analytic Server as the older versions (2.3.3 and earlier) can allow data to be written to disk unencrypted when encryption is enabled.
- The Vocera Communications Platform will need to be isolated if any of the following apply:
Requirements for isolation:
•Vocera servers cannot follow VA approved baselines.
•The servers cannot be managed in a SCCM environment.
•Status of McAfee availability for systems.
•TRM approved status.
•The solution uses or requires external connections.
•The vendor offers a remote support option.
A SNOW ticket must be submitted to the Specialized Device Security Division and ACL COMM Profile assigned to the system. | | [16] | 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. |
|