<Past |
Future> |
9.0.x |
Divest [4, 5, 6, 7] |
Divest [4, 5, 6, 7] |
Divest [4, 5, 6, 7] |
Divest [4, 5, 6, 8] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
9.1.x |
Divest [4, 5, 6, 7] |
Divest [4, 5, 6, 7] |
Divest [4, 5, 6, 7] |
Divest [4, 5, 6, 8] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
9.2.x |
Approved w/Constraints [4, 5, 6, 7] |
Approved w/Constraints [4, 5, 6, 7] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
9.3.x |
Unapproved |
Unapproved |
Approved w/Constraints [4, 5, 6, 7] |
Approved w/Constraints [4, 5, 6, 8] |
Approved w/Constraints [4, 5, 6, 8] |
Approved w/Constraints [4, 5, 6, 8] |
Approved w/Constraints [4, 5, 6, 8] |
Approved w/Constraints [4, 5, 6, 8] |
Approved w/Constraints [4, 5, 6, 8] |
Approved w/Constraints [4, 5, 6, 8] |
Approved w/Constraints [4, 5, 6, 8] |
Approved w/Constraints [4, 5, 6, 8] |
9.4.x |
Unapproved |
Unapproved |
Approved w/Constraints [1, 4, 5, 6, 7] |
Approved w/Constraints [4, 5, 6, 8] |
Approved w/Constraints [4, 5, 6, 8] |
Approved w/Constraints [4, 5, 6, 8] |
Approved w/Constraints [4, 5, 6, 8] |
Approved w/Constraints [4, 5, 6, 8] |
Approved w/Constraints [4, 5, 6, 8] |
Approved w/Constraints [4, 5, 6, 8] |
Approved w/Constraints [4, 5, 6, 8] |
Approved w/Constraints [4, 5, 6, 8] |
| | [1] | This Technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. | | [2] | Security Engineering (SE) conducted a pre-assessment and security requirements
verification of VanDyke SecureFX. It is advised that if this product is used within
the Department of Veterans Affairs (VA) that the following constraints be applied:
1. Administrators must ensure FIPS mode is enabled to meet FIPS 140-2
compliance.
2. Administrators must ensure only the most current version of VanDyke
SecureFX is deployed and the software remains patched.
3. The VanDyke SecureFX File Transfer Protocol (FTP) Client must utilize the
Secure File Transfer Protocol (SFTP) protocol instead of the FTP protocol as
FTP is currently unapproved.
4. If VanDyke SecureFX is deployed on any OS other than Windows, it will require
a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA
sensitive information. | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [4] | 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. | | [5] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (yourIT Service Portal:[SNOW Service Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | [6] | Per the Initial Product Review, users must abide by the following constraints:
- Administrators must ensure FIPS mode is enabled to meet FIPS 140-2 compliance.
- Administrators must ensure only the most current version of VanDyke SecureFX is deployed and the software remains patched.
- The VanDyke SecureFX File Transfer Protocol (FTP) Client must utilize the Secure File Transfer Protocol (SFTP) protocol instead of the FTP protocol as FTP is currently unapproved.
- If VanDyke SecureFX is deployed on any OS other than Windows, it will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information.
The File Transfer Protocol (FTP) features of this software must not be used as the FTP protocol is prohibited for use on the VA network. (For further information see: VA Policy Memo VAIQ 7615193 on Prohibited Use of File Transfer Protocol (FTP) and Telnet Services) | | [7] | 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. | | [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 both VA Handbook 6500 and VA Directive 6500. |
|
Note: |
At the time of writing, version 9.3.2 is the most current version, released 11/03/2022.A standard configuration of this technology was developed by the DDE team. At the time of writing, the standard version is 9.3.2. DDE is updating and starting to test version 9.4.0 of this application with an estimated completion date of three weeks from 08/07/2023. |