<Past |
Future> |
6.1 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
6.2 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
6.3.x |
Divest [3, 4, 5] |
Divest [3, 4, 5] |
Divest [3, 4, 5] |
Divest [3, 4, 5] |
Divest [3, 4, 5] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Mac 6.4 |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 5, 6] |
Approved w/Constraints [3, 5, 6] |
Approved w/Constraints [3, 5, 6] |
Approved w/Constraints [3, 5, 6] |
Linux 6.4 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 5, 6] |
Approved w/Constraints [3, 5, 6] |
Approved w/Constraints [3, 5, 6] |
Approved w/Constraints [3, 5, 6] |
Win 6.4 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 5, 6] |
Approved w/Constraints [3, 5, 6] |
Approved w/Constraints [3, 5, 6] |
Approved w/Constraints [3, 5, 6] |
| | [1] | Projects using this technology must meet Veterans Affairs (VA) Directive 6500 and implement Federal Information Processing Standards (FIPS 199) for all laptop devices and National Institute of Standards and Technology Special Publication 800-53 for all desktop devices when VA sensitive information is involved, or additional mitigating controls must be documented in an approved System Security Plan (SSP) to prevent potential disclosure of Personally Identifiable Information (PII) or Personal Health Information. | | [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] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [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] | 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. | | [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. |
|
Note: |
At the time of writing, the most current version for Mac is 6.4 and was released on 05/27/2018, and the most current version for Windows is 6.4 and was released on 05/23/2019. |