<Past |
Future> |
3.0 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.0 |
Divest [3] |
Divest [2, 3, 4, 5, 6] |
Divest [2, 3, 4, 5, 6] |
Divest [2, 4, 5, 7, 8] |
Divest [2, 4, 8, 9, 10] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.1.x |
Approved w/Constraints [3] |
Approved w/Constraints [2, 3, 4, 5, 6] |
Approved w/Constraints [2, 3, 4, 5, 6] |
Approved w/Constraints [2, 4, 5, 7, 8] |
Approved w/Constraints [2, 4, 8, 9, 10] |
Divest [2, 8, 9, 10, 11] |
Divest [2, 8, 9, 10, 11] |
Divest [8, 10, 12] |
Divest [8, 10, 12] |
Divest [8, 10, 12] |
Unapproved |
Unapproved |
4.2 |
Unapproved |
Approved w/Constraints [2, 3, 4, 5, 6] |
Approved w/Constraints [2, 3, 4, 5, 6] |
Approved w/Constraints [2, 4, 5, 7, 8] |
Approved w/Constraints [2, 4, 8, 9, 10] |
Divest [2, 8, 9, 10, 11] |
Divest [2, 8, 9, 10, 11] |
Divest [8, 10, 12] |
Divest [8, 10, 12] |
Divest [8, 10, 12] |
Divest [8, 10, 12] |
Unapproved |
4.3.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [2, 8, 9, 10, 11] |
Approved w/Constraints [2, 8, 9, 10, 11] |
Approved w/Constraints [8, 10, 12] |
Approved w/Constraints [8, 10, 12] |
Approved w/Constraints [8, 10, 12] |
Approved w/Constraints [8, 10, 12] |
Divest [8, 10, 12] |
4.4.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [8, 10, 12] |
4.5.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.6.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [1] | Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. | | [2] | 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. | | [3] | 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. | | [4] | Smart Meeting Pro itself does not appear to have encryption features. However, it uses Bridgit, another SMART Technologies product, to provide meeting collaborative services. Users must ensure that Smart Meeting Pro properly leverages FIPS 140-2 through Bridgit` in its interactions with various commercial software and application products as the potential is likely for VA meetings and conferences to involve PII/PHI/VA sensitive information.
This technology must not be used to replace VA standard collaboration tools but may be used to supplement VA standards such as Microsoft Lync when necessary. | | [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, 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). | | [7] | 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). | | [8] | 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. | | [9] | 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. | | [10] | 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). | | [11] | This technology must not be used to replace Veterans Affairs (VA) standard collaboration technologies but may be used to supplement VA standards such as Microsoft Lync when necessary. | | [12] | This technology must not be used to replace Veterans Affairs (VA) standard collaboration technologies but may be used to supplement VA standards such as Microsoft Lync when necessary.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. |
|
Note: |
At the time of writing, version 4.6.451.3 is the most current version, released 11/07/2023. |