|
<Past |
Future> |
| 0.x |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
| 1.x |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
| 2.x |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
| 3.x |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
| 4.x |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
| 5.x |
Authorized w/ Constraints (DIVEST) [4, 7, 8, 9, 12, 13] |
Authorized w/ Constraints (DIVEST) [4, 7, 8, 9, 12, 13] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
| 6.x |
Authorized w/ Constraints (DIVEST) [4, 7, 8, 9, 12, 13] |
Authorized w/ Constraints (DIVEST) [4, 7, 8, 9, 12, 13] |
Authorized w/ Constraints (DIVEST) [4, 7, 8, 9, 12, 13] |
Authorized w/ Constraints (DIVEST) [4, 7, 8, 9, 12, 13] |
Unauthorized, Conditions Required[b] [4, 7, 8, 9, 12, 14] |
Unauthorized, Conditions Required[b] [4, 7, 8, 9, 12, 14] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
| 7.x |
Authorized w/ Constraints [4, 7, 8, 9, 12, 13] |
Authorized w/ Constraints [4, 7, 8, 9, 12, 13] |
Authorized w/ Constraints [4, 7, 8, 9, 12, 13] |
Authorized w/ Constraints [4, 7, 8, 9, 12, 13] |
Unauthorized, Conditions Required[b] [4, 7, 8, 9, 12, 14] |
Unauthorized, Conditions Required[b] [4, 7, 8, 9, 12, 14] |
Unauthorized, Conditions Required[b] [4, 7, 8, 9, 12, 14] |
Unauthorized, Conditions Required[b] [4, 7, 8, 9, 12, 14] |
Unauthorized, Conditions Required[b] [4, 7, 8, 9, 12, 14] |
Unauthorized, Conditions Required[b] [4, 7, 8, 9, 12, 14] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
| 8.x |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints [4, 7, 8, 9, 12, 14] |
Authorized w/ Constraints [4, 7, 8, 9, 12, 14] |
Authorized w/ Constraints [4, 7, 8, 9, 12, 14] |
Authorized w/ Constraints [4, 7, 8, 9, 12, 14] |
Authorized w/ Constraints [4, 7, 8, 9, 12, 14] |
Authorized w/ Constraints [4, 7, 8, 9, 12, 14] |
Authorized w/ Constraints [4, 7, 8, 9, 12, 14] |
Authorized w/ Constraints [4, 7, 8, 9, 12, 14] |
| Note: |
At the time of writing, version 8.0.1 `Huffman` is the most current version, released 11/01/2025. Vendor uses names to differentiate updates (minor versions). |
| | | | [4] | 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. | | | [7] | 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. | | | [8] | 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. | | | [9] | 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. | | | [12] | 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. | | | [13] | Users must Divest the use of Bitmap Image File (BMP) with this technology. | | | [14] | Users must Divest the use of Bitmap Image File (BMP) with this technology.
Per the Initial Product Review, users must abide by the following constraints:
- FFmpeg will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing PHI/PII or VA sensitive information.
- System Owners and Administrators should verify the latest version of the software is being used and monitor the CVE database for mitigation of potential threat vectors.
- The use of open-source products, lacking any vendor support, hosting potentially critical VA production systems may pose severe security risks to the VA. Relying on vendor support may result in slow response times and non-timely patches. Users should check with their supervisor, ISSO or local OIT representative for permission to download and use this software.
- The use of AI is increasing, and guidance is still developing. Users must check the most recent VA guidance before using AI technologies and solutions. Consideration should be given to the source of any initial data for the AI tool, if any VA data will be collected and ingested into the data set, where that data will be stored, and what rights the VA has to that data. “No web-based, publicly available generative AI service has been approved for use with VA-sensitive data. Examples of these include OpenAI’s ChatGPT and GPT4, Google’s Bard, Anthropic’ s Claude, and Microsoft’s new Bing. VA follows existing federal requirements and processes to ensure VA data is protected. When users enter information into an unapproved web-based tool, VA loses control of the data.
|
|