Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.7

NVivo

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:	NVivo is a qualitative data analysis (QDA) software for researchers dealing with unstructured data, such as text and multimedia. The product is designed to help users organize and analyze large volumes of non-numerical, unstructured data to identify trends and test theories. Note: QSR International merged with other companies to form Lumivero. This product is now owned by Lumivero. At the time of writing, NVivo products include: NVivo Windows, NVivo Mac, NVivo Collaboration Server, Cloud Modules and Supplementary add-ons. This assessment includes: NVivo Windows, NVivo Mac and prior version NVivo 12 Plus for Windows, which includes access to macOS. The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g., VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e., SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO
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 been assessed by the Section 508 Office and found non-conformant. 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. Please see reference tab for more information concerning product versions.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v24.3
Decision Date:	03/13/2024 at 17:14:31 UTC
Aliases:	NVivo 12 Plus
Introduced By:	SCCM
Vendor Name:	Lumivero

Vendor Release Information

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

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
Win 9.x	10/21/2010
Win 10.x	06/02/2012
Win 11.x	09/30/2015
Mac 11.x	06/30/2014
Win 12.x	05/07/2019
Mac 12.x	05/01/2019
Mac 1.x	03/18/2020
Win 1.x	03/18/2020
Win 14.x	07/01/2023
Mac 14.x	10/01/2023

Current Decision Matrix (03/07/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 VA IT 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. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved 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	Unapproved: 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	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.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint: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 approved 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 approved 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.

<Past

CY2020

CY2021

CY2022

Future>

Release

Win 9.x

Unapproved

Win 10.x

Unapproved

Win 11.x

Unapproved

Mac 11.x

Unapproved

Win 12.x

Approved w/Constraints
[1, 3, 7, 8]

Divest
[1, 3, 5, 7, 8]

Divest
[1, 3, 5, 10, 11]

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

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

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

Approved w/Constraints
[3, 5, 10, 11, 15, 16, 17]

Approved w/Constraints
[3, 5, 10, 11, 16, 17, 18]

Mac 12.x

Approved w/Constraints
[1, 3, 7, 8]

Divest
[1, 3, 5, 7, 8]

Divest
[1, 3, 5, 10, 11]

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

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

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

Approved w/Constraints
[3, 5, 10, 11, 15, 16, 17]

Approved w/Constraints
[3, 5, 10, 11, 16, 17, 18]

Mac 1.x

Unapproved

Approved w/Constraints
[1, 3, 5, 7, 8]

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

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

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

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

Approved w/Constraints
[3, 5, 10, 11, 15, 16, 17]

Approved w/Constraints
[3, 5, 10, 11, 16, 17, 18]

Win 1.x

Unapproved

Approved w/Constraints
[1, 3, 5, 7, 8]

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

Unapproved

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

Approved w/Constraints
[3, 5, 10, 11, 15, 16, 17]

Approved w/Constraints
[3, 5, 10, 11, 16, 17, 18]

Win 14.x

Unapproved

Mac 14.x

Unapproved

Decision Constraints


[1]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

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

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

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

[11]	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).

[12]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. This technology must not be used on Windows because the Windows version is dependent upon TRM-Unapproved technologies (Powershell v4, SQL Server Express 2017, PostgreSQL). Per the Initial Product Review, users must abide by the following constraints: NVivo will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information where applicable. The current version of NVivo Collaboration Server can only be purchased as a bundle that includes Microsoft SQL Server 2017 Standard Edition which is currently in an unapproved status in the One-VA TRM. NVivo Windows client is bundled with SQL Server Express LocalDB 2017. According to the vendor, these are the only supported versions of SQL for their product and SQL updates are managed by them. Also, Windows Management Framework 4.0 supported operating systems have been deprecated within the Department of Veterans Affairs and the vendor has stated that they have not tested the product with newer versions of the Windows Management Framework that are bundled with the newer versions of Windows Operating Systems. 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 POA&M for the “TRM Unapproved technology”. Due to potential information security risks, SaaS/PaaS solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF. Users must ensure that Microsoft .NET Framework and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)

