1.5.x |
Approved w/Constraints [6, 7, 8] |
Approved w/Constraints [6, 7, 8] |
Approved w/Constraints [6, 7, 8] |
Approved w/Constraints [6, 7, 9] |
Approved w/Constraints [6, 7, 9] |
Approved w/Constraints [6, 7, 9] |
Approved w/Constraints [7, 9, 10, 11, 12] |
Approved w/Constraints [7, 9, 10, 11, 12] |
Authorized w/ Constraints [7, 9, 10, 11, 12] |
Approved w/Constraints [7, 9, 10, 11, 12] |
Approved w/Constraints [7, 9, 10, 11, 12] |
Approved w/Constraints [7, 9, 10, 11, 12] |
| | [1] | 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 authorized and the user should take the proper steps to decline those installations. | | [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 must ensure that Firefox, Google Chrome, Microsoft .NET Framework, and Microsoft Internet Explorer (IE) are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [4] | 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. | | [5] | Users must ensure that Microsoft .NET Framework, Firefox and Google Chrome are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must utilize authorized internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details. | | [6] | Users must ensure that Firefox and Google Chrome are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must utilize authorized internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details.
Per the Initial Product Review (IPR), users must abide by the following constraints:
- The use of EZ Tools must be limited only to Cyber Security Operations Center (CSOC) staff and shall be listed in the software baseline of the EnCase Endpoint Investigator (EEI) ATO boundary.
- System administrators must ensure that the latest authorized version of Microsoft .NET Framework is used with EZ Tools that integrates with .NET Framework. Version 6.x is listed as Unapproved on the VA Technical Reference Model (TRM).
- The VA requires support for all software used on the VA network. Vendor or third-party support at an enterprise level is not free and must be acquired for any open-source product to be deployed on the VA network. Support for the EZ Tools can be provided through Eric Zimmerman.
- The use of EZ Tools should be limited only to experienced system information security staff performing tasks related to digital forensics investigations, incident response, and Advanced Persistent Threat (APT) detection.
- Due to the rapid releases and updates of these tools, the VA should closely monitor the vendor’s website for critical updates and new releases.
| | [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] | 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 VA Handbook 6500. | | [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. | | [10] | Users must ensure that Firefox and Google Chrome are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Initial Product Review, users must abide by the following constraints:
-
EZ Tools Suite will require a 3rd party FIPS 140-2 certified solution for any data containing Protected Health Information (PHI)/Personally Identifiable Information (PII) or VA sensitive information.
-
The use of EZ Tools must be limited only to Cyber Security Operations Center (CSOC) staff and shall be listed in the software baseline of the EnCase Endpoint Investigator (EEI) ATO boundary.
-
System administrators must ensure that the latest authorized version of Microsoft .NET Framework is used with EZ Tools that integrates with .NET Framework. Version 6.x is listed as Unapproved on the VA Technical Reference Model (TRM).
-
The VA requires support for all software used on the VA network. Vendor or third-party support at an enterprise level is not free and must be acquired for any open-source product to be deployed on the VA network. Support for the EZ Tools can be provided through Eric Zimmerman.
-
The use of EZ Tools should be limited only to experienced system information security staff performing tasks related to digital forensics investigations, incident response, and Advanced Persistent Threat (APT) detection.
-
Due to the rapid releases and updates of these tools, the VA should closely monitor the vendor’s website for critical updates and new releases.
| | [11] | 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. | | [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. |
|