<Past |
Future> |
2.x.x |
Approved w/Constraints [1, 2] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [4, 5] |
Approved w/Constraints [4, 6] |
Divest [1, 4, 6] |
Divest [1, 4, 6] |
Divest [1, 4, 6] |
Divest [1, 4, 6] |
Divest [1, 4, 6] |
Unapproved |
Unapproved |
3.4.x |
Unapproved |
Approved w/Constraints [2, 3] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [4, 5] |
Approved w/Constraints [4, 6] |
Divest [1, 4, 6] |
Divest [1, 4, 6] |
Divest [1, 4, 6] |
Divest [1, 4, 6] |
Divest [1, 4, 6] |
Unapproved |
Unapproved |
3.12.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [1, 4, 6] |
Divest [1, 4, 6] |
Divest [1, 4, 6] |
Divest [1, 4, 6] |
Divest [1, 4, 6] |
Unapproved |
Unapproved |
3.13.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [1, 4, 6] |
Approved w/Constraints [1, 4, 6] |
Approved w/Constraints [1, 4, 6] |
Approved w/Constraints [1, 4, 6] |
Approved w/Constraints [1, 4, 6] |
Unapproved |
Unapproved |
3.15.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [1, 4, 6] |
Approved w/Constraints [1, 4, 6] |
Approved w/Constraints [1, 4, 6] |
Approved w/Constraints [1, 4, 6] |
Approved w/Constraints [1, 4, 6] |
Unapproved |
3.17.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [1, 4, 6] |
Approved w/Constraints [1, 4, 6] |
Approved w/Constraints [1, 4, 6] |
Approved w/Constraints [1, 4, 6] |
Unapproved |
3.19.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [1, 4, 6] |
Approved w/Constraints [1, 4, 6] |
Approved w/Constraints [1, 4, 6] |
Unapproved |
3.20.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [1, 4, 6] |
Approved w/Constraints [1, 4, 6] |
Unapproved |
3.22.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [1, 4, 6] |
Unapproved |
3.x.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [1, 4, 6] |
4.x.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [1] | 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. | | [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] | 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). | | [4] | 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. | | [5] | 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). | | [6] | 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). |
|
Note: |
At the time of writing, version 4.5.0 is the most current version |