| 5.x |
Divest
[2, 12, 13, 14, 15, 16] |
Divest
[2, 12, 13, 14, 15, 16] |
Divest
[2, 12, 13, 14, 15, 16] |
Divest
[12, 14, 15, 16, 17, 18] |
Divest
[12, 14, 15, 16, 17, 18] |
Divest
[12, 14, 15, 16, 17, 18] |
Divest
[12, 14, 15, 16, 17, 18] |
Divest
[12, 14, 15, 16, 17, 18] |
Divest
[12, 14, 17, 18, 19, 20] |
Divest
[12, 14, 17, 18, 19, 20] |
Divest
[12, 14, 17, 18, 19, 20] |
Divest
[12, 14, 17, 18, 19, 20] |
| | | | [1] | 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. | | | [2] | 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. | | | [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] | 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. | | | [5] | The latest version of FIPS-compliant Vocera Communication System software must be used as a precaution to guard against vulnerabilities regarding headset operation, and yet to be identified vulnerabilities.
The Vocera Communication System must be configured for FIPS mode only.
Only FIPS compliant client devices (badges and smartphones) must be used. The B3000n badge is the most current model available that is compliant with FIPS 140-2.
Vocera recommends the use of AES based WPA2-PSK w/ FIPS140-2 deployed in an enclave on its own Virtual Local Area Network (VLAN) and protected by firewalls, Access Control Lists (ACL`s) 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. A Baseline Configuration document must be created to include directions for the setup of Vocera alerts when a system is installed.
As of the writing of the attached Initial Product Review (IPR) the vendor has not made any changes within the current version of the software to fix this issue. Secure Sockets Layer (SSL) and HTTPS must be enabled during install to mitigate this vulnerability.
Upgrade to Apache Tomcat version 7.0.68 / 8.0.32 / 9.0.0.M3 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.
Reconfigure the affected application, if possible, to avoid use of RC4 ciphers. Consider using TLS 1.2 with AES-GCM suites subject to browser and web server support. Download and install Windows Security update 2868725 at https://support.microsoft.com/en-us/kb/2868725.
Upgrade to OpenSSL version 1.0.1t / 1.0.2h or later. Vocera will provide an update to OpenSSL 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. | | | [6] | The latest version of FIPS-compliant Vocera Communication System software must be used as a precaution to guard against vulnerabilities regarding headset operation, and yet to be identified vulnerabilities.
The Vocera Communication System must be configured for FIPS mode only.
Only FIPS compliant client devices (badges and smartphones) must be used. The B3000n badge is the most current model available that is compliant with FIPS 140-2.
Vocera recommends the use of Advanced Encryption Standard (AES) based WPA2-PSK w/ FIPS140-2 deployed in an enclave on its own Virtual Local Area Network (VLAN) and protected by firewalls, Access Control Lists (ACL`s) 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. A Baseline Configuration document must be created to include directions for the setup of Vocera alerts when a system is installed.
As of the writing of the attached Initial Product Review (IPR) the vendor has not made any changes within the current version of the software to fix this issue. Secure Sockets Layer (SSL) and HTTPS must be enabled during install to mitigate this vulnerability.
Users must upgrade to Apache Tomcat version 7.0.68 / 8.0.32 / 9.0.0.M3 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.
Users must reconfigure the affected application, if possible, to avoid use of RC4 ciphers. Consider using TLS 1.2 with AES-GCM suites subject to browser and web server support. Download and install Windows Security update 2868725 at https://support.microsoft.com/en-us/kb/2868725.
Users must upgrade to OpenSSL version 1.0.1t / 1.0.2h or later. Vocera will provide an update to OpenSSL 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. | | | [7] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (contact VA e-mail: [OIT ITOPS SD Engagement Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | | [8] | Per the Initial Product Review, users must abide by the following constraints:
- The latest version of FIPS-compliant Vocera Communication System software must be used as a precaution to guard against vulnerabilities regarding headset operation, and yet to be identified vulnerabilities.
- The Vocera Communication System must be configured for FIPS mode only.
- Only FIPS compliant client devices (badges and smartphones) may be used. The B3000n badge is the most current model available that is compliant with FIPS 140-2.
- Vocera recommends the use of AES based WPA2-PSK w/ FIPS140-2 deployed in an enclave on its own VLAN and protected by firewalls, ACL’s 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 utilities 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 7.0.68 / 8.0.32 / 9.0.0.M3 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.
- Reconfigure the affected application, if possible, to avoid use of RC4 ciphers. Consider using TLS 1.2 with AES-GCM suites subject to browser and web server support. Download and install Windows Security update 2868725 at https://support.microsoft.com/en-us/kb/2868725.
- Upgrade to OpenSSL version 1.0.1t / 1.0.2h or later. Vocera will provide an update to OpenSSL 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.
| | | [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] | This technology is only authorized for use as a secondary communications system and CANNOT be a primary life safety communications system.
It is advised that if
this product is used within the Department of Veterans Affairs (VA) that the
following constraints be applied:
-
The latest version of FIPS-compliant Vocera Communication System software
must be used as a precaution to guard against vulnerabilities regarding
headset operation, and yet to be identified vulnerabilities.
-
The Vocera Communication System must be configured for FIPS mode only.
-
Only FIPS compliant client devices (badges and smartphones) must be used.
The B3000n badge is the most current model available that is compliant with
FIPS 140-2. Vocera V5000 Release Notes Versions 5.1.0 and 5.1.1 are
currently on the “Under Test List” for FIPS 140-2 certification.
-
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.
-
Reconfigure the affected application, if possible, to avoid use of RC4 ciphers.
Consider using TLS 1.2 with AES-Galois Counter Mode (GCM) suites subject
to browser and web server support. Download and install Windows Security
update 2868725 at https://support.microsoft.com/en-us/kb/2868725.
| | | [11] | This technology is only authorized for use as a secondary communications system and CANNOT be a primary life safety communications system.
It is advised that if
this product is used within the Department of Veterans Affairs (VA) that the
following constraints be applied:
-
The latest version of FIPS-compliant Vocera Communication System software
must be used as a precaution to guard against vulnerabilities regarding
headset operation, and yet to be identified vulnerabilities.
-
The Vocera Communication System must be configured for FIPS mode only.
-
Only FIPS compliant client devices (badges and smartphones) must be used.
The B3000n badge is the most current model available that is compliant with
FIPS 140-2. Vocera V5000 Release Notes Versions 5.1.0 and 5.1.1 are
currently on the “Under Test List” for FIPS 140-2 certification.
-
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.
-
Reconfigure the affected application, if possible, to avoid use of RC4 ciphers.
Consider using TLS 1.2 with AES-Galois Counter Mode (GCM) suites subject
to browser and web server support. Download and install Windows Security
update 2868725 at https://support.microsoft.com/en-us/kb/2868725.
Users must ensure that Microsoft Internet Explorer, MySQL, and Apache Tomcat are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
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. | | | [12] | 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. | | | [13] | This technology is only authorized for use as a secondary communications system and CANNOT be a primary life safety communications system.
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.
Users must ensure that Microsoft Internet Explorer (IE), Google Chrome, and Firefox are implemented within VA-approved baselines. | | | [14] | Use of this technology is limited to VA staff charged with ensuring the security of the VA network infrastructure. VA staff performing analysis with this technology need to work closely with system owners and agree on security scanning rules, such as the assets scanned, along the schedule and frequency of those scans. | | | [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] | 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). | | | [17] | This technology is only authorized for use as a secondary communications system and CANNOT be a primary life safety communications system.
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.
Users must ensure that Google Chrome and Firefox are implemented within VA-approved baselines.
Users must Divest the use of Internet Explorer and Apache Tomcat with this technology. Other approved internet browsers are available. See Category Tab for details. | | | [18] | 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. | | | [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] | 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). |
|
