1.x |
Unapproved |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
| | [1] | Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
Per the Security Assessment Review, users must abide by the following constraints:
- System Owners/Administrators need to be aware the Windows SmartScreen blocks the installation of the product. Once the file is downloaded, the unblock option must be checked in the file properties to allow installation.
- VA needs to establish a working group or administrative team to develop and review policy regarding AI technology as it develops. It has several inherit risks and policy needs to be developed around those security risks.
- KoboldCpp will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing PHI/PII or VA sensitive information where applicable.
- 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.
- System Administrators shall monitor the .exe files used by the application with a file integrity checker to ensure no unauthorized changes occur.
- 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
- 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.
- 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.
| | [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 approved 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] | 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. |
|