| 2025.x |
Unapproved |
Unapproved |
Approved w/Constraints
[1, 2, 3, 4, 5, 6] |
Approved w/Constraints
[1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6] |
Approved w/Constraints
[1, 2, 3, 4, 5, 6] |
Approved w/Constraints
[1, 2, 3, 4, 5, 6] |
Approved w/Constraints
[1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6] |
| | | | [1] | Users must ensure that Google Chrome and Microsoft Edge are implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must not utilize Navisworks Simulate, as it is at the time of writing, unapproved in the TRM.
Per the Security Assessment Review (SAR), users must abide by the following constraints:
- Navisworks NWS Export Utility 2025 (v22.x) will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing PHI/PII or VA sensitive information.
- To mitigate, the vendor must maintain all third-party components during the entire product lifecycle, including responding to vulnerabilities discovered in third-party components used in the product.
- System owners should use the latest version of these products where possible and monitor both the CVE Details and NIST National Vulnerability Database websites for any new security vulnerabilities.
- To mitigate, the administrators shall install Navisworks NWS Export Utility 2025 (v22.x) into the program files directory (“C:\Program Files\” or C:\Program Files (x86)\”). If an application does not allow it to install into the program files directory the default location is acceptable. For any applications that install folders/files off the root
of c:\, the Windows Setting: `Network access: Let everyone permissions apply to anonymous users` must be set to `Disabled`. In addition, ensure folder permissions for system drive`s root directory (c:\) are as restrictive as the default permissions listed in the applicable Operating System VA Secure Configuration Baseline for this requirement. Temporary or unnecessary folder(s)/file(s) found off the root of c:\ should be removed or deleted if possible.
- Administrators must ensure only authorized versions of Visual C++ are installed.
| | | [2] | 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. | | | [3] | 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. | | | [4] | 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 ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities. | | | [5] | 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. | | | [6] | This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product. |
|
