<Past |
Future> |
0.3.2 |
Unapproved |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Divest [2, 3, 4, 5, 6] |
Divest [2, 3, 4, 5, 6] |
Divest [2, 3, 4, 5, 6] |
Divest [3, 5, 7, 8, 9] |
Unapproved |
Unapproved |
Unapproved |
2020.03 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [2, 3, 4, 5, 6] |
Approved w/Constraints [2, 3, 4, 5, 6] |
Approved w/Constraints [2, 3, 4, 5, 6] |
Approved w/Constraints [3, 5, 7, 8, 9] |
Approved w/Constraints [3, 5, 7, 8, 9] |
Approved w/Constraints [3, 5, 7, 8, 10] |
Approved w/Constraints [3, 5, 7, 8, 10] |
2022.07 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2023.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.2.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [1] | If Gen 3 Client is to be used within VA, the underlying operating system, full disk encryption, or other third-party Federal Information Standards (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.
Monitor Gen3 GitHub and the community site for applicable patches and support; test and apply fixes when they become available. | | [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] | 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. | | [4] | 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. | | [5] | If Gen 3 Client is to be used within VA, the underlying operating system, full disk encryption, or other third-party Federal Information Standards (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.
Monitor Gen3 GitHub and the community site for applicable patches and support; test and apply fixes when they become available.
- If Gen 3 Client is to be used within VA, the underlying operating system, full disk encryption, or other third-party Federal Information Standards (FIPS) 1402 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.
- Monitor Gen3 GitHub and the community site for applicable patches and support; test and apply fixes when they become available.
- 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.
| | [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] | 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] | 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. | | [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 Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [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 (PSF) 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.2.1 is the most current version, released 03/07/2024.
Note: The versioning schema of this technology changed with the release of version 1.2.0. |