Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.11

Vocera Analytics

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Vocera Analytics is a technology that provides data analysis, trends, dashboards, and reports to customers along with the capability to customize reports, trigger outbound communications based on a rule set, and schedule timed distribution of offline reports. This technology, while independent, integrates with and supports both Vocera Communications System (Legacy) and Vocera Communications Platform. Note: This application uses a specialized integrated instance of MariaDB which needs to be noted as a unique instance for this use only.
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v24.8
Decision Date:	08/07/2024 at 15:52:39 UTC
Aliases:	Vocera Analytics Server, Vocera Analytics Suite
Introduced By:	TRM Request
Vendor Name:	Stryker

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

You must be logged into the RSAA website prior to clicking the Attestation URLs or the URLs won't open.

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
1.0.x	05/18/2018
1.1.x
1.2.x	11/01/2019
1.3.x	06/01/2021
1.4.x	06/16/2022

Current Decision Matrix (07/29/2024)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VAIT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported.

Legend:

White	Authorized: The technology/standard has been authorized for use.
Yellow	Authorized w/ Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Authorized w/ Constraints (POA&M): This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Authorized w/ Constraints (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 unauthorized may be found on the Decision tab for the specific entry.
Black	Unauthorized: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Authorized w/ Constraints (PLANNING/EVALUATION): The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology authorized with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology authorized with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

Any major.minor version that is not listed in the VA Decision Matrix is considered Authorized w/ Constraints (POA&M).

<Past

CY2022

CY2023

CY2024

Future>

Release

1.0.x

Unapproved

1.1.x

Unapproved

1.2.x

DIVEST
[3, 5, 6, 7, 9]

Unapproved

1.3.x

Approved w/Constraints
[3, 5, 6, 7, 9]

DIVEST
[3, 5, 6, 7, 10]

DIVEST
[3, 5, 10, 11, 12]

DIVEST
[3, 5, 10, 12, 13]

Unapproved

1.4.x

Unapproved

Approved w/Constraints
[3, 5, 6, 7, 10]

Approved w/Constraints
[3, 5, 10, 11, 12]

Approved w/Constraints
[3, 5, 10, 12, 13]

Approved w/Constraints
[3, 5, 10, 13, 14]

Approved w/Constraints
[3, 5, 13, 14, 15, 16]

Decision Constraints


[1]	Users should ensure that Firefox, Google Chrome, and Microsoft Internet Explorer (IE) are implemented within VA-authorized 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]	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.

[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]	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-authorized 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-authorized baselines. Users must Divest the use of Internet Explorer with this technology. Other authorized 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 authorized baselines. The servers cannot be managed in a SCCM environment. Status of McAfee availability for systems. TRM authorized 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-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’) Users must utilize authorized 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 authorized baselines. •The servers cannot be managed in a SCCM environment. •Status of McAfee availability for systems. •TRM authorized 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-authorized 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. This technology should not be used with Open Java Development Kit (OpenJDK) as it is unapproved for use at this time. There are other authorized java environments available. See Category tab for details. Users must Divest the use of Vocera Communications Platform with this technology. 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. 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. Vocera Communications Platform should only be considered when a VA authorized solution does not meet the necessary requirements, and the use for more specialized tools are warranted. This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology. (Ref: FAQs on `Complying with the TRM` for information on Decisions and POA&M Compliance Enforcement. The Vocera Communications Platform will need to be isolated if any of the following apply: Requirements for isolation: •Vocera servers cannot follow VA authorized baselines. •The servers cannot be managed in a SCCM environment. •Status of McAfee availability for systems. •TRM authorized status. •The solution uses or requires external connections. •The vendor offers a remote support option.

[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.

Note:

At the time of writing, version 1.4.3 is the most current version, released 06/14/2024.

Name	Description
Maria Database (DB)	MariaDB is a relational database and a functional subcomponent of the Vocera Analytics application under the Vocera Communications System. The MariaDB is deployed automatically as part of the Analytics build and is not independently accessible, updateable or managed via user id/pw. This db will be updated by the vendor as part of updates to the analytics element as part of regular updates. There are no options to use an external db for this system.
Zulu build of Open Java Development Kit (OpenJDK)	Zulu 8.78.0.19 is a component of this technology that is managed by the vendor. Zulu is an open source Java


Collaboration and Electronic Workplace Collaboration Software	Unified Messaging

General Analysis

Adoption Benefits

This is a well-documented technology.
At the time of writing, no National Institute of Standards and Technology (NIST) vulnerabilities had been reported and no VA Cyber Security Operations Center (CSOC) bulletins had been issued for the latest versions of this technology.
There are minimal other TRM-authorized technologies that provide the same functionality.
This technology may improve productivity for specific staff whose responsibilities include reporting data.

Adoption Risks

This technology can integrate with and alter database technologies.
Vocera Communications Platform, an optional dependency of this technology, is in a divested state at the time of writing.
This technology can potentially use Open Java Development Kit (OpenJDK), a protocol which requires a POA&M for use on the VA network.
IPR/SAR Adoption Risk - The Vocera Analytics Server includes a packaged and managed installation of MariaDB which is Unapproved in the TRM.
IPR/SAR Adoption Risk - Vocera Communications Platform is now Divest status in the TRM as of Q3 2024. There are VA authorized technologies with similar functionality.
Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
The potential exists to store Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive data and proper security standards must be followed in these cases.
This technology may transmit data over the VA Wide Area Network (WAN).
The Vocera Communications Platform supports communication modes and protocols that are not FIPS compliant.
The vendor does not provide a threat model to validate that the system mitigates according to the Defense Information System Agency (DISA) Application Security and Development Security Technical Implementation Guide (STIG):
1. Disable or remove unneeded services
2. Enable disk quotas if available
3. Monitor the system to detect low resource condition
4. Limit the total number of concurrent sessions for a single user
The remote Apache Tomcat web server is affected by an information disclosure vulnerability in the index page of the Manager and Host Manager applications. An unauthenticated, remote attacker can exploit this vulnerability to obtain a valid cross-site request forgery (XSRF) token during the redirect issued when requesting /manager/ or /host-manager/. This token can be utilized by an attacker to construct an XSRF attack. Note that there are reportedly several additional vulnerabilities; however, Nessus has not tested for these.
In older versions of Vocera the remote host supports the use of Rivest Cipher 4 (RC4) in one or more cipher suites. The RC4 cipher is flawed in its generation of a pseudo-random stream of bytes so that a wide variety of small biases are introduced into the stream, decreasing its randomness. If plaintext is repeatedly encrypted (e.g., HTTP cookies), and an attacker can obtain many (i.e., tens of millions) ciphertexts, the attacker may be able to derive the plaintext.
If any components of the Vocera Communications Platform meet requirements for isolation, the system will need to be isolated.
This technology can potentially use Vocera Engage Platform, an unapproved technology.

Architectural Benefits

This technology is compatible with virtual machines, therefore consistent with the enterprise Server Virtualize First Policy (VAIQ 7266972 08-27-2012).

Architectural Risks

This technology does not use a VA-preferred database to store data.
This technology is not portable as it runs only on Windows platforms.

- The information contained on this page is accurate as of the Decision Date (08/07/2024 at 15:52:39 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.11

General Information

Vendor Release Information

Current Decision Matrix (07/29/2024)

Decision Constraints

References

Technology Components

VA Categories

View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.11

General Information

Vendor Release Information

Current Decision Matrix (07/29/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES

VA Categories

View the VA Categorization Framework