| 9.x |
Unapproved |
Approved w/Constraints
[1, 2, 3, 4, 5, 6] |
Approved w/Constraints
[1, 2, 3, 4, 5, 6] |
Approved w/Constraints
[1, 3, 5, 6, 7, 8] |
Approved w/Constraints
[1, 3, 6, 7, 9, 10] |
Approved w/Constraints
[3, 6, 7, 9, 11] |
Approved w/Constraints
[3, 6, 7, 9, 11] |
Approved w/Constraints
[3, 6, 7, 9, 11] |
Approved w/Constraints
[3, 6, 7, 9, 12] |
Approved w/Constraints
[3, 6, 7, 9, 12] |
Approved w/Constraints
[3, 6, 7, 9, 12] |
Approved w/Constraints
[3, 6, 7, 9, 12] |
| | | | [1] |
- Ensure that PeerSync is always operated in FIPS 140-2 mode. The two versions most likely to be used within VA are Enterprise Edition for Windows and NetApp. Only NetApp was identified as FIPS 140-2 compliant in this research.
- The system user or administrator initiating the PeerSync process must have robust authentication credentials that prevent unauthorized or casual access. Such robustness must include two-factor authentication (2FA) as a minimum, along with periodic and heightened awareness training to ensure administrator capabilities.
- PeerSync must be deployed in the local environment on VA owned and managed servers. If the cloud solution is used to satisfy a VA mission requirement, VA must clearly define the required security controls and document them in a VA approved Memorandum of Understanding and Interconnection Security Agreements (MOU/ISA), contract and other VA approved agreements (e.g., Data Use Agreement) as stated in VA Handbook 6500 and VA Directive 6513 - Secure External Connections. In addition, all external network connections must traverse through the VA Trusted Internet Connection (TIC) gateway to comply with critical OMB mandates as well as an ESCCB request be submitted for approval.
- This software offers a free trial period, which carries the potential for the disruption of service delivery and inaccurate financial planning. If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
| | | [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 potential information security risks, cloud based technologies may not be used without an Enterprise Security Change Control Board (ESCCB) approval. This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [5] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process. | | | [6] | 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. | | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | | [8] | Due to potential information security risks, cloud based technologies may not be used without the approval of the VA Enterprise Cloud Services (ECS) Group. This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [9] | Due to potential information security risks, cloud based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [10] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process. | | | [11] | Ensure that PeerSync is always operated in FIPS 140-2 mode. The two versions most likely to be used within VA are Enterprise Edition for Windows and NetApp. Only NetApp was identified as FIPS 140-2 compliant in this research.
The system user or administrator initiating the PeerSync process must have robust authentication credentials that prevent unauthorized or casual access. Such robustness must include two-factor authentication (2FA) as a minimum, along with periodic and heightened awareness training to ensure administrator capabilities.
PeerSync must be deployed in the local environment on VA owned and managed servers. If the cloud solution is used to satisfy a VA mission requirement, VA must clearly define the required security controls and document them in a VA approved Memorandum of Understanding and Interconnection Security Agreements (MOU/ISA), contract and other VA approved agreements (e.g., Data Use Agreement) as stated in VA Handbook 6500 and VA Directive 6513 - Secure External Connections. In addition, all external network connections must traverse through the VA Trusted Internet Connection (TIC) gateway to comply with critical OMB mandates as well as an Enterprise Security Change Control Board (ESCCB) request be submitted for approval.
This software offers a free trial period, which carries the potential for the disruption of service delivery and inaccurate financial planning. If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | | [12] | If free trial ware is utilized, the software must be purchased or removed at the end of the trial period.
Per the Initial Product Review, users must abide by the following constraints:
Users must ensure that PeerSync is always operated in FIPS 140-2 mode. The two versions most likely to be used within VA are Enterprise Edition for Windows and NetApp. Only NetApp was identified as FIPS 140-2 compliant in this research.
The system user or administrator initiating the PeerSync process must have robust authentication credentials that prevent unauthorized or casual access. Such robustness must include two-factor authentication (2FA) as a minimum, along with periodic and heightened awareness training to ensure administrator capabilities.
PeerSync must be deployed in the local environment on VA owned and managed servers. If the cloud solution is used to satisfy a VA mission requirement, VA must clearly define the required security controls and document them in a VA approved Memorandum of Understanding and Interconnection Security Agreements (MOU/ISA), contract and other VA approved agreements (e.g., Data Use Agreement) as stated in VA Handbook 6500 and VA Directive 6513 - Secure External Connections. In addition, all external network connections must traverse through the VA Trusted Internet Connection (TIC) gateway to comply with critical OMB mandates as well as an Enterprise Security Change Control Board (ESCCB) request be submitted for approval. |
|