[13]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. This technology must not be used on Windows because the Windows version is dependent upon TRM-Unapproved technologies (Powershell v4, SQL Server Express 2017, PostgreSQL). Per the Initial Product Review, users must abide by the following constraints: NVivo will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information where applicable. The current version of NVivo Collaboration Server can only be purchased as a bundle that includes Microsoft SQL Server 2017 Standard Edition which is currently in an unapproved status in the One-VA TRM. NVivo Windows client is bundled with SQL Server Express LocalDB 2017. According to the vendor, these are the only supported versions of SQL for their product and SQL updates are managed by them. Also, Windows Management Framework 4.0 supported operating systems have been deprecated within the Department of Veterans Affairs and the vendor has stated that they have not tested the product with newer versions of the Windows Management Framework that are bundled with the newer versions of Windows Operating Systems. 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 POA&M for the “TRM Unapproved technology”. Due to potential information security risks, SaaS/PaaS solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF. Users must ensure that Microsoft .NET Framework and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)

[14]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (PSF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[15]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Per the Security Assessment Review, users must abide by the following constraints: The administrator shall disable automatic update checking from the application. The ISSO shall educate and prohibit users from using the integrated cloud service capability until the VA Cloud Security Requirements have been met and the affected A&A package has been appropriately updated. The administrator shall choose not to participate in the Software Improvement Program by disabling it during installation or through the application menu. OSS may be used if there is adequate maintenance and support. As a condition of certification, Sponsor/Software admin personnel shall maintain and monitor the distribution of NVivo 1.6 (20.6.1.1137) software. The software shall be physically stored in Sponsor/Software admin software library for quality control. The administrator shall update the unsupported version of OpenSSL to a TRM approved version. Users must ensure that Microsoft .NET Framework, Microsoft Internet Explorer (IE), Google Chrome, and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Microsoft Internet Explorer, a dependency of this technology, is in a Divested status at the time of writing. Other approved internet browsers are available. See Category Tab for details. The user should not use the Secure Sockets Layer (SSL) protocols with this technology, SSL is unapproved at this time.

[16]	Browser plug-ins and extensions may only be installed by VA IT Operations (ITOPS) and must be used with official VA browser installation packages that are managed by ITOPS. For installation, contact the National Service Desk [Mail Group: National Service Desk - Austin]. Browser extensions must be kept up to date with security patches and enhancements.

[17]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the VA OIT Product Engineering team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[18]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that Microsoft Internet Information Services (IIS) and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) The user should not use the Secure Sockets Layer (SSL) protocols with this technology, SSL is unapproved at this time. Per the Security Assessment Review, users must abide by the following constraints: The administrator shall disable automatic update checking from the application. The ISSO shall educate and prohibit users from using the integrated cloud service capability until the VA Cloud Security Requirements have been met and the affected A&A package has been appropriately updated. The administrator shall choose not to participate in the Software Improvement Program by disabling it during installation or through the application menu. OSS may be used if there is adequate maintenance and support. As a condition of certification, Sponsor/Software admin personnel shall maintain and monitor the distribution of NVivo 1.6 (20.6.1.1137) software. The software shall be physically stored in Sponsor/Software admin software library for quality control. The administrator shall update the unsupported version of OpenSSL to a TRM approved version.

Note:

At the time of writing, version 14.23.3 (Win) and version 14.23.2 (Mac) is the most current versions, released 02/01/2024 (Win) and 12/01/2023 (Mac).

Please Note: NVivo versions 1.x. Versions 1.x may appear as 20.x after the software download and the corresponding License Key for version 1.x reflects NVT20 in the beginning of its naming convention.

The following reference(s) are associated with this entry:
Type	Name	Source	Description
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
NVivo Collaboration Cloud	Collaboration Cloud is an NVivo add-on module allowing teams to collaborate on NVivo projects.
NVivo Transcription	NVivo Transcription transcribes audio and video files and transfers them in an NVivo-ready format into the user's project. The editor allows the user to make changes, tag speakers, and ensure the transcription is formatted to their needs.


Information Management Technologies Business Intelligence and Data Warehouse Platforms	Data Analytics (Statistical Analysis, Prediction, and Modeling)
Information Management Technologies Business Intelligence and Data Warehouse Platforms	Unstructured Data / Natural Language Processing

- The information contained on this page is accurate as of the Decision Date (03/13/2024 at 17:14:31 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (03/07/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

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

General Information

Vendor Release Information

Current Decision Matrix (03/07/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES