2024.x |
Authorized w/ Constraints (DIVEST) [2, 3, 4, 5, 6, 7, 8, 9] |
DIVEST [2, 3, 4, 5, 6, 7, 8, 9] |
DIVEST [2, 3, 4, 5, 6, 7, 8, 9] |
DIVEST [2, 3, 4, 5, 6, 7, 8, 9] |
Authorized w/ Constraints (DIVEST) [2, 3, 4, 5, 6, 7, 8, 9] |
Authorized w/ Constraints (DIVEST) [2, 3, 4, 5, 6, 7, 8, 9] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
2025.x |
Authorized w/ Constraints [2, 3, 4, 5, 6, 7, 8, 9] |
Approved w/Constraints [2, 3, 4, 5, 6, 7, 8, 9] |
Approved w/Constraints [2, 3, 4, 5, 6, 7, 8, 9] |
Approved w/Constraints [2, 3, 4, 5, 6, 7, 8, 9] |
Authorized w/ Constraints [2, 3, 4, 5, 6, 7, 8, 9] |
Authorized w/ Constraints [2, 3, 4, 5, 6, 7, 8, 9] |
Authorized w/ Constraints [2, 3, 4, 5, 6, 7, 8, 9] |
Authorized w/ Constraints [2, 3, 4, 5, 6, 7, 8, 9] |
Authorized w/ Constraints [2, 3, 4, 5, 6, 7, 8, 9] |
Authorized w/ Constraints [2, 3, 4, 5, 6, 7, 8, 9] |
Authorized w/ Constraints [2, 3, 4, 5, 6, 7, 8, 9] |
Authorized w/ Constraints [2, 3, 4, 5, 6, 7, 8, 9] |
| | [1] | Users must ensure that Google Chrome, Firefox, and Microsoft Edge are implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [2] | 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 authorized and the user should take the proper steps to decline those installations. | | [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] | 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. | | [5] | 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. | | [6] | Users must ensure that Google Chrome, Firefox, and Microsoft Structured Query Language (SQL) Server are implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [7] | 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. | | [8] | 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. | | [9] | 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. |
|