|
<Past |
Future> |
| Win 9.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| Win 10.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| Win 11.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| Mac 11.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| Win 12.x |
Approved w/Constraints
[5, 16, 17, 19, 20, 21] |
Approved w/Constraints
[5, 16, 17, 19, 20, 21] |
Approved w/Constraints
[5, 16, 17, 19, 20, 21] |
Approved w/Constraints
[5, 16, 17, 19, 20, 21] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
| Mac 12.x |
Approved w/Constraints
[5, 16, 17, 19, 20, 21] |
Approved w/Constraints
[5, 16, 17, 19, 20, 21] |
Approved w/Constraints
[5, 16, 17, 19, 20, 21] |
Approved w/Constraints
[5, 16, 17, 19, 20, 21] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
| Mac 1.x |
Approved w/Constraints
[5, 16, 17, 19, 20, 21] |
Approved w/Constraints
[5, 16, 17, 19, 20, 21] |
Approved w/Constraints
[5, 16, 17, 19, 20, 21] |
Approved w/Constraints
[5, 16, 17, 19, 20, 21] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
| Win 1.x |
Approved w/Constraints
[5, 16, 17, 19, 20, 21] |
Approved w/Constraints
[5, 16, 17, 19, 20, 21] |
Approved w/Constraints
[5, 16, 17, 19, 20, 21] |
Approved w/Constraints
[5, 16, 17, 19, 20, 21] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
| Win 14.x |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints
[5, 16, 17, 19, 20, 21] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
| Mac 14.x |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints
[5, 16, 17, 19, 20, 21] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
Approved w/Constraints
[5, 16, 20, 22, 23, 24] |
| | | | [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.
| | | [19] | 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.
Users must not utilize Apple Boot Camp, as it is at the time of writing, unapproved in the TRM.
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.
- Maintenance and support will be provided for the Open Source Software used within NVivo 1.6 (20.6.1.1137) as per the application’s lifecycle
- The administrator shall update the unsupported version of OpenSSL to a TRM approved version.
| | | [20] | Users should check with their supervisor, Information System Security Officer (ISSO) 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. | | | [21] | 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). | | | [22] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Google Chrome, 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.
Users must not utilize Apple Boot Camp, as it is at the time of writing, unapproved in the TRM.
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.
- Maintenance and support will be provided for the Open Source Software used within NVivo 1.6 (20.6.1.1137) as per the application’s lifecycle
- The administrator shall update the unsupported version of OpenSSL to a TRM approved version.
| | | [23] | 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. | | | [24] | 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, visit the Product Marketplace.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). |
|
| 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. |
