<Past |
Future> |
7.1 (Standard) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.1 (Enterprise) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.1.x (Standard) |
Approved w/Constraints [1, 2, 3, 4, 6, 7] |
Approved w/Constraints [1, 2, 3, 4, 6, 7] |
Approved w/Constraints [1, 3, 4, 6, 7, 8] |
Approved w/Constraints [1, 3, 4, 6, 7, 8] |
Approved w/Constraints [1, 3, 4, 8, 9, 10] |
Approved w/Constraints [1, 3, 4, 8, 9, 10] |
Approved w/Constraints [1, 3, 4, 8, 9, 11] |
Approved w/Constraints [1, 3, 4, 8, 9, 11] |
Divest [1, 3, 4, 8, 9, 11] |
Divest [1, 3, 4, 8, 9, 12] |
Unapproved |
Unapproved |
2.0.x (Enterprise) |
Approved w/Constraints [1, 2, 3, 4, 6, 7] |
Approved w/Constraints [1, 2, 3, 4, 6, 7] |
Approved w/Constraints [1, 3, 4, 6, 7, 8] |
Approved w/Constraints [1, 3, 4, 6, 7, 8] |
Approved w/Constraints [1, 3, 4, 8, 9, 10] |
Approved w/Constraints [1, 3, 4, 8, 9, 10] |
Approved w/Constraints [1, 3, 4, 8, 9, 11] |
Approved w/Constraints [1, 3, 4, 8, 9, 11] |
Divest [1, 3, 4, 8, 9, 11] |
Divest [1, 3, 4, 8, 9, 12] |
Unapproved |
Unapproved |
86 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [1, 3, 4, 8, 9, 11] |
Divest [1, 3, 4, 8, 9, 12] |
Unapproved |
Unapproved |
87 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [1, 3, 4, 8, 9, 11] |
Divest [1, 3, 4, 8, 9, 12] |
Unapproved |
Unapproved |
88 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [1, 3, 4, 8, 9, 11] |
Divest [1, 3, 4, 8, 9, 12] |
Unapproved |
Unapproved |
1.1.x (Enterprise) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.1.x (Standard) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [1] | 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:
- If GS RichCopy 360 is to be utilized within VA the underlying operating system, full disk encryption or other third party FIPS 140-2 validated applications must be leveraged to protect VA sensitive information. VA Handbook 6500 CP-9: Information System Backup (d), states that VA system backups will be encrypted using FIPS 140-2 (or its successor) validated encryption.
- The enterprise version of the software must be purchased for a more efficient and secure backup solution.
- 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./li>
- Only approved products must be used within the VA; the TRM will only consider new technology if current approved backup solutions do not meet VA needs or requirements.
- Users must employ least privilege rule when granting access to IT support staff to ensure they are given only the necessary access rights or permissions to accomplish assigned tasks. IT support staff requiring elevated privileges must follow Office of Information Technology (OIT) approved processes. Leverage VA-approved directory services such as Active Directory (AD) for authentication/authorization and conduct regular audits of privileged accounts.
| | [2] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (contact VA e-mail: [OIT ITOPS SD Engagement Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | [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] | 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). | | [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] | 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). | | [8] | 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. | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [10] | 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). | | [11] | 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). | | [12] | 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). |
|
Note: |
At the time of writing, version 1.1.94 (Enterprise) and 2.1.19 (Standard) are the most current versions, both released 09/23/2023. |