| 7.x |
Approved w/Constraints
[1, 2, 3, 4, 5, 6, 7] |
Approved w/Constraints
[1, 2, 3, 4, 5, 6, 7] |
Approved w/Constraints
[1, 2, 3, 4, 5, 7, 8] |
Approved w/Constraints
[1, 2, 3, 4, 5, 7, 8] |
Approved w/Constraints
[1, 2, 3, 4, 5, 7, 8] |
Approved w/Constraints
[1, 2, 3, 4, 5, 7, 9] |
Approved w/Constraints
[1, 2, 3, 4, 5, 7, 9] |
Approved w/Constraints
[1, 2, 3, 4, 5, 7, 9] |
Approved w/Constraints
[1, 4, 7, 9, 10, 11, 12] |
Approved w/Constraints
[1, 4, 7, 9, 10, 11, 12] |
Approved w/Constraints
[1, 4, 7, 9, 10, 11, 12] |
Divest
[4, 7, 9, 11, 12, 13, 14, 15] |
| | | | [1] | Users must not utilize the none of the following services: Google Drive, DropBox, and Microsoft OneDrive. This is because none of these services are authorized to store VA information and patient data.
This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data.
If free trialware 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:
- System owners should deploy FIPS compliant software to ensure VA sensitive
data containing PII/PHI is protected with FIPS 140-2 validated technology.
- 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), Project Special Forces
(PSF), 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/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 PSF.
- SSL is considered no longer a secure connection and should be replaced by
TLS v1.2 or higher. System owners should ensure TLS is being used instead
of the default SSL protocol.
- The product should be configured to use Secure File Transfer Protocol (SFTP)
as this is the approved solution in the One-VA Technical Reference Model
- Ensure that all VA password requirements are met with regard to length and
complexity. VA Knowledge Service Control IA-5: Authenticator Management
requires a case sensitive 14-character password comprised of upper-case
letters, lower case letters, numbers and special characters, including at least
one of each category. VA defines and enforces at least 50% of characters in
the password must be changed when new passwords are created.
- VA currently is standardized to centrally control and enforce security policies
regarding the use of removable devices (e.g., USB flash drives) and media
(e.g., DVDs/CDs) to prevent data loss and theft, thwart malware intrusion, and
protect data. Care must be taken to ensure that if external Flash/USB drive or
CD/DVD is to be used for backup, only devices listed on the FIPS 140-2
Validated Removable Storage Device List shall be used. If approved, by the
supervisor and ISSO, the Removable Storage Devices - Secure Configuration
Guide must be strictly followed
| | | [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] | 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] | 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] | 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 with the Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [7] | 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. | | | [8] | 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 with the Project Special Forces (PSF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [9] | 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 with the VA OIT Product Engineering team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [10] | 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. | | | [11] | 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. | | | [12] | 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 ISSO (Information System Security Officer) can advise on the ESCCB review process. | | | [13] | Users must not utilize the none of the following services: Google Drive, DropBox, and Microsoft OneDrive. This is because none of these services are authorized to store VA information and patient data.
This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users should not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
Users should not utilize the File Transfer Protocol (FTP), as it is unapproved for use on the TRM.
Per the Initial Product Review, users must abide by the following constraints:
- System owners should deploy FIPS 140-2 (or its successor) certified solution
to ensure VA sensitive data containing PII/PHI is protected.
- 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.
- SSL is no longer considered a secure connection and should be replaced by
TLS v1.2 or higher. System owners should ensure TLS is being used instead
of the default SSL protocol.
- The product should be configured to use Secure File Transfer Protocol (SFTP)
as this is the approved solution in the VA Technical Reference Model.
- SmartSync Pro shall be configured to meet minimum password-based
authentication standards per VA Knowledge Service Control IA-5(1).
- VA currently is standardized to centrally control and enforce security policies
regarding the use of removable devices (e.g., USB flash drives) and media
(e.g., DVDs/CDs) to prevent data loss and theft, thwart malware intrusion, and
protect data. Care must be taken to ensure that if external Flash/USB drive or
CD/DVD is to be used for backup, only devices listed on the FIPS 140-2
Validated Removable Storage Device List shall be used.
| | | [14] | 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. | | | [15] | 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. |
|
