| 12.x |
Divest
[9, 10, 11, 12, 13] |
Divest
[9, 10, 11, 12, 13] |
Divest
[9, 10, 11, 12, 13] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| 2024.x |
Approved w/Constraints
[9, 10, 11, 12, 13] |
Approved w/Constraints
[9, 10, 11, 12, 13] |
Approved w/Constraints
[9, 10, 11, 12, 13] |
Approved w/Constraints
[9, 10, 11, 12, 13] |
Approved w/Constraints
[9, 10, 11, 12, 13] |
Approved w/Constraints
[9, 10, 11, 12, 13] |
Approved w/Constraints
[9, 10, 11, 12, 13] |
Approved w/Constraints
[9, 10, 11, 12, 13] |
Approved w/Constraints
[9, 10, 11, 12, 13] |
Approved w/Constraints
[9, 10, 11, 12, 13] |
Approved w/Constraints
[9, 10, 11, 12, 13] |
Approved w/Constraints
[9, 10, 11, 12, 13] |
| | | | [1] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure Secure File Transfer Protocol (SFTP) is used in place of File Transfer Protocol (FTP). | | | [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 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. | | | [4] | 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 ISO can provide assistance in reviewing the NIST vulnerabilities. | | | [5] | 1. Cerberus FTP Server must use version 11.0.3 or higher due to known vulnerabilities with previous versions.
2. Administrators must ensure that FIPS 140-2 encryption is always enabled.
3. Cerberus FTP Server should only be considered when a VA approved solution does not meet the necessary requirements, and the use for more specialized tools are warranted.
4. Only the Professional and Enterprise editions of Cerberus FTP Server must be used to ensure that the VA infrastructure is secure. | | | [6] | 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. | | | [7] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
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)
Per the Initial Product Review/Security, users must abide by the following constraints:
- Cerberus FTP Server must use version 11.0.3 or higher due to known vulnerabilities with previous versions.
- Administrators must ensure that FIPS 140-2 encryption is always enabled.
- Cerberus FTP Server should only be considered when a VA approved solution does not meet the necessary requirements, and the use for more specialized tools are warranted.
- Only the Professional and Enterprise editions of Cerberus FTP Server must be used to ensure that the VA infrastructure is secure.
| | | [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] | 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. | | | [10] | 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. | | | [11] | 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] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must not utilize Secure Hypertext Transfer Protocol (S-HTTP), as it is at the time of writing, unapproved in the TRM.
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)
Per the Initial Product Review, users must abide by the following constraints:
- Administrators must ensure that FIPS 140-2 encryption is always enabled.
- Only the Professional and Enterprise editions of Cerberus FTP Server must be used to ensure that the VA infrastructure is secure.
- Production data should not be used during the trial period. At the end of the free trial, the product should be removed, or a full software license purchased.
- Due to potential information security risks, SaaS/PaaS solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Digital Transformation Center (DTC), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS or Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by DTC.
| | | [13] | Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request, visit the Product Marketplace.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). |
|
